Workflows & integrations

Every call ends in an action, in the systems you already run.

A call is only useful if something happens after it. Xebit turns each outcome into an action: a CRM record updated, a slot booked, a ticket opened or a person alerted. It sits inside the stack you already run rather than replacing it: your carrier over standard SIP and WebSocket, your CRM through our connector, and everything else through REST and webhooks.

Workflows

How does a call become an action?

The agent captures what was agreed during the conversation. The moment the call ends, that outcome drives whatever should happen next.
  1. 01

    The call happens. Inbound or outbound, the agent works through the conversation and its business rules.

  2. 02

    The outcome is captured. Disposition, the fields your workflow needs, a summary and the transcript.

  3. 03

    Your systems are updated. Webhooks fire, the API is called or the CRM connector writes the record.

  4. 04

    The next step starts. A booking is confirmed, a ticket opened, a follow up scheduled or a person alerted.

Collections

A promise to pay date and amount is written to the loan management system, and disputes go to a person.

Recruitment

Notice period, availability and consent land on the candidate record, and the recruiter gets the outcome.

Customer support

A ticket opens with the transcript attached, and the summary and next action go to the support team.

Tier 1

What connects to Xebit today?

Built, in production, nothing for you to write.
Integrations available today
CategoryWhat connectsHow
CRMZoho, SalesforceIntegrations connector
TelephonyAny carrier or SBCStandard SIP, WebSocket, RTP
Models, speech to speechGemini ecosystemDefault pipeline
Models, cascadeYour own speech to text and text to speechBring your own components
DeploymentDocker, KubernetesSame artefact as our cloud
Agent handoffLive transfer to a human agentIn the call flow, both offerings
Tier 2

What connects through the API?

These do not have a prebuilt connector yet. They connect through our REST API and webhooks, and because the orchestration layer is ours we build the hook into your system as part of deployment rather than asking you to work around a fixed product.

Ticketing and service desk

Create, update and resolve tickets from call outcomes.

Collections and loan management

Pull due dates and balances, write back promise to pay.

ATS and HR systems

Candidate records, screening outcomes, interview scheduling.

Calendars and scheduling

Book, reschedule and confirm from inside the call.

Data warehouse and BI

Stream call events, outcomes and transcripts to your warehouse.

Workflow automation

Trigger any downstream process from a call event via webhook.

Tier 3

What does the developer surface include?

What an engineer wants to see before believing any of the above.
  • Agent SDK: build and control agents
  • REST API: campaigns, calls, lists, outcomes, recordings, transcripts
  • Webhooks: call lifecycle events, outcomes, transfers
  • Streaming protocols: WebRTC, WebSocket, RTP over SIP, gRPC in production
  • Observability: per call and per node metrics, event logs, transcript replay
  • On the roadmap: AudioSocket, QUIC and MoQ

Does Xebit provide telephony?

We are not your telephony provider, and that is on purpose. You keep the carrier relationship, the trunks and the rates you have already negotiated. Xebit connects over standard SIP and WebSocket, so switching carrier later is a configuration change rather than a rebuild of your voice application. For an enterprise with an existing SBC and contracted rates, this is usually worth more than a bundled offer.

Workflows and integrations questions

How does Xebit update my CRM after a call?

Through the Zoho and Salesforce connector, or for any other system through webhooks that fire on call lifecycle events, outcomes and transfers and through the REST API. The outcome, the fields the agent captured, the summary and the transcript land on the right record as the call ends.

Can I trigger my own workflows from a call?

Yes. Webhooks fire on call lifecycle events, outcomes and transfers, so any endpoint you run can start a downstream process: open a ticket, book a slot, schedule a follow up or alert a person. Because the orchestration layer is ours, we build the hook into your system as part of deployment.

Does Xebit provide telephony?

No. Xebit never provides telephony or numbers. You keep your carrier, trunks and rates, and Xebit connects over standard SIP and WebSocket, so switching carrier later is a configuration change rather than a rebuild.

CONNECT YOUR STACK

Bring one workflow. We will wire it up.

Tell us the system a call outcome should land in and what should happen next. We will show it working on a live agent.