"Abhi busy hoon, baad mein call karo" isn't a no. It's a yes, later. In real campaigns, busy people (in class, driving, at work) are a large share of connected calls, and losing them is one of the most common leaks. The fix is simple: ask for a time, confirm it, record it as a field, and make sure the call actually happens at that time.
Add callback handling to your agent: Try Edesy free — Rs 50 free credit, no demo needed.
The script
Caller: Abhi busy hoon. Agent: Koi baat nahi. Aaj shaam 6 baje ya kal subah 11 baje, kaunsa theek rahega? Caller: Shaam 6. Agent: Theek hai, main aapko aaj shaam 6 baje call karungi. Dhanyavaad.
Offer two specific options rather than "when?"; people choose faster.
Capture it as data
| Field | Example |
|---|---|
| outcome | CALLBACK |
| callback_time | today 18:00 |
| reason | busy / driving / in class / in meeting |
Make the callback actually happen
Two practical ways:
- Follow-up campaign. Each evening, collect CALLBACK rows and run a follow-up campaign with a calling window matching the requested times.
- API trigger. Your system or an automation tool (Zapier, n8n) triggers the call at the requested time. See trigger calls from your app via API.
Retries for no-answer and busy handle people who didn't pick up at all; callbacks handle people who did pick up but asked for later. You need both. See why half your campaign calls fail.
When the callback call starts
Remind them they asked: "Namaste {{name}} ji, aapne kaha tha shaam 6 baje call karne ke liye..." It feels respectful and gets a better hearing.
Don't end the call by mistake
"Baad mein" and "thank you" are not goodbyes on their own. The agent should first get the time. See why your AI voice agent hangs up too early.
When to stop
After one or two callbacks that go unanswered, send the information on WhatsApp instead. See WhatsApp follow-up after an AI call.
Try it
Create a free account, add a callback_time field to your agent, and call yourself saying "abhi busy hoon".