Websites & systems

That's the right thing to worry about, so it's the part I build first. The AI drafts a reply and code checks it before it sends: it can only quote prices and details that exist in your own system, and anything it must never discuss is blocked after the model has spoken, not politely requested in a prompt. A reply that trips a rule doesn't go out. A person gets that conversation instead.

They get one. Price negotiation, complaints and anyone who asks for a person are handed straight over, and the moment one of your team starts typing, the bot goes quiet for that customer. It re-checks that right before it sends, because a model takes a few seconds to think and that's long enough for two voices to answer the same person. The handover arrives in your team's own WhatsApp, not a dashboard nobody opens.

Yes - your number, your name on the messages, and nothing for anyone to install. Same for Instagram DMs, the chat on your website and your inbox: it picks up where enquiries already arrive, at 11pm, without you being awake for it.

It's published rather than quoted - an audit, a build, and a monthly run tier, with what's in each one written out. The build buys one clearly bounded workflow, not AI for the whole business, and the scope table says exactly where that boundary sits. Which of the three you need depends on what happens now: who handles the messages, how often, and what it costs you when nobody gets to them. If it isn't worth building, I'll say so.

No, and that's usually what decides whether any of it survives. The sales team I built for never opened a new tool: handovers land in the WhatsApp they already use, and the record of every conversation lives inside the website they already had. Anything that needs a login nobody remembers gets quietly abandoned.

Building it is the short part. The real work is the weeks after it goes live, when real customers do things no plan predicted - the showroom bot replied in the wrong language, offered photos nobody asked for, and answered "ok" with "noted, I'll follow up." Each one became a rule with a test behind it. So it starts on a small allowlist, supervised, before it goes anywhere near a customer.

Yes, and in whatever else your customers turn up speaking. The showroom assistant I run handles Arabic and Russian alongside English, and it files every message twice - the original and an English translation - so whoever's on shift can read a thread in a language they don't speak.

Me. Mayantha Jayasinghe, working on my own out of Dubai. The same person scopes it, writes it, and replies when you email. Nothing is white-labelled from someone else and there's no account manager in the middle, which is the trade: one person's full attention, and one person's calendar.