How do I handle a dropped call in a voice agent automation?
Short answer: stop treating a call as one webhook that either succeeds or fails. Treat it as a record with a status (started, in_progress, completed, dropped, unknown) that your workflow opens when the call starts and closes when the call ends. Every downstream action (booking, CRM update, follow-up SMS or email) reads that status first. A call that never reports a proper end gets closed by a timeout job and routed to a human or a callback queue, not silently forgotten.
This came up in r/n8n on 16 November 2026: "if u are automating using voice agents, how do u handle call-drop situtation or bad network scenarios?" and whether people "manually dry-run those cases" (thread). The same day another r/n8n thread described the wider problem for people running agents for clients: "a workflow dies, nobody notices for days, and the client finds out first" (thread).
What actually goes wrong when a call drops
| Situation | What the workflow sees | Typical damage |
|---|---|---|
| Caller hangs up mid-sentence | An end event with a short or partial transcript | Half-filled booking, or an AI summary that guesses the missing part |
| Network drops, call ends abnormally | An end event with an error or unusual end reason, or no end event at all | Record stays "in progress" forever |
| Call reconnects as a new call | Two separate call IDs for one person | Duplicate leads, two follow-ups |
| Your webhook is down when the end event fires | Nothing, unless the provider retries | Call happened, workflow never knew |
| End event arrives twice (provider retry) | Same call ID twice | Double SMS, double CRM note |
None of these are exotic. If your agent takes real calls, all of them will happen.
The pattern
1. Open a call record at the start
When the call starts (or when your workflow places an outbound call), write one row to a table you control: call ID, phone number, client, started_at, status started. A Postgres table, Airtable, or a Google Sheet all work for small volume. The call ID from your voice provider is the key.
2. Close it from the end-of-call event
Most voice agent platforms can send an end-of-call webhook with the call ID, an end reason, a duration, and the transcript. Field names differ by provider, so read your provider's docs and map them once. In n8n:
- Webhook node receives the end event.
- Look up the call row by call ID. If the row is already closed, stop here (this is your duplicate guard).
-
Classify the call with plain rules, not with the LLM:
- normal end reason and the required fields captured ->
completed - caller hung up or error end reason, or required fields missing ->
dropped - anything you do not recognise ->
unknown
- normal end reason and the required fields captured ->
- Update the row with status, end reason, duration, and transcript.
- Route by status (Switch node).
3. Only act on what was actually captured
The dangerous step is the AI summary. Given half a transcript, a model will often produce a confident, complete-looking summary. So:
- Define the fields a call must capture to count (for a booking: name, date, time, confirmation).
- Check those fields exist in the structured output before you book anything.
- If any are missing, the status is
dropped, whatever the summary says.
4. Route dropped calls to a recovery path
For dropped and unknown:
- Create a task or Slack message for a human with the phone number, what was captured, and the transcript.
- Or queue one callback attempt, if the client has agreed to callbacks and local rules allow it. Keep it to a small, fixed number of attempts and log each one.
- Never send the "your appointment is confirmed" message from this path.
5. Close stuck calls with a timeout job
A Schedule Trigger every 10 to 15 minutes finds rows still started or in_progress older than your longest realistic call plus a margin. Mark them unknown, and send them down the same recovery path. This catches the case where the end event never arrived, which is the one nobody notices.
6. Merge reconnects
Before creating a new lead from a call, check for another call from the same number for the same client in the last few minutes. If there is one, attach this call to it instead of creating a second lead.
Testing drop cases without making live calls
You do not need to dry-run calls by hand. Once your workflow is built around the call record:
- Save real payloads. From your provider's logs or n8n execution history, save one end-of-call payload for each case: normal end, caller hang-up, error end, very short call, and a duplicate of a normal end.
- Replay them. Use a Manual Trigger plus a Code or Set node that emits each saved payload into the same processing sub-workflow the webhook uses. Pinned data in n8n works for this too.
- Assert the outcome. For each payload, check the row ends in the expected status and that only the expected side effects ran (no booking for a hang-up, one SMS for a duplicate end event).
-
Test the silent case. Insert a
startedrow with an old timestamp and confirm the timeout job picks it up. - Re-run after every change to the prompt, the provider, or the field mapping.
Keep the payloads free of real personal data: replace names and numbers with test values before you store them.
Checklist
- [ ] Every call has one row keyed by the provider call ID
- [ ] End events are idempotent (second arrival does nothing)
- [ ] Status comes from rules and captured fields, not from the AI summary
- [ ] Confirmation messages only go out on
completed - [ ] Dropped and unknown calls reach a human or a bounded callback queue
- [ ] A timeout job closes calls that never reported an end
- [ ] Reconnects from the same number merge into one lead
- [ ] Saved payloads replay every drop case after each change
Does this work in Make too?
Yes. The same shape applies: a webhook scenario for the end event, a Data Store or sheet for call records, a router on status, and a scheduled scenario for the timeout sweep. If you are choosing a tool to run this, you can try Make here.
Sources: r/n8n threads collected 17 November 2026 (Asia/Saigon). Field names and end-reason values depend on your voice provider; check its documentation before mapping.
Want to build this visually? You can try Make here.
Disclosure: Some links are affiliate links — I may earn a commission at no extra cost to you.
Top comments (0)