Glossary

Escalation

Escalation is where automation either proves its value or destroys it, depending entirely on what travels with the customer.

Start freeNo credit card. 2 minute setup.

Why it matters

If the customer repeats themselves to the first human, everything the assistant did was wasted and the interaction is now longer than if they had emailed directly. One such experience teaches people to bypass the bot forever.

  • Customers re-explaining their question to an agent
  • Agents receiving a name with no conversation
  • Escalations landing where nobody is watching

What must travel with it

The full transcript, any contact detail collected, and the page the visitor was on. The transcript is the load-bearing part — it is the difference between an agent replying and an agent interviewing.

When to escalate

On a refusal, and immediately on explicit request. Making a customer argue with a bot to reach a person is the single most reliable way to make them resent both.

Escalation and availability

Offering a live person when nobody is online creates a promise you break. Availability-aware handover offers live chat during hours and captures contact details outside them.

Common questions

Should a bot try once before escalating?
For a genuine question, yes. For an explicit request to speak to someone, no — attempting to deflect that is what makes people distrust the whole system.
Where should escalations go?
Wherever someone will actually see them inside your target response time. That is usually Slack for teams that live there, and a helpdesk where one already exists.

From the blog

All posts

Answer honestly. Capture the rest.

Point Matter Chat at your site and see what it can — and can't — answer. It's honest about both.

Start free — chat in your site

No credit card. 2 minute setup.

Every answer cites the source it came from. When there isn't one, it says so — and hands the visitor to you.

Installs on the tools you already run.