Platform · The handover

The handover is the product.

The AI runs the call until it needs a person. The person arrives with the summary, the intent and the next action already on screen, in seconds, and the customer never repeats themselves. No hold, no re-verification, no second screen to hunt through.

Book a demo →
What the agent sees, in order

Five things land on the screen before the agent says hello.

Summary, intent, suggested action, a masked identity, and a wrap-up already drafting. Watch the console assemble as the call moves from the AI to a person.

AI leg · Hindi + EnglishHandoverYour agent · already briefedHold 0:00
Customer · collections callwith the AI
RK
Caller · verified by account+91 98··· ···12
1:08on the call
HindiEnglish12 more

Customer

AI

Dispute detectedRouting · collections specialistContext packed

Agent · first sentence

Customer

Agent consoleReady · next in line
Queue · my groupsCalls land here the moment the AI hands over.
Before youAI leg · verified by account
DisputeRs 500 late fee; auto-debit failed on bank side
Amount dueRs 8,450 EMI, due 30 Oct
IntentWill pay today once the fee is waived
SuggestedWaive Rs 500 as one-time; send UPI link

"Could you confirm your account number again?"not asked

Wrap-up drafted by AI · 7 of 7 fieldsDisposition · promise to pay · waiver Rs 500 · link sent
0.0s
When it hands over

Four triggers, all of them rules you set.

Asks for a person

"I want to speak to someone." The AI stops selling and starts handing over, politely, with the summary already packing.

Disputes a charge

A late fee, a penalty, a wrong bill. Money disputes go to a person with the authority to waive, not to a script.

Frustration or abuse

Negative sentiment or a raised voice triggers the transfer early, so the person inherits a customer, not a fight.

Edge of knowledge

When the question is outside the brief, the AI says so and routes, rather than inventing an answer.

Routing

Many bots, one floor. A call can change teams mid-call.

Three collections bots can land on one specialist group. A sales call can move to support when an existing customer raises a billing issue, context intact. When nobody is free, the rule you chose decides what happens next.

Bucket 2 call needs a person · routed to the collections groupAI agents · one brainAgent groups · by skillCollections · bucket 1Collections · bucket 2Collections · bucket 3Sales · lead qualificationSupport · billing and service3 bots · 1 groupCollections specialistsfree seatsSales repsfree seatsSupport specialistsfree seatsmid-call · context travelsgatecallbackback to the assistantqueue · announced wait
When no agent is free, the call:
Runs beside your dialler

Your desk stays. The handover costs nothing.

Your side

Your dialler and trunk

Genesys, Cisco, Ozonetel or your own SIP. The AI agent takes the call where it already lands; a one-time dialler integration connects them.

call in
Oriserve

AI agent and handover

Runs the call, decides the moment, packs the summary. Handing the call to a person is free, on our console or on yours.

summary out
Your side

Your agent and CRM

Summary by webhook to your console; customer lookup, call context and disposition pushed to your CRM on handover.

Agents work in our console during calibration if you want transcripts and wrap-up on the human leg; CRM-embedded views arrive with the integration. We say which one you will have, before you sign.
Who sees what

Context travels. Identifiers do not have to.

The agent gets intent, history and the next action. Account and mobile numbers can be masked and shown by customer ID. Your policy decides the mask; the console enforces it on every handover.

  • Summary and intent on screen before the agent speaks
  • Verification carried from the AI leg, no re-authentication
  • Identifiers masked by policy, customer ID in the clear
  • AI leg recorded and transcribed; human leg too on Vox Agent Desktop
  • Every handover logged with the trigger that caused it
  • Transfers grouped so you can see what the AI should learn next
Questions buyers ask
Can several AI agents route to one agent group?

Yes. Collections buckets 1, 2 and 3 can each run their own AI agent and all hand over to the same specialist group. Routing is by skill and rule, not by which bot the call came from.

Can a sales call move to a support specialist mid-call?

Yes. If an existing customer raises a service issue during a sales call, the call moves to the support group with the transcript and summary attached. The customer stays on the same call.

Does the customer have to verify again after the handover?

No. The AI leg's verification and every captured detail travel with the call. The agent opens holding the summary, so the customer is never asked to repeat the story.

What does the agent see of the customer's personal information?

What your policy allows. Account and mobile numbers can be masked on the agent screen and shown by customer ID. The summary carries intent and next action, not raw identifiers, unless you choose otherwise.

Do we have to replace our dialler or Genesys, Cisco or Ozonetel desk?

No. The AI agent can sit in front of the floor you already run: your dialler and trunk carry the call, the summary reaches your agent as a webhook, and the handover itself is free. Vox Agent Desktop is there when you want transcripts and wrap-up on the human leg too.

Can agents keep working in our CRM?

Yes. Customer and plan lookup, call context and disposition can be pushed into your CRM on handover. During calibration agents may work in our console; CRM-embedded views come with the integration.

What happens when every agent is busy?

You choose the rule: the call stays with the assistant, a callback is booked, or the caller waits in a queue and is told how long. Waits, announcements and hold music are configurable per group.

Is the transfer live, or a callback?

Live. The AI holds the line until a briefed person is on. Callback is one of the fallbacks when no agent is free, not the default.