A Google Sheets AI voice agent setup has two directions: a new row in the sheet triggers a call (Edesy Workflow's Google Sheets "New Row Added" trigger plus the Edesy Voice Agent step), and every call writes its result back to the sheet (the voice agent's built-in "Save to Google Sheets" post-call workflow). Your team adds a name and number, and a few minutes later the same sheet shows the outcome, summary and answers. Calls cost Rs 6 a minute on pay as you go.
We have two narrower posts already: a ready n8n template to trigger calls from Google Sheets, and how to design a results sheet. This post puts both directions together without n8n. The click-by-click setup is the call results to Google Sheets tutorial.
What is this recipe?
- Trigger: a row is added to a sheet, by a person, a form (Google Forms writes to a sheet), or another tool.
- Voice call: the agent calls the number in that row, using the other columns (name, product, amount, appointment time) in the conversation.
- Write-back: outcome, summary, extracted fields and the recording link land in the sheet, either in the same row or a results tab.
It is the simplest way to run AI calls without a CRM, and a good pilot before you connect one.
Why it matters
Most small Indian businesses already run their leads, orders or dues on a sheet shared on WhatsApp. Asking them to move to a CRM before trying AI calls is the wrong order. Starting with the sheet means the team keeps working where it works, and the calls slot in.
An illustrative example (assumed numbers): a solar installer's office staff paste 10 to 15 new enquiries a day into a sheet from WhatsApp, IndiaMART and walk-ins. The AI agent calls each one, asks roof type, monthly bill and city, and books a site survey. By evening, the sheet has a "survey booked" column the field team can work from.
How the setup works: trigger, voice call, write-back
| Direction | How | Status |
|---|---|---|
| Sheet → call, automatically | Edesy Workflow: Google Sheets New Row Added trigger → Edesy Voice Agent step | Via Edesy Workflow |
| Sheet → call, one batch | Download as CSV or Excel and upload to a voice agent campaign | Native |
| Sheet → call, with n8n | Our n8n template | Via n8n |
| Call → sheet | Voice agent post-call workflow Save to Google Sheets (Google Sheets Append; Lookup and Update to edit an existing row) | Native |
| Call → Edesy Tables | The same post-call workflow's Webhook step calling the Tables API | Via API |
| Call → anywhere else | call.analyzed webhook → Zapier, n8n or Make |
Via webhooks in Zapier, n8n or Make |
1. Trigger
Connect your Google account in Edesy Workflow and add the New Row Added trigger on your sheet. It
polls the sheet, so expect a short delay rather than an instant call. Keep a header row with clear
column names: name, phone, product, city, notes. Store phone numbers with the country code
(+91…) and format the column as plain text so Sheets doesn't drop the plus sign.
2. Voice call
Add the Edesy Voice Agent step, Make Outbound Call:
- Phone Number: the
phonecolumn - Variables: the other columns, used in the agent's prompt as
{{name}},{{product}} - A row ID variable (or use the phone number), so the result can update the same row
3. Write-back
In the voice agent, open the agent's Post-Call Workflows section and choose Save to Google Sheets. This creates a workflow that runs after every call; map columns such as:
| Column | Value |
|---|---|
| Called at | call time |
| Outcome | disposition (e.g. QUALIFIED for a survey booked, CALLBACK_REQUESTED, NOT_INTERESTED) |
| Summary | AI summary |
| Roof type, Monthly bill | extracted fields |
| Recording | recording link |
Google Sheets Append always adds a row. To update the original row instead, use Google Sheets Lookup (by the row ID or phone you passed as a variable) and then Google Sheets Update. If columns come back blank, see blank Google Sheets columns from AI calls.
Try it yourself: Build an agent free, add your own number to a test sheet, and watch the row fill in.
A sample call script
Agent: Hello Mr Iyer, this is the assistant from SunRoof Solar. You enquired about rooftop solar for your home in Coimbatore. Is this a good time for two minutes?
Lead: Yes, tell me.
Agent: What is your average monthly electricity bill, and is your roof concrete or sheet?
Lead: About Rs 4,000, concrete.
Agent: Great, that's a good fit. Our engineer can do a free site survey on Thursday or Friday morning. Which suits you?
For Hindi-speaking customers: "Aapka mahine ka bijli bill lagbhag kitna aata hai?" The agent switches language when the customer does.
What does it cost?
Edesy's published prices, excluding 18% GST. Volumes are assumptions:
| Item | Example |
|---|---|
| New rows per month | 250 |
| Calls answered | 175 (assumed 70%) |
| Average call | 2 minutes (350 minutes) |
| Pay as you go (Rs 6/min) | about Rs 2,100 |
| Pro (Rs 1,499 incl. 300 min, then Rs 5/min) | about Rs 1,749 |
| Google Sheets | free |
| Telephony | billed separately |
Sheet vs Edesy Tables vs CRM for call results
| Google Sheets | Edesy Tables | CRM (Kylas, Zoho, Edesy CRM) | |
|---|---|---|---|
| Setup time | Minutes | Minutes | Hours |
| Good for | Pilots, small teams | Teams that outgrow a sheet | Sales pipelines |
| Access control | Share settings only | Workspace members | Full, per user and role |
| Voice agent connection | Native write-back | Via API (post-call Webhook step) | Native for Kylas (update only), Bitrix24 and Edesy CRM; Zoho CRM via n8n, Make or Zapier |
Start in the sheet; move when more than a few people edit it or the data gets sensitive.
Consent, DND and calling hours
- Only call rows of people who asked to be contacted. A sheet makes it easy to paste a bought list; don't.
- Daytime calls: 9 am to 9 pm IST. Set the agent's calling window; rows added at night are called when the window opens.
- Add a do-not-call column and a condition in the workflow that skips those rows. Fill it from the
DO_NOT_CALLdisposition, and add those numbers to Settings → Blocked Numbers. Edesy does not check numbers against the NCPR (DND) registry. - Limit sheet access. It holds names, numbers and call summaries: personal data under the DPDP Act.
Not legal advice. Our AI outbound calling guide for India has more.
What it can't do
- The New Row trigger polls, so calls start after a short delay, not the instant the row appears.
- Editing an existing row doesn't trigger a call; only new rows do.
- No native Edesy Tables step. Tables is reached through the Webhook step and its API.
- Google Sheets has write limits. For thousands of calls an hour, use Tables or a database.
- Sheets isn't a dialler. For thousands of numbers, use a voice agent campaign with retries and calling windows.
- The Zapier app isn't published yet, so in Zapier use webhooks.
Related recipes
- Auto-call form leads with an AI voice agent: Google Forms writes to a sheet, so the two combine
- COD order confirmation calls to reduce RTO
- Facebook Lead Ads to AI call
- Integration page: Google Forms + AI voice agent
- Use case: outbound campaigns
Keeping your data somewhere else? Tell us where.
Start free
Follow the step-by-step Google Sheets tutorial, then sign up and build your agent. Want a hand with the column mapping? Book a demo.