Skip to content

Call Metadata

Uspeech analyzes what happens inside a call. Everything around the call — when it happened, which agent handled it, whether it was inbound or outbound, who hung up first, which campaign it belonged to — comes from your own systems. There are three ways to provide it:

  • A CSV manifest for a whole project — the fastest way to cover a batch of recordings
  • The Edit call metadata dialog on a single file — for fixing or filling in one call
  • The API, either at upload time or afterwards — see Call Metadata API

All three write to the same place, so you can mix them freely.

Without metadata, Uspeech falls back to the file’s upload time and to the agent name the AI hears in the conversation. That still produces a report, but:

  • The compliance trend and the date filters use the upload date instead of the call date
  • The shift comparison cannot classify calls (only calls with real date/time are counted)
  • Agent performance relies on the name spoken in the call, which varies between recordings
  • Direction and campaign are unavailable as filters
  • Closing steps can be docked on calls the customer cut short, because a transcript rarely shows who hung up — see Who hung up first

Providing metadata fixes all of these at once.


  1. Click Conversations on the navigation bar
  2. Select your call center project
  3. On the Files tab, click Call Metadata (CSV)
  4. Choose your CSV file and click Upload

Upload call metadata dialog

The dialog reports how many files were matched, how many rows are still pending (no matching file uploaded yet), and any rows that could not be read.


One row per call, with a header row:

ColumnRequiredDescription
filenameYesName of the audio or transcript file as uploaded
call_datetimeYesWhen the call took place
agent_idNoThe agent’s identifier in your own systems
agent_nameNoThe agent’s display name
agent_emailNoThe agent’s email, which lets an invited agent see their own calls — see Agent email
directionNoinbound or outbound
ended_byNoWho hung up first: customer or agent — see Who hung up first
caller_numberNoPhone number of the customer
campaignNoCampaign or queue name

Example:

filename,call_datetime,agent_id,agent_name,agent_email,direction,ended_by,caller_number,campaign
call_001.mp3,2026-06-15 09:12:00,A-06,Ana Diaz,ana.diaz@example.com,inbound,customer,+34600111222,Retention
call_002.mp3,2026-06-15 09:41:00,A-10,Luis Gomez,luis.gomez@example.com,outbound,agent,+34600333444,Winback
call_003.mp3,2026-06-15 10:02:00,A-06,Ana Diaz,ana.diaz@example.com,inbound,,+34600555666,Retention

Accepted date/time formats:

  • 2026-06-15T09:12:00 (ISO 8601, with or without a time zone)
  • 2026-06-15 09:12:00 or 2026-06-15 09:12
  • 15/06/2026 09:12:00 or 15/06/2026 09:12

Values without a time zone are interpreted in the server’s time zone.


  1. Exact filename match first (call_001.mp3 → call_001.mp3)
  2. Name without the extension, case-insensitive, as a fallback — so a manifest that lists call_001.wav still matches an uploaded call_001.mp3

Two useful consequences:

  • Order doesn’t matter. Rows that don’t match anything yet are kept on the project and applied automatically to files uploaded later. You can upload the manifest before, during, or after the recordings. With automatic analysis, uploading it first means no call is ever shown under a guessed name.
  • Transcripts count as calls. SRT and VTT uploads are matched exactly like audio files.

You can upload a manifest more than once; later uploads add to and update the stored rows.


A row is rejected — and reported back in the dialog — when:

  • filename is empty
  • call_datetime is missing or not in one of the accepted formats

Everything else is optional: unknown or empty optional columns are simply ignored. A direction or ended_by value that isn’t one of the accepted values is dropped, and so is an agent_email that isn’t a valid address. The rest of the row still applies.


Most dialers and ACDs record which side disconnected first, often as a termination or release reason. Send it in the ended_by column:

ValueMeaning
customerThe customer hung up first
agentThe agent hung up first

The manifest also accepts cliente, client and caller for the customer, and agente, asesor and asesora for the agent, in any capitalization, so most dialer exports work as they are. Leave the cell empty when the dialer did not record it.

Why send it. A customer who says “okay, thanks” and hangs up while the agent is still closing looks, in the transcript, exactly like an ordinary goodbye. With ended_by, the closing-script steps you mark in your rubric are not docked on those calls — see Closing steps when the customer hangs up.

Three things worth knowing:

  • It is optional. Calls without it are scored exactly as before.
  • customer on a normal call is expected. Many customers hang up after the agent’s goodbye. Those calls are still scored normally: a step is only excused when the agent never got to say goodbye.
  • It is read when the call is scored. Adding or changing it on a call that is already scored changes nothing until you analyze that call again.

The value also appears as Hung up first in the call detail and in the Excel export of COPC results.


In a call center project the files table shows two extra columns — Call time and Agent — so you can see at a glance which calls already carry metadata. A call time shown in grey is the file’s upload time, used as a placeholder because no real call time has been provided yet.

Files table with the Call time and Agent columns

To change a single call, open the ⋯ menu on its row and choose Edit call metadata.

Edit call metadata dialog

The dialog has a field for every manifest column, including Hung up first. It is available on audio files and on SRT/VTT transcripts. A few things worth knowing:

  • Empty clears. Saving a field left blank removes the value that was there. This is the opposite of the CSV manifest, where a blank cell simply leaves the existing value alone. Agent email is the exception: it stays on the agent while the call keeps its agent ID or name. See Agent email.
  • Call time can’t be emptied. Clear it and the call falls back to the file’s upload time.
  • A later manifest wins. If you upload a CSV manifest afterwards, its rows overwrite what you typed here. Edit individual calls after the bulk load, not before.
  • Editing metadata never re-runs analysis. Scores, topics and sentiment are left exactly as they are; only the descriptive fields change. That includes Hung up first: to apply a new value to a call’s score, analyze the call again.

Uspeech keeps one agent record per person and links every call to it:

  • If you provide agent_id, it is the key — renaming the agent later keeps the history intact
  • If you provide only agent_name, agents are matched by name (case and spacing are normalized)
  • If you provide neither, the agent name the AI extracted from the conversation is used as a fallback

Metadata always wins. A name extracted from the audio never overwrites an agent supplied by the manifest or the API.


agent_email links an agent’s calls to their login, so they can see their own results. It has no effect on the report until you invite that address with the Agent role.

  • Send it with the agent_id. The email belongs to the agent record, so one row with both is enough for every call carrying that agent_id, including calls uploaded earlier.
  • An agent_id that is an email counts. If your systems identify agents by email, you don’t need the extra column: an agent_id that is a valid address is read as the agent’s email too.
  • Avoid an email without an ID. A row with no agent_id is matched by email instead. If no agent has that email yet, a new agent record is created, even when an agent with the same name already exists, so the same person can appear as two agents.
  • Entering a different email replaces it on the agent record, for all of that agent’s calls. Whoever was invited with the old address loses access to them. See Managing agents.
  • Clearing the field doesn’t remove it. To take away an agent’s access, remove them from the team instead.

If you upload recordings programmatically, you can attach the same fields to each file at upload time instead of maintaining a CSV, change them afterwards, and read back what a call currently carries — see Call Metadata API.