If portal leads wait until morning for a reply, this is for you. A fast first reply, on whatever channel your leads use, is the fix, and two kinds of supplier will sell it to you: an automation agency or an implementation partner. This is not for you if no one owns the lead after the first reply. Name that person first, because neither supplier can do it for you.
Why do two quotes for the same job disagree so much?
Because "an automated reply" is not one product. In September, Nexus Labs AI, a UAE vendor that says where it stands, laid three published UAE price guides side by side. They put the same basic FAQ chatbot at starting prices 25 times apart. Price will not tell you which supplier to pick, and neither will the pitch.
Nexus's advice is to get six answers in writing before you sign, among them "What does month thirteen cost?" and "Who owns the code and the prompts at the end?" We agree with all six. We would put one question ahead of them: who owns month seven?
What does month seven look like?
Month one is a demo. By month seven the portal has changed its lead format, a new area has joined your price list, and a buyer has been told something wrong. Someone has to read what the agent did, change the rule and, if needed, switch it off.
A made-up example, not a client. A portal lead arrives at 11pm. The first reply is one action, and the update to your record is another. In month one both go out at once and nobody looks. In month seven the owner opens the log in the morning, sees what went out and what was held back for a person, and changes one rule before the next lead arrives.
A team that dropped its WhatsApp support tool, writing on DEV Community in October, described the failure as an agent "talking fast and wrong" with "no log showing why." The speed was never the problem. The missing log and the missing owner were.
Which supplier fits which job?
Sort the job before you sort the supplier. A step that follows a fixed rule, such as copying a portal lead into your sheet and sending a template reply, has no judgment in it. A step that reads an enquiry, decides what it is asking and writes to your CRM does.
An agency can pass the second row, and some do. The test is not the label on the supplier. It is the three questions below.
Which three questions go to either supplier?
Our method is called Spec, shadow, gate. Put it to any supplier as three yes or no questions.
- 01Spec: can I read the job on one page before you build? Inputs, the write, the limit, who approves, and what it must never do.
- 02Shadow: will it run beside my person and write nothing, until I have compared its replies with what my person sent to the same leads?
- 03Gate: does every write go live behind a human approval, and can I stop it myself?
Leads that arrive at 11pm and a human gate do not clash if the spec says which writes wait for a person. We settle that write by write in the spec, and the offer page says the gate loosens only where the shadow run earned it. Ask any supplier which writes would go out overnight, and who agreed to that.
A "no" to any of the three is your answer. A "yes" to all three moves the choice back to month seven: who reads the log, and what that costs after go-live.
Who reviews the exceptions?
Every agent hits a lead it should not decide alone. Ask each supplier for the name of the person who takes those, and what authority they have to change the outcome.
UAE law gives a reason to settle this early. Article 18 of the PDPL (Federal Decree-Law No. 45 of 2021) lets a person object to decisions resulting from automated processing "particularly those decisions which have legal impact on or adversely affect" them. It says the controller "shall include the human element in reviewing automated processing decisions at the request of the Data Subject." Contract, other law and prior consent are excluded.
Our reading, which is not legal advice: a quick first reply probably sits outside the article, while an agent that ranks, screens or turns away enquiries sits closer. Either way, a reviewer slot is cheaper to design in than to add after a complaint. We do not call any tool compliant. Ask your counsel which side your process falls on, and read human approval for AI agents for how approvals are recorded.
What do we put on the table?
The assessment is free: a short read of the org and a written note. If you go ahead, the first build week is a fixed AED/SAR 14,900 (about USD 4,050), credited in full when you sign the build within 60 days. That week produces the one-page job, not a finished agent; the shadow run comes after it.
After go-live there is the Run plan, for teams with a named admin on your side. Run 8 is 8 hours a month at AED/SAR 6,900 (about USD 1,880) a month. Run 20 is 20 hours at AED/SAR 15,900, and Run 40 is 40 hours at AED/SAR 30,900. Prices exclude VAT. You start with three months, then go monthly, with 30 days' notice and no exit fee. Each week we read a sample of the agent's transcripts and handoffs and fix what went wrong (the plan and its terms). Licences and third-party fees are not in the plan. If you have no admin, say so when you ask: the plan page asks for a named admin on your side, and we would tell you what fits instead.
That is month seven, written down with a price. Ask every supplier, us included, for the same.
When are we the wrong answer?
When the work has no judgment in it and your team will keep running it. Then an automation agency is the simpler buy, and we will say so. We are also the wrong answer if you want a full-time person inside your team, or a desk on call around the clock: the Run plan is neither. And if no one owns the lead after the first reply, see the top of this page.
For a checklist on choosing a partner in general, see choosing an AI implementation partner in the UAE. This post is about the step before it: which kind of supplier your job needs.
What would we do first?
Five steps, none of which need us.
- 01Write the lead process as it runs today: where the lead arrives, who sees it, who replies, and when.
- 02Name the owner of the lead after the first reply.
- 03Mark each step as a fixed rule or a judgment.
- 04Put the three questions, and Nexus's six, to two suppliers in writing.
- 05Ask for a shadow run before any write goes live.
If you would rather have the first read done for you, send us the process. Before you send anything to any firm, us included, ask what access its read needs and whether it is read-only. The control side of an agent, who acted and how to stop it, is covered in our architecture and in AI governance. For the Gulf view of agents, see AI agents in the UAE.
