AI customer service that answers on WhatsApp, web chat and the phone, and hands your team what needs a person

In most support teams a small set of questions comes up far more than the rest: where is my order, how do I reset my password, what is the returns policy, when does my subscription end. A person who answers them one by one has no time left for the case that needs digging and a decision, and the customer who writes in the evening waits until tomorrow.

The digital employee takes that repetitive share. It answers on the spot from the knowledge base, carries out the simple actions your systems allow, and passes the rest to your team in order. The aim is not to do without support staff. It is that only work worth their time reaches them.

Automated customer service is only as good as what it is fed. We start by collecting questions as your customers actually write them, from your archive of chats and tickets, then write an answer for each that someone at your company reviews. Prices, policies and time limits are kept as fixed wording the digital employee does not rephrase.

Before launch we test it on real messages it has never seen, some typed in a hurry and some with two questions in one, and give you the results to judge for yourself. Accuracy is not assumed. It is measured on your own customers’ messages. After launch, every question it had no answer for shows in the report, and you add the answer from a simple panel without waiting for a developer.

A handover is not a failure of the digital employee. It is part of the design. We write with you the list of cases that always go to a person: the customer asks for one outright, there is clear anger or a complaint, an amount of money is in dispute, the issue touches safety or privacy, or a question has come twice without being understood.

At handover the member of staff sees a short summary: who the customer is, what they want, what they were told and what details were collected. During working hours the conversation moves across directly. Outside them a ticket is opened and the customer is told plainly when to expect a reply, with no promise the team cannot keep.

WhatsApp runs through the official business interface, and it has rules. You can reply freely to a customer for a limited time after their last message. After that, a message needs a template that Meta has approved. So the digital employee sends notifications and follow-ups only to people who agreed to receive them, using approved templates, such as an update on a ticket or a request for feedback once it is closed.

On the website it appears in a chat window, where those rules do not apply. On the phone it answers in a natural voice and introduces itself as an automated assistant. If calls are recorded or transcribed, the caller is told at the start of the call. Conversations from all three channels appear in one place, so staff never ask a customer what they already said elsewhere.

The digital employee does not approve a refund, promise compensation, change account details before verifying the owner, or give legal, medical or financial opinions. It explains what the written policy says and records the request. The decision stays with your staff.

Customer data is kept in a database dedicated to your project, with access limited to those entitled to it, in line with the requirements of the Saudi Personal Data Protection Law, and we collect only what the service needs. We connect to your systems where the system offers an interface. Where it does not, tickets reach the team on a panel or by email. The number, the accounts and the code belong to your company.

The demo page opens on a fictional sample business. Write it a complaint, ask something outside its remit, ask for a person halfway through, then call it. What matters is how it behaves at its limits, not on the easy questions, and everything it does shows in the system panel beside it.

Yours is built on your customers’ questions and your policies, and your support team tests it before it opens to customers. Before launch we agree what we will measure: time to first reply, what was solved without a person, and the reasons for handover.