AI Workforce & Assistance
Customer service agent: answers, actions, and a clean handoff
The questions are simple. The answers are in your systems.
When's the technician coming? Did my payment go through? Can we do Friday instead? Each takes a minute to answer, if someone has the scheduling and billing screens open. A website chatbot can see neither, so it apologises and gives out the phone number.
A customer service agent is connected to those systems. Once it knows who it's talking to, it answers from their records and your approved articles, takes the routine actions you've allowed, and passes anything about money, safety or feelings to a person.
Today, and with the agent
Today
- 01Customers call or email about arrival times, invoices and rescheduling.
- 02The office answers between other work; after hours, nobody does.
- 03The website chatbot answers general questions and gives out the phone number for everything else.
- 04A reschedule means a call back, a look at the calendar and a confirmation.
Simple questions wait as long as hard ones, and the office spends its day on them.
With the agent
- 01Customers ask in chat or by text, at any hour.
- 02The agent checks who they are, then answers from their own jobs, invoices and your approved articles.
- 03Routine actions, like moving an appointment, happen within your rules and are confirmed by text.
- 04Money, complaints, safety and anything it can't find go to a person with the conversation attached.
The office handles what needs a person. The rest is done, and on the record.
What it may do, decided first
Does on its own
- Answers from approved articles and the customer's own jobs, invoices and appointments
- Checks who's asking, with a code to the number on file
- Moves an appointment within your rules
- Resends an invoice or receipt
- Books a maintenance visit into open slots
Hands to a person
- Refunds, credits and disputes
- Complaints and unhappy customers
- Anything it can't find in the sources
- Anyone it can't verify who asks about an account
Never
- ✕ Handles a gas smell, flooding or anything unsafe. It gives the emergency line at once
- ✕ Changes prices or offers discounts
- ✕ Diagnoses faults or gives repair instructions
- ✕ Shares one customer's details with another
One conversation, and the record it leaves
Chat · M.D.
Conversation record · CS-5512
- Customer
- M.D. · 555-0148, not yet verified
- Verified
- —
- Job
- —
- Action
- —
- Handoff
- —
- Summary
- —
Turn 1 of 8: When's my technician coming tomorrow?
When a person takes over
01
Safety
At once, every time
A gas smell, flooding, no heat for someone vulnerable. It gives the emergency line and alerts the on-call person. It never tries to help with the problem itself.
safety words in the middle of an ordinary question.
02
Money
Refunds, credits, disputes
It collects the details and hands them over. It never promises an outcome.
“can you just take something off?”
03
Feelings
Unhappy or upset
Complaints go to a person with the whole conversation attached, so nobody asks the customer to start again.
politeness that hides a complaint.
04
The unknown
Not in the sources
If the answer isn't in your articles or the customer's records, it says so and passes the question on.
questions that sound routine but aren't covered.
The parts it's built from
Answer
LLM Application Development · Retrieval-Augmented Generation (RAG)
From approved articles and the customer's own records.
Act
- verified customer
- the rule for this action
- open slots
rule not met → offer options or hand to a person
What changes from one business to the next
A common starting point is a hosted language model with tool calling, your existing scheduling and billing systems, Twilio for text messages, and Langfuse for tracing and test cases. These are starting candidates, not requirements.
Is a customer service agent the right system?
Good fit
- Many customer questions are about their own appointments, invoices and jobs.
- Some actions are routine and have clear rules, like rescheduling.
- Someone will own the handoffs and read the conversations.
Avoid when
- Most contacts are complaints or judgement calls. A person is the better first answer.
- Your scheduling or billing system can't be connected.
- You want it to diagnose problems or give repair advice.
How we'd approach it
01
Understand
As much as the problem needs
We map how the work runs today: who does what, which systems hold the records, and where it breaks.
02
Design
Decided before it's built
Ownership, rules, integrations and exceptions, agreed with you and written down with acceptance criteria.
03
Build
Connected to what you use
We build the scoped system, connect it to the tools you already run, and test it on the cases that matter.
Questions about customer service agents
Will customers know they're talking to AI?
Yes. It says so at the start, and anyone can ask for a person at any point.
What if it gets something wrong?
Its actions are limited to ones with clear rules, every conversation is recorded, and answers your team flags become test cases for the next version.
Can it see every customer's account?
Only the account of the customer it has verified, and only the records it needs to answer.
What happens after hours?
It keeps answering and acting within its rules. Handoffs wait for the morning, except safety issues, which go to the on-call person at once.
Answer customers from their own records
Tell us which questions customers ask most. We'll show you which ones an agent could answer and act on safely.