Home WhatsApp | Connection, templates and sending
πŸ’¬

WhatsApp | Connection, templates and sending

Connect numbers, Meta templates, sending tiers and delivery errors.
Manuela Farias
By Manuela Farias and 9 others
β€’ 18 articles

Master Guide β€” How to connect your WhatsApp number to Cloud Chat

This guide exists to answer a single question: πŸ‘‰ β€œWhich WhatsApp FAQ should I read before integrating my number?” Before starting any integration or migration, read this page. It helps prevent number loss, blocks, configuration errors, and rework. 🧠 Overview: two important points before connecting your number Connecting WhatsApp to Cloud Chat involves the following key points: 1. Identify whether the number is new or existing, and ensure all Meta prerequisites are validated before starting the connection. 2. Choose the integration model (with or without coexistence). Each scenario has specific documentation. πŸ“Œ First step: New number or existing number? πŸ†• New number Never used in: - WhatsApp Business App - Another Tech Provider (e.g., Cloud Chat) - Another WABA on Meta ⚠️ Integration is a sensitive process. Improper implementation can lead to blocking or loss of the number. πŸ‘‰ Be sure to read before migrating: Mandatory prerequisites before connecting a new WhatsApp number πŸ”„ Existing number (migration) Already used in: - WhatsApp Business App - Another Tech Provider (e.g., Cloud Chat) - Another WABA on Meta ⚠️ Migration is a sensitive process. Improper migration can lead to blocking or loss of the number. πŸ‘‰ Be sure to read before migrating: Mandatory prerequisites for WhatsApp number migration πŸ“₯ Import of ticket history (via API) during migration After migration is completed, you can import tickets from another help desk directly via Cloud Chat API. This is recommended for companies that: - Are migrating from another support system - Want to bring old tickets for consultation, auditing, or operational continuity The import is performed via a specific Cloud Chat API endpoint, sending structured ticket data (contacts, dates, messages, and identifiers). πŸ‘‰ Read the full technical documentation with request examples and required structure: Ticket history import πŸ“Œ Second step: Choose the integration model β€” With or Without Coexistence Before starting the connection, you need to decide how the number will operate in your daily operation. πŸ”’ WITHOUT coexistence integration (exclusive API) The number works exclusively via Meta’s official API (WABA) within Cloud Chat. After connection: - All messages are sent and received only through Cloud Chat (or other systems connected to the API) - It is no longer possible to use the number in WhatsApp Business App. Ideal for companies that: - Operate 100% through help desk - Use automations and bots - Do not need WhatsApp on mobile devices - Seek greater stability and operational control πŸ’‘ If you still need to use the number on your mobile, this is not the ideal model. πŸ‘‰ Read the full step-by-step on how to perform the integration: How to connect a WhatsApp number via official API (without coexistence) πŸ” WITH coexistence integration (Mobile + API simultaneously) The number operates at the same time: - In WhatsApp Business App (mobile) - On the official API (WABA) via Cloud Chat This allows maintaining part of the operation on the mobile while Cloud Chat operates in parallel. πŸ“₯ Message history When performing coexistence integration, conversation history from the last 6 months is automatically synchronized and imported into Cloud Chat. This ensures continuity in support, maintaining context of recent conversations already conducted on the mobile. ⚠️ Important: there is a technical limitation in this synchronization, attachments (images, videos, audios, documents) are not imported into Cloud Chat. Workaround: if you need to access old attachments, they should be checked directly on the mobile device within the WhatsApp Business app. πŸ“Œ Where does coexistence appear on the mobile? In WhatsApp Business App, in the Connected Devices area. Cloud Chat will appear as an additional device connected via API. ⚠️ What happens if someone disconnects? If someone with access to the mobile removes the connected device: - Cloud Chat will immediately stop receiving messages - The entire connection process will need to be redone ⚠️ Important limitation of coexistence Messages sent by unsupported apps by Meta are not reflected in Cloud Chat. Examples of unsupported apps: - WhatsApp Desktop (Windows) - WhatsApp on WearOS These messages remain visible on the main mobile but do not generate webhooks, so they do not appear in Cloud Chat. πŸ‘‰ To understand in detail why this happens, how to diagnose, and what are the alternatives, visit: Messages do not appear in Cloud Chat? Understand coexistence limitations Ideal for companies that: - Still need to operate through the mobile - Have salespeople, consultants, or account managers using the mobile app - Want to automate support gradually - Wish to test the API without giving up the app πŸ‘‰ Read the full step-by-step on how to perform the integration: How to connect a WhatsApp number with coexistence (mobile + API) ❌ Common errors this guide helps avoid - Starting integration without validating WABA status - Not disabling Two-Step Verification before migration - Not understanding the limitation of WhatsApp Desktop in coexistence - Confusing a new number with a migrated number - Not validating the payment method when required

Last updated on Sep 22, 2026

WhatsApp Templates: Structure Rules, Categorization (Authentication, Utility, and Marketing), and How to Avoid Rejection

πŸ“Œ This article is about Meta's rules This guide explains Meta's official rules that impact template approval: - Structure (Header, Body, Footer, Buttons) - Proper use of variables (placeholders) - Difference between Authentication, Utility, and Marketing - Main reasons for rejection - Checklist to increase approval chances If you want to learn how to create, edit, or delete templates within Cloud Chat, access: WhatsApp Templates Guide in Cloud Chat: Creation, Editing, and Approval 🧩 What is a template Pre-approved messages by Meta for messages initiated by the company (e.g.: notifications, transactional updates, authentication, and campaigns), usually used when you need to send messages after the 24-hour window. We also include official references from Meta documentation on template categorization: https://developers.facebook.com/documentation/business-messaging/whatsapp/templates/template-categorization 🧱 Template structure (components) A template consists of up to 4 main blocks: Header, Body, Footer, and Buttons. 🧷 Header (optional) Text: up to 60 characters and supports 1 variable. Media: can be configured as image, video, or document (see details in β€œAttachments”). πŸ“ Body (mandatory) Main text of the template. Supports variables. Limit: up to 1024 characters. 🧾 Footer (optional) Short notes (e.g.: β€œDo not reply to this message”). Limit: up to 60 characters. πŸ”˜ Buttons (optional) Templates can have up to 10 buttons (depending on type/category). ⚠️ Display caution: if there are more than 3 buttons, WhatsApp may show only some and group the rest under β€œSee all options”. πŸ”’ Variables (placeholders): rules that most lead to rejection Variables allow personalization (e.g.: customer name, ticket number, status). βœ… Mandatory rules (Meta validation) 1. Cannot start or end with a variable Meta blocks creation when the template begins or ends with a placeholder. βœ” Correct: Hello {{name}}, your ticket {{ticket}} has been updated. ❌ Incorrect: {{name}} your ticket has been updated. Your ticket has been updated: {{update}} 2. Variable cannot be β€œleft alone” (without context) Avoid templates that are just a placeholder (e.g.: {{test}}) or with overly generic text. This greatly increases rejection risk due to low quality or ambiguous use. 3. Variable name pattern Must be within {{ }} and cannot contain accents or spaces. If you need to separate words, use an underscore: βœ” {{reference_month}} ❌ {{mΓͺs de referΓͺncia}} 🧭 Categories (according to official Meta documentation) When creating the template, you choose the category: Authentication / Utility / Marketing. ⚠️ However, Meta analyzes both content and message intent. It may: - Reclassify automatically - Reject the template if the category is not compatible Official documentation: https://developers.facebook.com/documentation/business-messaging/whatsapp/templates/template-categorization πŸ” Authentication Use for verification codes (OTP) and authentication flows. βœ” Should include: - Verification code - Expiration information - Login or security context ❌ Cannot contain: - Promotion - Offer - Upsell Example: Your verification code is {{code}}. It expires in {{time}} minutes. 🧾 Utility (Utility / Transactional) According to Meta documentation, Utility should: - Be related to a previous user action - Be operational or informational - Not contain promotional content - Lack persuasive language - Not aim to generate new conversion πŸ”Ž Main reasons for rejection as Utility 1. Vague language ❌ β€œWe have news for you” ❌ β€œCheck out this special update” 2. Disguised promotional language ❌ β€œEnjoy your next purchase” ❌ β€œDon’t miss this opportunity” 3. Lack of transactional context If it's not clear what action the user performed, Meta tends to classify as Marketing. βœ… Best practices for approval as Utility βœ” Clearly mention the context: - Order - Protocol - Ticket - Appointment - Subscription - Payment - Delivery βœ” Include a clear identifier: - Order number - Ticket number - Protocol - Transaction ID βœ” Use objective and neutral language βœ” Focus on informing, not persuading βœ” Correct example (Utility with higher approval chance): Hello {{name}}! Your order {{order_id}} has been shipped and is on its way. Estimated delivery: {{delivery_date}}. βœ” Correct example (Support): Hello {{name}}, your ticket {{ticket}} has been updated: {{update_text}}. If you need to add information, reply here. ❌ Example that could be reclassified as Marketing: Hello {{name}}! Your order is ready. Take a look at our new offers! πŸ“£ Marketing Includes: - Promotions - Offers - Coupons - Re-engagement - Launches - Cross-sell / Upsell Practical rule: If the message tries to generate new revenue or conversion β†’ it's Marketing. πŸ“Ž Attachments in the template (Media Header) πŸ–ΌοΈ Image: JPEG or PNG up to 2MB 🎞️ Video: MP4 or 3GP (H.264/AAC) up to 2MB πŸ“„ Document: PDF up to 2MB 🎬 GIF: treated as MP4 (approximate limit of 3.5MB; larger might turn into video). βœ… Quick checklist before submission - Context-specific and tailored Body - Neutral language if Utility - Transactional identifier included - No promotional terms (for Utility) - Header text: up to 60 characters and 1 variable - Check media format and size - Create per language/locale - Validate placeholders (do not start/end with a variable) ❓ Frequently asked questions Why did Meta change my category? Because categorization is based on content + intent. If there is any indication of promotion, persuasion, or conversion attempt, the message may be classified as Marketing, even if you select Utility. My template was rejected as Utility. What to check first? 1. Remove any commercial tone 2. Include clear user action context 3. Add transactional identifier 4. Make the text more objective and less generic For more details on managing templates in Cloud Chat: https://cloudchat.cloudhumans.com/hc/cloud-chat/articles/1754505671-gestao-de-templates-whats_app

Last updated on Feb 25, 2026

WhatsApp Templates: Create, Edit, Delete, and Builder Usage

Overview The Cloud Chat WhatsApp template builder has received a new form with live preview, instant validation, and a rejected templates panel by Meta. Now, you can assemble messages with the full range of buttons supported by Meta β€” quick reply, URL, phone, and the new Copy Code (coupon the customer copies with one click). Templates under review (status PENDING) are now editable, and document attachments now preserve the filename for the recipient. The idea is to solve the most common template issues without needing to open Meta Business Manager β€” especially useful for teams without access to the Meta dashboard because it is managed by another department. :::info This article covers the use of the template builder within Cloud Chat. To understand Meta's official rules on structure, categories, and rejection reasons, go to WhatsApp Template Rules (Meta): categories, structure, and rejections. ::: What are WhatsApp templates? Templates are pre-approved by Meta messages that allow your business to initiate conversations with customers. They are required for: - Sending promotions and campaigns - Confirming orders and appointments - Sending verification codes - Notifying about deliveries Prerequisites - Be an administrator of the Cloud Chat account - Have a WhatsApp inbox configured already Where to find it Settings β†’ Inboxes β†’ select a WhatsApp inbox β†’ Templates tab. From here, you can: - Create a new template - Edit PENDING (under review) and APPROVED (approved) templates - View rejection reasons for REJECTED templates - Delete templates - Manually sync status with Meta How to create a template How to use the WhatsApp template builder in Cloud Chat 1. Click Add template. 2. Fill in the basic information (name, category, language). 3. Assemble the template components (header, body, footer, buttons) β€” all optional except for the body. 4. Monitor the live preview next to the form (or below on mobile) to see how the template will appear on WhatsApp. 5. Click Save. The template is sent to Meta and remains in PENDING status until reviewed. :::info The Save button remains disabled until all fields are valid. If it’s gray, scroll through the form to find the highlighted error in red. ::: Basic information | Field | Rules | | --- | --- | | Name | Lowercase letters, numbers, and underscore. No spaces or accents. | | Category | Marketing, Utility, or Authentication. | | Language | Content language (e.g., Portuguese (Brazil), English, Spanish). | Category affects rules: Authentication templates do not accept header, footer, URL buttons, or Copy Code β€” only quick reply buttons. :::info Recommended name pattern: category_purpose (e.g., order_confirmation, promotion_black_friday). Avoid accents, spaces, and uppercase letters β€” names like Black Friday Promotion do not pass validation. ::: Header (optional) Single type per template. Four options: | Type | What appears | Max limit | | --- | --- | --- | | Text | A bold text line above the body | 60 characters, with up to 1 variable | | Image | Large image at the top of the message | JPG or PNG, up to 5 MB | | Video | Inline playback video | MP4, up to 16 MB | | Document | Attachment (PDF, spreadsheet, etc.) with visible filename | PDF, up to 100 MB | For media (image, video, document), upload the sample file β€” Meta uses this file to review the template. When sending a campaign, you can replace it with the final file. :::success The uploaded filename is preserved for the recipient in Document attachments. ::: Body (required) The main message text. Accepts variables in the format {{...}} for personalization. Two formats of variable: | Format | Syntax | Recommended use | | --- | --- | --- | | Positional | {{1}}, {{2}}, {{3}} | Simple templates, API integrations by position | | Named | {{customer_name}}, {{coupon}} | Templates with many variables, more readable | The format is automatically detected by the body content. Mixing both in the same template is not allowed. Rules: - Limit of 1024 characters - Variables in snake_case (lowercase letters, numbers, underscore) - Cannot start or end with a variable - For each variable, a sample value must be provided (used by Meta during review) Footer (optional) Short text below the body, no variables. - Limit of 60 characters - Useful for signatures, legal notices, or instructions like "Reply STOP to unsubscribe" Buttons (optional) Up to 10 buttons in total. Four available types: | Type | Function | | --- | --- | | Quick reply | Sends a predefined text response when pressed | | Static URL | Opens a fixed URL | | Phone | Initiates a call to the configured number | | Copy Code | Copies a code (coupon, voucher) to clipboard when pressed | Limits by category: - Marketing / Utility: up to 10 buttons. Can mix types. - Authentication: only quick reply buttons. Copy Code button Displays a button that, when pressed, copies a code to the recipient's clipboard. Ideal for coupons, vouchers, promotional codes. - Available for Marketing and Utility categories - The current version uses static code (same code for all recipients) Live preview Next to the form (or below on smaller screens), a simulation of how the template will arrive on WhatsApp is shown: - Header, body, footer, and buttons in actual order - Variables appear with example values filled - Media attachments display the preview Template statuses Templates appear in the list with a colored badge: | Status | Color | Meaning | | --- | --- | --- | | APPROVED | Green | Approved by Meta β€” ready to use | | PENDING | Yellow | Under review by Meta β€” can be used and edited | | REJECTED | Red | Rejected by Meta β€” open the template to see the reason | | PAUSED | Gray | Paused by Meta (usually due to low usage quality) | :::info Meta's review typically takes a few minutes but can take up to 24 hours in rare cases. Cloud Chat automatically synchronizes the status. ::: When a template is rejected REJECTED templates show a dedicated panel at the top of the edit modal with: - Rejection reason in pt-BR (translated from Meta codes) - CTA "Edit and resubmit" opening the correction form - If the rejection code is not yet mapped, a generic fallback with the original code is shown :::info To understand why Meta rejected it and how to improve the content, see WhatsApp Template Rules (Meta). ::: Flow: 1. Open the rejected template from the list. 2. Read the reason in the red panel. 3. Click Edit and resubmit. 4. Adjust the content according to the indicated reason. 5. Save β€” the template returns to PENDING and Meta will review it again. Editing templates under review (PENDING) Templates in PENDING are editable. Saving will restart Meta's review. :::warning The yellow badge in the status field serves as a reminder: editing a PENDING template restarts the review. Use this if you notice a mistake shortly after creating the template. ::: How to delete a template 1. Find the template in the list. 2. Click Delete. 3. Enter the exact template name to confirm. 4. Click Yes, Delete. :::error Deletion cannot be undone β€” Meta retains the template name for 30 days before permanent deletion. During this period, you cannot create another template with the same name. ::: Frequently Asked Questions Can I use variables anywhere in the template? In the body, yes β€” as long as they are not at the beginning or end. In the header, up to 1 variable. Footer does not accept variables. Can I mix positional ({{1}}) and named variables ({{name}}) in the same template? No. Cloud Chat detects the format based on the body content and enforces consistency β€” what is in the body must also be in buttons and header. What happens if I edit an approved template? It reverts to PENDING and undergoes review again. Campaigns using the template continue to work during review. Meta limits edits to 1 per day and 10 per month per template β€” if exceeded, saving fails until the window resets. Does Copy Code support different codes per recipient? Currently, no β€” the code is static and set in the template. Support for unique codes per message is planned for a future phase. Why was my template rejected even if it passed Cloud Chat validation? Cloud Chat validation covers Meta's structural rules (sizes, formats, syntax). Meta also applies content quality criteria (promotional language, formatting, context) that can only be assessed during final review. The rejection panel shows the specific reason. For details on each rejection reason, see WhatsApp Template Rules (Meta). Can I create Authentication templates with Copy Code button? No. Authentication templates only accept quick reply buttons. For OTP codes, consider using the Utility category. Common errors "Name already exists" A template with that name already exists β€” including in the 30-day retention period after deletion. Choose a different name. "Invalid name format" The name has special characters, spaces, or uppercase letters. Use only lowercase letters, numbers, and underscore. "Edit limit reached" Meta limits edits on APPROVED templates to 1 per day and 10 per month (per template). Wait for the window to reset. "Template cannot be edited" Appears when Meta has not yet released the editing window (usually in PAUSED). Manually sync to ensure the status is updated and try again. Best practices :::success Use the live preview as a visual checklist. Before saving, review the preview and ask: Is the message clear? Are variables in the right places? Does the button have the expected text? ::: :::info Fill in realistic examples in variables. Meta uses these values for review β€” generic examples like "test" or "abc" increase the chance of rejection. ::: :::warning Marketing templates have more rigid criteria. If possible, classify as Utility when the message is transactional (order confirmation, consultation reminder, status update). ::: Official Meta documentation For detailed rules on template structure, categories, and rejection reasons, see Meta's documentation: - Meta Developers β€” Message Templates

Last updated on May 27, 2026

How to Avoid Blocks and Bans on WhatsApp

How to Reduce the Risk of WhatsApp Blocking? - 🚫 Avoid sending messages to many different contacts right at the start. - πŸ” Request opt-in before promotional campaigns ("Want to receive news"). - πŸ’¬ Use personalized messages that encourage responses. - πŸ“† Warm up the number before starting (use it normally for a few days). - 🧠 Avoid repeating patterns from previous numbers (name, photo, text). - πŸ›‘ Never send messages without providing an opt-out option. - ⚠️ If more than 3% mark your message as spam, the number could be banned. - πŸ§ͺ The algorithm changes. The only foolproof strategy is to adapt constantly. Introduction WhatsApp is one of the main communication tools in Brazil β€” and also one of the most regulated. The platform follows strict criteria to identify suspicious behavior, aiming to protect users from spam, scams, and unwanted content. Therefore, it is essential to understand the main factors that can lead to number blocking and how to protect yourself. Below, we share field lessons learned from analyzing and operating thousands of accounts over recent years, along with updated, easy-to-apply recommendations. What are the main reasons for bans? 1. High recipient turnover WhatsApp detects suspicious behavior when a number tries to send messages to many different contacts in a short period β€” especially if these people have never interacted with that number before. Practical tip: Start slowly. Send messages in a gradually increasing rhythm, prioritizing contacts who have already interacted with you. 2. Suspicious content or overly standardized messages Message content is analyzed by machine learning algorithms. Words like "invoice," "PIX," "card," among others related to financial transactions, increase the risk β€” especially if sent without context or real interaction. Practical tip: Avoid sending generic messages to large bases. Prefer personalized approaches with responses encouraged. Phrases that invite customer interaction reduce the chances of being blocked. 3. New numbers without history Recently activated accounts that start sending bulk messages tend to be banned more quickly, even if the sending is manual or via WhatsApp Web. Practical tip: Use the number normally for a few days before starting campaigns. Send messages to known contacts, interact via the app, and fill out the profile with name, photo, and description. 4. Reusing patterns after blocking It’s common to reactivate a new number after the previous one is banned and repeat the same strategy (photo, name, messages, etc.). This facilitates profile association and leads to near-immediate ban. Practical tip: Change profile photo, name, and communication style. Also vary initial timings and recipients. The goal is not to appear as a direct continuation of the previous number. 5. Complaints and spam markings If more than 3% of recipients of a campaign mark your message as spam, the number may be suspended or banned. Practical tip: Always provide a clear opt-out option (e.g., β€œReply 2 to unsubscribe”) and monitor responses to automatically exclude these contacts. Additional effective strategies βœ… Build the "maturation" of the number Before automation, use the number organically. Talk with real contacts, participate in groups, respond to messages. βœ… Request opt-in before sending promotions Only send promotional messages to those who explicitly authorized it. This can be done via form, checkbox, or the simple β€œWant to receive promotions” in WhatsApp itself. βœ… Start with WhatsApp Web Use the number first on WhatsApp Web before connecting it to your platform. This signals that a human is behind the account. βœ… Vary message content Use dynamic attributes (client's name, purchase data, date, etc.) or shuffle sentences to avoid identical repetitions. βœ… Avoid sudden sending peaks If scaling a campaign, distribute message volume throughout the day or week. Platforms with automatic queues help control this rhythm. What doesn’t work (or works less than you think) - ❌ Constant IP rotation: may help in some cases but doesn't resolve issues related to content or number behavior. - ❌ Recycled numbers: previous history matters. A number previously used for spam can be banned even with few messages sent. - ❌ Changing numbers without changing approach: repeating previous patterns causes automatic tracking. Conclusion There’s no magic formula β€” WhatsApp’s algorithm is constantly evolving. What truly matters is: - The quality of the contact database. - The context and personalization of messages. - Real interaction with users. Businesses that build relationships with customers, respect consent, and maintain a healthy frequency have near-zero block rates.

Last updated on Feb 25, 2026

What is the limit of connected WhatsApp numbers and how to increase it?

What is the limit of numbers on WhatsApp Business Platform? When you use the official WhatsApp API (WABA), your account has a limit on how many phone numbers can be added and connected. This limit is controlled by Meta based on technical and reputational criteria. What is the initial limit? - If the Business Manager is not verified, the default limit is: 2 numbers per WABA - If the Business Manager is verified, the limit can be increased to up to 20 numbers, but this is not automatic Important: Even after company verification, Meta may maintain the limit at 2, 5, 10, or another value below 20, depending on a combination of criteria (see below). It is possible to increase the volume to more than 20 lines, but as you'll see below, you will need to open a support ticket with Meta to request this exception. What criteria influence the limit? In addition to company verification, Meta also considers: Technical and reputational criteria: - History of API usage (stability, message volume) - Compliance with business policies - Message quality and user experience - Absence of blocks, complaints, or abusive behaviors - Ability to support and operate multiple numbers Subjective/behavioral criteria: - Relevance of using multiple numbers for the business model (e.g., franchises, departments) - Type of operation (e.g., multi-brand, different countries) - Company or partner agency's level of structure Conclusion: Company verification is necessary, but does not automatically guarantee 20 numbers. The unlock also depends on reputation and operational consistency. How to know if your account is verified? Access the Meta dashboard: https://business.facebook.com/settings/info - If it shows as β€œVerified”, you have met the first prerequisite. - If not, click on β€œStart verification” and follow the steps with documents and domain. How to request a limit increase? If your account is not verified yet: 1. Access the link above and complete the verification. 2. The account will be analyzed and the limit may be adjusted automatically or maintained with restrictions. If your account is already verified, but you: - Still have a limit of 2 or 5 numbers - Or have reached 20 numbers and need more You will need to open a support ticket with Meta. How to open a support ticket to request a limit increase The best and fastest way is if you are a Meta client with an Account Manager, who can help you and open a ticket directly with that person. If that’s not your case (or your account manager is unresponsive), access: https://business.facebook.com/business/help/support Feel free to use this message template: Subject: Request to increase the number of connected numbers on WABA Hello, I would like to request an increase in the number of phone lines we can add to our WhatsApp Business account (WABA). Our Business Manager is verified, and we are using the current limit. The operation requires more numbers due to our model (e.g., multi-brand, countries, different departments). Business Manager ID: [insert here] WABA account ID: [insert here] Thank you for your support. We are available for any further information. Useful links - Business Manager Verification - Meta Help Center for WhatsApp Business - Open support ticket on Meta - Guide to adding numbers to WABA - Understanding message sending tiers

Last updated on Feb 25, 2026

What is "Coexistence" on WhatsApp (WABA + Phone)?

Coexistence is a Meta feature that allows the same WhatsApp number to be used simultaneously on a phone (via WhatsApp Business App) and through tools that use the official WhatsApp API (WABA)β€”such as Cloud Humans. In other words: You can continue to use the number on your phone normally and at the same time automate messages or support via the official API with solutions like ClaudIA, CloudChat, or Controlled Flow. How does it work in practice? With coexistence enabled: - On the phone (WhatsApp Business App): you can still send and receive messages manually, as usual. - On the official API (WABA): you can use bots, helpdesks, system integrations, automated sends, etc. - Both access the same conversation history. Important: synchronization between phone and API is in real-time. If someone replies via the phone, the system on the API sees it. If ClaudIA responds through the API, it appears in the app. What changes for Cloud Humans users? You can use: - ClaudIA for automating part of support via API; - CloudChat as a helpdesk with human agents; - Controlled Flow to fetch data from your system and respond via API; - Keep groups (they won't work in Cloud Chat because it doesn't work via API, but they remain on the phone); - And continue using the number on the phone as a support tool for the team. This is great for teams that want to gradually automate support or keep part of manual support on the phone while testing AI. For example: salespeople or account managers who need the phone. How to enable coexistence? Follow the step-by-step in this FAQ or contact our support. What are the main use cases for coexistence? - Gradual transition to the API without losing phone use. - Small teams using the phone as support but wanting to automate part of the support. - Testing automations or bots while still having human support via the app. - Manual redundancy/backup in case of automation issues. Are there limitations? Yes, some: - The experience on the phone may become slower if many flows are running through the API. - It's not possible to send messages simultaneously via phone and API to the same contactβ€”sessions might conflict. - Some advanced API features (like templates with buttons or interactive media) are not fully visible on the mobile app as they are on the Cloud Humans system. - Groups are still not supported by the official API (meaning they only exist on the phone). - ⚠️ Messages sent or received on unsupported devices (like Windows WhatsApp Desktop or WearOS WhatsApp) are not reflected in Cloud Chatβ€”even though they remain visible on the main phone. This is because Meta does not generate webhooks (smb_message_echoes) for these devices. For more details, see the article: Coexistence Limitation: messages from unsupported apps by Meta (e.g., WhatsApp Desktop) are not reflected in Cloud Chat. πŸ“˜ Important: WhatsApp Web (browser) is supported, and messages continue to be reflected normally via API. Is Cloud Humans compatible with coexistence? Yes! All our platform (ClaudIA, CloudChat, and Controlled Flows) is 100% compatible with coexistence, but you need to be using CloudChat. How many numbers can I connect via API? How to increase the limit? By default, each verified account starts with an initial limit of 2 WhatsApp numbers connected via the official API (WABA). To increase this limit, Meta automatically assesses certain criteria: - Significant usage volume (at least 1,000 conversations initiated by the company in 30 days). - High message quality (low block/reports rate). When these criteria are met, your limit may automatically increase to up to 20 numbers. If you need more than 20 numbers, you must contact Meta support directly via Enterprise Support. We created a specific FAQ about limits (line limits) that you can access here. More information is available on Meta's site: https://developers.facebook.com/docs/whatsapp/cloud-api/phone-numbers/?utm_source=chatgpt.com Useful links - Meta official page on Coexistence (WhatsApp Business App + API) - Migration and support guide for the official WhatsApp API

Last updated on Sep 01, 2026

How to connect a WhatsApp number with coexistence (App + API)

When to use - You already use the number on the WhatsApp Business App (mobile) and want to continue using it - You want to test the API and automations without giving up manual use via mobile - Your team (salespeople, consultants, account managers) needs to continue using the mobile - You want a gradual transition to the API without disrupting current operations Important limitation of coexistence: unsupported devices Meta has an official limitation in the coexistence model: messages exchanged through WhatsApp Desktop (Windows) or through WhatsApp on WearOS do not arrive in Cloud Chat β€” even if they appear on the phone, they also do not reach the recipient. This limitation only affects coexistence; in the non-coexistence model (exclusive API), the problem does not exist. Typical customer report: Messages sent by the agent are not reaching the customer. Customer messages appear on the phone but not in Cloud Chat. :::info Technical details in the Meta official documentation β€” in summary, these apps do not trigger the webhook smb_message_echoes that the API uses to mirror the conversation. ::: How to work around Switch to the NON-coexistence model (exclusive API): all messages pass through the API, there is no more device conflict, and the number stops working on the mobile. Step-by-step guide: How to connect a WhatsApp number via official API (without coexistence). Prerequisites :::error Starting integration without validating the points below may result in number loss, block by Meta, verification errors, or the need to redo the entire setup. ::: :::warning Migrating an existing number? Read the migration guide first β€” mandatory reading. If the number you want to connect is already active on another support platform or provider (BSP), DO NOT start the Embedded Signup process before reading: Migrating WhatsApp to Cloud Chat from another support platform Skipping this step may result in: - Verification failure and stuck migration - Inability to release the number from the previous provider - Having to redo the entire setup from scratch The migration guide shows all the Meta prerequisites (WABA ownership, Two-Step Verification, Business Manager status, payment method, message history) that must be validated before starting the integration in Cloud Chat. ::: :::warning New number? You need to warm it up before trying to integrate. Meta evaluates the usage history of the number before authorizing the connection via API. Newly created numbers, without history on the WhatsApp Business App, may be blocked immediately in the Embedded Signup β€” Meta returns the error: "Your phone number is not qualified to connect to the WhatsApp Business platform. More activity in the WhatsApp Business app is required to determine qualification." How to warm up before integrating: - Use the number on the WhatsApp Business App (mobile) for several days/weeks, receiving real conversations - Promote the number on your channels (website, social media, email) to generate organic entry - Respond within the 24-hour window, without spam, repeated messages, or suspicious links After warming up, the number enters the API with better tier and Quality Rating, and the Embedded Signup proceeds without the above error. Official Meta documentation: Messaging Limits Β· Quality Rating. ::: :::warning Validating Business Portfolio status The Business Portfolio must have the status "Verified" in Meta. This means Meta has recognized and validated your company's identity. Why does this matter? Without verification, you are subject to very low sending limits (up to 250 messages/day), cannot migrate numbers from other providers, and may have restrictions on API functionalities. Verification is the first requirement for healthy operation on Meta’s platform. How to verify: 1. Visit ++business.facebook.com/settings/info++ 2. Check the Verification Status field 3. It should be "Verified" βœ… If it shows "Not Verified" or "Pending", click Start Verification and follow the process with company documents and domain validation before proceeding. ::: :::warning Not using WhatsApp Business App on mobile? Coexistence is designed for those maintaining an active number on the mobile (WhatsApp Business App) alongside the API. If you won't use the number on the mobile β€” only in Cloud Chat / API β€” this model doesn't make sense. Use the non-coexistence method: How to connect a WhatsApp number via official API (without coexistence) ::: :::warning Number already registered and active on WhatsApp Business App (mobile) before starting β€” coexistence only works if the number was already linked and in use in the app before Embedded Signup. If the number is not yet in the WhatsApp Business App, install the app and register the number. ::: Step-by-step integration with coexistence :::info Once all prerequisites above are validated, you can start the integration. Have on hand: - Be administrator of the Cloud Chat account - Admin access to the Business Portfolio on Meta (necessary to authorize the connection during Embedded Signup) - A mobile device with WhatsApp Business App to scan the QR code during synchronization - Credit card enabled for USD payments β€” mandatory for migration or proactive campaigns ::: Step 1 β€” Access Cloud Chat Settings 1. In Cloud Chat, go to Settings 2. Navigate to Inbox section Step 2 β€” Start creating the WhatsApp inbox 1. Click Add Inbox 2. Select WhatsApp 3. In the WhatsApp Channel screen, choose Embedded Signup provider and fill in the desired name for the inbox. Then, click Enter via WhatsApp Step 3 β€” Authenticate with Meta In the Meta pop-up window that opens, log in with the personal Facebook account of the person who has admin access to the company's Business Portfolio in Meta. :::warning The login is not done with a generic corporate email or a "company account" β€” it’s with the personal Facebook of the person who is an admin of the Meta Business Portfolio. Without this admin permission, the Embedded Signup flow cannot authorize the connection, and the process will get stuck at this step. ::: 1. After logging in, click Continue Step 4 β€” Select Business Portfolio and enable coexistence 1. Choose the Business Portfolio in Meta and click Next 2. Select Connect existing WhatsApp Business App and click Next Step 5 β€” Verify the number 1. Select Add a new number, enter the phone number, and verify it :::warning If the number is a landline or digital number, verification must be done via phone call, not SMS. ::: Step 6 β€” Synchronize with WhatsApp Business App via QR code 1. After verification, click Finish to start synchronization with WhatsApp Business App 2. Open WhatsApp Business on the mobile, scan the QR code, and follow the instructions on the device Importing contact and message history During integration, the mobile will receive a notification asking to import the number’s history. Confirming, Meta automatically syncs the message and contact history of the last 6 months to Cloud Chat. :::warning Although import is documented in Meta’s official documentation, recent observations show Meta may not send the complete history at the time of synchronization. Some messages or contacts might not be imported. This behavior is intermittent and outside Cloud Chat's control, depending on Meta’s delivery. Keep parallel records if necessary. ::: Step 7 β€” Set up payment (if applicable) :::error When payment method registration is MANDATORY: - Number migration β€” always mandatory, no exceptions. Without a valid payment method, Meta does not complete the WABA migration. - Proactive messaging (template / campaign / single message via API) β€” mandatory, because Meta charges for templates sent outside the 24h window. - Reopening the 24h window β€” mandatory. To start a new conversation outside the active window, a template must be sent, which incurs a direct cost charged by Meta to the registered card. - Satisfaction survey (CSAT) β€” CSAT message is also a Meta template. If sent outside the 24-hour window (common if the customer doesn’t respond immediately), without a registered payment method, the CSAT is not sent β€” the customer does not receive the evaluation question, and the metric remains empty. Without a valid card registered in WABA, no proactive message is sent, no window is reopened, and no CSAT is delivered outside the window β€” the number is limited to replying within 24h after the last customer message. ::: 1. Click Add Payment Method to add the payment method to WABA. For purely reactive support (responding within the 24h window, without proactive sends or migration), click Finish. Step 8 β€” Add agents to the inbox 1. Configure agents who will have access to the new inbox 1. Click Add Agents :::success The inbox with coexistence is integrated and ready to use. βœ… ::: Notes :::error Cloud Chat appears on the mobile as connected device, in WhatsApp Business App β†’ Connected Devices If someone removes Cloud Chat from the device list on the mobile, the integration will be broken and the entire process must be redone. ::: - Meta templates: for any proactive send or 24h window reopening, a valid card and approved template are required β€” see Meta WhatsApp Template Rules and How to create, edit, and delete WhatsApp templates in Cloud Chat - Payment method is mandatory for migration, proactive sends, and 24h window reopening β€” for reactive support within the active window, it is not required at setup. - Official Meta documentation: Meta Developers β€” Embedded Signup with Coexistence

Last updated on May 08, 2026

How to connect a WhatsApp number without coexistence (API-only mode)

When to use - You want to connect a number to Cloud Chat that will operate exclusively via API, without a phone - You are creating a 100% digital operation, with helpdesk or automation support - You do not need to use the number in the WhatsApp Business App on a phone - You want greater stability, without conflicts between devices Prerequisites :::error Starting the integration without verifying the points below may result in number loss, blockage by Meta, verification errors, or the need to redo the entire setup. ::: :::warning Migrating an existing number? Read the migration guide first β€” mandatory reading. If the number you want to connect is already active on another support platform or provider (BSP), DO NOT start the Cloud Chat integration flow before reading: Migrating WhatsApp to Cloud Chat from another platform Skipping this step may result in: - Verification and migration failures or stuck - Inability to release the number from the previous provider - Need to reconfigure everything from scratch The migration guide shows all Meta prerequisites (WABA ownership, Two-Step Verification, Business Manager status, payment method, message history) that need to be validated before performing the Cloud Chat setup. ::: :::warning Number already registered in the WhatsApp Business App on your phone? The non-coexistence integration (this article) does NOT allow the number to continue functioning in the WhatsApp Business App. To proceed here, you will need to: 1. Delete the account of the number in the WhatsApp Business App (delete the app or remove the account inside it) before starting the Embedded Signup 2. Accept that the number will stop working on the phone after the integration β€” all messages will only arrive in Cloud Chat If you want to keep the number working in the WhatsApp Business App alongside Cloud Chat, DO NOT follow this article. Use the coexistence method: How to connect a WhatsApp number with coexistence (phone + API) ::: :::warning New number? It needs to be warmed up before attempting integration. Meta evaluates the number’s usage history before enabling API connection. Newly created numbers, with no history in WhatsApp Business App, may be blocked right at the Embedded Signup β€” Meta returns the error: Your phone number is not qualified to connect to the WhatsApp Business platform. More activity in the WhatsApp Business app is required to help determine qualification. (#3441045) How to warm up before integrating: - Use the number in the WhatsApp Business App (phone) for a few days/weeks, receiving real conversations - Promote the number on your channels (website, social media, email) to generate organic entries - Respond within the 24-hour window, without spam, repeated messages, or suspicious links After warming up, the number enters the API with better tier and Quality Rating, and the Embedded Signup proceeds without the above error. Official Meta documentation: Messaging Limits Β· Quality Rating. ::: :::warning Validating Business Portfolio Status Your Business Portfolio must have the "Verified" status in Meta. This means Meta has recognized and validated your company's identity. Why does this matter? Without verification, your messaging limits are very low (up to 250 messages/day), you cannot migrate numbers from other providers, and certain API features may be restricted. Verification is the first requirement for healthy operation on Meta's platform. How to verify: 1. Access ++business.facebook.com/settings/info++ 2. Check the Verification status field 3. It should be "Verified" βœ… If it shows "Not verified" or "Pending", click Start verification and follow the process with company documents and domain validation before proceeding. ::: Step-by-step guide for API-only integration :::info With all the above prerequisites validated, you can start the integration. For this, have on hand: - Be a manager of your Cloud Chat account - Manager access to the Business Portfolio in Meta (necessary to authorize connection via Embedded Signup) - Access to the number to receive verification code via SMS or call - A credit card enabled for USD payments β€” mandatory for platform migration or proactive messaging ::: Step 1 β€” Access Cloud Chat Settings 1. In Cloud Chat, go to Settings 2. Go to the Inboxes section Step 2 β€” Create a WhatsApp inbox 1. Click Add Inbox 2. Select WhatsApp 3. In the WhatsApp Channel screen, select the Embedded Signup provider and fill in the desired inbox name. Then click Enter via WhatsApp to start the integrated flow Step 3 β€” Authenticate with Meta A Meta pop-up will open; log in with the personal Facebook account of the person who has admin access to the company's Business Portfolio in Meta. :::warning The login is not done with a generic corporate email or a "company account" β€” it is with the personal Facebook of the admin of the business portfolio in Meta. Without this administrative permission, the Embedded Signup process cannot authorize the connection, and the setup will be stuck at this step. ::: 1. After logging in, click Continue Step 4 β€” Select Business Portfolio and start WhatsApp account 1. Choose the Business Portfolio in Meta and click Next 2. Select Start with a new WhatsApp phone number and click Next :::info If you want to connect a number already on WhatsApp Business App (coexistence mode), stop this flow and follow the coexistence integration step-by-step. ::: 3. Select Create a WhatsApp Business Account and click Next Step 5 β€” Configure Business Account and Number 1. Enter the WhatsApp Business Account name, display name, and choose a valid category 2. Select Add a new number, enter the phone number, and verify it :::warning If the number is a landline or digital number, verification should be done by voice call, not SMS. ::: Step 6 β€” Complete and set up payment (if applicable) :::error When payment method setup is MANDATORY: - Existing number migration β€” always mandatory, without exception. Without a valid payment method, Meta will not complete the WABA migration. - Proactive messages (template/campaign/single message via API) β€” mandatory, because Meta charges for templates sent outside the 24h window. - Re-opening the 24h window β€” mandatory. To initiate a new chat outside the active window, a template must be sent, which incurs a direct cost charged by Meta to the registered card. - Customer satisfaction survey (CSAT) β€” the CSAT message is also a template from Meta. If sent outside the 24h window (common if the customer does not respond right after support), without a registered payment method, CSAT is not sent β€” the customer does not receive the survey question, and the metric remains empty. Without a valid card registered in WABA, no proactive message will be sent, no window will be reopened, and no CSAT will be delivered outside the window β€” the number will only be able to respond within 24h after the last customer message. ::: 1. Click Add Payment Method to add your payment method to WABA. For purely reactive support (responding within the 24h window, without proactive messages or migration), click Finish. Step 7 β€” Add agents to the inbox 1. Configure the agents who will have access to the new inbox 1. Click Add Agents :::success The inbox is ready to send and receive WhatsApp messages. βœ… ::: Notes - Migration: if this number is already in use on another platform, DO NOT follow this isolated article β€” start with the Migration Guide to validate Meta's prerequisites before embedded signup - WhatsApp Business App: API integration does not coexist with an active number on the WhatsApp Business App; delete the account before proceeding or use coexistence if you wish to keep the phone active - Meta Templates: for any proactive sending or reopening of the 24h window, a valid card + approved template are required β€” see WhatsApp Template Rules (Meta) and How to create, edit, and delete WhatsApp templates in Cloud Chat - Payment method is mandatory for migration, proactive sends, and window reopens β€” for reactive support within the active window, it is not required at the moment of setup - To keep the number active on your phone in parallel, use the coexistence setup - In case of doubts or errors, contact support before proceeding β€” incorrect adjustments may lead to number blocking - Official Meta documentation: Meta Developers β€” Embedded Signup

Last updated on Sep 01, 2026

Migrating WhatsApp to Cloud Chat from Another Support Platform

When to Use - You are switching from a support platform (Zendesk, Intercom, Zenvia, Twilio, Take Blip, etc.) and need to bring your number along. Pre-requisites :::error Before starting the migration, confirm all the items below. Skipping any of them may result in number loss or blockage by Meta. ::: - Access to the number to receive SMS or verification call - Administrative access to the Meta Business Portfolio - Business Portfolio status: "Verified" - WABA status: "Approved" - Number status: "Connected" - Two-factor verification disabled for the number in WABA (most critical step β€” see below) - Credit card enabled for dollar payments β€” mandatory for platform migration or proactive messages Migration Steps Step 1 β€” Confirm Business Portfolio status Validating Business Portfolio Status The Business Portfolio must be "Verified" in Meta. This means Meta has recognized and validated your company's identity. Why does it matter? Without verification, your sending limits are very low (up to 250 messages/day), you cannot migrate numbers from other providers, and some API features may be restricted. Verification is the first requirement for healthy operation on Meta's platform. How to verify: 1. Visit business.facebook.com/settings/info 2. Check the Verification status field 3. It should say "Verified" βœ… :::warning If it shows "Not Verified" or "Pending", click on Start Verification and follow the process with company documents and domain before proceeding. ::: Step 2 β€” Confirm WABA ownership and validate pre-requisites What is WABA? WABA stands for WhatsApp Business Account β€” it's the entity created by Meta representing your company's official WhatsApp account. It connects a phone number to the official API and links it to a support provider (like Cloud Chat). The WABA always resides within a Business Portfolio in Meta. The owner of this portfolio is essentially the owner of the WABA. :::warning ⚠️ In many cases, the previous provider created and maintains the WABA within their portfolio β€” not yours. This means you lack administrative control over your own number. Before migrating, it is essential to confirm where your WABA is. ::: How to confirm you own the WABA: 1. Access Meta Business Manager 2. In the sidebar menu, go to Settings β†’ WhatsApp Accounts 3. You can locate your WABA either by the number listed or using the search bar. :::success If it appears in your portfolio β†’ you have control. Proceed to validate the pre-requisites below. ::: :::warning If it does not appear (or is in the previous provider’s portfolio) β†’ contact our support team before continuing. It will be necessary to request the transfer of the WABA to your portfolio before migrating. ::: Validating WABA Status: "Approved" With the WABA located in your portfolio, confirm its status is "Approved": 1. Still in WhatsApp Manager, locate your WABA :::success The status should read "Approved" βœ…. Also, a valid payment method should be registered under Payment Settings. ::: :::warning If it shows "Restricted" or "Flagged", the WABA has pending issues with Meta that must be resolved before migration. ::: Validating Number Status: "Connected" The number to be migrated must have a "Connected" status in the WABA: 1. Within WABA, go to WhatsApp Manager. A new tab will open with the list of linked numbers. :::success The number should appear as "Connected" βœ… ::: :::warning If it’s "Disconnected" or "Offline", this needs to be resolved before starting the migration. ::: Step 3 β€” Disable Two-Factor Verification for WABA :::error This is the most critical step and often causes migration issues. ::: Two-Step Verification is a security PIN set on the number within WABA. While active, Meta does not allow the number to be migrated to another provider. How to disable: 1. Access WhatsApp Manager 2. Select the number to be migrated 3. Go to Settings β†’ Two-step verification 4. Click Deactivate :::warning ⚠️ If your current provider controls the Two-Step Verification (common if WABA was created by provider), you must request them to disable it. Without this, migration is not technically possible. ::: Step 4 β€” Start integration with Cloud Chat :::info With all pre-requisites validated, you can begin the integration. Have ready: - Admin access to the Business Portfolio in Meta (necessary to authorize the connection during Embedded Signup) - Access to the number to receive the verification code via SMS or call - A valid credit card for dollar payments β€” during the process, Cloud Chat will create a new WABA linked to your portfolio with Cloud Humans as the partner (Tech Provider) in Meta. This WABA will need a registered payment method. ::: πŸ“Œ How does the WABA created by Cloud Chat work? When integrating, Cloud Chat creates a WABA within your Meta portfolio, with Cloud Humans registered as a partner (Tech Provider). This means you remain the owner of your WABA β€” Cloud Humans only operate as the technical channel connecting to the API. You can unlink at any time without losing the number. Choose the integration model and follow the corresponding steps: - πŸ‘‰ INTEGRATION WITHOUT coexistence (Exclusive API) β€” number works solely via API, no phone required - πŸ‘‰ INTEGRATION WITH coexistence (Phone + API) β€” number works on the phone and API simultaneously :::warning If you're unsure which integration model to pick (with or without coexistence), first read the Master Guide. ::: Step 5 β€” Validate with Cloud support team Before connecting, send us confirmation that all pre-requisites are validated. This ensures immediate support in case of any issues during the process. Notes - Migration time may vary from a few minutes, depending on the previous provider and Meta's response. - After migration, the message history from the previous provider is not automatically imported β€” old messages remain with the previous provider. - If you need to import old tickets into Cloud Chat, it can be done via API. Refer to: Import ticket history. - Never make adjustments if unsure β€” an error during this process may block the number. Contact support before proceeding. - Official Meta documentation on provider migration: Meta Developers β€” Migrating phone numbers.

Last updated on Sep 22, 2026

How to reconnect your WhatsApp inbox in Cloud Chat

When to use this - Your WhatsApp inbox connection was lost and you stopped sending or receiving messages - You received an email letting you know that the inbox was disconnected - You need to update the WhatsApp credentials on the inbox Prerequisites - Be an administrator of the Cloud Chat account - Have access to the Meta (Facebook) account linked to the number's WABA Step-by-step reconnection Step 1 β€” Open the inbox in Cloud Chat 1. In the side menu, go to ConfiguraΓ§Γ΅es β†’ Caixas de Entrada (Settings β†’ Inboxes) 2. Click the WhatsApp inbox you want to reconnect 3. Go to the ConfiguraΓ§Γ΅es avanΓ§adas (Advanced settings) tab Step 2 β€” Start the reconnection 1. In the Reconectar WhatsApp (Reconnect WhatsApp) section, click the Reconectar (Reconnect) button 2. A Meta (Facebook) window will open β€” log in if needed 3. Select the WABA and the phone number you want to reconnect 4. Confirm the authorization and wait for the window to close :::success When the message "WhatsApp reconectado com sucesso" (WhatsApp reconnected successfully) appears, the integration has been restored and the inbox goes back to working normally. ::: Notes - The process only takes a few seconds. - After reconnecting, the internal integration steps run automatically in the background. - If any error occurs, try again. If the problem persists, contact support. - If you suspect the disconnection was caused by manually removing the device (on a coexistence integration), check on your phone whether Cloud Chat still shows up under WhatsApp Business App β†’ Dispositivos Conectados (Linked Devices) before reconnecting.

Last updated on Aug 03, 2026

WhatsApp messaging tiers: what they are and how to move up

When to use this - You want to understand the limit of proactive messages you can send through your WABA - Your account hit the limit and you want to know how to move up a tier - You are planning a campaign and need to size the tier you'll need - Your tier went down and you want to understand why About this article Messaging tiers are the limits on business-initiated messages you can send within a 24-hour window. They are controlled by Meta and apply only to templates (proactive messages). :::info Tiers do not limit incoming messages or replies within the 24-hour window. The limit applies only to conversations started by the business using templates. ::: Tier table | Tier | Conversation limit per 24h | How to get here | |-------------|------------------------------|-------------------------------------------------| | Tier 1 | 1,000 conversations | Starting point for every new verified account | | Tier 2 | 10,000 conversations | Automatic upgrade based on quality and volume | | Tier 3 | 100,000 conversations | Automatic upgrade based on quality and volume | | Tier 4 | Unlimited | Automatic upgrade based on quality and volume | :::warning Unverified accounts start with an even lower limit (250 conversations per 24h) and only move up after the Business Portfolio is verified with Meta. ::: How the tier moves up automatically Meta raises your tier when it detects the following signals: 1. Growing volume β€” you are starting a lot of conversations and getting close to your current limit 2. High quality β€” a low rate of blocks and spam reports from users 3. Consistency β€” regular usage with no suspicious volume spikes The process is automatic: you don't need to request the upgrade, it happens within 24h once the criteria are met. Why did my limit go up? Meta assessed that your account has growing volume + a good quality reputation. That's a good thing β€” it means you can scale your campaigns with more headroom. Why isn't my limit moving up? The most common causes: - High block rate β€” users marking your messages as spam. Above a 3% report rate, the upgrade is blocked and the tier may even go down - Volume still too low β€” you are far from your current limit and Meta sees no need to raise it - Poor template quality β€” templates with overly promotional language or without a clear transactional context tend to generate more reports - Unverified Business Portfolio β€” without verification, the maximum limit is 250 conversations/24h and it does not move up How to track your current tier 1. Go to WhatsApp Manager 2. Select the number you want 3. Click Insights or Phone Number Settings 4. You'll see the current tier and the conversation limit per 24h What if I need more than 1,000 conversations right at the start? :::warning It is not possible to "skip" tiers by direct request. The only way is to grow organically with quality. ::: Some practices that help: - Start with a contact base that has already interacted with you β€” these people are less likely to mark you as spam - Use well-structured templates with clear context (order, ticket, case number) - Monitor the quality metrics in WhatsApp Manager weekly - Avoid sending to cold lists without explicit opt-in Are tiers and the connected numbers limit the same thing? No β€” they are two different things: - Messaging tier: how many conversations per day you can start with one specific number - Numbers limit: how many WhatsApp numbers you can connect to your WABA To understand the numbers limit: What is the limit of connected WhatsApp numbers and how do I increase it? Notes - The tier can go down if quality drops β€” take continuous care of the number's reputation - Tiers are per phone number, not per account or WABA β€” each number has its own tier - To avoid blocks and keep the number's quality up: How to avoid blocks and bans on WhatsApp - Official Meta documentation: Meta Developers β€” Message Sending Limits

Last updated on Aug 03, 2026

FAQ β€” WhatsApp Integration: Frequently Asked Questions

When to use - You have a specific question about WhatsApp integration and want a quick answer - You are in pre-onboarding and want the team's most frequent answers at hand - You want to map out alternative paths before opening a support ticket About the number and the account Do I need a physical SIM card or a cell phone to integrate? Not necessarily. For the integration without coexistence (API only), you don't need a physical SIM card β€” you can use a virtual number. For the integration with coexistence, you need the cell phone with the WhatsApp Business App installed at the time of setup. What is a virtual number? Where do I buy one? A virtual number is a phone number that works without a physical SIM card, purchased online. Cloud Chat recommends BR DID for anyone who needs a virtual number to use with the API. Can I use my personal WhatsApp number? We don't recommend it. The WhatsApp Business API is designed for business numbers. Also, when you integrate without coexistence, the number stops working in the cell phone app β€” which would cause problems if it's your personal number. Can I have two different WhatsApp numbers connected to Cloud Chat? Yes. Each number goes into a separate inbox. By default, a verified account can have up to 20 numbers connected. Details: What is the limit of connected WhatsApp numbers? Can I connect the same number to two tools at the same time (e.g., Cloud Chat and another platform)? :::warning No. A number can only be connected to one API provider at a time. To migrate to Cloud Chat, you must first disconnect it from the previous provider. ::: About the migration Will I lose my message history when I migrate? The message history from the previous provider is not migrated automatically β€” it remains accessible only on the old platform. If you need to import old tickets, you can do so through the Cloud Chat API: Ticket history import. In the integration with coexistence, the last 6 months of history from the WhatsApp Business App is synced β€” but only partially, with no guarantee of completeness (a Meta limitation). My current provider won't release the number. What do I do? Reach out to the Cloud Humans support team β€” there are alternative paths that depend on a case-by-case analysis. Before that, confirm: is the WABA in your Meta Business Portfolio or in the provider's portfolio? If it's in yours, you have administrative control and can migrate on your own. I need to turn off Two-Step Verification before migrating. How do I do it if I don't know the PIN? - If you are the WABA owner β†’ go to WhatsApp Manager and turn it off directly - If the previous provider controls Two-Step Verification β†’ ask them to turn it off :::error Without turning off Two-Step Verification, the migration is not technically possible. ::: About coexistence What is coexistence? Coexistence is the Meta feature that lets you use the same number simultaneously on the cell phone (WhatsApp Business App) and on the official API (Cloud Chat). Details: What is coexistence on WhatsApp. If I use coexistence, what happens if the cell phone runs out of battery or loses internet? Cloud Chat keeps working normally through the API. Coexistence does not depend on the cell phone being active. :::warning If someone manually removes Cloud Chat from the list of linked devices in the cell phone app, the integration will be interrupted and will have to be set up again. ::: My WhatsApp Desktop (Windows) messages don't show up in Cloud Chat. Why? WhatsApp Desktop for Windows and WhatsApp WearOS are not supported by Meta for mirroring through the API in coexistence mode. The messages are visible on the cell phone, but they don't generate a webhook and therefore never reach Cloud Chat. WhatsApp Web (browser) works normally. Details: WhatsApp messages not reaching Cloud Chat? Understanding the coexistence limitation. Can I use WhatsApp groups in Cloud Chat? No. Meta's official API does not support groups. Groups remain visible only on the cell phone (in coexistence mode), but they do not appear in Cloud Chat. About templates and sending What are templates and when do I need them? Templates are messages pre-approved by Meta, used to start conversations with customers or to send messages after the 24-hour window of inactivity. For replies within 24 hours of the customer's last contact, you don't need a template. Why was my template rejected as Utility? Meta reclassifies templates from Utility to Marketing when it detects promotional language, a lack of transactional context, or text that is too generic. To reverse this: - Include a clear identifier (order number, ticket, case number) - Use objective language - Remove any commercial tone Details: WhatsApp template rules (Meta): categories, structure, and rejections. Why can't I send messages to many contacts at once? You have most likely hit the limit of your messaging tier. Every account starts at Tier 1 (1,000 conversations/24h) and moves up automatically as volume and quality grow. Details: WhatsApp messaging tiers: what they are and how to move up. Quick troubleshooting Cloud Chat stopped receiving WhatsApp messages. What should I check? 1. Check whether the inbox is active under Settings β†’ Inboxes 2. If you use coexistence, check on the cell phone whether Cloud Chat still appears under Linked Devices 3. If the device was removed, reconnect it: How to reconnect your WhatsApp inbox in Cloud Chat 4. If the problem persists, contact support My message shows an error. What does it mean? Check the complete guide with causes and actions for each code: Why isn't my message being sent? Complete Error Guide. Notes - To choose the integration model: Master Guide β€” How to connect your WhatsApp number to Cloud Chat. - Meta's official documentation on the WhatsApp Business Platform: Meta Developers β€” WhatsApp Business Platform.

Last updated on Sep 22, 2026

Connecting Your WhatsApp to Cloud Chat (via Twilio)

In this tutorial, you will learn how to start using WhatsApp through Twilio's API in Cloud Chat. Step 1: Begin by navigating to settings. Step 2: Select Inboxes. Step 3: Choose add inbox. Step 4: Then, select WhatsApp. Step 5: In the API provider field, select Twilio. Then, assign an inbox name and the phone number you're integrating. Step 6: You will need your Twilio Account SID and Auth Token, which you can find on your Twilio Account Dashboard. Step 7: Locate your account SID on the dashboard then click the side button to copy it, then paste it into the Account SID field. Step 8: Obtain the Twilio auth token from the dashboard and paste it in the Auth Token field. Step 9: Click on Create Twilio Channel to proceed. Step 10: In this section, you can add the desired agents of your new inbox. Step 11: Copy the generated callback URL, then return to your Twilio account dashboard. Step 12: In your Twilio account, go to Senders -> WhatsApp senders Step 13: Select the number you wish to use for your new inbox. Step 14: Ensure the Messaging Service field is set to None and paste the generated callback URL into the Webhook URL for incoming messages field. Step 15: Click Update WhatsApp Sender. Step 16: Your newly created inbox is now configured. To ensure ClaudIA has the necessary permissions, go to the Collaborators tab. Step 17: In the Agents list, ensure that ClaudIA's agent ClaudIA is assigned to this inbox. Step 18: Enter Automation settings. Step 19: On the Automation list, find the Assign to Claudia automation and click the edit button. Step 20: On the Edit Automation Rule screen, add your new inbox to the list of inboxes highlighted below: Step 21: Repeat the above process with the Message created automation: By following these steps, your Twilio inbox is set up, and you should be able to send and receive messages on your Cloud Chat using the configured number.

Last updated on Sep 02, 2026

Why Is My Message Not Being Sent? Complete Error Guide (WhatsApp, Twilio, and Email)

Sometimes your message may not be sent and an error message appears. We have mapped all cases using the details from Meta about what to do when each specific error appears. Example of how the error message appears. The box will be red and will display a see details link that opens a modal: You can view the error details by clicking see details: Cloudchat displays the details for all error codes from Meta Common Errors and Detailed Explanations πŸ”΄ 131049 – WhatsApp – Policy Violation - Description: Message not delivered to maintain healthy ecosystem engagement - Channel: WhatsApp - What it means: WhatsApp has blocked delivery due to policy violation. - Common Causes: - Content considered spam or of low quality. - High block/report rate from users. - Lack of valid opt-in. - Recommended Action: - Review approved templates and language used. - Improve opt-in collection. - Monitor quality metrics in Meta Business Manager. 🟠 131026 – WhatsApp – Message Undeliverable (generic) - Description: Message Undeliverable - Channel: WhatsApp - What it means: The message could not be delivered, without specific details. - Common Causes: - Invalid, deactivated, or blocked number. - User uninstalled the app. - Temporary error in Meta's infrastructure. - Recommended Action: - Validate numbers before sending. - Ensure updated opt-in data. - Reprocess sends in case of transient error. 🟑 131048 – WhatsApp – Spam Rate Limit Hit - Description: Spam rate limit hit - Channel: WhatsApp - What it means: The account has exceeded the allowed sending limit. - Common Causes: - Sending volume above the quality tier. - Low reputation account. - Recommended Action: - Segment sends. - Monitor reputation metrics. - Request limit review if necessary. 🟑 63024 – Twilio/Email/WhatsApp – Generic API Error - Description: Generic WhatsApp Cloud API error code - Channel: Multichannel (Twilio, Email, WhatsApp) - What it means: A generic API error without detailed cause. - Common Causes: - Network timeout or failure. - Invalid payload. - Transient API error. - Recommended Action: - Implement automatic retries. - Validate payloads. - Escalate to provider support in case of repeated errors. 🟑 130472 – WhatsApp – User Not Eligible - Description: User’s number is part of an experiment / not eligible - Channel: WhatsApp - What it means: The user's number cannot receive messages at this time. - Common Causes: - Number in Meta sandbox/test environment. - User not enabled to receive commercial messages. - Recommended Action: - Confirm number eligibility. - Escalate to provider if recurring. 🟠 #100 – Facebook – Invalid Action - Description: Invalid action (not owner of topic / invalid API call) - Channel: Facebook (API) - What it means: The call made is invalid. - Common Causes: - Incorrect endpoint. - Token without permission. - Invalid parameters. - Recommended Action: - Review payloads and permissions. - Check Graph API documentation. πŸ”΄ 131042 – WhatsApp – Business Eligibility Issue - Description: Payment or account not allowed - Channel: WhatsApp - What it means: The account is not eligible to send messages. - Common Causes: - Business in a restricted category. - Lack of verification in Business Manager. - Pending payment. - Recommended Action: - Resolve billing issues. - Verify eligibility in Meta Business Manager. 🟑 131047 – WhatsApp – Re-engagement Failed - Description: 24h window exceeded – Re-engagement message failed - Channel: WhatsApp - What it means: Message sent outside the 24h window without using a template. - Common Causes: - Response sent after the allowed limit. - Recommended Action: - Use approved templates for re-engagement. - Set up alerts to respect the window. 🟑 Additional Errors (by channel): - Email: - 451 4.7.1 β†’ Rate limit reached on email server. - 535-5.7.8 β†’ SMTP authentication failure. - 003 β†’ Network timeout during send. - 2603 β†’ Network unreachable. - Twilio: - 21617 β†’ Message exceeds 1600 characters. - 63007 β†’ Invalid β€œFrom” channel. - 63018 β†’ Rate limit. - 63049 / 63032 / 63016 β†’ General provider errors.

Last updated on Sep 02, 2026

How to set up single conversation on WhatsApp

When to use - You want every new message from the customer after a resolved conversation to open a new ticket - Your operation treats each interaction as an isolated (non-recurring) event - You prefer more granularity in reports (1 ticket = 1 service interaction) Prerequisites - Be logged in as an administrator - Have a WhatsApp inbox set up About this tutorial In this article you will learn how to configure the single conversation feature in the WhatsApp inbox so that, when a conversation is resolved, it results in a new ticket (instead of continuing an existing conversation forever). Instructional video: https://youtu.be/sB6baeooG28 Step by step Step 1 β€” Access the WhatsApp inbox Settings 1. Go to Settings 2. Click Inboxes 3. Select the WhatsApp inbox Step 2 β€” Enable Single Conversation Scroll to the bottom of the settings until you find Lock to single conversation. Behavior: - Disabled (default) β†’ if the customer sends a new message after the conversation has been resolved, a new ticket is opened. If there is still an ongoing (unresolved) conversation, the message goes into that same conversation - Enabled β†’ the conversation stays the same, with the same owner and the same person replying :::info We recommend keeping this setting disabled, except in very specific cases that require a single conversation. ::: Remember to Update the settings at the end. Notes - To understand CSAT and configure it: How to configure CSAT per channel and view results - To understand ticket statuses (Open, Resolved, etc.): Ticket statuses in Cloud Chat - To configure the auto-close time: Automatic ticket resolution

Last updated on Sep 02, 2026

How to replicate WhatsApp templates between WABAs via API

When to use it? When you need to move your WhatsApp templates from one WhatsApp Business Account (WABA) to another. For example: number migration, a company with more than one WABA that wants the same templates in all of them, or a change of portfolio in Meta Business. Meta has no "duplicate" button between accounts, but you can do it through Meta's API (Graph API) in a few steps. This procedure requires someone familiar with API calls. If you prefer, contact our support team and we'll help. :::warning There is no way to clone the approved status. Every template recreated in the destination WABA goes through Meta's approval again (usually minutes, but it can take up to 24h). Plan the switch with this in mind, so you're not left without approved templates in the new account. ::: What do I need beforehand? - The source WABA ID and the destination WABA ID - An access token with the whatsapp_business_management permission that has access to both WABAs (from a Business Manager system user, for example) How do I do it, step by step? 1. List the approved templates in the source WABA curl -G "https://graph.facebook.com/v{version}/{SOURCE_WABA_ID}/message_templates" \ -d "status=APPROVED" \ -d "fields=name,language,category,parameter_format,components" \ -d "limit=100" \ -H "Authorization: Bearer {TOKEN}" The response includes the name, language, category and content (components) of each template. If there are more than 100, follow the paging.next link in the response until the end. 2. Create each template in the destination WABA For each item in the list, send a POST with the same data. Remove the fields that belong to the source account (id, status, quality, etc.) and send only name, language, category, parameter_format (if present) and components. curl -X POST "https://graph.facebook.com/v{version}/{DESTINATION_WABA_ID}/message_templates" \ -H "Authorization: Bearer {TOKEN}" \ -H "Content-Type: application/json" \ -d '{ "name": "welcome", "language": "en_US", "category": "UTILITY", "components": [ ...copied from the source... ] }' 3. Track the approval Run the GET again on the destination WABA and check the status field until all templates are APPROVED. Any that come back REJECTED need manual adjustment. What should I watch out for? - Templates with media in the header (image, video, document): the sample file from the source doesn't work in the other account. Upload the media again through the Resumable Upload API, get the new handle and replace it in header_handle before the POST. - Variables: keep the examples (example) that come in the components. Without them, Meta rejects the template. - Creation limit: at most 100 templates created per hour in each WABA. If you have a lot, do it in batches. - Total limit: 250 templates per WABA if the portfolio is not verified (verified portfolios allow many more). - Category: Meta may reclassify the category during the new approval (e.g. from utility to marketing), which changes the sending cost. - Name: the same name + language can't already exist in the destination WABA. Notes - To create, edit and use templates inside Cloud Chat, see WhatsApp templates: create, edit, delete and use the builder. - To understand categories and rejection reasons, see WhatsApp template rules (Meta). - Any questions? Contact our support team. Official reference: Message templates (Meta for Developers)

Last updated on Sep 23, 2026