Short answer: a missed call number captures the lead and sends a signed call.missed webhook in
real time. Your system (or ours, if you ask us to set it up) receives that webhook and places an
outbound call to the caller through an AI voice agent. The agent qualifies the
lead, books the next step and writes the outcome back to your CRM. Every lead gets a call within about
a minute, including at 11 pm on a Sunday.
Get a Missed Call Number to start capturing leads, and tell us if you want the callback wired up for you.
Why Callback Speed Matters
People give missed calls on impulse: at a traffic signal looking at a hoarding, reading the morning paper, watching a TV ad. Intent is highest in that moment and fades quickly. The person may also have given missed calls to two of your competitors in the same minute.
Most teams lose leads not at capture but at callback:
- Calls arrive at night and on weekends when nobody is at the desk.
- A campaign spike produces more leads in an hour than the team can call in a day.
- Callbacks happen in whatever order the executive scrolls the list.
An AI voice agent removes the queue for the first call. Your human team still closes; the agent makes sure nobody waits.
The Architecture
Caller gives missed call
|
v
Missed call number -- busy tone, caller not charged
|
v
call.missed webhook (signed, retried, real time)
|
v
Your endpoint: verify -> dedupe on call_sid -> queue
|
v
Worker: rules (hours, repeat caller, campaign) -> place outbound call
|
v
AI voice agent calls the lead, qualifies, books next step
|
v
Outcome written to CRM; hot leads routed to a humanStep 1: Capture
Each campaign gets its own missed call number, labelled in the portal. The call is rejected with a busy tone, so the caller pays nothing. Number, time and number label are logged instantly. See the callback request use case.
Step 2: Receive the webhook
Your endpoint receives:
{
"event": "call.missed",
"timestamp": "2026-10-20T21:14:03Z",
"data": {
"call_sid": "...",
"from": "+919876543210",
"to": "+918045xxxxxx",
"phone_number_name": "Diwali print ad"
}
}Verify X-Edesy-Signature, store the event keyed on call_sid, return 200. The details are in
missed call webhook best practices.
Step 3: Decide whether to call
This is where most of the business logic lives. A small rules function is enough:
| Rule | Example |
|---|---|
| Calling hours | Call immediately between 9 am and 9 pm; queue night leads for the morning, or call at night only if your use case and consent allow it |
| Repeat caller | If this number was called back in the last 24 hours, do not call again; notify the assigned executive instead |
| Existing customer | If the number matches an active customer in the CRM, route to support, not sales |
| Campaign script | Choose the agent script from phone_number_name (project A vs project B, JEE vs NEET) |
| Capacity | Cap simultaneous outbound calls so a TV spike does not exhaust your channels |
| Delay | Wait about 60 seconds before calling so it does not feel like an instant robocall |
Follow applicable telemarketing rules (including DND and calling-hour requirements) for your use case. A callback to someone who just asked for one is a different situation from cold calling, but get your own compliance advice.
Step 4: Place the outbound call
Your worker calls the AI voice agent's outbound API (or the Voice API if you run your own agent) with the caller's number, the script or agent to use, and context such as the campaign name. Pass your own lead ID as an external reference so the result can be matched back.
Step 5: Run the conversation
A good missed call callback script is short:
- "Hi, this is the assistant from [business]. You gave us a missed call about [offer] a minute ago. Is this a good time?"
- Two or three qualifying questions (budget range, location, course, timeline).
- One clear next step: book a site visit, a counselling slot, a test drive, or "our executive will call you at 5 pm".
- Confirm and close.
Because the missed call was language-neutral, choose the callback language by number or region. Edesy's AI voice agent supports Hindi and several other Indian languages.
Step 6: Write back and hand off
Write the outcome (answered or not, qualification answers, booked slot) to the CRM. Route hot leads to a human immediately; your team can call them from the outbound dialer. Retry unanswered leads once or twice at different times, then stop.
Build It or Have It Set Up
| Build it yourself | We set it up for you | |
|---|---|---|
| Missed call capture | Self-serve portal | Same |
| Webhook receiver and rules | Your code | Configured by us for your account |
| AI voice agent | Configure in the AI voice agent app and call its API | We configure the agent and script with you |
| CRM write-back | Your code | Edesy CRM, or your CRM connected by us |
| Time to live | Depends on your team | Usually a few days after we understand your flow |
Automatic AI callback is not a switch in the missed call portal today. It is available on request: we connect your missed call number to an AI voice agent for your account. If you have developers, the webhook plus API route above gives you full control.
Cost Shape
Two parts, billed separately:
- Missed call capture: ₹499 per month per number plus ₹0.30 per webhook event delivered, or ₹1,498 per month for the unlimited plan (plus GST). See pricing.
- Callback minutes: the AI voice agent is billed per minute of conversation. Short qualifying calls keep this low; check the current rates in the AI voice agent pricing.
Only leads that pick up generate meaningful call minutes, and every lead gets a first attempt.
When Not to Automate
An AI first call is not right everywhere:
- Very high-value, low-volume leads (luxury property, large B2B deals) may deserve a human first call.
- Sensitive contexts such as some healthcare or financial conversations may need a human.
- Campaigns without a clear next step produce awkward AI calls. Fix the offer first.
In those cases, use the webhook to alert a human instantly (CRM task, notification) instead.
Measuring the Callback Funnel
Once callbacks are automatic, measure each stage so you know where leads are lost:
| Stage | Source |
|---|---|
| Unique callers | Missed call dashboard, per number |
| Callback attempted | Your worker logs or CRM |
| Callback answered | AI voice agent call logs |
| Qualified | Agent's captured answers in the CRM |
| Next step booked | CRM stage |
| Converted | CRM stage |
If attempted is far below unique callers, your rules are too strict or the worker is failing. If answered is low, try a short delay, a different time of day, or a recognisable caller ID. If qualified is low, the ad is attracting the wrong audience or the script asks the wrong questions. Review a sample of call recordings every week during the first month; scripts improve fastest when someone listens.
Get Started
- Get a Missed Call Number and complete KYC.
- Set up a webhook to your system, or to Edesy CRM on its free plan.
- Either build the callback worker above, or ask us to set up the automatic AI callback for your account.