To auto-call form leads with an AI voice agent, send each form submission to a webhook, pass the
name, phone number and answers to the voice agent's Calls API (through n8n, Make, Zapier or your own
server; for Google Forms, through an Edesy Workflow), and write the call result back to your sheet or CRM when the
call.analyzed event arrives. The lead gets a qualifying call within about a minute, and on
pay-as-you-go it costs Rs 6 per minute of agent time plus telephony.
This post explains the recipe, the honest connection method for each kind of form, what the agent should say, what it costs and what it can't do. The click-by-click setup is in the form submission to AI call tutorial.
What is an auto-call for form leads?
It is a three-part automation:
- Trigger: someone submits your form (a contact form, a quote request, a demo request, a course enquiry).
- Voice call: an AI voice agent calls the number they entered, greets them by name, confirms what they asked for, asks your qualifying questions and books a slot or hands over to a person.
- Write-back: the outcome, summary and extracted answers (budget, timeline, preferred time) are saved where your team works.
It is the form-specific version of the speed-to-lead playbook, which covers why response time matters across all lead sources. This post is about wiring the form itself.
Why it matters for Indian businesses
Form leads go cold quickly, and in India they are usually shopping around: the same person fills in three or four quote forms in an evening. Whoever calls first, in the lead's own language, usually gets the conversation.
An illustrative example (assumed numbers, not a benchmark): a coaching centre gets 300 website enquiries a month and its two counsellors reach about half of them the same day. The other half are called the next day or not at all. An AI agent that calls every enquiry within a minute, and passes only interested people to the counsellors, changes who the counsellors spend their day with, not how many people they have.
For scale on our side: Edesy agents have handled over 3.4 lakh connected conversations across 6,000+ sign-ups. We don't publish a form-lead answer rate yet, so measure your own in the first week.
How the setup works: trigger, voice call, write-back
| Your form | How it reaches the voice agent today | Status |
|---|---|---|
| Voice agent call-request form ("Call me now") | Built in: the form places the call itself | Native |
| Edesy Forms | Forms webhook integration → n8n, Make or Zapier → Calls API | Via webhooks in n8n, Make or Zapier, or via API (native planned) |
| Google Forms | Edesy Workflow App event "New Form Response" (polled every minute) → Voice Agent step | Via Edesy Workflow |
| Website or WordPress form | Your backend calls the Calls API, or the plugin's webhook goes to n8n or Make | Via API |
| Typeform, Tally, Jotform and others | Their webhook → n8n, Make or Zapier → Calls API | Via webhooks in Zapier, n8n or Make |
1. Trigger
Edesy Forms: in n8n (or Make), add a Webhook node with header authentication (Edesy Forms doesn't sign its webhooks, so a secret header is how you reject fake requests). In Edesy Forms, go to Integrations → Add integration → Webhook, paste the URL and the header, and pick your form. Answers arrive keyed by each field's internal ID, so copy the IDs of the phone and name fields first.
Google Forms: in Edesy Workflow, connect Google Forms and the Edesy Voice Agent, and start the workflow with the App event trigger "New Form Response", checking every minute. Google Forms has no push webhook, so Flow polls it. (Flow can also start from an Edesy Forms webhook, but its webhook trigger isn't self-serve in the editor yet; we set that up on request.)
If you don't need a separate form tool, the voice agent's call-request form is simpler. You embed it on your site, the visitor enters their number and ticks a consent box, and the agent calls. It ships with bot protection (Cloudflare Turnstile, a honeypot and a minimum fill time), an India-only country allowlist by default, and caps: one call per number per form per day by default, three per number across your workspace per day, and a daily total cap you set.
2. Voice call
In n8n or Make, add an HTTP request to the Calls API (add an IF step first that continues only when the consent box is ticked). In Edesy Workflow, add the Edesy Voice Agent step, Make Outbound Call, and map the same fields. Either way it is one request:
POST https://voice-agent.edesy.in/api/v1/calls
Authorization: Bearer vp_live_xxxxxxxx
Idempotency-Key: <form response ID>
{ "agentId": 123, "phoneNumber": "+919876543210",
"variables": { "customer_name": "Priya", "service": "Kitchen interiors" },
"retry": { "enabled": true, "maxAttempts": 2, "delayMinutes": 30,
"dispositions": ["NO_ANSWER", "BUSY"] } }The Idempotency-Key stops a resent webhook from calling the same lead twice.
The full reference is in the trigger-call API docs.
3. Write-back
Subscribe to call.analyzed under Settings → Webhooks in the voice agent. Each delivery is signed
with an X-Webhook-Signature: t=…,v1=… header and carries the disposition (QUALIFIED,
NOT_INTERESTED, CALLBACK_REQUESTED, NO_ANSWER, DO_NOT_CALL and others), the summary and the
extracted fields. From there:
- Google Sheets: native, with the agent's post-call Google Sheets Append step.
- Kylas: native, updating an existing lead.
- Edesy Tables: via its API.
- Zoho CRM, HubSpot, Salesforce: via webhooks in n8n, Make or Zapier.
Try it yourself: Build a lead-call agent free and have it call your own number from a test form.
A sample call script
Keep the first call under two minutes:
Agent: Hi Priya, this is the assistant from Sharma Interiors. You asked about kitchen interiors on our website a minute ago. Is now a good time for two quick questions?
Lead: Haan, boliye.
Agent: Thank you. Aapka kitchen kis area mein hai, aur aap kab tak kaam start karna chahte hain?
Lead: Andheri, next month.
Agent: Great. Our designer has a free site visit slot on Saturday at 11 am or 4 pm. Which one works for you?
Then confirm the slot, say what happens next and end the call. Tell the agent which disposition to set:
QUALIFIED (visit booked), CALLBACK_REQUESTED, NOT_INTERESTED, WRONG_NUMBER or DO_NOT_CALL, so
your reports stay clean, and capture the slot as an extracted field. The AI voice script generator
can draft a first version.
What does it cost?
Worked example using Edesy's published prices (excluding 18% GST). The volumes are assumptions; replace them with yours.
| Item | Example |
|---|---|
| Form leads per month | 300 |
| Leads who answer | 210 (assumed 70%) |
| Average call length | 2 minutes |
| Agent minutes | 420 |
| Pay as you go (Rs 6/min) | about Rs 2,520 |
| Pro (Rs 1,499/month incl. 300 min, then Rs 5/min) | about Rs 2,099 |
| Telephony | billed separately, 60-second pulse |
| Automation tool | your n8n, Make, Zapier or Edesy Workflow plan (n8n is free self-hosted) |
That is roughly Rs 8 to 12 per answered lead before telephony. New accounts get Rs 50 free credit with no card, which is enough to test the whole flow on your own number.
Manual calling vs IVR vs AI voice agent
| Telecaller calls back | Keypad IVR call | AI voice agent | |
|---|---|---|---|
| Time to first call | Minutes to next day | Under a minute | Under a minute |
| Asks open questions | Yes | No, keypress menus only | Yes |
| Hindi / Hinglish | Depends on the caller | Recorded prompts | Yes, switches mid-call |
| Books a slot | Yes | Rarely | Yes, through a connected calendar |
| Cost driver | Salary and seats | Per minute, lowest | Per minute |
| Best for | High-value, complex deals | Simple yes/no confirmations | Qualifying every lead the same way |
Most teams use the AI agent for the first call and hand qualified leads to a person.
Consent, DND and calling hours
- Collect consent on the form. A line such as "I agree to receive a phone call about my request at the number above. The call may be recorded." with a checkbox. That is the default text on the call-request form.
- Call about the request only. A call about the enquiry the person just made is a service call. Pitching unrelated offers turns it promotional, and TRAI's rules for promotional calls (including the DND register and 140-series numbers) then apply.
- Respect calling hours. 9 am to 9 pm IST is the usual safe window. Set a calling window on the agent; the default policy defers out-of-hours calls to the next opening rather than dropping them.
- Give a do-not-call option. When a call ends
DO_NOT_CALL, add the number to Settings → Blocked Numbers. Edesy does not check numbers against the NCPR (DND) registry for you. - Say it's automated and offer a person on request.
Our AI outbound calling guide for India and the voice agent compliance checklist go deeper.
What it can't do
- No native Edesy Forms to voice integration yet. It goes through n8n, Make, Zapier or your server today; Edesy Workflow's webhook trigger is set up on request, not self-serve.
- The Zapier app isn't published yet. In Zapier, use webhooks to call the API.
- HubSpot, Salesforce and Zoho CRM aren't native write-back targets today. Reach them through n8n, Make or Zapier; Kylas is native (update only).
- It can't fix bad numbers. Validate the phone field on the form and require a country code.
- It shouldn't call people who didn't ask. Bought lists are a compliance risk, not a lead source.
Related recipes
- Facebook Lead Ads to AI call: the same pattern for Meta instant forms.
- IndiaMART leads to AI call: marketplace enquiries.
- Google Sheets and the AI voice agent: call from a sheet and log results back.
- Use case: AI voice agent for lead qualification.
Using a different form or app? Tell us what you use and we'll tell you the best way to connect it.
Start free
Follow the step-by-step tutorial, then sign up and build your agent. Want us to look at your form and script first? Book a demo.