WhatsApp API Limitations: 12 Things It Can't Do
The sales demo looked great. Then you connected your number and found the gaps: your groups are missing, last year's chats are gone, a quick "Hi, just checking in" gets rejected, and a typo in a sent message cannot be fixed. None of it was on the pricing page.
The WhatsApp API limitations that hurt most are the ones nobody mentions until after you have migrated a number. This is the honest list for Meta's official WhatsApp Business Platform as of October 2026, twelve things it cannot do, each with what to do instead.
Still choosing a route? The complete guide to the WhatsApp API compares the official platform with linked-number options.
The short list
| # | Limitation | What to do instead |
|---|---|---|
| 1 | Cannot see or post in groups your number is already in | Use a linked-number tool, or rebuild small groups with the Groups API |
| 2 | No chat history from before you connected | Use coexistence for up to 180 days of Business app history, or export first |
| 3 | Cannot start a conversation without an approved template | Let customers write first, and keep utility templates ready |
| 4 | Marketing templates are not guaranteed to arrive | Earn engagement, respect opt-outs, use another channel for US audiences |
| 5 | Sending limits start low | Verify your business and ramp up steadily |
| 6 | The number leaves the normal WhatsApp app | Use coexistence for Business app numbers, or a second number |
| 7 | Cannot edit or unsend a sent message | Send a clear correction |
| 8 | Comes with no inbox or screen | Add a provider's inbox, a helpdesk or your own build |
| 9 | Templates need approval and can be paused or recategorized | Write tight templates and watch quality |
| 10 | Many app features are missing | Keep those jobs in the app or another tool |
| 11 | Replies are no longer free beyond 1,000 a month per number | Budget for service messages and use free windows |
| 12 | General-purpose AI assistants are not allowed | Keep bots focused on customer service |
Groups and history
1. It cannot see the groups you are already in
The Cloud API has no access to existing groups. Meta's Groups API, open to businesses with an Official Business Account, can only create new groups that people join by invite link, with a maximum of 8 participants and one Cloud API business per group, per Meta's Groups page. Interactive messages, calls and commerce messages are not supported in them, and WhatsApp Business app numbers on coexistence cannot use them at all.
If your business runs on broker, dealer or class groups, the official API will not reach them; a linked-number tool, operating the account that is already a member, can. Our guide to sending to a WhatsApp group by API compares both routes.
2. It has no chat history from before you connected
The Cloud API delivers messages to your webhook from the moment you connect. There is no endpoint to fetch older conversations. The one exception is coexistence: when a WhatsApp Business app number is onboarded, a partner can import messages from the 180 days before onboarding, excluding group chats, and must start that sync within 24 hours.
A full migration requires deleting the number from WhatsApp, which removes its chats and groups from the phone. Export what you need first. Our post on WhatsApp API chat history covers the options.
Who you can message, and when
3. It cannot start a conversation without a template
Free-form messages only work inside the 24-hour customer service window that opens when a customer writes or calls. Outside it, every message must be a pre-approved template, and late free-form sends fail with error 131047. You also need the person's opt-in before messaging them at all.
Instead, design for customers writing first, through QR codes, click-to-chat links and Click-to-WhatsApp ads, and keep approved utility templates for follow-ups. Our guide to the WhatsApp 24-hour window shows how to build around it.
4. Marketing templates are not guaranteed to arrive
WhatsApp limits how many marketing templates a person receives from all businesses when they are unlikely to engage, and blocked sends fail with 131049. People can also stop marketing from your business, which fails with 131050. And as of October 2026, Meta's per-user limits page says marketing templates are not delivered to users with US phone numbers at all.
Send fewer, better marketing messages to people who opted in, and plan another channel for US audiences. Our comparison of the WhatsApp API vs SMS covers when SMS wins.
5. Sending limits start low
A new business portfolio can message 250 unique users outside the customer service window per moving 24 hours, shared across all its numbers, and can register two numbers. Separately, a number can send one message every 6 seconds to the same user, with short bursts allowed.
The way up is verifying your business, or delivering 2,000 high-quality template messages to unique users within 30 days, after which Meta raises the limit automatically as you use it. See WhatsApp API messaging limits.
Your number and your phone
6. The number leaves the normal WhatsApp app
A number registered to the Cloud API can still take ordinary calls and SMS, but it cannot be used in WhatsApp Messenger, and a number already on WhatsApp must be deleted from it first. Personal WhatsApp numbers have no way around this.
WhatsApp Business app numbers can use coexistence, which keeps the app working alongside the API. It comes with a fixed throughput of 20 messages per second, group chats that stay out of the API, broadcast lists that become read-only, and a disconnect if the main phone is inactive for roughly 14 days. Our guides to WhatsApp coexistence and using the WhatsApp app after the API go into detail.
Messages, features and tooling
7. It cannot edit or unsend a message
As of October 2026, Meta's messages reference documents sending, read receipts and typing indicators, but no call to edit or delete a message you have already sent. The Groups API documentation lists editing and deleting as unsupported outright.
Send a short correction ("Sorry, the slot is 4 pm, not 3 pm") and test template variables before campaigns. More in WhatsApp API edit and delete messages.
8. It comes with no inbox
The API is a pipe: no agent screen, assignment, notes, history view or roles. WhatsApp Manager handles numbers and templates, not conversations. You need software on top: a provider's inbox, a helpdesk integration or your own build. Our WhatsApp API team inbox post weighs build against buy.
9. Templates are gatekept
Every template is reviewed and categorized by Meta, which can later recategorize it and change its price. Templates with poor feedback get paused for 3 hours, then 6 hours, and are disabled on a third strike. An unverified portfolio is capped at 250 templates per Messaging account.
Write short, specific templates that match what the user asked for, and watch quality weekly. Start with our guide to WhatsApp message templates.
10. Many app features are missing
Meta's coexistence documentation lists Status, Channels, broadcast lists, disappearing messages, view-once messages and live location as unsupported on the Cloud API. Calling exists, but business-initiated calls need the user's permission and at least a 2,000 messaging limit, cannot be placed from business numbers with US, Canadian, Egyptian, Vietnamese or Nigerian country codes, and are not supported in groups. Keep those jobs in the app.
Cost and policy
11. Replies are no longer free
Since October 1, 2026, each business number gets 1,000 free service messages a month, then pays per reply at the service rate for the user's country. Utility templates inside an open window are charged again, and providers add their own fees. Free entry point windows from Click-to-WhatsApp ads stay free for up to 7 days. Our WhatsApp API pricing guide has the full model.
12. General-purpose AI assistants are not allowed
Since January 15, 2026, Meta's Business Solution Terms bar general-purpose AI assistants from AI model providers on the platform. Businesses using AI for their own customer service, such as support bots, booking or order help, are still allowed, and Meta offers its own Meta Business Agent. See the WhatsApp AI chatbot policy.
Where Tenashi fits
Several of these limits, notably groups, history, templates, the phone and the inbox, come from the official platform itself, not any provider. Tenashi takes a different route: you link your existing WhatsApp or WhatsApp Business number by QR scan, as a linked device, so your groups and recent history come with it and the phone keeps working. Your team gets one shared inbox for DMs and groups, with a CRM, notes, tickets and follow-ups, and there are no templates or per-message fees. Plans start from $18/mo.
It has its own limits, stated plainly. Tenashi is not Meta's platform and is not endorsed by Meta, so it offers no green tick, buttons, lists, Flows or templates. Sends are paced at one every 4 to 12 seconds per number, the API allows 50 new chats per number per day, and WhatsApp can still ban numbers that spam. For OTPs and high-volume alerts, the official API is still the right tool.
See every feature · Read the API docs
FAQ
What are the main limitations of the WhatsApp Business API?
The biggest are: no access to groups your number is already in, no chat history from before you connected, templates required to start conversations, no editing or unsending, the number leaving the normal app, low starting limits and per-message charges that now include replies beyond 1,000 per number each month.
Can the WhatsApp API read my existing WhatsApp groups?
No. Meta's Cloud API cannot read, join or post in groups your number is already a member of. The Groups API only lets Official Business Accounts create new, invite-only groups of up to 8 participants. To work existing groups by API, you need a tool that links your current account as a device.
Can I see old chats after moving to the WhatsApp API?
Not through the API itself. A full migration requires deleting the number from WhatsApp, which removes its chats from the phone, and the Cloud API only delivers messages from connection onwards. Coexistence onboarding for WhatsApp Business app numbers can import up to 180 days of one-to-one history, excluding groups.
Why can't I send a normal message to a customer?
Because more than 24 hours have passed since they last messaged your number, so the customer service window is closed. The API returns error 131047. Outside the window, Meta only allows approved template messages, which you create in WhatsApp Manager or by API and submit for review before sending.
Can the WhatsApp API send marketing messages to US numbers?
As of October 2026, no. Meta's per-user marketing limits page states that WhatsApp does not deliver marketing template messages to users with US phone numbers, and sends return an error. The statement covers marketing templates. Check Meta's page before planning any US campaign, since policies change.
Knowing the edges early saves a painful migration. If groups, history and your own phone matter more than templates and scale, try the linked-number route with Tenashi.