# Escalating a complaint, end to end

A complaint is handled as a case rather than as a message. Connect acknowledges it in the conversation, opens a support case against the person, puts it in front of somebody with the conversation attached, and schedules a follow-up that carries its reason. What it does not do is agree a remedy, a refund or a timescale the business has not authorised.

- **Status:** Available
- **Audience:** both
- **In the app:** #/needs-you, #/relationships, #/follow-ups
- **Last verified:** 2026-09-10
- **Canonical:** https://connectbyjbrh.com/docs/workflows/complaint-escalation/

## How a complaint is recognised

There is no complaint button for a customer to press, so recognition is part of classifying the message. The signals are ordinary: dissatisfaction stated directly, a second message about an unresolved problem, an escalation in tone across a thread, a reference to a commitment that was not kept, or an explicit threat to leave, review or report.

Recognition is deliberately generous. Treating an irritated message as a case costs a person one glance; missing a real complaint costs the relationship. Where the classification is wrong, closing the case is one action and the record of it stays on the timeline.

## Detection to resolution, stage by stage

1. Trigger — a message, a call or a chat that carries dissatisfaction, whether or not the word complaint appears.
2. User event — the customer's own words arrive on their usual channel. Nothing asks them to repeat it somewhere else.
3. Authentication and workspace resolution — the conversation is already inside its workspace; the case inherits it.
4. Ingest — the message is on the record before the classification, so the original wording survives however it is later summarised.
5. Canonical record — a support case is opened against the Person, linked to the conversation rather than copied out of it.
6. Classification — severity and subject. A commitment that was broken is different from a product problem, and they reach different people in most businesses.
7. Knowledge, memory and rules — what the business has said about remedies, plus any standing instruction for this contact or channel.
8. Autonomy and approval — the reply that acknowledges is subject to the channel's rule like any other. Anything that would settle the complaint is a person's decision.
9. Action — acknowledge in the conversation, open the case, queue it, and schedule the follow-up.
10. Result — the customer has an answer that does not pretend to resolve, and the business has a record it cannot lose.
11. Relationship, timeline and memory — the case sits on the person's history, so the next conversation begins with it rather than discovering it.
12. Audit, usage and Needs You — the escalation, the reason and any refusal are recorded, and the item is ranked in the queue rather than filed chronologically.

## What is said, and what is withheld

| Connect does | Connect does not |
|---|---|
| Acknowledge the specific problem in the customer's own terms | Restate it as something milder |
| Confirm that a person is picking it up | Name a person who has not agreed to own it |
| Give a next step that exists as a scheduled follow-up | Promise a time nobody committed to |
| Answer factual questions grounded in knowledge | Offer a refund, credit, discount or remedy the business has not authorised |
| Record the complaint whatever the outcome | Close the case because the reply was polite |

> **Note** The refusal to settle is the same rule that stops a price being invented. A remedy offered by something speaking in the business's name is a commitment the business then has to honour or withdraw, and withdrawing one during a complaint makes the complaint worse.

## Who it reaches, and how fast

- Needs You holds it as a ranked item, not a chronological one — an escalating complaint outranks a routine approval that arrived earlier.
- The support case carries the whole conversation, so the person picking it up reads what the customer wrote rather than a summary of it.
- A follow-up on the task channel represents the human work. No drain ever sends a task, so it cannot turn into an unintended message.
- The person's timeline shows every earlier exchange, which is usually where the reason for the complaint is visible.
- If the complaint arrived by phone, the call, its transcript and its summary are all attached to the same person.

How fast it reaches somebody is a property of the workspace, not of Connect: the queue is immediate, and the response time is whatever the business's own working pattern makes it. Documenting an escalation target and honouring it is the business's decision to make and record.

## Follow-through, and how it fails

**The case is resolved but the customer was never told** — Resolution is a state change, not a message. Closing a case does not write to the customer; that reply is a deliberate act.
**Two people work the same complaint** — Both see the same case rather than two copies, which is the point of the record living on the person rather than in a mailbox.
**The complaint arrives on a second channel** — Identity resolution attaches it to the same person, so a customer who phones after emailing does not become a second, unrelated problem.
**A commitment made during the complaint is forgotten** — Only if it was never scheduled. A follow-up carries a reason precisely so the person who inherits it knows what was promised and why.
**The complaint is about Connect itself** — It is still a case, and the operational side of it — a line, a mailbox, a failed send — usually already has its own entry in the queue.

## Questions

### Will Connect apologise on the business's behalf?

It acknowledges and takes the complaint seriously in plain language. What it avoids is admitting fault or liability the business has not established, because that is a statement with consequences beyond the conversation. The person who owns the case decides what is conceded.

### Can a complaint be escalated automatically to a specific person?

Routing is expressed as the workspace's own instruction rather than as a fixed rule inside Connect. What is fixed is that the case exists, carries its conversation, and is visible in the queue until somebody deals with it.

### Does a complaint stop other automation for that customer?

It does not stop everything by default, which surprises some workspaces. If you want outreach suspended for somebody with an open complaint, express that as a standing instruction or a block — a block is a memory row that holds across channels and future conversations rather than a per-thread flag.

## Related

- [Support in Connect](https://connectbyjbrh.com/docs/support/)
- [Relationships in Connect](https://connectbyjbrh.com/docs/relationships/)
- [Follow-ups in Connect](https://connectbyjbrh.com/docs/follow-ups/)
- [Handling a request Connect cannot fulfil](https://connectbyjbrh.com/docs/workflows/out-of-scope-request/)
- [Communicating during an interruption](https://connectbyjbrh.com/docs/workflows/service-interruption/)
- [Relationship memory versus chat history](https://connectbyjbrh.com/research/relationship-memory/)

## What this page is based on

- Connect source pack §5 — Needs You is ranked, and a refusal is recorded as a decision (`docs-source/sources/GENERAL.md`)
- Connect source pack §5 — cases, `open_case` and the relationship record (`docs-source/sources/CHANNELS.md`)
- Connect source pack §7 — follow-ups carry a reason; the task channel is never sent (`docs-source/sources/CHANNELS.md`)