ScaileAI  /  Call library  /  BPO & contact centers

BPO & contact centers · written example

Out of scope, six-second handoff

Handling time 0:44 · Human intervention: Specialist received the warm handoff · Illustrative transcript, written to spec

What happens when a contact falls outside what the AI is allowed to handle?

It hands over immediately, with context. The agent identified this request as out of scope eleven seconds in and told the customer plainly that a specialist was needed, rather than attempting a partial answer. It transferred within six seconds, carrying a structured summary. The customer explained nothing twice and the SLA clock was never at risk.

ScenarioMember services contact that opened as a billing query and immediately exceeded tier-0 scope: three disputed charges plus a compensation request.
ObjectiveRecognize the boundary fast, hand over without friction, and carry the context across.
OutcomeEscalated — context preserved
Handling time0:44
Human interventionSpecialist received the warm handoff
Action takenOut-of-scope request identified in 11 seconds and transferred in 6, with a structured summary attached
Data capturedIntent, scope decision and reason code, summary generated, transfer target and elapsed time
Written toGenesys — escalated with the summary attached, reason code: out of scope.

Transcript

The whole call, unedited.

ScaileAIThanks for calling member services. What can I do for you?

CallerI'm disputing three charges and I want compensation for the trouble.

ScaileAIThat needs one of our specialists rather than me, and I don't want to waste your time trying. I'm passing you over now with everything you've told me.

CallerSo I don't have to explain it again?

ScaileAIYou don't. They'll have the three charges and your request in front of them when they pick up.

What ScaileAI did

Six things happened on this call.

  • Identified the request as out of scope in eleven seconds.
  • Said so honestly rather than attempting a partial answer to look useful.
  • Named the reason, not wanting to waste the customer's time, instead of citing a policy.
  • Transferred in six seconds, which is inside the abandonment window rather than testing it.
  • Attached a structured summary of the three charges and the compensation request.
  • Promised the customer they would not repeat themselves, and was right.

Why it matters

The commercial consequence.

This is the call a BPO evaluates before it will put AI in front of a client’s customers, and containment rate is not the number that decides it. The risk in front-line automation is rarely the contact it cannot handle. It is the time burned before admitting that, because a failed AI attempt followed by a queue is worse than no AI at all. Eleven seconds to recognize and six to transfer is the difference between AI improving the program and AI becoming the thing the client escalates about. The summary is what makes the handoff commercially real. Without it the specialist restarts the contact, and the automation has added handling time rather than removed it.

Keep reading

BPO & contact centersSee the industry page → Every published callOpen the call library → Call a live agent yourselfTry to break it →

Hear one of these on your own call flow.

We measure your baseline before we touch a call.

Talk to an Expert Call a live line