Integrations
Your agent has to write into the system you already run
A voice agent that cannot see the customer record is a voicemail box with better manners. Connecting one to your CRM or your ERP is not a toggle you flip. It is an HTTP request made while somebody waits on the line, and every system has one rule that decides how it has to be built.
Systems
What each one costs you in design
Three we get asked about most. The pattern generalises to anything with an API.
HubSpot
Caller lookup is a search call, and search is capped far lower than the rest of the API.
HubSpotERPAFAS Profit
The blocker is almost never code. It is that somebody has to publish a connector first.
AFAS ProfitERPExact Online
The token expires in ten minutes and you are not allowed to refresh it on demand.
Exact OnlineAPISomething elseSalesforce, Dynamics, Pipedrive, a scheduling tool, your own back office.
The tool contract does not care what sits behind your endpoint. If the system has an API and somebody can tell us its rate limits and its auth model, it can be wired the same way.
Tell us what you runHow a connection works
Four steps, and a deadline
The same mechanism carries every integration on this page. Learn it once and the per-system pages are only about what makes each one awkward.
The agent decides it needs something
Mid-sentence, the model calls a tool you defined: look up this caller, check this slot, log this outcome. It is a normal function call, and the agent stays in the conversation while it runs.
We post to an endpoint you own
A signed request goes to your URL with the call context and the arguments. Your endpoint talks to HubSpot, AFAS or Exact with your credentials. Ours never touch them.
Thirty seconds, attempted once
A synchronous tool call waits up to thirty seconds and is tried exactly once. There is no retry, because a retry lands after the conversation has already moved on, and because several of these systems block a key that produces repeated errors.
The answer becomes something the agent can say
What you return is handed straight back to the model. If nothing arrives in time, the agent is told the lookup failed and says so out loud, rather than inventing an answer.
The connector runs on your side.
VoiceDock posts to an endpoint you own. Your CRM and ERP credentials stay in your own environment and are never stored on our platform. That is a deliberate limit: it means we cannot offer a one-click integration, and it also means a breach on our side cannot reach your customer records.
Self-serve and arranged
What you can build alone, and what we do together
Yours the moment you sign up
- Defining tools on an agent and pointing them at your own endpoint
- The REST API, the SDK and webhooks for call events
- Post-call analysis fields you can push into any system yourself
- Bringing your own provider keys
Scoped with us
- We build and operate the connector endpoint alongside your team
- Access to the compliance documentation behind the Trust Center
- On-premise or private-cloud deployment of the platform itself
- Invoicing instead of prepaid credit, a custom SLA, a security review
That split is not a paywall. Writing into somebody's ERP correctly means knowing which fields are mandatory in their configuration, and no dashboard can guess that.
Questions we get first
Do you have native integrations?
No, and we would rather say so plainly. There is no button that connects VoiceDock to HubSpot. What exists is a tool contract: your agent calls a tool, we post to an endpoint, and that endpoint talks to the system with your credentials. We build that endpoint with you, or you build it against our API.
Why not build native connectors like other platforms?
Because the connector is the easy half. Every real deployment we have seen needed field mapping specific to that customer's configuration, and a native connector that guesses wrong writes bad data into the system of record. We would rather do it correctly with you than quickly without you.
Who writes the endpoint?
Either side. Software companies embedding us usually write it themselves against the API. Mid-market customers usually want us to build and run it, which is the done-with-you model the company was set up for.
Does a lookup slow the call down?
It adds whatever your system takes to answer. A cached lookup is invisible. An uncached query against a slow ERP is audible, which is why reads that can be prepared ahead of the call are prepared ahead of the call, and writes are pushed to the background.
Tell us what you run
Bring the system, its API documentation and one call you want to automate. We will tell you on the call whether the awkward part is the code or the configuration.