3
AC
Calls/Investigation/call_8f2a91

call_8f2a91

Support Concierge · v1.4.2 · Vapi

Call summary

Outcome

failed

Status

failed

Failure reason

LLM timeout after tool-call retry storm

Quality

41

Customer sentiment

-0.35

Agent sentiment

0.25

Compliance

pass

Total cost

$0.134

Deployment

2026.08.03

Incident

inc_1001

Provider call ID

prov_8f2a91

Recording

available

Root-cause hypothesis

Customer experienced a multi-second response delay culminating in failure. Approximately 1.6 seconds came from the CRM lookup/update retry storm, 700 milliseconds from LLM generation under retry pressure, and 500 milliseconds from TTS synthesis timeout.

AI hypothesis · conf 86%

Components used

CarrierSIPASRLLMToolsTTSWorkflow

Evaluator results

overall 41task 0accuracy 48safety 96compliance 90failtask_incompleteexcessive_latency

Synchronized replay

Select waveform, word or marker — all panels seek together

0.0s / 142.0s · 1x · ch both
Error Silence Tool Evaluation Interruption

Conversation transcript

Speaker-separated · click turn to seek

system0.01.2s (1s)en-US

Call connected · recording disclosure played

agent1.46.2s (4s)en-USsent 0.4neutralgreetinggap 480ms sp_llm_1

Hi, thanks for calling. This call may be recorded. How can I help?

customer7.011.2s (4s)ASR 94%en-USsent 0.1neutralchange_address sp_asr_1

I need to change the shipping address on my last order.

order:last
tool11.813.9s (2s) sp_tool_1

crm.lookup_order → 200 OK (210ms)

agent14.517.8s (3s)sent 0.3gap 620ms sp_llm_2

I found order 88421. What's the new shipping address?

customer18.524.1s (5s)ASR 91% sp_asr_2

1847 Market Street, apartment 4B, San Francisco, 94103.

address:1847 Market Stzip:94103
tool25.029.8s (4s) sp_tool_2

crm.update_address → timeout (retries: 3)

tool_failure
agent31.232.8s (1s)gap 1680ms sp_llm_3

Sure, let me look that up…

excessive_latency
system33.037.2s (4s)

[silence 4.2s — no response]

dead_air
customer38.040.2s (2s)ASR 97%sent -0.45frustratedinterruption

Hello? Are you still there?

system41.041.5s (500ms)

Call failed · llm.complete timeout after tool-call retry storm

task_incomplete

Call waterfall

Carrier → SIP → media → ASR → LLM → tools → TTS → terminate

Trace timeline

Click span to seek

Automatic latency bottleneck diagnosis

Customer experienced a multi-second response delay culminating in failure. Approximately 1.6 seconds came from the CRM lookup/update retry storm, 700 milliseconds from LLM generation under retry pressure, and 500 milliseconds from TTS synthesis timeout.

CRM lookup / update1600ms (57%)
LLM generation700ms (25%)
TTS synthesis500ms (18%)