Bulk Voice calls are still the fastest way to reassure a prospect, qualify a lead, or update an existing customer. But juggling manual call lists or switching between apps slows your team down. That’s why the new Google Sheets voice-call automation script from SMS Gateway Center has become a favorite among customer-facing teams – it sends voice calls automatically the moment a row is created, while still giving managers full control over what goes out.
In this guide, we’ll walk through how the solution fits into your ecosystem, the benefits for sales and support teams, and the exact steps to configure the integration so it shares space comfortably with any existing third-party scripts (such as WhatsApp workflows).
Why it matters: Real-time voice follow-ups close gaps between your brand and your customers. Automating those touchpoints directly from the spreadsheet where your teams already live is a game changer.
1. Integrated Webhook Magic: Let Sheets Talk to SMS Gateway Center
At the heart of the solution is a webhook that bridges new spreadsheet activity with the SMS Gateway Center voice platform. The workflow looks like this:
- A new row enters your Google Sheet-perhaps from a form submission or an API.
- The script sanitizes the contact information, aligns it with the configured country code, and prepares the voice call payload.
- The voice call fires instantly via the SMS Gateway Center API, logging success or failure back in the sheet.
Because the script lives inside the sheet, you can easily see outcomes, retry calls manually, or stop auto-processing altogether with a simple toggle.
Need a refresher on voice APIs? Check out the broader benefits of automated outreach in our voice marketing resource library.
2. Auto Trigger / Auto Process: Hands-Off When You Need It
For teams that receive a steady stream of leads, auto-processing is the unsung hero:
- Real-time reactions: The script’s on-change trigger detects new entries the moment they land in the sheet.
- Duplicate safety: Once a row is tagged as “Sent” or “Failed” the auto-processor ignores it on future passes. Your customers receive exactly one outbound call unless you intentionally reset the status.
- Visual status tracking: A dedicated status column flashes yellow while a call is in progress, then flips to green or red once the API responds.
Prefer to send calls manually? Disable the trigger, or use the built-in side panel to select specific rows. Manual and automatic flows can live together, letting supervisors spot-check before letting the automation run wild.
3. Step-by-Step Functionality Inside the Sheet
Here’s how users experience the system day to day:
- Row arrives: A new row with name and phone number is appended – perhaps by a third-party chatbot via webhook.
- Auto or manual send: Depending on your settings, the script either fires immediately or waits for someone to click “Send.”
- Status update: The script writes the outcome (success, fail, or retry needed) into the status column and (optionally) colors the cell.
- Detailed logging: Every action is captured in the embedded log viewer, so managers can audit the sequence or copy URLs for browser testing.
By keeping logs within the spreadsheet, non-technical teammates can troubleshoot without touching the Apps Script editor. That also means less dependency on engineering resources whenever a client asks, “Did the call go out?”
4. Configuration Essentials: Make It Yours
Most clients need just a few minutes to tune the script for their environment:
- Set your default country code so 10-digit numbers get formatted correctly.
- Point the script at the right columns (e.g., column C for mobile numbers, column N for the status badge).
- Adjust the API credentials and library IDs to match the voice library you want to use.
- Enable or disable highlights with a single flag – useful when you share grids with other teams that prefer a minimalist aesthetic.
- Choose the timezone for stamps in the status column so the call history lines up with your local reporting.
const CONFIG = {
// API Credentials
sgc_username: 'YourUsername', // CHANGE THIS: Your SMS Gateway Center username
sgc_password: 'YourPassword', // CHANGE THIS: Your SMS Gateway Center password
sgc_voice_api: 'https://unify.smsgateway.center/VoiceApi/send',
// Voice Call Settings
reDial: 2, // Retry attempts (0, 1, or 2)
redialInterval: 5, // Minutes between retries (1-15)
// Sheet Configuration
firstDataRow: 2, // First data row (row 1 = header)
mobileColumn: 3, // Column C = mobile number
nameColumn: 2, // Column B = name (optional)
processedColumn: 14, // Column N = status marker
highlightStatusColumn: true, // Set false to disable background highlights
statusTimeZone: 'Asia/Kolkata', // Timezone for status timestamps (e.g., 'America/New_York')
// Auto-Processing
sendAutoEmail: false, // Send email for auto-processing? (true/false)
autoDelay: 500, // Milliseconds delay between calls (prevent rate limit)
defaultCountryCode: '91', // Default country code to prepend when not present
};It’s all driven by a single CONFIG block near the top of the script, so there’s no rummaging through dozens of functions whenever requirements change.
5. Coexisting with Other Scripts: Add a Secondary Email
Many organisations already run a third-party Apps Script – think WhatsApp follow-ups or CRM connectors. To avoid permission conflicts:
- Add a secondary email (often a shared automation account) as an editor of the spreadsheet.
- Authorize the voice call script under that account as well. This keeps ownership balanced and allows both scripts to run without stepping on each other’s authorization tokens.
- Let both scripts write to their own columns (for example, WhatsApp updates column L, while the voice call script monitors column N). Separation reduces the chance of overwriting someone else’s notes.
The result is a clean choreography: WhatsApp updates, voice calls, and even marketing automation rules can all fire from the same dataset while staying out of each other’s way.
6. Permissions Checklist (Without the Jargon)
To run smoothly, the script needs access to your sheet, the script’s runtime, external HTTPS calls, and the custom sidebar interface. The OAuth scopes you approve – namely spreadsheet, ScriptApp, external requests, and container UI – grant exactly those abilities, nothing more. When you deploy the script in your Google Workspace, make sure the consent screen and scopes are recorded so administrators can verify compliance.
"oauthScopes": [
"https://www.googleapis.com/auth/spreadsheets.currentonly",
"https://www.googleapis.com/auth/script.scriptapp",
"https://www.googleapis.com/auth/script.external_request",
"https://www.googleapis.com/auth/script.container.ui"
],7. Ready for Production: A Quick Recap
- Webhook integration sends voice calls instantly whenever a new lead arrives.
- Auto trigger / auto process keeps the pipeline moving without human intervention, yet avoids duplicate calls.
- Manual controls and logs empower your team to step in whenever needed.
- Config flags (time zone, country code, highlighting) let you tailor the experience in minutes.
- Cooperative permissions ensure the solution plays nicely with existing scripts and shared accounts.
If you’re reimagining how your sales or support teams follow up, this combination of Google Sheets + SMS Gateway Center is a lightweight yet powerful answer. You get granular control, a transparent audit trail, and the speed of voice – all without leaving the spreadsheet your team already loves.
Looking to explore more automation ideas? Browse our voice campaign best practices and see how other businesses are streamlining customer outreach.
Need help rolling it out? Reach out to the SMS Gateway Center support desk and we’ll guide you through onboarding, best practices, and advanced automations tailored to your industry.
