Home / Integrations

Integrations

Plugs into what you already run.

Voze connects to the systems your team already lives in — HubSpot, Salesforce, and 8,000+ other apps through Zapier. Companies, contacts, and notes flow both ways. Set it up yourself from Voze Web in about five minutes. No code. No IT ticket.

Live sync · both directions

Voze captures

VCompanies
VContacts
VVisit notes
VSignals

Your stack

HHubSpot
SSalesforce
ZZapier · 8,000+ apps
DYour DMS & ERP
Setup time
~5 min
Native setups
2 of 2
Via Zapier
8,000+
The integration model

Two tiers. Both self-serve.

Voze ships pre-built setups for the CRMs your team most likely runs on. Everything else — DMS, ERP, scheduling, comms — connects through Zapier's library. Either way, your team turns it on from Voze Web. Your IT team doesn't get a ticket.

Tier 01 · Native pre-built

HubSpot & Salesforce, click-to-connect.

Two-way sync of companies, contacts, and visit notes — purpose-built for the CRMs Voze customers most often run on. Turn it on from Voze Web in under five minutes.

  • Pre-built field mapping for companies and contacts
  • Visit notes attach to the right CRM record automatically
  • Filter by territory, team, or rep before pushing data
  • Two-way: CRM updates flow back into Voze the same way
Tier 02 · Zapier + 8,000+ apps

Everything else — your DMS, ERP, calendar, comms.

Voze speaks Zapier natively. If your tool's in Zapier's library (almost everything is), you can wire it to Voze without code. Map fields in Zapier's setup screen, filter what flows, and you're done.

  • Send Voze companies, contacts, and notes anywhere
  • Pull customer info from your CRM or DMS into Voze
  • Filter by territory, team, or rep on the way out
  • If you'd rather a native connector — our integrations team can usually build one
Two directions, not one

Data moves both ways. Filtered the way you want.

Most "CRM integrations" are one-way — your reps' work feeds a system they don't get anything back from. Voze runs it both directions, with rep-level, territory-level, and team-level filters so each side gets only what it needs.

Voze → your stack
Outbound
  • New companies and contacts reps add in the field flow into your CRM the moment they're saved.
  • Visit notes attach to the right CRM record automatically, with timestamps, audio, and transcript.
  • Structured signals (competitor mentions, expansion hints, at-risk flags) export with their source attribution intact.
  • Filter on the way out — push by territory, team, or rep so each system gets only what it needs.
Your stack → Voze
Inbound
  • Customer details from your CRM sync into Voze so reps have the right account info on day one — no manual import.
  • Account ownership and territory assignments come from your system of record — Voze respects who owns what.
  • Contact updates from CRM-side activity flow into Voze, so reps see the latest before the next visit.
  • Sync is near real-time — Zapier delivers in seconds to a few minutes. Native connectors sync continuously.
Self-serve setup

Three steps. About five minutes.

Most Voze customers connect their first integration without involving IT. The flow is the same whether you're connecting HubSpot, Salesforce, or any of the 8,000 Zapier-supported apps.

01

Open Integrations

In Voze Web, navigate to Settings → Integrations. You'll see the apps Voze can connect to, with the most common ones pinned at the top.

Voze Web Settings Integrations
02

Pick your app

Choose HubSpot or Salesforce for the click-to-connect setup. For anything else, choose "Connect a different app" and Voze opens a Zapier flow with the most common Voze triggers already configured.

HubSpot · Salesforce · 8,000+ via Zapier
03

Sign in and go

Authenticate to your other tool, choose what flows in each direction, set your filters (territory, team, or rep), and turn the sync on. The first data starts flowing within a minute.

Sign in Filter Sync live
Need a hand? Reach out to your Voze rep or visit help.voze.com — we'll walk you through it.
What Voze stays out of

Voze stays focused on field activity. Your CRM stays focused on pipeline.

The fastest way for a sales tool to lose its rep audience is to start duplicating their CRM. Voze deliberately stops at the edge of pipeline management. Here's exactly where the line is — so you know what to expect before you sign.

No deal or pipeline sync

Voze doesn't push or pull deals, opportunities, or stages.

Deal stages, forecasting, quote-to-cash — those stay in your CRM where they belong. Voze sends the signals that should inform pipeline (competitor pressure, expansion hints, at-risk flags), but the pipeline itself isn't ours to own.

No real-time, sub-second sync

Sync is fast — seconds to a few minutes — but not instant.

Zapier delivers in seconds to a few minutes depending on the trigger; native connectors sync continuously. If your use case needs sub-second latency (rare for field-sales workflows), Voze isn't the right fit for it yet.

No retroactive backfill

Sync starts the moment you turn it on.

We don't backfill old Voze data into a newly-connected system at connect time. If you need historical export, your team can pull a one-time CSV from Voze Web and upload it to the destination on your own schedule.

Task & follow-up sync — coming

Two-way task sync isn't shipped yet.

Voze creates tasks and follow-up reminders from voice notes, but they don't yet sync bidirectionally with your CRM's task system. On the roadmap; not in production. Until then, tasks live inside Voze.

The principle: Voze sends the signal. Your CRM owns the pipeline. Each system does what it's best at.
The integrations

Native, Zapier, or custom — whatever your stack needs.

The integrations Voze customers run most often, grouped by what they do. Native = click-to-connect from Voze Web. Zapier = self-serve via the Zapier library. Custom = our integrations team builds it if neither covers you.

Don't see yours? It's almost certainly in Zapier's library — and if not, our integrations team can usually build a custom connector.

FAQ

Questions your RevOps lead will ask.

How long does it actually take to connect HubSpot or Salesforce?
For HubSpot and Salesforce, about five minutes start to finish. Open Voze Web → Settings → Integrations, pick your CRM, sign in with the admin account, choose your filter rules (territory/team/rep), and turn the sync on. Data starts flowing within the first minute. The slowest step is usually deciding which records to push, not the technical connection.
What about our DMS — Karmak, Procede, MaddenCo, CDK?
Each of these connects through Zapier today (most of them have official Zapier apps, the rest have community apps that work reliably). For higher-volume accounts, our integrations team can build a native connector — it's typically a few weeks of work and we coordinate the spec with your IT lead. If you need DMS-specific data flowing into Voze on day one, we'll plan that during onboarding.
Does our IT team need to be involved?
Usually not. The native HubSpot/Salesforce setup is admin-level click-through — no API keys to manage, no server-to-server config. Zapier setup is the same. The only time IT gets involved is if you want a custom connector built for a system we don't already support, or if your security team needs to review the data flow before you turn it on.
Can we filter what gets sent — by territory, team, or rep?
Yes. Every integration has filter rules so each connected system gets only the data it should. Common patterns: "push the Southeast territory's notes to HubSpot, but route Northwest to a separate environment," or "send only notes flagged with At-Risk signals to the manager dashboard in Slack." Filters are set in Voze Web for native integrations and in Zapier for everything else.
What's the data direction — does Voze read from our CRM too?
Both directions. Voze pushes new companies, contacts, and notes outbound, and pulls customer details, contact updates, and territory assignments inbound. The point is that your reps see the latest CRM context on day one without you doing a manual import — and your CRM stays current with what reps capture in the field.
What if we already have a sales intelligence tool — does Voze conflict?
No. Voze sits upstream of CRM activity (rep voice → structured field data), not in the same lane as sales intelligence platforms that score leads or research accounts. We routinely run alongside Apollo, ZoomInfo, sales-i, Gong, and similar tools — they enrich the account, we capture what happens at the visit.
Where do we read the security and data handling details?
SOC 2 controls, SSO via your identity provider, US data residency, encryption in transit and at rest, role-based access at account/territory/rep levels. We'll share the full security packet during the technical review portion of your evaluation — and our standard responses cover about 80% of the typical security questionnaire before your team has to fill anything out.
Integrations · Demo

See it sync. Five minutes, no IT ticket.

A 30-minute demo with a live connection to your stack — HubSpot, Salesforce, or whichever DMS, ERP, calendar, or comms tool you need to see talking to Voze. We'll bring the technical lead if you want one in the room.

No credit card · 30-min call · We come prepared