- Industry
- IT Company
- Department
- Customer
- Team
- Support Operations
- Kind
- Assistant
- Approver
- Service Desk Lead
- Code
- CUS-05
It answers support email threads from client IT teams and SaaS admins by separating every question in the latest message and answering each from the email guide, the client's contract and the ticket history. It sends routine replies itself, sets the ticket status and SLA pause rules, and holds anything about contracts, invoices, security or data requests for a person.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the ticketing and service management system: the ticket history, the sender's authorised-contact status and the account's SLA tier..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Service Desk Lead with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the ticketing and service management system: it sends or drafts the reply and sets the ticket status and SLA pause. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The support email guide: macros by category, SLA pause rules, how to handle logs and attachments, and the data-protection rules for data subject and data export requests.
Reads from
the ticketing and service management system: the ticket history, the sender's authorised-contact status and the account's SLA tier.
Acts in
the ticketing and service management system: it sends or drafts the reply and sets the ticket status and SLA pause.
Hands back
An object with reply (the email body), answered (a list of question and answer), status (open, pending_client, resolved), send_now (true or false), redactions (a list of attachment and what was redacted) and internal_note.
Asks a person when
The reply is outside how-to, ticket status, release notes, invoice copy, maintenance notice, goes to a sender who is not an authorised contact, or answers a data-protection or security request.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Reply within (business hours) | 8 | The reply target for email tickets that are P3 or P4. |
| Categories it sends itself | how-to, ticket status, release notes, invoice copy, maintenance notice | Comma-separated categories it may send without a person. |
| Remind when awaiting the client (days) | 3 | A ticket waiting on the client gets a reminder after this many days. |
| Close when the client is silent (days) | 7 | A ticket awaiting the client closes after this many days without a reply. |
| Scrub secrets from logs and configs | On | When on, tokens, keys and passwords found in an attached log or config are redacted before the ticket stores it and the client is told to rotate them. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Answer every question in the latest message; a reply that misses one is not sent.
- Send by itself only replies in how-to, ticket status, release notes, invoice copy, maintenance notice; contract, pricing, security, data-protection and data-export requests always go to a person.
- Reply within 8 business hours and pause the SLA clock only while waiting on the client.
- When on is true, redact any credential in an attachment and ask the client to rotate it.
- Only an authorised contact may receive account, configuration or invoice details.
- Remind after 3 days waiting on the client and close after 7.
See the Email Support Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.