VoiceOI does not have a native CRM integration yet. It does write a row to a Google Sheet for every call that reaches the Google Sheets step, and that sheet can reach most CRMs two ways: a CSV import, or an automation tool that watches the sheet for new rows.
Last reviewed by the VoiceOI team
No. VoiceOI does not push call data to HubSpot, Salesforce, GoHighLevel or any other CRM by itself, and it has no outbound webhooks or public API. Native integrations are planned. No release date has been announced.
What works today is the Google Sheets step, included on the Pro LG bot tiers. Each call that reaches it appends a row with the lead details and the answers the bot collected. From that sheet you can import a CSV file into your CRM, or let an automation tool such as Make, n8n or Zapier watch the sheet and pass each new row on.
If you run VICIdial, call outcomes are also written back to VICIdial as dispositions, so VICIdial's own reports and exports keep working.
Pick by how much manual work your team will accept and how soon the results need to arrive.
| Method | Setup | When results reach the CRM | Watch for |
|---|---|---|---|
| Read the VoiceOI dashboard and log by hand | None | When someone logs them | Works with every bot type. Fine for a pilot, slow at scale. Call logs, dispositions, recordings and transcripts stay in VoiceOI. |
| Google Sheet, then a CSV import | A Google Sheets step in the script (Pro LG tiers), and an import in the CRM | When you run the import | One manual step per batch, and the CRM's own import rules apply. |
| Google Sheet, then an automation tool | A Google Sheets step (Pro LG tiers), and a trigger plus a CRM step in the tool | When the tool picks up the new row | A third-party tool and its plan. VoiceOI does not build, host or support the connection. |
These steps are the same whichever way the rows travel on to the CRM.
Download the sheet as a CSV file and use your CRM's import tool. The rule is the same in every CRM: the first row holds column names, and the CRM matches them to its fields. What the tools accept:
Automation tools can start a workflow whenever a new row appears in a Google Sheet, then hand the row to another app. All three of these document a trigger for it:
A suggested mapping, not a built-in feature. Field names differ in every CRM.
| Sheet column | Typical CRM field | Tip |
|---|---|---|
| Phone | Phone or mobile phone | Use it as the match key and keep one format, such as digits with the country code, so a repeat call updates one record instead of creating a copy. |
| Name | First name and last name, or full name | Split the name before the import, or in the tool, if your CRM stores the two parts separately. |
| Answers to your script's questions | Custom fields or properties | Create the custom field in the CRM first. HubSpot, for one, matches headers to properties that already exist or that you create before importing. |
| Call date and time | Activity date, or a call record | HubSpot's import tool can bring in calls as activities. In other CRMs a date field or a note works. |
Source for the HubSpot statements: HubSpot, Format import files and Import records for multiple objects, read October 1, 2026.
A row is written only when a call reaches the Google Sheets step, and in most scripts that is after a lead qualifies. A caller who asks not to be called again usually never gets there, so that request will not show up in the sheet. VoiceOI records it as a do-not-call disposition in the call log, and in VICIdial if you use it.
Copy those numbers to your own suppression list. Under 47 CFR § 64.1200(d)(3), a company making telemarketing calls must record a do-not-call request and place the number on its do-not-call list at the time the request is made, must honor it within a reasonable time that may not exceed ten business days, and stays liable if another party keeps the records and fails to honor it. This is general information, not legal advice. See also how VoiceOI handles do-not-call requests.
Native connections are planned for HubSpot, Salesforce, GoHighLevel, and Make and n8n, along with outbound webhooks and an API. None is available today and no dates are announced. Each status page says what works now:
Everything above about other products comes from these pages, read on the date shown. Product pages change, so check them against the version you use.
Straight answers on what VoiceOI connects to today.
Not natively yet. Native integrations are planned and no release date has been announced. Today you can send call data to a Google Sheet and move it into your CRM with a CSV import or an automation tool.
On the Pro LG bot tiers, add a Google Sheets step to your call script. Each call that reaches it appends a row to your sheet. Then either download the sheet as a CSV file and import it into your CRM, or connect an automation tool such as Make, n8n or Zapier to watch the sheet and pass new rows on.
No. VoiceOI has no outbound webhooks or public API today, and both are planned. The Google Sheets step is the way call data leaves VoiceOI now; if you run VICIdial, call outcomes are also written back to VICIdial as dispositions.
No. The Google Sheets step only writes call data to a sheet. Load leads with a CSV upload, or keep your lists in VICIdial and let VoiceOI bots work as VICIdial remote agents.
The Google Sheets step is included on the Pro LG bot tiers, on VICIdial or hosted SIP. The Simple LG, Fronter and Closer tiers do not include it, so with those, call logs, dispositions, recordings and transcripts in the dashboard, and VICIdial dispositions if you use it, are where results live. The pricing page lists each tier.
A caller who opts out is recorded as a do-not-call disposition in the call log, and in VICIdial if you use it. The sheet only receives calls that reach the Google Sheets step, so copy do-not-call numbers to your own suppression list. Under 47 CFR 64.1200(d)(3) a request must be honored within a reasonable time that may not exceed ten business days. This is general information, not legal advice.
One is planned for the main CRMs, with no date announced. Tell us how your team works on the contact page so we know what matters to build first.