VAPI•8mo ago

End Of Call Report - Pin Pointing thedynamicDestinationTransferCall number

I am having an issue pin pointing the value of the dynamicDestinationTransferCall number. The only place I can see the number within the End-of-call-report is within the Messages > Artifact > Inside one of the collections.

Pinpointing this is proving difficult, as there's a different number of messages each time. How can I extract the number the caller was transferred to, within the end-of-call-report.

Vapi Support BotAPP•5/23/25, 6:29 PM

To reliably extract the number the caller was transferred to in a Vapi end-of-call report, use the top-level destinationdestination field, not the nested tool call arguments. For example, in your JSON:

"destination": {
  "type": "number",
  "number": "+441925559"
}

"destination": {
  "type": "number",
  "number": "+441925559"
}

This field gives you the actual transfer destination, regardless of how many tool calls or messages are present.

Sources:

⤵️ Mention @Vapi Support Bot for follow-ups 🐥

Vapi Support BotAPP•5/23/25, 6:29 PM

To clarify: When there are multiple dynamicDestinationTransferCall numbers in the report, do you want to extract the first, last, or only the successful transfer destination? If you have access to timestamps or status fields for each tool call, that could help pinpoint the correct number.

Source:

Dynamic Call Transfers documentation

dead-brownOP•5/23/25, 8:15 PM

There is only one number in the report, but this is dynamically retrieved from a 'getNumber' tool.

I can't see an option for 'destination' in the end-of-call-report.

dead-brownOP•5/23/25, 8:21 PM

What server messages do I need to have enabled?

extreme-purple•5/24/25, 6:14 AM

Loop through messages[].toolCalls[].function.arguments.location, and return the first value that starts with + to reliably extract the transferred phone number from the end-of-call report.

Vapi Support BotAPP•5/24/25, 6:16 AM

To reliably extract the transferred number, make sure your assistant's serverMessagesserverMessages include both "transfer-destination-request""transfer-destination-request" and "end-of-call-report""end-of-call-report". Here’s how you can configure it:

"serverMessages": [
  "transfer-destination-request",
  "end-of-call-report"
]

"serverMessages": [
  "transfer-destination-request",
  "end-of-call-report"
]

This ensures your server receives the necessary events to track dynamic transfers and extract the number from the end-of-call report payload.
Reference: Dynamic Call Transfers documentation

Sources:

dead-brownOP•6/1/25, 1:07 PM

Thanks, got it working. Used an iterator to loop through the arrays until I found the toolcall with the transfer number:

VapiAPP•6/2/25, 11:01 AM

Glad it's solved

End Of Call Report - Pin Pointing thedynamicDestinationTransferCall number

Similar Threads

Similar Threads

Similar Threads