01Who this is for
- Businesses that send WhatsApp messages through HighLevel need to know why a message was not delivered.
- Teams responsible for compliance and list hygiene must prevent blocks caused by invalid numbers or frequency limits.
02Error 131026 messages, explained
The error appears in the API response when HighLevel submits a WhatsApp message that Meta’s servers cannot deliver. It is shown as a code 131026 with the title “Message Undeliverable.” The platform does not charge for these messages because no conversation is opened. The error is a bucket code, meaning many different underlying problems share the same identifier.
You can find the error in the message logs of the WhatsApp integration within HighLevel. From there, you run a series of checks to isolate the root cause, then apply a targeted fix based on the identified reason. The process lives entirely inside the HighLevel dashboard and uses the same messaging and contact management tools you already have.
03How businesses use error 131026
- Ecommerce store. Send a plain text utility template to a customer who did not receive an order confirmation. If the test delivers, ask the customer to update WhatsApp. If it fails, remove the number from the promotional list.
- Dental practice. When appointment reminders return error 131026, verify whether the patient’s number is on WhatsApp or has blocked the practice. Delete blocked or invalid numbers to keep the reminder list clean.
- Real estate agency. If a marketing template to a prospective buyer shows error 131026, switch to a utility message to test delivery. If the utility message succeeds, inform the buyer to upgrade the app; otherwise, consider the frequency capping limit and wait before retrying.
04The numbers and rules that matter
- You are not billed for messages that return error 131026.
- Minimum app versions: Android 2.21.15.15 or higher, iOS 2.21.170.4 or higher, KaiOS 2.2130.10 or higher.
- Authentication templates cannot be sent to India (+91) numbers.
- Marketing frequency limits are dynamic and not disclosed by Meta.
- Related error codes: 131049, 131051, 131021, 130497.
05How to set up and use error 131026 in HighLevel
Diagnose error 131026
- Send a plain text utility template to the same phone number without any buttons, media, or links.
- Check whether the test message is delivered successfully.
- If it delivers, conclude that the recipient’s WhatsApp version is too old and request an app update.
- If the test also fails, assume the number is not on WhatsApp, has been disconnected, or has blocked your business number, and remove it from active contacts.
- Determine whether the failure occurs for a single number or for many contacts.
- If only one number fails, treat that contact as possibly invalid, blocked, or lacking accepted terms of service.
- If many contacts fail on marketing templates, suspect Meta’s marketing frequency capping and try sending utility messages instead.
- Verify phone number formatting, confirm the correct template category for India (+91) numbers, and check Meta’s platform status for outages.
Resolve identified cause
- If the number is not on WhatsApp, delete it from your contact list or validate it with a phone number service before future sends.
- If the contact has blocked your business number, cease sending messages to that number.
- When the recipient has not accepted Meta’s Terms of Service or Privacy Policy, no action is possible; the user must open WhatsApp to accept them.
- If the recipient’s app version is outdated, first send a simple text only message and then ask the user to update WhatsApp.
- When an Authentication template is being sent to a +91 number, replace the template with SMS, email, or another OTP channel.
- If marketing frequency capping is the cause, send a utility message instead and wait before retrying marketing templates, increasing the interval between attempts.
- For contacts located in restricted or sanctioned countries, remove those numbers from your messaging lists.
- If you attempted business to business messaging, stop using the API for that purpose and open a conversation through the consumer app first.
06Things to know before you rely on it
- Error 131026 bundles many different delivery failures, so the exact reason is not disclosed.
- Meta does not bill for messages that return this error.
- Marketing frequency caps are dynamic and not published; they may cause this error.
- Authentication templates cannot be sent to India (+91) numbers; this restriction cannot be overridden.
- Messages to users in sanctioned or restricted countries are blocked, but Meta does not list those countries.
07If something goes wrong
- Message returns error 131026. Follow the diagnostic steps to isolate the cause, then apply the matching resolution from the cause specific actions.
08How it connects to the rest of HighLevel
- Set up WhatsApp automation workflows in HighLevel WhatsApp workflow guide
- Link a LeadConnector phone number with WhatsApp LeadConnector number guide
- HighLevel pricing and plans Pricing page
Michael's take

I would start with phone number validation. Using a service that confirms a number exists on WhatsApp before adding it to a campaign helps address one of the most common causes of 131026 and keeps your list clean.