Skip to main content
Webhooks and API

Pre-Call Decisions: Call Later, Do Not Call and Reject

Let your pre-call webhook decide each campaign call: call now, call later, never call, or turn an inbound caller away, and see why on each lead.

Written By voiceaiwrapper

Last updated 26 days ago

Your pre-call context webhook can do more than pass details to the agent. It can decide what happens to the call: place it now, try the lead again later, never call the lead, or turn an inbound caller away. Use it as a final check against your own systems, for example to skip customers who converted in your CRM since the campaign started.

A lead that's skipped or postponed this way never reaches the voice engine, uses no call attempt and is never marked invalid. The campaign moves straight on to the next lead.

Before you start

  • Set up the Pre-call context webhook on the campaign. See Pre-Call Context Webhook.
  • Decisions work on every engine for outbound campaigns, and on VAW Native, Vapi and Retell AI for inbound campaigns.

Add a decision to your reply

Add a _decision object to your webhook's reply, beside the call context. A reply without _decision works exactly as before: the call goes ahead.

KeyRequiredWhat it does
actionYesOutbound: call, call_later or do_not_call. Inbound: answer or reject.
reasonNoFree text, up to 500 characters (longer text is cut). It's kept on the lead so you can see why. It's never spoken to a caller.
next_attempt_afterNoFor call_later only. An ISO 8601 time with its timezone offset, for example 2026-10-20T15:00:00-05:00.

Outbound actions

actionWhat happensUses an attempt
callThe agent calls the lead, with the rest of your reply as call context, as if there were no decision.Yes, as usual
call_laterThe lead isn't called now. It waits until next_attempt_after, then your webhook is asked again.No
do_not_callThe lead isn't called. Its Do not call switch turns on with your reason, so it's never called again.No
{
  "_decision": {
    "action": "call_later",
    "reason": "CRM sync pending",
    "next_attempt_after": "2026-10-20T15:00:00-05:00"
  }
}
{
  "_decision": {
    "action": "do_not_call",
    "reason": "Converted in CRM"
  }
}

To call a lead with your context, put the decision beside your engine's usual keys. For example, on VAW Native:

{
  "_decision": { "action": "call" },
  "variables": { "plan": "Gold" }
}

When the call-later time can't be used

If next_attempt_after is missing, in the past, has no timezone offset or can't be read, the campaign's retry rule sets the time instead, at least 15 minutes from now. The lead's hover text then says why, for example "The time had no timezone, so the campaign's retry rule was used."

Inbound actions

actionWhat happens
answerThe agent answers, with the rest of your reply as call context, as if there were no decision.
rejectThe caller is turned away before the agent answers. The caller's lead is kept with your reason, and its Do not call switch is left as it was.
{
  "_decision": {
    "action": "reject",
    "reason": "Known spam number"
  }
}

What the caller experiences depends on the engine:

EngineWhat a rejected caller hears
VAW NativeA busy tone. The call is never answered, so it isn't billed. In Call Logs its end reason is Rejected by inbound webhook.
Vapi"Sorry, we can't take your call right now." Then the call ends. Your reason is never spoken.
Retell AIRetell rejects the call before the agent answers.

Decisions we can't read

These count as a decision we can't read:

  • _decision isn't an object, or has no action.
  • The action is unknown, or belongs to the other direction (for example reject on an outbound call).

A reason that isn't text is dropped, but the decision still counts. A decision we can't read is treated as no answer (next section). On inbound calls, and on outbound campaigns set to Call anyway, the lead then shows Decision not understood with what was wrong. Under Call later, it shows Called later with the cause.

If your webhook doesn't answer

These all count as no answer: a timeout, an unreachable URL, a status other than 2xx, a body that isn't a JSON object, or a _decision we can't read.

Inbound calls: the agent answers as usual, without your context.

Outbound calls: the campaign's If the webhook doesn't answer setting decides. You'll find it under Pre-call context webhook in Settings β†’ Webhooks and Emails, once a URL is filled in.

OptionWhat happens
Call anyway (default)The lead is called as if there were no webhook, with its own details.
Call laterThe lead moves to its next attempt from the campaign's retry rule, at least 15 minutes away, and your webhook is asked again then.
Campaign β†’ Settings β†’ Webhooks and Emails on a paused outbound campaign, Pre-call context webhook filled in, with the 'If the webhook doesn't answer' dropdown open showing Call anyway and Call later, and the help text below it.

Choose Call later when no lead must be called without your check, for example a compliance lookup. Choose Call anyway when your context is nice to have but the call matters more.

With Call later, a webhook that stays down means no lead in the campaign gets called. While leads are being moved this way, the campaign's Health check shows Pre-call webhook not answering: "Leads are being moved to later because the pre-call webhook isn't answering. Check the webhook URL and that your endpoint is up." The warning covers the last 60 minutes, on active outbound campaigns set to Call later. See Campaign Health Check (Beta).

See what your webhook decided

Open the campaign's Leads tab. In the Lead column, a label next to the lead's name shows the latest decision. Hover over it for the details.

LabelWhen it showsHover text
Called laterYour webhook sent call_later, or didn't answer under Call later"Your pre-call webhook asked to call this lead later." or "Your pre-call webhook didn't answer (…), so the call was moved.", then the reason, the next attempt and when it was decided
RejectedYour webhook sent reject on an inbound call"Your pre-call webhook turned this caller away.", then the reason and when it was decided
Decision not understoodYour webhook sent a _decision we couldn't read, and the call went ahead"Your pre-call webhook sent a decision we couldn't read: … The call went ahead."

call and answer show no label. A lead stopped with do_not_call has its Do not call switch on. Hover the info icon next to the switch to see "Your pre-call webhook said not to call." and your reason. See Do-Not-Call: Sources and Reasons.

An outbound campaign β†’ Leads tab. One lead row shows the blue 'Called later' label (clock icon) in the Lead column, next to the lead's name, with its hover card open: 'Your pre-call webhook asked to call this lead later. Reason: CRM sync pending. Next attempt: … Decided ….' Another row shows the amber 'Decision not understood' label. Blur lead names, emails and phone numbers.

The do-not-call reason is also included in the leads event webhook (do_not_call_reason) and the leads export. On VAW Native, on plans that include API & webhook logs, every request and reply is also in API & Webhook Logs.

Frequently asked questions

No. A reply without _decision is used as call context, and the call goes ahead. Two things to check: on every engine except VAW Native, outbound requests carry _lead_metadata, _campaign_metadata and _attempt beside the engine's own fields, so allow them if your endpoint rejects unknown fields. And any 2xx status with a JSON object counts as an answer.

Turn its Do not call switch off in the Leads tab, or select leads and use Bulk Actions β†’ Do Not Call β†’ Do Not Call = False, then confirm Allow Calling. You can also send do_not_call: false through the API. For a pause that should lift on its own, have your webhook send call_later instead.

No. The caller's lead keeps its Do not call setting. Only the reason and the Rejected label are recorded.

The campaign's own attempt limits still apply to real calls. call_later and do_not_call don't use attempts, so a webhook that keeps sending call_later keeps postponing the lead. Use _attempt (or call.attempt on VAW Native) in the request to apply your own limit, and send do_not_call when you want to stop.