Channel · WhatsApp
Where your customers already are.
The Velor agent runs inside the WhatsApp conversation — same knowledge base, same custom actions. On WhatsApp a customer who asks for a person is handed to your team's inbox; the agent also hands off when it judges it cannot resolve something or the customer is clearly frustrated, as it does on chat and voice. Who is notified depends on who you set to receive escalations. For markets and customers where WhatsApp is the default channel, you meet them there without a second deployment.
What it does.
Global reach, one deployment
WhatsApp is the primary messaging channel in dozens of markets. One Velor agent configuration serves your WhatsApp number alongside your chat and voice channels — no separate setup.
Grounded replies in the thread
Every response is grounded in your current knowledge base. The same retrieval pipeline as chat and SMS — accurate, cited, auditable.
Action execution in-thread
Order lookups, booking changes, subscription status — custom actions available on every channel work inside WhatsApp. Any destructive action is held for a teammate to approve.
Straight answers about reaching a person
When a customer asks for a person, the conversation is escalated into your team's inbox and the customer is told a teammate has it, but only if the handoff actually went through. If it could not be raised, the customer is told that plainly and nobody is promised. The agent also hands off on its own judgment when it cannot resolve something or the customer is clearly frustrated, under the same rule: nobody is promised unless the handoff went through.
How the WhatsApp channel works.
- 01
Customer messages in
Inbound WhatsApp message to your WhatsApp Business number routes to the Velor agent. No app change for the customer — standard WhatsApp.
- 02
Agent retrieves and replies
Same retrieval pipeline as chat. The agent pulls KB passages and, where your schema allows, calls your APIs — all within the WhatsApp thread.
- 03
Destructive actions wait for a human on your team
A write action that needs confirmation never fires from the thread. It is held, queued for a teammate to approve or decline in the dashboard, and the customer is told someone will review it and follow up.
- 04
When the customer asks for a person
An explicit request for a person raises an escalation in your inbox, ahead of any AI answer. Whether a teammate is paged depends on who is set up to receive escalations in your workspace. If the assistant itself fails to produce an answer, the customer is asked to try again shortly, your team gets a dashboard notification, and the thread stays with the assistant.
What teams ask about WhatsApp.
Do I need a WhatsApp Business account?
Yes — you'll need a WhatsApp Business API account (via Twilio or Meta directly). Velor connects to your existing number; you retain ownership.
How is this different from WhatsApp Business's built-in chatbot?
WhatsApp's built-in flows are template-based and rules-driven. Velor's agent is retrieval-grounded and can execute API actions — it handles open-ended questions, not just button flows.
What about rich media — images, PDFs, location?
The agent replies in text. Images and files a customer sends are received and stored with the conversation. The agent cannot send files back over WhatsApp — attachments on an agent reply go out by email only.
Does this work alongside my existing WhatsApp setup?
Yes — Velor routes through your WhatsApp Business API number. If you have existing automation on that number, migration and co-existence options are discussed during onboarding.
One agent, every channel
Configure once. Deploy everywhere.
WhatsApp runs on the same brain as the rest of Velor — one knowledge base, one set of guardrails, one scoped action schema, one audit trail. Tune a behavior once and every channel respects it. No per-channel re-training, no drift between how the agent answers on the phone versus in chat.
Run it on your own tickets.
Every workspace starts with a 14-day free trial. No credit card. If you want a guided walkthrough against your data, we're happy to run one with you.