Why WhatsApp Wedding Invites Fail to Deliver
Last updated:
Quick Answer
Why do WhatsApp wedding invites fail to deliver?
Almost every failure traces back to one of two root causes: the number isn't on WhatsApp at all, or the guest hasn't opened the 24-hour messaging window a marketing template needs - what WhatsApp's own error bucketing labels a 'terms' issue. Meta's error 131026 ('Message Undeliverable') covers both of these plus a few rarer causes under one deliberately vague code. The first cause is unfixable by definition; the second has a real, documented workaround.
Last updated:
"100% delivery rate" gets thrown around by every WhatsApp tool selling to wedding planners, and most of the time it's marketing, not a fact - a number that was never on WhatsApp cannot be delivered to, no matter how good the platform is. What actually matters, and what almost nobody explains clearly, is that there are only a handful of real reasons a message fails, most of them are fixable the moment you know which one you're looking at, and Meta’s own error codes are written to obscure exactly that.
Every reason a WhatsApp wedding invite fails to deliver
In order of how often each one actually shows up on a real wedding guest list.
Number not on WhatsApp
Not fixable on WhatsAppThe single most common cause. A landline, a typo in the guest list, or an elderly relative who genuinely doesn't have the app - there is no delivery workaround for a number that isn't registered on WhatsApp. The only fix is a different channel: a phone call, SMS, or a voice broadcast to that specific guest.
Guest hasn't opened the messaging window ("hasn't accepted terms")
FixableMarketing-category templates can only be delivered inside a 24-hour window that opens once the guest has messaged you or tapped an opt-in button. Outside that window, WhatsApp blocks the send rather than delivering it - and this is the failure reason platforms often label "hasn't accepted terms." Fix: switch to a service-category template, or send a short opt-in prompt first.
Recipient hasn't accepted WhatsApp's own Terms of Service
FixableA narrower, less common case: the guest's own WhatsApp app is sitting on an outdated Terms of Service / Privacy Policy prompt it hasn't dismissed. Meta provides a direct link - wa.me/tos/20210210 - that, when opened by the guest, takes them straight to that acceptance screen so future messages can deliver.
Invalid phone format
FixableMissing or wrong country code, extra digits, or a number copied with stray characters from Excel. Fix: normalise the number (add the correct country code) and resend - this is usually a one-line correction in the guest list.
Blocked by recipient
Not fixable on WhatsAppThe guest has actively blocked your sending number on WhatsApp. There is no template or timing fix for this - the guest has to unblock the number themselves, so this is best resolved with a phone call rather than another WhatsApp attempt.
Template not approved
FixableMeta hasn't yet cleared the specific message template you're using. Fix: use an already-approved template for anything time-sensitive while the new one is under review, which typically clears within a day.
What Meta's error 131026 actually means
If you have ever looked at a WhatsApp Business API webhook and seen 131026 - Message Undeliverable and nothing more specific, this is why.
131026
Meta's umbrella "Message Undeliverable" code
4+
Distinct real causes bucketed into that one code
₹0
You are not billed for a 131026 failure
Error 131026 is deliberately a "bucket" error. Meta does not disclose the exact underlying reason in the webhook response for most 131026 failures - partly to protect recipient privacy (WhatsApp does not want to tell a sender "this specific person blocked you"), and partly because several genuinely different problems all resolve the same way from Meta's side: the message simply cannot be handed to the recipient's device.
The causes bucketed under 131026 include, in roughly descending order of frequency:
- The phone number is not registered on WhatsApp at all.
- The recipient has opted out of messages from your business, or has blocked your sending number.
- The recipient's own WhatsApp app hasn't accepted a recent Terms of Service or Privacy Policy update from WhatsApp itself - unrelated to your business or your template.
- Meta is applying a frequency or engagement-based delivery restriction to a marketing template - referred to informally as "Meta chose not to deliver" rather than a true failure.
A related, more specific code worth knowing is the "template rejected" family (covering an unapproved or since-disabled template) and the pairing frequently seen alongside 131026 in third-party dashboards, 131049, which specifically flags the marketing-template engagement-limit case rather than the broader undeliverable bucket.
The actual fix, not the generic advice
Two distinct workarounds for two distinct causes - using the wrong one wastes a resend and teaches you nothing.
If it's the messaging-window issue
Switch that guest to a service-category template, or send a short opt-in prompt first - a message like "there's an update for [couple]'s wedding" with OK and STOP buttons. A tap on OK opens the 24-hour window a marketing template needs to land. This is the fix for the vast majority of "hasn't accepted terms" failures.
If it's genuine WhatsApp ToS non-acceptance
Send the guest this direct link - it takes them straight to WhatsApp's own Terms of Service acceptance screen, with nothing for you or your platform to configure:
wa.me/tos/20210210Our honest take: the reason "100% delivery" claims are mostly marketing is that most WhatsApp tools show you a single word - "failed" - and stop there, leaving you to guess whether to resend, call, or give up. The real unlock isn't a magic delivery rate; it's getting the specific reason per guest, because "number not on WhatsApp" and "hasn't opened the messaging window" need completely different fixes, and treating them the same wastes a resend on a guest who was never going to receive it either way.
Frequently asked questions
Why do WhatsApp wedding invites fail to deliver?+
Almost every WhatsApp delivery failure traces back to one of two root causes: the number simply isn't on WhatsApp (wrong entry, landline, elderly guest without the app), or the guest hasn't opened the 24-hour messaging window a marketing-style template needs (what WhatsApp buckets as an opt-in / terms issue). A smaller number of failures are invalid phone formats, being blocked by the recipient, or an unapproved template - all fixable once you know which one you're looking at.
What does WhatsApp error 131026 mean?+
131026 ("Message Undeliverable") is a deliberate bucket error - Meta groups several distinct causes under one code rather than exposing the exact reason, partly to protect recipient privacy. It fires when the number isn't on WhatsApp, the recipient has opted out or blocked the sender, the recipient hasn't accepted WhatsApp's own updated Terms of Service, or Meta is enforcing frequency/engagement limits on marketing templates. You are not charged for a message that returns 131026.
Is there really a 100% WhatsApp delivery rate?+
No tool can promise literal 100% - a number that was never on WhatsApp cannot be delivered to, full stop. What a good WhatsApp platform can promise is close to 100% of the deliverable numbers on your list, by surfacing the exact per-guest failure reason instead of a generic "failed" so you can fix each one instead of guessing.
How do I fix "guest hasn't accepted terms" on a WhatsApp send?+
This almost always means a marketing-template message was sent to a guest who hasn't messaged you (or tapped an opt-in) in the last 24 hours - WhatsApp requires that open conversation window before a marketing template can land. The fix is to switch that guest to a service-category template first, or send the opt-in prompt (a short "there's an update for you" message with OK/STOP buttons) to open the window before sending the real content.
More on how Weddingkart delivers WhatsApp messages in the full messaging channels guide and the full Weddingkart FAQ.
See the exact failure reason for every guest
Weddingkart surfaces the specific reason behind every failed WhatsApp send - not just "failed" - so your team fixes the actual problem instead of guessing.
By Mayank JaiswalLast updated
Was this article helpful?
Share