Feature · SLAtech Business

Escalation to a Human

An assistant is judged on the answer it should not have given. Deciding what it refuses is the configuration that matters most.

Your list
What it refuses
Whole thread
Not a summary
Said plainly
No vague attempt
Logged
Every refusal

Sound Familiar?

🎭

The confident wrong answer

Nothing else erodes trust as fast, and it is the one failure a satisfied-looking conversation log will not show you.

🕳️

Conversations that just stop

The assistant could not help, said something vague, and nobody was told. The enquiry is gone and no record says so.

📞

Escalation that loses the thread

Handed to a person as a name and a number, so the customer explains the whole thing again to someone starting from nothing.

What You Get

🛑

Refusal as a setting, not a surprise

The subjects it will not attempt are yours to list: safety, legal exposure, money, anything where being wrong costs more than being silent.

📨

The whole conversation, to you

Escalation sends the exchange, not a summary of it, so the person picking it up knows what was asked and what was already answered.

🧭

Said plainly to the customer

That it cannot answer, that a person will, and how to reach one now if it is urgent. A clear stop beats a vague attempt.

📑

A record of every refusal

What it refused and how often is a list worth reading: some entries are gaps in your material, and the rest are boundaries working as intended.

Frequently Asked Questions

What should it refuse to answer?
Anything where a wrong answer costs more than no answer. In practice that means safety, medical and legal judgement, money owed, disputes, and anything about a specific person's file. The list is short, it is specific to your business, and writing it is the hour that decides whether this works.
How do I know it is actually escalating?
By the record, not by the absence of complaints. Refusals and escalations are logged, so the question is answerable by reading them, and an escalation path nobody has looked at is an assumption rather than a feature.
Does it escalate when it is simply unsure?
That is the behaviour to aim for, and it is a tuning decision with a real cost either way. Escalate too readily and you have a slow forwarding service; too rarely and you get the confident wrong answer. Start cautious, read the log, and loosen it where the refusals were unnecessary.
Can it reach someone immediately, out of hours?
It sends the conversation immediately, but whether anyone reads it at two in the morning is your rota, not the assistant's. Where something genuinely cannot wait, the right answer is a phone number in the refusal message rather than a promise that a person is coming.

Related

Ready to Get Started?

Free tier. No credit card. Setup in 10 minutes.

Get started free