Service agency: inbox triage with escalation

Case study · service agency (customer contact on behalf of clients)

Sort by what it is, escalate when it does not fit

Sort incoming email by question type, prepare drafts for recurring cases and forward anything unusual to a staff member with context.

Book an introduction

A row of small green blocks leads to one large green area; one small orange block is diverted upwards out of the row towards a separate dark green circle.

September 13, 2026Email

Evidence status

Status: not yet approved for publication. Results on this page are only included with the customer's approval.

Starting point

Where it began

The pattern described by this case: a shared mailbox receives daily questions that broadly fall into two groups. Recurring questions whose answer is in a source, and questions requiring judgment — an exception, complaint or issue spanning several clients. Sorting the two takes employees the first hours of the day, leaving the second group until last.

Approach

What we built

This type of workflow reads incoming messages, identifies the question type and retrieves relevant data from systems the employee may access. For recurring questions, it prepares a draft with its source, so the employee can check where the answer came from. For anything outside the categories, or when uncertain, it proposes nothing: the question goes to a person with the gathered context.

That second route is a full outcome, not merely exception handling. A question the workflow answers with “I don't know” reaches the right person sooner than if it had landed at the bottom of the pile.

Control

Where people stayed involved

Nothing goes out without human approval. The employee sees the proposed reply alongside its source, edits, approves or rejects it. The route to a person is visible to the sender, not hidden behind three failed attempts.

Rejected and edited proposals stay in the log. That log is the only basis for later deciding whether a category may be handled without intervention — and nothing changes until that evidence exists.

The underlying workflows are under inbox triage with human approval and handling customer questions with escalation; the design framework is under customer service with a human route. Other cases follow the same structure.

Result

What it achieved

This customer has not yet approved the measurable outcome for publication. Once that happens, the results will appear here.

Does this look like your process?

Bring it to a conversation. We assess whether the same approach fits and where the differences lie.