Customer-service decision table
Fill in one row per support job. Most UAE teams end with a mix of person, chatbot and agent.
| Support job | Better fit | What you must have ready | Person stays in when |
|---|---|---|---|
| Same FAQ every day, answers live in your policies or site | Document chatbot, or a help article | Up-to-date documents the bot may quote | It cannot find the answer, or the customer asks for a person |
| Sorting inbox mail or WhatsApp into queues | AI agent (triage) or simple rules | Labels, priority rules, channel access | Urgent, angry or unclear threads |
| Order status, booking lookup, ticket update across systems | AI agent (action) | Limited access to each system, test accounts | Before any change that emails or charges the customer, at least at the start |
| First reply draft for a human agent | AI agent assist | Tone guide, approved macros, CRM notes | Always: a person sends |
| Refunds, complaints, legal or medical advice, anything that commits the company | Person decides; agent may draft only | A written ban list for the agent | Always |
| Low volume, founder still answers personally | Person only for now | A shared inbox and response targets | N/A |
| Voice notes in Gulf Arabic | Pilot only after a voice test | Real recordings, a speech tool you have tried | Always until accuracy is proven on your files |
Handoff sheet (print with the table)
| Rule | Your answer |
|---|---|
| Channels in scope (WhatsApp, web chat, email, phone) | |
| Languages to test (Arabic, English, mixed) | |
| Systems the agent may read | |
| Systems the agent may write to | |
| Actions allowed alone | |
| Actions that need approval before send | |
| Actions banned | |
| Named owner for escalations | |
| Where transcripts and logs are stored | |
| Review date for the pilot |
Use Print or save this sheet under it to keep a copy. Follow Voyuma on X at @getvoyuma.