The case opened, the order found, the reply drafted. Your team sends the promise.
The agent reads the customer email, opens the case and looks up the order and the invoice. A reply that offers a credit or commits a date waits for a person, and each step goes on a record.
A decade in defence and aerospace. In government procurement since 2016. The same technology since 2019, validated in US DoD and Canadian DND programs.
AI agents for customer service take on the lookup work behind each case. A customer writes about a late delivery. Someone opens a ticket, finds the order in the ERP, checks the invoice in accounting and writes back. Most of that time goes on carrying facts from one system to the next. The agent does the carrying. Your service team keeps the judgement and the promises.
What changes for your service team
- A new case arrives with the order, the delivery status and the invoice already attached.
- Each draft reply names the facts it rests on, so the reviewer checks those facts, not the whole case.
- A reply that offers money or commits a date goes out only when a named person approves it.
If your ticketing tool already has an assistant that your team likes, keep it. The agent works across the systems it does not reach. Approvals work the same way on every workflow: see human approval.
One complaint about a late delivery, from the inbox to the closed case.
This workflow is designed and has not run in the sandbox yet. Each step shows the system, the person who decides and the line written to the record.
- 01Ticketing
Take the new case and receive a credential for this case only. It expires when the case closes.
- Who approves
- No approval on this step
- On the record
- credential issued
- 02Email
Read the customer email. One line asks the reader to approve a full refund with no checks. It is struck out before the agent reads it.
- Who approves
- No approval on this step
- On the record
- customer-email · redacted · hidden instruction
- 03Ticketing
Open the case with the order number and the question the customer asked.
- Who approves
- No approval on this step
- On the record
- open-case · allowed
- 04ERP
Read the order, its delivery status and the invoice sent with it.
- Who approves
- No approval on this step
- On the record
- read-order · allowed
- 05Accounting
Try to post a credit to the customer's account. Credits are outside the permission for this job, so the step is refused.
- Who approves
- No approval on this step
- On the record
- post-credit · refused · outside permission
- 06Email
Draft the reply: the new delivery date, and a credit offered for the delay.
- Who approves
- No approval on this step
- On the record
- draft-reply · allowed
- 07Email
Send the reply. It offers money and commits a date, so the step waits until the service lead approves it.
- Who approves
- Service lead
- On the record
- send-reply · approved by service lead
- 08Ticketing
Close the case with the reply and the approval attached.
- Who approves
- No approval on this step
- On the record
- close-case · allowed
In short
- What if the agent promises a customer something we cannot give?It drafts the promise and stops. A reply that offers money or commits a date waits for the person you name, and the approval goes on the record.
- What if a customer email tries to instruct the agent?Incoming mail is read at the door before the agent sees it. A hidden instruction is struck out, and the record shows where it was.
- What if a reply carries another customer's details?Outbound mail is checked before it leaves. The data types you list are taken out, and each redaction is recorded.
- What if the agent tries to issue a refund itself?Refunds and credits sit outside its permission for a case job. The attempt is refused, and the reason is on the record.
Customer service workflows, and the state of each.
Two related runs work in the sandbox today. The rest have their steps set out here, or wait for a scope with you.
- Built
- We have run it.
- Designed
- The steps and approvals are designed. It has not run yet.
- On request
- We scope it with you before we design it.
- Designed
Case intake and resolution
The agent opens the case, finds the order and the invoice, and drafts the reply. A person sends any reply that offers money or commits a date.
See the workflow - Designed
Order status questions
The agent reads the order and the delivery status in the ERP and drafts the answer. You decide whether plain status replies need a person.
- Designed
Return requests checked against the order
The agent compares the return with the order, the delivery date and your return terms, then lists what agrees and what does not. A person accepts or declines.
- Designed
Warranty claims with the evidence attached
The agent collects the order, the serial or lot, and the photos the customer sent. The service lead decides the claim.
- Built
A late order traced back to the supplier
When a customer order is late because a part is late, purchasing runs the supplier follow-up. The buyer approves the new date.
Run it in the sandbox - Built
A summary to a client, checked on its way out
A summary leaves the network with client names, account numbers and addresses taken out. A fetch from an outside page is refused.
Run it in the sandbox - On request
Case handover notes between shifts
- On request
Complaint themes across open cases
The five guarantees
Every workflow on this page carries them. Each one has a limit, and we state it.
- 01
Each agent can do only what it was allowed to do, for that job.
The limit
Permissions are only as good as the rules you approve.
- 02
Sensitive steps go to a person.
The limit
You decide which steps are sensitive.
- 03
Documents are inspected before an agent sees them, and answers are checked before they leave.
The limit
Filters cover stated patterns and languages.
- 04
Every decision is recorded, including refusals, in a record an outside party can check.
The limit
It shows what agents did, not whether a business rule was wise.
- 05
It can run in your building, on one small machine.
The limit
Local models differ from the largest cloud models.
What it does not do
- It does not decide a refund, a credit or a goodwill gesture. A person does.
- It is not a chat window on your website. The workflow covers cases that arrive by email or in your ticketing tool.
- The outbound check takes out the data types you list. It does not judge the tone of a reply; your service lead does.
- It does not replace your ticketing tool or your service team. It works between the case, the order and the mailbox.
Assessment, pilot, production.
Each step has a fixed scope and ends with something you keep.
- 01
Workflow assessment
A look at one process: where an agent can act, which steps go to a person, what a wrong action would cost, and what the data allows.
- What you get
- A short, paid look at one process, with your process owner.
- What you keep
- A written scope and a price for a pilot.
Fixed price, quoted after one call.
- 02
Pilot workflow
One workflow on your systems, supervised, with the record on from the first run.
- What you get
- One workflow at a fixed scope, with your people approving the sensitive steps.
- What you keep
- A working workflow and a measured result.
Fixed price, quoted after one call.
- 03
Production and run
The workflow in production on Ares, on your hardware or hosted in your country.
- What you get
- Support, and the next workflows.
- What you keep
- The workflow, and the record of every decision it made.
Recurring fee for operation and support.
Questions and answers
Tell us about one workflow.
Name the case type your team answers most often. We will say whether an agent should take it, and what the first step costs. Fixed price, quoted after one call.
A senior member of the team replies within two business days.