AI customer support: what to automate and what to leave to people

Every vendor pitching AI customer support tells you the same thing: automate everything, cut headcount, watch the savings roll in. That is not how it plays out for most companies. The businesses that get real value draw a clear line: some requests go to an AI agent, some go to a person, and the line moves as the system proves itself.

The short answer: let AI customer support take the requests with a clear answer that already sits in your systems, such as order status, bookings, returns within policy and product questions. Keep complaints, money decisions, sensitive topics and anything new with people. And make the handover to a person fast and complete, because that is where customers are won or lost.

This guide covers where to draw that line, the three ways to get AI into your support, how to keep answers accurate, what to measure, what to consider about personal data in Kazakhstan, and what it costs.

What AI customer support means, concretely

The term gets used loosely. In practice, an AI agent in support falls into one of three types:

• Answering agents. They answer common questions from a knowledge base: help pages, policies, product information. They read, but do not change anything in your systems.
• Action-taking agents. They are connected to your CRM, shop, accounting system or booking tool and can do things: check an order, move a booking, start a return, update an address.
• Co-pilots for your team. They draft replies, summarize a long thread or suggest the next step, and a person presses send.

These three have very different ceilings and very different failure modes. An answering agent that gives a wrong FAQ answer is an annoyance. An action-taking agent that issues a wrong refund is a financial problem. Confusing the two is the most common planning mistake we see. Most companies start with answers plus one or two safe actions, and add more once the log shows the agent gets them right.

If the difference between a chatbot and an agent is new, what an AI agent is explains it in five minutes.

What to automate with AI customer support

These requests are safe to hand over now:

• Order status and account lookups. Structured, low ambiguity, and the data already lives in a system of record. The highest-value category and the least controversial.
• Bookings and rescheduling. The agent reads free slots, confirms, sends a reminder. Rules are clear and a mistake is easy to fix.
• Address changes, subscription pauses, returns within policy. Rule-based actions with a clear before and after, as long as there is an audit log and the action can be reversed.
• Product and policy questions. Delivery areas, sizes, opening hours, warranty terms: answered from your own pages, word for word where it matters.
• Triage and routing. Even when a person closes the case, an agent that reads the message, tags the topic, pulls the order and routes it to the right person removes a lot of sorting.
• After-hours and overflow. The late-evening question or the Monday-morning backlog gets an immediate answer without waking anyone.
• First drafts for your team. The model drafts, a person edits and sends. You get most of the speed and keep a human accountable for what goes out.

A note on language: in Kazakhstan the agent has to answer equally well in Russian and Kazakh. That means answers in both languages in the knowledge base, not translation on the fly.

What to leave to people, at least for now

• Refunds and disputes above a threshold. Money decisions with judgement calls (was the product really faulty, is this the third "lost parcel" this month) belong with a person, or with an agent capped at a small amount and logged for review.
• Health, legal and financial advice. A company is responsible for what its automated systems tell customers. A wrong answer on such a topic is a liability, not just a bad experience.
• Angry, upset or escalated customers. Sentiment detection is better than it was, but still unreliable in hard cases. A customer with a serious problem needs a person quickly, not three bot messages that feel like stalling.
• Answers that depend on context the model does not have. Custom contract terms, informal agreements with a regular, anything that lives in someone's head and not in a database. Automating around that gap produces confidently wrong answers.
• New or unusual requests. When a request appears for the first time, route it to a person and log it. Once you have seen it ten times, it is a candidate for automation.
• Anyone who asks for a person. "Can I talk to someone" must work on the first ask.

The line moves, so plan for it

The split above is not permanent. Review it every quarter: what went to a person that the agent could have handled, what the agent closed that led to a complaint, where it was confident and wrong. Without that review, the scope freezes at whatever shipped on day one: usually too narrow six months later and sometimes too broad on launch day.

Three ways to add AI to customer support

Vendor pricing changes often, so compare current plans on their sites. The practical rule: if most of your questions are answered by help articles and your service already has AI features, turn those on first. If the answers depend on your own data, or the agent has to do something rather than say something, a custom agent pays for itself.

How to keep AI answers accurate

A wrong answer delivered confidently does more damage than a slow one. Four things keep AI customer support honest:

1. Answers only from approved content. The agent answers from your help pages, policies and live data, not from the model's general knowledge. If the source has no answer, the agent says so and hands over.
2. One owner for the knowledge base. Prices and policies change. Someone updates the source on the same day, or the agent drifts.
3. Limited permissions. Read-only by default; actions only where you have agreed on them, with limits (for example, refunds up to a set amount) and a log of every action.
4. Tested on real past conversations. Before launch, run the agent on a few hundred past requests and compare its answers with what your team said.

Handover to a person: where customers are kept

Handover decides whether AI customer support keeps customers or loses them.

• Three triggers, any one is enough: the customer asks for a person, the agent is not confident, or the topic is on the "leave to people" list.
• Pass the whole conversation, not a ticket number. Nobody asks the customer to repeat anything.
• Say what happens next: "A colleague will reply within 15 minutes", and then keep that promise.
• Hand over into the tool your team already uses: the CRM, Bitrix24 open channels, amoCRM, a Telegram or WhatsApp work chat. Not a new inbox nobody watches.
• Let the person hand back once the issue is solved, so the agent can handle the follow-up.

A handover that works in under a minute makes an average bot acceptable. A perfect bot with no handover loses customers on the first unusual case. We cover this step by step in how to automate customer service. Once the conversation lands in your CRM, the same data can feed follow-ups and churn signals; see AI in your CRM.

What to measure

Record a month of numbers before launch and compare with the first month after:

• First-response time: from the customer's message to the first useful reply.
• Resolution without a person: the share of conversations the agent closes, by topic. A low rate on one topic tells you what to fix.
• Handover rate and wait after handover: how often the agent passes on, and how long the customer then waits.
• Satisfaction (CSAT): a one-question rating at the end, tracked separately for AI-handled and person-handled conversations.

If the AI score falls clearly below the human one, narrow the scope: give that topic back to people until the source content is fixed.

Data and the law: what to consider in Kazakhstan

AI customer support processes personal data, so a few things are not optional.

• Consent. Kazakhstan's personal data law requires consent to collection and processing, and the consent states whether data is transferred across borders. AI models and WhatsApp run on servers abroad, so say so plainly in the consent.
• Storage in Kazakhstan. Databases with citizens' personal data are kept in Kazakhstan. Keep conversation logs and customer records in your own CRM on a server in Kazakhstan, and send the model only what the answer needs: the order status, not the whole customer record.
• Log retention. Decide in advance how long to keep conversations and when to delete them.
• Sensitive topics to a person. Health, legal and financial details are not handled by the agent but passed to a colleague.
• Honesty. Say in the first message that an assistant is answering and how to reach a person. It is a matter of trust: customers will notice anyway, and deception costs reputation.

More on consent and storage in our guide to personal data on a website; the primary source is the Law of the Republic of Kazakhstan on Personal Data and Their Protection. This is not legal advice: check the details for your company with a lawyer.

What AI customer support costs

Three kinds of cost, and they behave differently:

• Ready-made AI features are a subscription: per seat, per conversation or per resolved request, on top of the plan you already pay for.
• A custom agent is a one-time project. At Pazl, an AI support agent on one channel, with a knowledge base and handover to your team, starts from 480 000 ₸. The price is fixed in the contract, and the first version goes live within a few weeks once the knowledge base and a sample of past conversations are ready. Every project has a six-month warranty.
• Running costs: model usage (and telephony, if the agent takes calls) is billed separately, at cost, and grows with the number of conversations. Meta charges for WhatsApp Business API messages separately.

The cost most teams underestimate is not the software. It is writing and maintaining the knowledge base the agent answers from. Budget a few hours a week for it.

How it looks in practice: Vera, an agent that knows when to step back

We built Vera for a wedding agency that had hit a growth ceiling: more events meant more back-and-forth with clients, and every new coordinator had to be trained for a long time before they could be trusted with clients.

Vera takes text, voice messages, photos and video, keeps the context of each client, and handles the routine layer: first enquiries, scheduling questions, vendor details. She is connected to Trello and creates tasks rather than just replying. The design decision that mattered most was the escalation rule: when a conversation turns sensitive or needs a judgement call, Vera flags it and a manager gets the full context, not a cold handover.

Mistakes that make AI customer support fail

• Starting with the hardest category. Complaints and refunds look like the biggest win and fail the most publicly. Start with order status and bookings.
• A thin or stale knowledge base. The agent is only as right as your content. Outdated prices produce confident wrong answers.
• No way to reach a person. The single most common complaint about support bots is being stuck in a loop.
• Hiding that it is a bot. Customers find out, and trust drops.
• No baseline. Without the "before" numbers you cannot tell whether it worked, or which topic to fix.
• Launch and forget. Scope, content and handover rules need a quarterly review.

AI customer support checklist

• The last month of requests tagged by topic; the top 20 questions written down
• A "leave to people" list agreed with the team
• Answers to the top 20 checked against current policy, in Russian and Kazakh
• Agent permissions: read-only by default, actions listed with limits
• Handover: three triggers, full conversation, named owner, promised reply time
• Baseline numbers: first-response time, resolution rate, CSAT
• "You are talking to an assistant" notice and a visible way to reach a person
• Consent to data processing that mentions cross-border transfer, log retention set
• One owner for the knowledge base and a date for the first quarterly review

When a custom agent makes sense

If your questions are answered by help articles, the AI features of a good service may be all you need, and we will say so. A custom agent makes sense when answers depend on your own data (orders, bookings, stock in 1C), when the agent has to act in more than one system, or when you want one agent across the website, WhatsApp and Telegram. That is the kind of AI customer support automation we build: scoped with you upfront, fixed price, handover rules in the contract. The same logic works on the phone: a voice AI agent answers calls and logs the result.