Use case · Customer
AI customer support automation, in every language.
Customers message businesses on WhatsApp, LINE and web chat and expect an answer in minutes. An autonomous support system resolves routine requests end to end, at any hour, and hands the rest to your people already diagnosed.
The problem
Why this work does not scale.
Support teams spend most of the day on questions that have known answers: order status, opening hours, refund rules, how to change a booking. Each one is simple, but they arrive in volume, in several languages, and often with a screenshot rather than an order number.
Hiring to match volume is slow and expensive, and a chatbot that only recites FAQs frustrates customers who need an action taken. The gap is a system that can look something up, decide within your policy and complete the request, while recognizing when to stop and call a person.
How it works
From first signal to finished work.
- _01_
Receive
A customer writes on a messaging app, web chat or email, in their own language or a mix.
- _02_
Understand
The system reads the message and any attachment, and identifies what the customer wants.
- _03_
Check
It looks up the order, account or booking in your systems and checks the request against your policy.
- _04_
Act
Within the authority you set, it replies, refunds, rebooks or updates the record.
- _05_
Escalate
Anything outside policy or emotionally charged goes to a person with the case summarized and a suggested reply.
Example
An example conversation, step by step.
Hi, I was charged twice for order #48213
Sorry about that. I can see two charges of $2,450 on 3 October. I've refunded the duplicate; it will reach your account within 3 to 5 days.
✦ Billing verified, refund within policy, case closed, follow-up survey sent.
An illustrative case. Real volumes, policies and approval limits are set with you during mapping.
Authority
You decide how far it goes.
The same function can run at different levels. Most systems begin at Level 2, where people approve each action.
- L1 AssistDrafts a suggested reply for the agent, who sends it.
- L2 ApprovePrepares the full reply and any refund. A person approves each one.
- L3 LimitsAnswers routine questions and refunds up to your limit alone. Escalates the rest.
- L4 RunRuns first-line support. People review exceptions, quality samples and trends.
What makes it different from a chatbot
A chatbot answers from a script. This system reads the customer's situation, checks your systems, applies your policy and takes the action. It handles exceptions and unstructured messages, such as photos of receipts, and it adapts when your policy changes without being rebuilt.
Built for how customers communicate
Replies are in the language the customer used, with tone and politeness defined for your brand and tested with native speakers. The same knowledge and hand-off sit behind every messaging app, web chat and email, so customers get consistent answers on whichever channel they choose. See our notes on designing AI for multilingual customers.
Governance
Guardrails built in from the first week.
Refund and action limits
Hard caps on what the system may do alone, set by you and enforced in the system.
Escalation by design
Complaints, legal threats, vulnerable customers and unclear cases route to a person with full context.
Data protection
Scoped access, purpose limitation and a complete audit trail, designed to support data-protection compliance (GDPR, PDPA, DPDP). See Security.
Questions
Customer support automation, answered.
Which messaging apps does it work with?
It connects to the channels you already use, such as WhatsApp, LINE, Telegram, email and web chat. Which channels apply depends on your stack, and we confirm them during mapping.
Can it issue refunds by itself?
Only within limits you define. Most deployments begin with every refund approved by a person and extend authority as measured results justify it.
What happens when it does not know the answer?
It says so, escalates to your team with the conversation and its findings attached, and tells the customer what to expect.
How long does it take to go live?
Most first systems move from mapping to production in three to six weeks, depending on the systems involved and the approvals required.
Further reading
Go a little deeper.
- AI customer support on messaging apps: a practical guide: Customers ask questions where they already chat. This guide explains what AI can do on messaging apps, how to set it up in stages and how to judge the result.
- Messaging app chatbot vs AI agent: Auto-reply, scripted bots and AI agents: which a business account needs.
- Data protection and AI: a practical checklist: Using AI with customer messages, documents or HR files brings data protection law into play. A practical checklist of what to know, decide and ask your vendor.
- Designing AI for multilingual customers: language, channels and data: AI built for one default customer often disappoints everywhere else. Four practical lessons for serving customers in many languages, on the channels they already use.
Begin
Start with this one function.
Tell Primues where work slows down. It will outline the opportunity and connect you with an architect from our team.