An agent that cannot reach your systems is a very expensive answering machine. There are two directions to wire up, and most deployments need both.

Agent reaches out

During the call, the agent calls your systems: logging a ticket, checking an order, booking a slot. These are actions.

Voho pushes to you

After a call, Voho notifies your systems with what happened, so downstream work starts without anyone watching a dashboard.

​
During the call

Actions are the integration surface that matters most. Each one calls a single endpoint in one of your systems, authenticated as a service account you control, and returns something the agent can say out loud. Design them for speech and for latency, a three-second lookup is three seconds of silence on the line. See Actions and Latency.

​
Webhooks

Voho can notify your systems when a call ends, so a completed conversation triggers whatever comes next: a CRM record, a ticket, a notification to a team channel, a follow-up task. This is what makes an agent part of an operation rather than a silo. The alternative, someone reading transcripts and re-keying them, undoes most of the value.

​
Transcripts and exports

Every call leaves a transcript and a bilingual summary. Those are available in the console for people, and through the API for systems that need to store, search, or report on them. Common destinations: a data warehouse for quality reporting, a CRM record attached to the customer, or an archive that satisfies a retention obligation. See Transcripts and summaries for what a record contains, and Security and data handling for what to settle about retention first.

​
Automation tools

Tools like n8n, Zapier, and Make connect through the same REST API and webhooks, no dedicated connector required. The typical shape is a loop: a webhook from Voho starts a workflow, the workflow updates a CRM or creates a ticket, and a step in that workflow can trigger an outbound call back to the customer.
A finished call fires a webhook into your automation tool, which routes on the outcome: a complaint opens a ticket, a qualified lead lands in the CRM, an emergency pages someone.
Your workflow calls the Voho API to place an outbound call: a reminder the day before an appointment, a callback after a form submission. See Telephony.
Push what the agent collected into the system of record, so the next person who talks to that customer sees it.

​
Speech on its own

If you already have a call platform and only need the voice, the Speech API is usable independently: HTTP, streaming, and WebSocket, with telephony-ready output.

API reference

Authentication, endpoints, errors, and limits.

Streaming

First audio in ~200 ms instead of ~1.7 s.