AI customer service agent
AI customer service agents, at the level you are ready for
Build an agent for each job. Start with answers from your knowledge base, add skills that work the ticket, and let it take real actions in your systems when you decide it should.
Three levels
"AI agent" means three different things
One answers questions. One works the ticket. One issues the refund. Each level includes the one below it and asks more of the company running it. Theymes does all three, and you choose the level agent by agent.
Read why we think about it this wayLevel 1
Answers
Reads your help center and documents
- Integrations
- Security
- Maturity
Read only
Level 2
Skills
Works the ticket: fields, notes, routing
- Integrations
- Security
- Maturity
Writes in the helpdesk
Level 3
Actions
Refunds, account changes, record updates
- Integrations
- Security
- Maturity
Reads and writes in your backend
To make the difference concrete, here is one customer message handled at each level: "I was charged twice for my subscription this month. Can I get a refund?"
Level 1 Answers
It answers from what you have already written
The agent reads your help center and the documents you give it, finds what applies and writes the answer in the customer's language. Most repeat questions end here, before a ticket exists.
What it takes A knowledge base worth reading. Theymes shows you the questions it could not answer, so you know which article to write next.
Level 2 Skills
It works the ticket the way your best triage person would
Give the agent a scenario and tell it what to do when it sees one. It recognizes what the customer wants, asks for the missing details, fills in the fields, writes a private note and routes the ticket to the right team.
What it takes Your routing rules, written down. If you can name the ten things customers ask for most, you can write the scenarios.
Level 3 Actions
It fixes the problem in your own systems
Connect the agent to billing, accounts or orders and it can look things up and make changes: issue a refund, restore a purchase, update a record. The customer's problem is gone and nobody on your team had to touch it.
What it takes An API the agent can reach, and a decision from you on what it may do: which actions, up to what amount, and when a human has to approve.
In practice
One agent per job, working three ways
An agent can close a conversation by itself, prepare it for a human, or work for your own agents inside a ticket. Pick a mode below to follow one conversation from start to finish.
AI agent
Purchase agent
Its job, in your words
“Help customers whose purchase is missing. Check the order, find out why, and walk them through the fix.”
Gets the ticket when
Issue type: PurchaseAny language
AI agent
Bug report agent
Its job, in your words
“When someone reports a bug, collect the device, the app version and what they did right before. Then pass it to the QA queue.”
Gets the ticket when
Issue type: BugAny mood
AI agent
Compensation agent
Its job, in your words
“When one of our agents asks, check what the customer lost and suggest compensation that follows our policy.”
Runs when
Started by your teamFrom any ticket
- One agent per job, described in your own words
- Theymes decides which conversations each agent takes
- See where every agent hands over, and what would fix it
Control
How far it goes is your decision
The models are capable enough. What matters is how much you trust software to act for you, and that answer is different for every company and every kind of request.
You write the job
Each agent has one job, described in plain language. You can read exactly what it has been told to do, and so can the person who takes over from you.
You set the limits
Decide which actions an agent may take, up to what amount and for which customers. Anything outside those limits goes to a human.
Your team sees what matters
Agents run separately from the ticket queue. Conversations they resolve never land on your team, and the ones they hand over arrive with the details collected.
You can see how to improve it
For every agent you see what it resolved, where it handed over and why. The gaps become your to-do list: an article to write, a rule to add, an instruction to change.
Before you start
What each level asks of you
Going from level 2 to level 3 turns a support project into a company project. It is better to know that before you begin.
| Level 1Answers | Level 2Skills | Level 3Actions | |
|---|---|---|---|
| Works with | Help center and documents | Plus ticket fields, notes and queues | Plus billing, accounts and backend records |
| Access | Reads content | Writes inside Theymes | Reads and writes in your backend |
| Setup | Connect a knowledge base | Describe scenarios and routing | An API integration per system |
| Worst case | A wrong answer | A misrouted ticket | A wrong refund or a changed record |
| Guardrails | Content quality and tone | Scenario rules and review | Identity checks, limits, approvals, audit log |
| Who's involved | Support | Support operations | Support, engineering, security and finance |
CX AI maturity assessment
Which level is your support organization ready for?
Ten questions, about two minutes. You get a score, the level you can run today and the three things to fix next. No email needed.
FAQ
Questions about AI agents
- What is an AI customer service agent?
- An AI customer service agent is software that handles a customer conversation by deciding what to do and then doing it. Depending on how far you let it go, it answers from your knowledge base, works the ticket by filling in fields and routing it, or takes real actions such as issuing a refund.
- What is the difference between an AI agent and a chatbot?
- A chatbot follows a script or retrieves an answer. An agent chooses between actions. The useful question to ask any vendor is what the agent can change. If the answer is nothing, it is a chatbot with better language skills, which can still be the right product for you.
- Which level should we start with?
- Start with answers. Every level builds on the one below, and an agent with poor knowledge will take the wrong action with confidence. Add skills once you know your top contact reasons, and add actions one at a time, beginning with something high in volume and low in risk.
- Can we run different agents at different levels?
- Yes. Each agent has its own job and its own permissions. You can let one agent issue small refunds on its own while another only collects details for your billing team.
- What happens when the agent cannot solve something?
- It hands the conversation to a human, with a summary and the details it has collected, and routes it to the right team. The customer does not have to repeat anything.
- Can our human agents use AI agents too?
- Yes. Your team can start an agent from inside a ticket, for example to check an account and suggest compensation that follows your policy. The human reviews the result and sends it.
- How are AI agents priced?
- Every Theymes plan includes a monthly allowance of AI answers, which covers questions resolved before a ticket is created. Agents that work inside the ticket are an add-on on every plan, sold as monthly conversation packages.
Find out which level your setup is ready for
Bring your top contact reasons. We'll show you which ones an agent can take today, and what the next level would need.