By Yousef Shaiban · Last updated August 2026
In production, an AI agent does one defined job.
A demo does everything. A deployment answers customer questions in Arabic, or qualifies an inbound lead before it reaches a person, or takes an order, and hands over on an explicit trigger. Scoping it that narrowly is what makes it dependable enough to leave running.
Key takeaways
- In production, an AI agent does one defined operational job, not everything.
- Arabic support automation handles the highest volume of repetitive conversation.
- Lead qualification and order intake run on the same channels customers already use.
- Explicit escalation triggers route sensitive conversations to a human with full context.
- Sheba runs 35+ AI agent personas across 14+ industries over two years of shipping.
What do AI agents actually do for a business?
What separates an operational agent from a demo is a definition of done. Each agent gets one workflow and a point at which its job is finished: the order captured with every field, the lead qualified with a budget and a timeline, the conversation handed to whoever completes it. Because that point is defined, the work can be measured and reviewed, and because the agent is wired into the company's own data and tools, what it completes is the work a team would otherwise have done by hand rather than a simulation of it.
How is Arabic customer support automated?
Most MENA deployments start with customer-service automation, because that is where repetitive Arabic conversation volume is highest. ChatSheba handles customer questions natively in Arabic — across every dialect — and in 10+ UI languages. It runs on exactly four channels: WhatsApp Business API, Telegram, a web widget, and a custom-app SDK. A full CRM sits underneath, so every conversation is logged against the customer record instead of vanishing into a chat thread. The Arabic is authored natively rather than translated, which is why answers read the way a regional support agent would actually write them.
How do AI agents qualify leads and take orders?
An inbound message is the start of a workflow, not just a question. For lead qualification, the agent asks the qualifying questions a sales team would ask, captures the answers against the customer record in the CRM, and routes only the ready buyers to a person — so the team spends its time on conversations that are worth a human. For order and booking intake, the agent collects the details a transaction needs, confirms them back to the customer, and records a structured entry the operations team can act on. Both patterns run on the same channels customers already message on, so there is no new app for anyone to adopt.
When does the agent escalate to a human?
It escalates on explicit triggers, not guesswork. Each deployment defines the conditions that hand a conversation to a person — a request the agent is not scoped to handle, a sensitive or high-value case, an unhappy customer, or a direct ask for a human. When a trigger fires, the conversation moves to the team with its full history attached, so the person picks up in context instead of starting over. The agent automates the volume that should be automated and routes the rest, which is what keeps an automated channel trustworthy rather than a wall customers have to argue with.
How broad is this across industries?
Across roughly two years of shipping, Sheba runs 35+ AI agent personas in production across 14+ industries — banking and microfinance, healthcare, education, retail, manufacturing, food and beverage, real estate, travel and documentation, and more. Each persona carries the vocabulary, tone, and rules of its industry rather than one generic script, because a banking conversation and an F&B order are not the same job. The breadth comes from the same operational patterns applied to different workflows — and where a business needs something beyond the four standard channels or the standard support flow, that work goes to custom AI.
What about work beyond customer support?
Not every job fits a support agent. Where a workflow is specific enough that no standard flow holds it, the system gets built around the operation instead: agents wired into a company's own data and tools, scoped to a defined task, running in production inside a per-deployment data boundary. The practical test is simple. If a workflow is real, repetitive, and has a clear definition of done, it is a candidate for an agent. If it is not, the problem is not which tool you pick.
Frequently asked questions
See which agent pattern fits your operation
Tell us the workflow you want to automate, and we will map it to a pattern we already run in production.
See customer results