Integrations and carriers: Google Sheets, Twilio and SIP setup

Open Integrations in the sidebar (the SubManager role does not see it). Connected shows one card per connection, with a status and an on/off switch. Add integrations shows the tiles you can add.

• A tile button reads Connect, Add another (several connections allowed) or Manage (LLM provider, Java and Cloud Precision have one each). A card shows Live, Switched off or Not signed in. One that needs a fix is listed under “1 connection needs attention”.
• Carriers are not a tile. See how do I add a carrier.

The screen says saved changes reach your bots within a minute, but a Google Sheets or Twilio change reaches them on their next sync, which can take longer. Force bot sync (the button on Integrations, and Force Bot Sync in the sidebar footer) pushes your settings, integrations, scripts and other bot data to every bot now, without cutting off live calls. A notification follows it for up to 8 minutes. Press it if a test call behaves the old way.

The Google Sheets tile signs VoiceOI in to Google with an OAuth client from your own Google Cloud project: a Client ID and Client secret that you create in Google Cloud, which let VoiceOI ask for permission to your sheets (see the glossary). The script step that writes the rows is covered in Script Builder and Monitoring and reports.

1. 1

   Create an OAuth client

   You

   In Google Cloud, create an OAuth client of the type Web application and enable the Google Sheets API and the Google Drive API. The How to create one link beside Client ID opens Google’s instructions. Then set up the consent screen (see the note below the steps).

2. 2

   Add the redirect address

   You

   On the tile choose Connect, open Redirect URI for your OAuth client, copy the address and add it to your OAuth client as an authorized redirect URI. It must match exactly.

3. 3

   Sign in

   You

   Enter the Client ID and Client secret and press Save and sign in to Google. VoiceOI saves the connection switched off and opens a Google pop-up. Allow pop-ups, choose the account and approve the permissions.

4. 4

   Check it

   You

   The pop-up closes itself, and the panel shows the connected Google account. Test checks the connection.

5. 5

   Use it in a script

   You

   Add an Integration node, pick this connection under Integration Account, then the spreadsheet and tab. Run a test call in the Simulator and look at the sheet.

• Permissions. VoiceOI asks Google for access to all spreadsheets of the account you sign in with (it can read and change them), read access to that account’s Google Drive files (used to list your spreadsheets) and its email address. Sign in with an account that holds only the sheets you want VoiceOI to reach.
• Buttons once signed in. Sign in again, Test and Change OAuth client (shows the Client ID and Client secret fields again).
• Sign in again clears the sign-in first. It switches the connection off until the Google pop-up finishes. If you close the pop-up, the card reads Not signed in and is listed with Finish setup.

The Twilio tile is for incoming calls. Twilio sends each call that arrives on your number to a web address VoiceOI gives you, and VoiceOI replies with what to play, listen for or do next, following a campaign’s script. It is not an inbound receptionist. The tile’s summary also says it “places” calls, but dialing out through Twilio uses a Twilio SIP trunk added as a carrier.

1. 1

   Prepare the campaign

   VoiceOI team

   The team creates the campaign, links your script and makes it active.

2. 2

   Fill in the tile and copy the address

   You

   Enter the number, Account SID and Auth token, choose the Campaign, save, then copy the Webhook URL into Twilio.

3. 3

   Call the number

   You

   Check that the script plays and the call appears in Call Logs (titled Interaction Logs).

• If the caller is not among your leads, VoiceOI adds one named Inbound Caller.
• On this route VoiceOI runs Play Audio, Listen, Check Condition, Wait, Transfer Call and End Call steps. Listen follows its keyword branches, without Smart Listen’s AI. Age Extraction works the same way and extracts no age. AM Detect passes straight through to the next step and does not detect an answering machine. The AI Voice Agent, Smart Reply and Google Sheets steps are not handled, so do not attach a script that needs them.
• The call is hung up at once if the campaign is not active, has no script or no longer exists, or if your account has reached its call-log limit.

These tiles hold keys and endpoints that belong to you. Saving reaches your bots with no redeploy or restart. Each has a switch that turns it off and keeps the saved key.

LLM provider: the model behind your AI agents and Smart Listen

Test connection works before or after you save. It sends one real request and checks the endpoint, key, model, speed and tool calling. A pass reads “The endpoint answered” with Round trip and Exit tool calling (works or not used). If it is not used, a call may never end on its own, so try a larger model. A reply slower than the budget warns that callers will often hear the fallback line, so raise the timeout.

In effect now shows what a call uses at this moment, with the badge From this page when your saved settings are in use. Until you save, bots keep the values they were deployed with and the card can read Using deploy settings, No API key or Key unreadable. See the AI model.

Java

The Java tile appears only when Smart Listen is on. Paste your Tavora API key, press Connect and leave Use Java for Smart Listen on. When Java is unsure, slow or down, the turn goes to the backup the panel names: your LLM provider, or keywords. When you connect your own key, Tavora bills that key, not VoiceOI. Held by support means support is keeping your calls on your LLM provider for now. See Java on the Smart Listen page.

Cloud Precision

Cloud Precision is your own speech-to-text key. It affects only Listen and Age Extraction questions you set to Cloud Precision Engine (Best on Phone Calls) under Recognition Engine (ASR) (see the engine list). If the cloud engine is slow, fails or runs out of credit, Deep Precision transcribes that answer instead.

Add carriers on Dialer > Carriers (titled Carrier Connections), on the Management tab. You may see this screen called the “Carrier Manager” elsewhere. The Dialer group shows only to the Admin, and only when the VoiceOI team has switched on the built-in dialer. If VICIdial is your dialer, it places calls through the carriers in your own VICIdial and you add nothing here (which setup do I have).

You can use a SIP carrier of your own, including a Twilio Elastic SIP trunk or a Telnyx SIP connection. Your carrier bills the minutes; VoiceOI bills per bot. The Handbook tab says the carrier must support SIP (RFC 3261), G.711 u-law audio and RFC 2833 keypad tones, and must accept calls from the VoiceOI dialing servers. Check your carrier’s rules for automated and AI-voice calling before you rely on it. See the SIP trunk guide.

1. 1

   Collect the details from your carrier

   You

   You need the SIP server address, how it authenticates you (your IP address, or a username and password with registration), the caller ID numbers you may show and the number format it expects. See Twilio and Telnyx.

2. 2

   Get the addresses to allow

   Both

   Ask the VoiceOI team for the addresses of your dialing servers and add them to your carrier’s access list. The servers can change, so allow the whole range the team gives you if your carrier lets you.

3. 3

   Add the carrier

   Both

   On Management, under SIP Carrier Registry, press Add Carrier. Fill in Carrier Name, Registration String and Account Entry from your carrier’s details. Dialplan Entry is required to save: the VoiceOI team enters or confirms it with you on your first carrier, so do not paste a dialplan from VICIdial or another system. Then press Create Carrier.

4. 4

   Confirm it is live

   Both

   Saving stores the carrier on your account. Ask the VoiceOI team to confirm it is live before you rely on it.

5. 5

   Test with your own phone

   You

   On Dialer > Missions, set the mission’s Outbound Carrier to this carrier (the mission form). Load a list with only your own number and place one call. Check that it rings, shows the caller ID you expect and appears in Call History.

The carrier form

exten => _9.,1,NoOp(Outbound call)
same => n,Set(CALLERID(num)=+15555550123)
same => n,Dial(SIP/${EXTEN:1}@ExampleCarrier,,tTo)
same => n,Hangup()

Each carrier card has an Active or Disabled switch (only active carriers are used), Edit and a delete button. Protocol on a card is a label guessed from the pasted text, not a test. For Live Traffic, see the built-in dialer guide.

Yes. VoiceOI offers its own carrier service as a separate product. It is never part of the bot price, and carrier prices are not listed here. Contact the team for prices and setup. You can also use a SIP carrier of your own.

• Built-in dialer. The number comes from your carrier and dialplan. Tell the VoiceOI team which number to show. It goes in the Dialplan Entry as a line such as same => n,Set(CALLERID(num)=+15555550123) before the Dial line, and it must be a number you own or are authorized to use. The sample number is a placeholder.
• Your carrier decides which numbers it lets you show, so ask it whether it accepts the number you set. Twilio, for example, accepts only a Twilio number on your account or one you have verified with it. See the Twilio guide.
• VICIdial accounts. The number comes from your VICIdial and its carrier, not from a VoiceOI setting.

No. VoiceOI has no outbound webhooks, no public API or SDK, and no native CRM sync with HubSpot, Salesforce, GoHighLevel, Zapier, Make or n8n. The only webhook address on the Integrations page is the Twilio one, and it carries calls into VoiceOI, not data out.

Put the Google Sheets step only where you count the caller as qualified, because a call that reaches it is logged as SALE (details).