I’m new, and want to carry over most of my original data, like Client ID, Name, Address, etc. in the exported data, so I don’t have to “marry” my original file with what happened in the call. How can I do this?
Hey @EddieParnelli The best way to carry over your original data (Client ID, Name, Address, etc.) is to use the metadata parameter when creating a call. It’s a free-form object you pass when initiating an outbound call, and it gets stored with the call record — so it’s available in exports and API responses without needing to re-join files.
Example:
{
"metadata": {
"client_id": "cust_123",
"name": "Jane Doe",
"address": "123 Main St"
}
}
This data is stored with the call and can be retrieved via the List Calls API or webhooks.
Thank You
In the post call data retrieval, can I create a new field with this logic: “The Subscriber ID for this call, exactly as provided in the dynamic variable {{Subscriber}}. Do not infer or alter it — output its value verbatim.” Should this work for static fields?
Hello @EddieParnelli Yes, this approach can work — but with an important caveat.
Post-call analysis fields use an LLM to extract data from the conversation transcript. The description field is the prompt given to that LLM. So a description like:
“The Subscriber ID for this call, exactly as provided in the dynamic variable
{{Subscriber}}. Do not infer or alter it — output its value verbatim.”
may work, but it’s not guaranteed to be perfectly reliable since the LLM is still interpreting the instruction. For truly static passthrough data, metadata (passed at call creation) is the more reliable approach — it’s stored verbatim with no LLM involvement.
See Post-Call Analysis: Define Fields for field configuration details.
Thank You