Avora Markets, a trading & brokerage platform, now answers every client message on WhatsApp instantly — using an AI system built end-to-end for how a real trading desk actually operates.
Client questions about deposits, accounts and open issues came in on WhatsApp around the clock. A small team could only be online so many hours a day — so replies were delayed, leads went cold waiting for a response, and complaints sat mixed in with everyday questions instead of getting the attention they needed.
An AI system now sits between WhatsApp and Avora's team. It reads every message the moment it lands, pulls the right information before answering, and replies in a natural, paced way — while complaints are automatically routed down a separate path so nothing serious gets missed in the noise.
No jargon here — this is the same journey a client's message takes, described plainly.
Any question, any time — deposits, accounts, a complaint, anything.
No one has to be at their desk for the message to be picked up.
Rather than a canned script, it looks up what's actually relevant before replying.
Written to sound like a person, and paced so it doesn't read as an instant machine reply.
Same conversation thread, no app-switching for the client.
Messages get answered nights, weekends and holidays — not just during business hours.
A prospect asking about accounts gets a useful answer immediately, while interest is still warm.
Replies are grounded in Avora's own material, retrieved per question — not a fixed script.
A dedicated flow separates real issues from routine questions, so nothing urgent sits in a queue.
Response pacing is tuned so it reads like a person typing, not an instant machine reply.
Conversations and login sessions survive updates and reboots — clients never see a "scan again" moment.
For the technical reader: how a WhatsApp message actually moves through the system, end to end.
Rather than sending an entire knowledge base to the model on every message, source content is broken into chunks, converted to embeddings, and the relevant pieces are retrieved just before generation. Only that relevant context reaches Gemini — which is what keeps answers accurate instead of generic.
Every release moves through a blue/green handoff — a new version is proven healthy before it ever sees traffic.
A VM restart changed the external IP, so deploys couldn't reach it over SSH. Traced to a stale secret, fixed by updating it — and it's now a known part of the deployment checklist.
Running both deployment slots at once caused a polling conflict. Fixed with a strict handoff: new slot health-checked, traffic switched, old slot retired — never both live for long.
The WhatsApp session layer needed more headroom than first provisioned. Diagnosed with resource monitoring, fixed by scaling the VM and raising the container's memory limit.
Kubernetes (Pods, Services, Ingress) was explored as a scaling track alongside this build — the production system documented here runs on Docker and a GCP VM.
A reply is only half the job. Whatever a client shares on WhatsApp — registering, referring someone, or raising a complaint — is captured and categorized, so the team sees it in one place instead of scrolling through chat history.
New account interest captured from the conversation and logged as a record, not just a chat thread.
When one client refers another, it's tracked back to who sent it — visible in the CRM, not lost in a message.
Flagged and categorized separately, so a support lead can see open issues at a glance.
Avora Markets now runs its WhatsApp channel on a system that reads context before it replies, hands off complaints instead of burying them, and deploys new versions without a client ever seeing a gap.
ClustRatio builds WhatsApp AI automation end to end — from the conversation flow to the infrastructure behind it.