wa.me Links vs the WhatsApp API: When to Use Which
Many businesses start with a simple wa.me link on their website: "Chat with us on WhatsApp." As soon as they also want to send automatic confirmations, reminders, or order updates, the question comes up: should that go through the API, or can the link handle it too? The answer is that both have their place, and most businesses end up needing both. This article explains the difference and shows how to combine them.
What a wa.me link can and can't do
A click-to-chat link (https://wa.me/<number>?text=<prefilled text>) simply opens the visitor's WhatsApp app, with your number and a prefilled message ready to send. There's no account, no API key, and no server involved — it's a piece of HTML, not an integration.
That makes it perfect for:
- A "Chat with us" button on your website or in your email signature.
- A link in an Instagram bio or on a menu QR code.
- One-off, human contact where the customer sends the first message.
But a wa.me link can't send anything back automatically. You (or someone on your team) has to open the conversation manually in the WhatsApp app itself and reply. There's no confirmation, no status, no trigger from your own systems — the link only starts the conversation, it doesn't send anything.
What the API adds
The TextMeFlow API flips the roles: your system sends the message, without anyone needing WhatsApp Web open. That's what you need once a message is the result of an event in your own software — a new order, an appointment, a payment, a status change — rather than a visitor clicking a button themselves.
So the difference isn't "better" versus "worse," it's about who takes the initiative:
- wa.me: the customer starts the conversation.
- API: your system starts the conversation, at the moment you decide.
See /en/docs/api for the full endpoint documentation and /en/docs/getting-started to connect an account and WhatsApp number via QR scan — just like the pairing flow we covered earlier, no Meta Business verification is required.
Combining both: a realistic scenario
Most webshops and service businesses end up using both, in different places:
- On the website: a wa.me button on the contact or product page, for pre-purchase questions. Fast, low-friction, no setup.
- After purchase or booking: the API automatically sends the order confirmation, tracking link, or appointment reminder — without anyone having to type that message by hand.
- On an incoming reply: when the customer responds to that automated message, it comes back through a webhook to your system, where you can show it to your support team or process it automatically.
An example: a customer clicks the wa.me button on your site asking "Is this model in stock?" Your team replies manually. That same customer then orders through your webshop — from that point on, the API automatically sends the order confirmation and, a day later, the shipping update. Two channels, the same number, each one used at the moment it fits.
In practice: building a wa.me link
A wa.me link needs no tooling at all:
https://wa.me/32470123456?text=Hi%2C%20I%20have%20a%20question%20about%20my%20order
Note that the number is written without a +, without spaces and without a leading zero, in international format (country code + number). The text after ?text= must be URL-encoded (spaces become %20 or +).
For messages sent from your own system, you instead make a POST request to the TextMeFlow API with the phone number in E.164 format and the message text in the body — sent from your server, not from the customer's browser.
Which approach fits your business
If you don't have any WhatsApp presence yet, start with a wa.me button: it takes five minutes and no development time. Once you notice your team typing the same message over and over by hand — order confirmations, appointment reminders, status updates — that's the signal to move that part to the API. The button and the API don't compete with each other: they solve different problems, on the same number.
Want to automate it? Create a free TextMeFlow account and connect your WhatsApp number at /en/signup?plan=free — up to 50 messages a month free, with no time limit.
Want to send WhatsApp messages via API yourself?
Free forever up to 50 messages/month. Scan a QR and send your first message within 5 minutes.
Free forever