A customer case read, checked and routed before anyone opens it.
The agent reads the message, finds the order behind it and puts the case in the right queue with a draft reply. Your service lead decides what you offer the customer.
DesignedThe steps and approvals are designed. It has not run yet.
A decade in defence and aerospace. In government procurement since 2016. The same technology since 2019, validated in US DoD and Canadian DND programs.
An AI agent for customer case intake does the first pass on every case: reading the message, finding the order, deciding which queue it belongs to and drafting a first answer. That pass repeats on every case, and it sits across the mailbox, the ticketing tool and the ERP. The agent does that pass. Your service team keeps the promise to the customer.
This workflow is designed. The steps below are how we build it in a pilot. It has not run in the sandbox yet.
What a person still decides
- What you offer the customer: a replacement, a credit, a visit or a no.
- Which categories of case the agent may route without review.
- When a case leaves intake and goes to a named owner.
The rest of the library is on the workflows page. The guarantees say what each control covers and where it stops.
One damaged delivery, from the inbox to the right queue.
The case, the order and the customer are examples. Each step names the system, who approves and the line written to the record.
- 01Ticketing
Take the new case from the service queue and receive a credential for this case only. It expires when intake ends.
- Who approves
- No approval on this step
- On the record
- credential issued · one case
- 02Email
Read the customer message and its attachments. They are read at the door before the agent sees them.
- Who approves
- No approval on this step
- On the record
- read-case · allowed
- 03ERP
Find the order, the delivery date and the items shipped for this customer.
- Who approves
- No approval on this step
- On the record
- read-order · allowed
- 04Ticketing
Set the category and the priority, then move the case to the deliveries queue with a summary.
- Who approves
- No approval on this step
- On the record
- route-case · allowed
- 05Accounting
Issue the refund the customer asks for. This job may read the account but never move money, so the step is refused.
- Who approves
- No approval on this step
- On the record
- issue-refund · refused · no payment rights in intake
- 06Documents
Draft a reply that offers a replacement, from your approved reply text.
- Who approves
- No approval on this step
- On the record
- draft-reply · allowed
- 07Email
Send the reply that commits to the replacement. The step waits until the service lead approves it.
- Who approves
- Service lead
- On the record
- send-reply · approved by service lead
- 08Ticketing
Close intake. The case stays open with its owner. The credential stops working.
- Who approves
- No approval on this step
- On the record
- intake complete · credential closed
The systems, by type
We name systems by type. Yours are named in the assessment.
The service mailbox. Cases arrive here, and the approved reply leaves from here.
Ticketing
Holds the case, its category, its priority and its queue. The agent sets all four.
ERP
Answers what was ordered, what shipped and when. The agent reads it and changes nothing.
Accounting
Holds the account and its payments. Intake may look, never pay.
Documents
Your approved reply text and service terms. The draft is built from them.
The approval, the refusal, the record
- A person approves: Send the reply that commits to the replacement. The step waits until the service lead approves it.A reply that offers a replacement is a commitment the customer will hold you to, so the service lead approves it before it is sent.
- Refused: Issue the refund the customer asks for. This job may read the account but never move money, so the step is refused.A refund moves money out of the business, and intake has rights to read the account, not to pay from it.
- On the recordThe case as received, the order read, the route chosen, the refused refund with its reason, and the reply with the name of the person who approved it.
What goes on the record
- credential issued · one case
- read-case · allowed
- read-order · allowed
- route-case · allowed
- draft-reply · allowed
- send-reply · approved by service lead
- intake complete · credential closed
One record per step, as designed. This workflow has not run yet.
What it does not do
- It does not decide what the customer gets. Your service lead does.
- It does not answer calls or chat. It works on cases that arrive in writing.
- It does not resolve the case. It hands a sorted, checked case to the person who owns it.
Questions and answers
Tell us about one workflow.
We will say whether an agent should do it, and what the first step costs.
A senior member of the team replies within two business days.