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.
How does a call become an action?
- 01
The call happens. Inbound or outbound, the agent works through the conversation and its business rules.
- 02
The outcome is captured. Disposition, the fields your workflow needs, a summary and the transcript.
- 03
Your systems are updated. Webhooks fire, the API is called or the CRM connector writes the record.
- 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.
What connects to Xebit today?
| Category | What connects | How |
|---|---|---|
| CRM | Zoho, Salesforce | Integrations connector |
| Telephony | Any carrier or SBC | Standard SIP, WebSocket, RTP |
| Models, speech to speech | Gemini ecosystem | Default pipeline |
| Models, cascade | Your own speech to text and text to speech | Bring your own components |
| Deployment | Docker, Kubernetes | Same artefact as our cloud |
| Agent handoff | Live transfer to a human agent | In the call flow, both offerings |
What connects through the API?
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.
What does the developer surface include?
- 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?
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.
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.