File names

From the name of each recording, Caller reads the agent, the date, the time, the customer’s phone number and whether the call was inbound or outbound. It works the same whether you upload by hand or send through the API, where it is the fallback for anything you do not send as a field.

None of this is required. A file called final-recording.mp3 uploads all the same. It arrives without an agent or a date, and you set them yourself.

In Integrations, click Try a file name and paste the name of one of your recordings. You see which parts are recognized and whether the agent matches someone on your team. It is the fastest way to find out whether your telephony system already names files in a way Caller understands.

File name	What is read
AG1143_Lucia_Romero_2026-10-09_10-42-11_611284.mp3	Code AG1143, name “Lucia Romero”, October 9, 2026 at 10:42:11, phone 611284
call_AG1143_20261009_1042.ogg	Code AG1143, October 9, 2026 at 10:42
09-10-2026 10h42 outbound OP 07 Marta Vidal.m4a	Code OP07, name “Marta Vidal”, October 9, 2026 at 10:42, outbound
IMG_2026-10-09.mp3	Only the date. The time is set to 12:00
final-recording.mp3	Nothing

One of the prefixes AG, AGT, AGENT, EXT or OP, followed by 2 to 6 digits. There can be a hyphen, an underscore or a space between the prefix and the digits, and case does not matter: AG1143, ext-204 and Op 07 are all valid.

The code has to be separated from the rest of the name. It is recognized in queue3_AG1143_… but not in queueAG1143….

The words right after the code, up to three, and up to the first one that contains a number. A single letter between the code and the name is ignored (AG1143 T Lucia Romero).

A four-digit year, a month and a day, in one of these two orders:

• Year, month, day: 2026-10-09, 2026_10_09, 2026.10.09 or 20261009
• Day, month, year: 09-10-2026, 09_10_2026 or 09.10.2026

The month, day, year order is not recognized: 10-09-2026 is read as September 10. An impossible date, such as February 31, is discarded.

It has to come immediately after the date: 10-42-11, 10_42_11, 10.42.11, 10:42:11, 104211 or 10h42. Seconds are optional. If there is a date but no time, noon is used.

One of these words, separated from the rest: in, inbound, entrante or recibida for an inbound call; out, outbound, saliente or emitida for an outbound one. The Spanish words are also accepted in the plural (entrantes, salientes); the English ones are not.

The last run of 6 to 15 consecutive digits left in the name once the date, the time and the agent code are set aside. It can start with +.

Recognizing a code is not enough: there has to be someone in Team it belongs to. Caller tries in this order:

1. By code. It compares the code it read with each agent’s Code in the telephony system, ignoring case, hyphens, underscores and spaces. AG-1143 and ag1143 are the same code.
2. By name. If there is no code or nobody has it, Caller looks for an agent’s full name inside the file name, ignoring case and accents. This only works for agents with a first name and a last name: a single word, such as “Pablo”, is not used to assign a call.

If nobody matches, the call is uploaded without an agent. You can assign one later from the call itself or, for several calls at once, from Calls.

A file name does not say which time zone its time is in.

• When you upload by hand, the time is read in your browser’s time zone.
• Through the API, the time is read as UTC. If your telephony system names files in local time, send the time in the started_at field with its offset and do not rely on the name.