Your WhatsApp message to a guest just failed. There's a red icon in the Butler AI inbox and a number next to it — 131049, or 131047, or one of eleven others — and no explanation. Before you resend it: don't. Most of these codes aren't a mistake you made, and they're not a Butler AI bug. They're rules WhatsApp and Meta enforce on every business sending messages through their platform, and each one needs a genuinely different response. This is the guide.
First, know what 'failed' doesn't mean
Sent, delivered, and read are delivery receipts, not guest behavior. A message can be sent and then later come back failed — WhatsApp reports these asynchronously. A guest not replying is never the same thing as a delivery failure; don't resend a message just because nobody's answered yet. The only signal that something actually needs your attention is the red failed icon with a code next to it. Everything below is about reading that code correctly.
131026 — Message undeliverable
WhatsApp accepted your send but couldn't get it to the guest's device. This is a broad recipient-side error — the guest's number may not actually be on WhatsApp, their app may be out of date, or they haven't accepted WhatsApp's latest terms. WhatsApp doesn't tell you which. What to do: double-check the contact details on the guest profile. Don't keep resending — if it's urgent, use your hotel's approved alternative-contact process. If you're seeing this across many guests at once rather than one, that's worth flagging to a manager as a pattern, not a one-off.
131047 — The 24-hour reply window is closed
This is the one every front-desk team runs into eventually. WhatsApp only allows free-form replies — the normal typed messages your staff send — for 24 hours after a guest's last inbound message. Once that window closes, WhatsApp rejects a plain reply outright, even if it's completely reasonable and expected. What to do: don't keep retrying the same typed message. A guest reply reopens the window immediately — but until they write back, the only way in is an approved WhatsApp template message. Request one rather than trying to work around the block.
130403 and 131056 — Blocked and rate-limited contacts
Two different problems that both live at the individual-guest level. 130403 means this specific guest has blocked your hotel's WhatsApp business number — there's no sending around that; it needs a manager decision on the guest-contact side, not a retry. 131056 is a pair rate limit: too many messages went from your number to that one guest too quickly. If your team sent three follow-ups in ten minutes, this is why. What to do either way: stop the sequence of messages, combine what you need to say into one, and only reach for an urgent alternate contact method when it's genuinely necessary.
131048 — Your hotel's own number is temporarily restricted
This one isn't about a guest at all — it's about your hotel's sender number. WhatsApp has temporarily capped how many messages your number can send, usually triggered by quality or spam signals building up over time (too many blocks, too many reports, low engagement on automated sends). What to do: pause outbound messages and alert the duty manager instead of testing the limit with more sends. A manager or admin should review recent volume, WhatsApp Manager's quality score, and whatever automation might be contributing before anything resumes.
131049 — Not a Butler AI bug, and not your mistake
This is the code that causes the most unnecessary panic, because it sounds like an accusation: "This message was not delivered to maintain healthy ecosystem engagement." Read that again — it's WhatsApp protecting the guest, not flagging a problem with you. Meta caps how many marketing-style template messages a person can receive across every business messaging them in a day, and once that guest hits the limit, WhatsApp quietly declines the next one. It has nothing to do with your hotel's number, your account standing, or anything Butler AI did. What to do: don't resend immediately — that's the instinct to resist. Back off 12–24 hours and let the limit clear on its own before trying again, and keep the code with the conversation so a manager has the context if the guest asks why they didn't hear back sooner.
131042, 190, and 10 — Admin problems, not staff problems
If you see any of these, there's genuinely nothing to fix from the guest chat — this is a back-office issue. 131042 is a billing or account-eligibility problem on the WhatsApp account itself. 190 means the connection between Butler AI and Meta has an expired or invalid access token. 10 means a required Meta permission is missing. What to do: escalate immediately with the exact code — retrying the message changes nothing here. Whoever manages your WhatsApp Business account needs to check billing, refresh the token, or restore the permission before sends will work again.
132001 and 133010 — Template and setup errors
Configuration issues that show up before a guest ever sees anything. 132001 means the template name, language, or approval status Butler AI tried to use doesn't match what's actually approved in WhatsApp Manager. 133010 means the hotel's phone number itself isn't correctly registered for the WhatsApp Cloud API. What to do: don't try to work around either by rewriting the message in the chat — that doesn't touch the underlying problem. Tell whoever owns the WhatsApp setup which guest journey and template failed, and let them fix the configuration.
130429 and 131000 — Platform limits and the unexpected
The catch-all category. 130429 means WhatsApp's platform-wide sending throughput limit has been hit — a busy-traffic problem, not a guest or account problem. 131000, or any code not covered above, is either a generic failure Meta doesn't specify further, or simply one Butler AI hasn't documented yet. What to do: the instinct is the same regardless — stop manual retries, record the code, the time, and the guest, and escalate. Don't guess at a cause you can't confirm.
The two-second gut check
You don't need to memorize thirteen codes to work a shift. Every one of them collapses into one question: is this about the guest, or about us? 131047, 130403, and 131056 are about this specific guest and need a human decision. 131048, 131042, 190, 10, 132001, and 133010 are about the hotel's own setup and need an admin, not a resend. And 131049 — the one that reads like an accusation — is neither; it's WhatsApp managing its own ecosystem, and it clears itself. Whatever the code, the one thing that's never the right move is resending the same message and hoping.
All 13 codes, side by side — tap any card to enlarge
Butler AI already surfaces every WhatsApp delivery status and error code directly in your guest inbox — this guide exists so your team can read it with confidence instead of guessing. If your hotel is still fielding these questions manually, or wants the guest-messaging side of your PMS actually automated end to end, take a look at heybutler.io.
