Lead Callback

A lead fills in your form. Before they have closed the tab, their phone is ringing and an agent is qualifying them. If they are worth talking to, a human picks up. This is the single highest-value thing on the platform.

Why seconds matter

Speed to lead is the most consistently reproduced finding in sales research: contact someone within a minute of enquiring and you are dramatically more likely to reach them and to convert them than if you call an hour later. It is not a small edge.

The reason is not mysterious. A minute after submitting, the person is still at their desk, still thinking about you, and has not yet filled in three competitors’ forms. An hour later they are in a meeting and you are a stranger.

What a trigger contains

A trigger is one lead source and everything that should happen to leads from it. Create them at Lead CallbackNew Trigger. You will usually have one per form or campaign, because different sources deserve different handling.

Where leads come from

Setting up a webhook source

When you create a webhook trigger, Vociply gives you an intake URL and a secret. The secret is shown once — copy it then.

POST https://vociply.com/api/leads/inbound/<your-trigger-key>
x-vociply-secret: <your-trigger-secret>
Content-Type: application/json

{
  "data": {
    "full_name": "Amina Otieno",
    "phone_number": "+254712345678",
    "email": "amina@example.com",
    "consent_checkbox": true,
    "timezone": "Africa/Nairobi"
  }
}

Send x-vociply-secret as a header. If your system can compute an HMAC, send x-vociply-signature: sha256=<hex> over the raw body instead — it is stronger, because it authenticates the payload rather than just the caller. Either is accepted.

Field mapping

Every form platform names its fields differently, so you tell Vociply where to look. Mapping uses dotted paths into the JSON you send:

Paths can reach into arrays: data.contact.0.phone takes the first contact’s phone. A default calling code is used to complete local-format numbers — a form that submits 0712345678 with a default of +254 becomes +254712345678.

Calling windows and consent

The calling window

Set a timezone, the days of the week, and the hours calling is allowed. The default is Monday to Friday, 08:00–20:00.

The important detail: the window is judged in the lead’s timezone when you have mapped one, and in the trigger’s timezone otherwise. A lead arriving at 3am local time is not called at 3am — it is held and dialled when the window opens.

Consent evidence

Turn on Require consent evidence and a lead with no consent value is not called at all. If your form has a “yes, you may call me” checkbox, map it and switch this on.

Vociply also checks the number against your do-not-call list and de-duplicates repeat submissions before dialling, so the same person filling in your form three times does not get called three times.

Qualification

After the call ends, Vociply reads the transcript and works out whether this lead is worth a human’s time. It does this in two distinct halves, and the split is deliberate:

• The AI extracts facts. “What budget did they state?” “Do they own the property?” “When do they want to start?”
• Your rules decide. Which of those answers must be present for the lead to count as qualified is a setting, applied in code.

This matters because it makes the verdict consistent and auditable. Ask an AI “is this lead good?” and you get an answer that drifts between calls and cannot be argued with. Ask it only what the person actually said, then apply your own rule, and the same facts always produce the same verdict — and when you disagree, you can point at the field.

Setting criteria

Each criterion has a key, a label, a type, and a description that tells the AI what to look for:

key: budget        type: number   "The monthly budget the caller stated"
key: decision_maker type: boolean  "Whether the caller can sign off themselves"
key: timeline      type: string   "When they want to start"
key: property_type type: string   "House, apartment, or commercial"

Required for qualified:  budget, decision_maker

Then make sure the agent’s instructions actually ask these questions. Criteria describe what to extract; they do not make the agent ask. Both halves are needed.

Warm transfer

The highest-value part of the whole flow: while the lead is still on the phone, the call is handed to a human.

Set the destination number, and optionally a whisper — a short line played to your salesperson before they are connected, so they know what they are picking up: Qualified solar lead from Facebook, budget 50,000.

Telling your other systems

As a lead moves through the flow, Vociply emits events you can send anywhere — an n8n workflow, a CRM, a Slack channel.

Deliveries are queued and retried rather than sent inline, so a slow endpoint on your side never delays a dial. Each delivery is recorded, so “did my workflow get told?” is answerable without digging through logs. See the n8n playbook for what to build on the other end.

Lead Callback questions