Does this work with the tools we already use for email?

The pattern needs an authorized way to read the thread and record a draft. Any system that exposes that can carry it; the audit confirms whether yours does and what is in scope.

What happens when a reply does not match any category?

It is held and goes to a person. No default branch runs, and a new category exists only once somebody writes it down.

What happens next depends on who read the message and when

Today

Your rules exist, in somebody's head

The reply lands while the owner is in a call, and it sits.
Your rules for what comes next exist, in somebody's head, so what actually happens depends on who read the message and when.
The follow-up that eventually goes out reads as though the last reply never arrived.
Afterwards nobody can say why that step was the one taken.

With agents

The written rules run, and everything stops before it leaves

The next step follows the reply rather than the calendar.
The owner sends rather than composes.
A disputed sequence can be inspected.

How an agent runs it

The rules already exist; they are simply not written anywhere a process can use. The workflow runs on the ones you write down and stops at the point where something would leave.

Reads

Takes the replies on the threads you authorize, so the trigger is the reply rather than a timer.

Classifies

Puts each reply against the categories you have written down, and says which category it matched.

Selects

Applies your own sequence rules to pick the next step for that category, rather than inventing one.

Prepares

Drafts the message for that step with the thread and the record attached, so the owner is reading in context.

Human gate

Nothing is sent and nothing is scheduled to send. Every draft goes to its owner to send, change or discard, a reply the rules cannot classify goes to a person rather than to a default branch, and the whole sequence can be run by hand at any point because the rules and the threads are yours.

Holds

Keeps anything the rules cannot classify out of the flow entirely, rather than guessing a branch.

Records

Keeps which rule selected which step, so a disputed sequence can be inspected rather than argued.

Results

What changes when the rules are written down

The step follows the reply

The trigger is a classified reply, matched against the categories you wrote down.

Send rather than compose

The draft for the selected step arrives with the thread and the record attached.

A disputed sequence is inspectable

The rule that selected the step is kept with the draft.

Where this fits

Workflow / Automate a Workflow

Tier 1 through the Automate a Workflow door: one process end to end, from a reply to a draft a person sends. The boundary is the send. The rules are yours and the send is a person's, every time. It extends toward The sales ops coordinator as an AI Employee as a possible next step rather than a promised state. How It Works shows how the gates and the authorizations are built.

Tier 1 / Prove

How It Works

Questions, answered

No. It prepares the draft and a person sends. Nothing is scheduled to send, no customer is contacted by the workflow, and the gate is closed by default. The rules and the threads stay in your systems, so the sequence can be run by hand at any point without the agent.

AI Opportunity Audit

See which of last week's replies your rules already answer

Bring the last week of replies and see which of them your written rules already answer.

Book an audit