The WhatsApp notice "This business uses (or is now using) a secure service from Meta to manage this chat" explained: what changed, who can read the chat, and when to block or report.
8 min read
WhatsApp Business API · Compliance · Getting started
Why incoming messages sometimes fail with code 131060, how it ties to WhatsApp Business app coexistence and unsupported linked devices, and why it usually needs no fix.
What Meta's max price feature for marketing messages does, why error 131065 appears in some countries, and how to send once you remove the unsupported setting.
AiSensy's low entry plan and add-on builders against Gallabox's AI-credit plans billed quarterly or yearly. Both vendors' India message prices against Meta's rate card, a worked month for a real-estate brokerage, and the break-even point.
AiSensy and Interakt compared head to head: AiSensy's five-seat entry plan and free tier against Interakt's unlimited agents, both vendors' India message prices against Meta's rate card, and a sample month for a clinic.
Gallabox's AI-credit plans with per-user limits against Interakt's unlimited-agent plans with AI as an add-on. Feature and price table, India message rates, a worked month for an eight-agent Shopify brand, and switching notes.
A neutral Wati vs AiSensy comparison for Indian businesses: plan prices checked on 1 Nov 2026, per-message markup worked out against Meta's rate card, a sample monthly bill, and who should pick which.
Wati bundles AI agents and credits but charges by seat; Interakt includes unlimited agents but sells AI separately. Plans, India message rates, a worked month for a coaching institute and switching notes.
Why a fast broadcast or a busy integration triggers 130429, how many messages per second a number can send, how to build a queue with back-off, and which neighbouring rate-limit codes mean something else.
A field-by-field checklist for 131008: messaging_product, to, type, the message object, template language and media headers, with a broken and a corrected request and a validation habit that stops it reaching Meta.
Why 131009 appears when a field is present but wrong: phone number format, phone number ID, character limits on buttons and list rows, expired media IDs and unsupported enum values, with fixes and a checklist.
131016 is Meta telling you the problem is on its side, for now. How to confirm it on the platform status page, which sends to retry and when, and how to avoid double messages when a request may have half-succeeded.
Where your own business number sneaks into recipient lists (test scripts, store orders, staff alerts, imported contacts), how to find it in a failed campaign, and a filter that keeps it out.
Meta's 131031 has two causes with very different fixes: an account restricted for policy, or data that does not match the account, like a wrong two-step verification PIN. How to tell them apart with the Health Status API and recover.
What the spam rate limit is, how it differs from the pair rate limit, throughput limits and the per-user marketing limit, why retrying makes it worse, and a recovery plan built on quality rating, audience and frequency.
Error 131052 arrives on an incoming message when the image, video, voice note or document a customer sent could not be downloaded. How to read the webhook, how it differs from your own expired download URLs, and what to say to the customer.
Why WhatsApp rejects the media in a message with 131053: unsupported file types such as HEIC and MOV, files over the size limit, links that need a login or send the wrong Content-Type, and stale media IDs, with commands to inspect each one.
Why a number suddenly returns 131057 for a minute, how it links to Meta's automatic upgrade to higher throughput, which webhook tells you the upgrade finished, and how to keep a big send from losing recipients meanwhile.
131063 appears when a business has set disable_marketing_messages_on_cloud_api to true and then sends a marketing template through /messages. What the flag does, how recategorisation triggers it, and the two ways to fix it.
How to fix template sends rejected with 132000: header and button variables that were forgotten, empty CRM fields dropped by code, templates edited after the integration was written, and language versions with different variables.
132005 fails a template send when the text for the chosen language is too long. How to check the translation in WhatsApp Manager, which component limits to test against, and how long product names and Hindi text cause it.
132007 is Meta refusing template content on policy grounds: restricted products, sensitive data requests, misleading wording or risky links. How to rewrite and resubmit, and how it differs from formatting rejections.
Why the Cloud API rejects a template send with 132012 when the count of values is right but their shape is wrong: named vs positional variables, header types, currency objects, and reading the live template first.
What a paused template means: Meta's 3-hour and 6-hour pause rules, why the third low-quality strike disables the template, whether to wait or edit, how to check quality_score by API, and how to fix the audience that caused it.
6 min
Put these guides into practice
Launch WhatsApp campaigns, chatbots and a shared inbox on the official Cloud API, under your own brand.