WhatsApp API Multi-Device: One Number, a Whole Team
One WhatsApp number, one phone, one person who has to read all the messages — that works fine as long as you work alone. As soon as a support team, a front desk with rotating shifts or multiple locations need to use the same number, you get stuck. The solution isn't "give everyone their own number" — that breaks exactly the recognisability that customers trust. The solution is multi-device.
What multi-device actually means
With TextMeFlow, you link your WhatsApp number to the platform via a QR scan, just like WhatsApp Web. On the Free and Starter plans, that's allowed on 1 device/session at a time. From the Business plan (€29/month, 25,000 messages/month) you can keep that same link active on 3 devices at once, and on Enterprise it's unlimited. In practice, this means three colleagues — or three systems — can send and receive through the same API credentials and the same WhatsApp number, without one breaking the other's session.
That's fundamentally different from "just logging in on multiple phones with the same account": the sessions run through the platform, not through WhatsApp's own multi-device limit on your phone. Your integration (CRM, helpdesk tool, booking system) keeps using one API key; who sits "behind" it — a front-desk employee, a night shift, an automated bot — is a routing question in your own system, not something WhatsApp gets involved in.
Typical setup for a team
A layout that works well for support teams:
- One incoming number, multiple senders. Messages arrive through the webhook at one central point; your helpdesk (for example a ticketing system) assigns the conversation to an employee, who then replies through the API — still from the same WhatsApp number.
- Shift schedule without passing on a phone. Because the link sits at platform level, nobody has to hand over a physical phone with a SIM card at shift change. Login to the dashboard (or API access) determines who can send.
- Automation alongside people. One of the three devices can be an automated flow (for example appointment reminders via a script), while the other two are used by people for ad hoc customer questions — all recognisable as the same business number.
What multi-device doesn't solve
Multi-device shares capacity to use the number, not your message quota. All messages sent via the three linked sessions count together against the Business plan's 25,000/month — and against the hourly ceiling of 300 messages. So plan your sending volume at team level, not per device. Check your current usage and cap via /docs/rate-limits before scheduling a large action (for example a campaign or bulk reminder).
Multi-device also doesn't change anything about the anti-spam rules: opt-in, rate limits, STOP handling and quiet hours still apply per number, regardless of how many devices are attached. More people sending at the same time therefore also means more responsibility to apply those rules consistently as a team — not every employee may just start sending to whoever they like.
Getting started
If you're on Free or Starter with one device now and you're running into the limits of "one person manages everything", moving to Business is a matter of upgrading in the billing portal — no new link, no new number, no downtime. Take a look at the API basics in /docs/api if you want to prepare the integration with your own helpdesk or CRM before scaling up.
Want to try multi-device on a small scale first? Start for free and test the link yourself.
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