The enquiries you lose are rarely the ones on your website. They are the ones sitting unread in a WhatsApp thread from Saturday night, from someone who messaged the number on your invoice because that is the number they had, and who booked with whoever answered first on Monday morning.
A chat widget only reaches people who came to your site and noticed a small button in the corner. The number already saved in your customers' phones reaches everyone who has ever dealt with you. Orastra links that number and answers on it, which is a WhatsApp auto-reply for your business without Meta verification, a new number, or an approval queue — and the reason it can be that quick is worth understanding before you switch it on.
Linking takes about twenty seconds, and there is nothing to register
You open the WhatsApp connector in the dashboard, press Show QR code, and scan it with the phone that owns the number — the same pairing flow you have already used for WhatsApp Web. The wording in the product is deliberately plain about what this costs you: "Link the number your customers already message. It takes about twenty seconds and there is nothing to register."
There is no Business Manager account, no sender registration, no message templates waiting on approval. Your existing number keeps working on your phone exactly as it did; the AI simply also sees what arrives on it.
The official route is not slower by a little
WhatsApp's Business API is the sanctioned way to do this, and it is a genuinely better arrangement once you are through it: supported, stable, and nobody can take it away for using it. Getting through it means Meta Business Verification, a WhatsApp Business Account, a clean number that has never been used on the consumer app, and template approval for anything you want to send first. That is weeks, and the slow parts are gates you cannot hurry.
Both doors are open. If a business has already been through verification, Orastra will send through the official API instead — the connector picks whichever route that business actually connected. What the QR route buys is not a better integration. It is the difference between being live this afternoon and being live next month.
It is the same employee, not a second bot
This is the part that matters more than the channel. Every channel converges on one pipeline: an inbound message resolves which business owns the number, then runs through the same context, the same personality, the same knowledge base and the same tools as the phone line and the chat page.
So the WhatsApp conversation is not a separate assistant with a separate memory. It answers from the same knowledge, books into the same diary, and writes to the same contact record. Someone who rang you last week and messages you today is one person with one history, not two threads that never meet. In practice that is the difference between a customer having to re-explain themselves and the AI already knowing what they asked about.
It has been running in production since the end of August. The first real message on the channel — a stranger writing "Hi I need a website" — was read and answered in four seconds, using the sender's own WhatsApp display name.
Where each channel actually earns its place
| Channel | Reach | What it costs to set up | Best at |
|---|---|---|---|
| Everyone who has your number already | About twenty seconds, one QR scan | Repeat customers, out-of-hours enquiries, anything conversational | |
| QR code and chat page | Anyone standing in front of a poster, door or invoice | Nothing — it is a link, on every plan including Starter | Walk-ins, physical premises, printed material |
| Website widget | Visitors who came to your site and noticed it | Paste a snippet; included from Growth upward | Turning existing web traffic into enquiries |
| Phone line | Anyone who would rather talk | Choose a number in the dashboard; included from Growth | Urgent enquiries, and callers who will not type |
| Anyone with your address | Connect the mailbox | Longer questions, quotes, anything with an attachment |
The pattern in that table is that reach and setup cost are not correlated. The cheapest thing to switch on is the one your existing customers are most likely to use.
The catch: Meta has not agreed to any of this
The QR route works by linking your account the way WhatsApp Web does, and that is not an arrangement WhatsApp formally supports. The product says so on the setup screen rather than in a footnote, and it is worth repeating here: Meta can restrict a linked number, and the number at risk is your business number, not ours.
We have not seen it happen, but "we have not seen it happen" is not a guarantee and should not be read as one. The honest way to weigh it is by what losing that number would cost you for a week. A salon whose bookings mostly come by phone can carry that risk cheaply. A business whose entire customer relationship lives in WhatsApp threads should either use the official API or link a secondary number first.
Two smaller limits. Messages on WhatsApp count against your plan's monthly message allowance like any other text channel — going over is billed rather than blocked, because cutting a receptionist off mid-conversation is worse than charging for the message. And group chats are deliberately ignored: the AI answers one-to-one threads only, and stays silent if someone adds it to a group.
Four messages to send it before you trust it
- Message it from a number it has never seen, asking something your knowledge base covers.
- Reply directly to one of its own messages. A reply is a technically different kind of message from a plain one, and it is the case most worth checking yourself.
- Send a photo with a caption, and see whether it reads the caption.
- Add it to a group. It should say nothing at all.
Then do the same booking test you would run on any channel: book something, cancel it, reschedule it, and check that your diary matches what you were told.
Who should link it today, and who should wait
Link it now if your customers already message you on WhatsApp, the threads are mostly enquiries and bookings rather than long-running relationships, and losing that number for a week would be painful but survivable. That describes most salons, clinics, trades and small service businesses.
Wait, and go through the official API, if the number is the business — if years of customer history live in it, or you are in a regulated field where an unsupported integration is not a decision you are allowed to make on your own. Waiting costs you weeks. It is the correct call anyway.
And if you are not sure, the QR chat page is on every plan and carries none of this risk. It is a link and a printable code that opens the same AI in a browser, which is a smaller version of the same idea with nothing to lose.
Give it one week on the channel where your enquiries actually arrive. Count four things before and after: how many messages came in, how long the first reply took, how many turned into a booking, and how many times you had to correct it. If the reply-time number collapses and the correction number stays near zero, that is the result worth acting on.