DialogHive

WhatsApp Business Cloud API Setup: Verification, Numbers & Templates Explained

DialogHive Team12 min read
WhatsApp Business APIMeta Business VerificationWhatsApp TemplatesBusiness Messaging API
Smartphone displaying WhatsApp login screen on a dark surface. Overhead view.
Photo by Rahul Shah on Pexels

The WhatsApp Business Cloud API is the only way to send automated messages at scale without relying on manual workarounds like broadcast lists. But setting it up correctly—especially Meta’s verification process, choosing the right phone number, and designing compliant templates—is where most businesses encounter delays. These aren’t just technical challenges; they’re the difference between a system that operates smoothly over time and one that fails under real-world usage after a few months. This guide explains how the process works, including the common pitfalls that trip up businesses after launch, and how to structure your setup to avoid them.

Why the Cloud API isn’t just ‘WhatsApp for businesses’

The WhatsApp Business Cloud API is not an extension of the WhatsApp Business app. It’s a separate system with stricter rules, designed for businesses that need to send high volumes of messages—whether for customer service, order confirmations, or marketing. The key differences that affect your setup include:

  • Message templates: All non-transactional messages (e.g., promotions, reminders) require pre-approved templates. Meta reviews these for compliance with their Business Messaging Policy. Rejections occur when language is unclear, placeholders are missing, or the message’s purpose isn’t specified (e.g., distinguishing between a reminder and an update).

  • Opt-in requirements: Users must actively agree to receive messages. This isn’t just a checkbox—it’s a legal requirement under GDPR and similar regulations. The opt-in must be explicit (e.g., “Send me order updates via WhatsApp?”) and documented. If a user hasn’t opted in, you cannot message them, even for order confirmations.

  • Message frequency limits: Meta enforces restrictions on how often messages can be sent to a single user within a 24-hour period. Exceeding these limits can result in temporary blocks. This means businesses must design their messaging flows to minimize unnecessary follow-ups (e.g., combining updates into single messages).

  • Phone number ownership: The number used for the API must be linked to a verified business entity, and Meta may reject numbers based on past usage patterns (e.g., complaints about spam).

The Cloud API is also the only way to use WhatsApp for broadcasts (sending identical messages to multiple users) without violating Meta’s policies. The WhatsApp Business app doesn’t support this feature, and attempting to use it for broadcasts risks account suspension.

Step 1: Meta Business Verification—What Actually Gets Rejected

Meta’s verification process isn’t about completing forms; it’s about proving you’re a legitimate business that won’t misuse the platform. The most common reasons for rejection—and how to avoid them—include:

  1. Inconsistent business details: Your business name, address, and tax identification must match exactly across all submissions (Meta’s dashboard, WhatsApp Business Manager, and any uploaded documents). Even small discrepancies, such as a typo in your registered address or a mismatch in the legal business name, can trigger a manual review, which can take weeks to resolve.

Example: If your business is registered as “Brighton Cycle Repairs Ltd” but you submit “Brighton Cycles” in the API application, Meta may flag it as suspicious. Always use the exact legal name from your official documents.

  1. Lack of proof of operation: Meta requires evidence that you’re already using WhatsApp for customer communication. This means providing screenshots or recordings of actual conversations with customers—not just internal tests. If your business hasn’t used WhatsApp before, you’ll need to set up a temporary WhatsApp Business account (not the API) and generate real conversations first.

  2. Unclear use case: Vague descriptions like “customer support” or “marketing” are rejected. Meta requires specific details, such as “sending appointment confirmations and reminders to salon clients” or “order status updates for e-commerce customers.” If your use case involves multiple functions (e.g., support and marketing), list them separately.

  3. Missing or incorrect documents: Depending on your country, you may need to provide:

  • A business license or registration certificate.
  • Tax documents (e.g., VAT registration in the EU).
  • Utility bills or bank statements proving your business address. If your documents are in a language other than English, you must provide a certified translation. Meta will reject submissions with untranslated documents, even if the content is clear.

Pro tip: Begin the verification process before you need the API. Meta’s review can take several weeks, and delays here can affect template approvals and number assignment. If you’re in a regulated industry (e.g., healthcare, finance), add extra time for additional checks.

Step 2: Choosing the Right Phone Number—and Why It Matters

Your WhatsApp Business Cloud API number isn’t just a contact detail—it’s tied to your business’s reputation and message-delivery reliability. Here’s how to select and manage it correctly:

Option 1: Dedicated Business Number (Recommended for Most)

  • What it is: A phone number exclusively for WhatsApp Business API use, assigned to your business.
  • Pros:
  • Full control over message templates and opt-ins.
  • No risk of mixing personal and business conversations.
  • Required for broadcast messages and high-volume automation.
  • Cons:
  • Takes time to provision after Meta approval.
  • Some countries have limited availability (e.g., high demand for UK numbers).

Option 2: Shared Number (For Testing or Low Volume)

  • What it is: A number shared with other businesses (via a provider like Twilio or MessageBird).
  • Pros:
  • Faster to set up.
  • Lower upfront cost.
  • Cons:
  • No broadcast capability—you can’t send identical messages to multiple users.
  • Shared numbers have lower message limits.
  • Higher risk of rejection if Meta detects abusive usage patterns.

Option 3: Porting an Existing Number

  • What it is: Moving your current WhatsApp Business number to the Cloud API.
  • Pros:
  • No need to change your published number.
  • Preserves existing customer relationships.
  • Cons:
  • Porting can fail if your current number has a poor reputation (e.g., spam complaints, low response rates).
  • Meta may require additional verification if the number was previously used for personal chats.

Critical trade-off: A dedicated number provides scalability and compliance but requires time to set up. If you’re testing or have low volume, a shared number might work, but it limits future capabilities. For example, if you later need to send broadcasts (e.g., for promotions or re-engagement campaigns), you’ll need to switch to a dedicated number, which requires re-verifying your business.

Example scenario: A salon using a shared number for booking reminders reaches its message limit mid-month. Without the ability to send a last-minute cancellation reminder, a client may not attend their appointment. With a dedicated number, this limitation wouldn’t apply.

Step 3: Template Design—How to Avoid Rejections and Delays

Templates are essential to the Cloud API, but Meta’s approval process is strict. A rejected template isn’t just a setback—it can delay your entire launch while you revise and resubmit.

The Anatomy of an Approved Template

Every template must include:

  1. A category: Specifies what the message is for (e.g., “account_update,” “appointment_reminder,” “marketing”). Meta uses this to detect misuse.
  2. A language code: e.g., “en_GB” for British English. Mixing languages in one template will result in rejection.
  3. Placeholders: Variables like {{1}} for dynamic content (e.g., order numbers, names). Missing or incorrectly formatted placeholders are the most common reason for rejections.
  4. A clear purpose: The template must specify exactly why you’re sending it. Vague purposes like “notification” are rejected. Instead, use:
  • “appointment_reminder” for rescheduling prompts.
  • “order_update” for shipping notifications.
  • “marketing” for promotions (with opt-in confirmation).

Common Pitfalls and Fixes

Issue Why It Fails How to Fix It
Missing placeholders Meta cannot verify dynamic content without them. Add {{1}} for order IDs, {{2}} for names, etc.
Vague category “Update” could apply to many scenarios. Use precise categories like “order_update” or “appointment_cancellation”.
Incorrect language code Using “en” instead of “en_GB”. Always use full language codes (e.g., “es_ES,” “fr_FR”).
Too many placeholders Templates with more than five variables are flagged. Combine related data (e.g., {{1}} {{2}} for “Order #12345 – John”).
Missing opt-in reference Required for marketing templates. Include *{{opt_in}}* in the template text (e.g., “You opted in on [date]”).

Example of a rejected template:

Category: notification
Language: en
Text: Your order is on the way!

Why it fails: No placeholders for the order number or customer name, and “notification” is too broad.

Approved version:

Category: order_update
Language: en_GB
Text: Your order {{1}} is out for delivery. Track it here: {{2}}

Testing Templates Before Submission

Meta’s Template Tester lets you preview how your template will appear with real data. Use it to:

  • Verify placeholder formatting (e.g., {{1}} vs. {{order_id}}).
  • Ensure the language code matches the text.
  • Confirm the category aligns with the message purpose.

Pro tip: Submit templates well in advance of when you need them. Approvals can take several days, and rush submissions often face delays due to review backlogs.

What Happens When You Ignore the Rules—and How to Recover

Most businesses focus on the setup process but overlook the long-term consequences of not following Meta’s policies. Here’s what tends to go wrong after several months of operation, and how to avoid it:

  1. Message restrictions: Sending too many messages to a user within a short period (e.g., daily reminders combined with updates) can trigger temporary blocks. Recovery requires manually resetting the user’s message window via the Meta API dashboard—a process that can take time if done manually for each affected user.
  • Fix: Combine related updates into single messages (e.g., include order status and tracking link in one message). Use tools to monitor message frequency and adjust accordingly.
  1. Template misuse: Using an approved template for a different purpose (e.g., sending a “marketing” template for a support query) can lead to account suspension. Meta reviews message samples, and mismatches trigger manual checks.
  • Fix: Clearly document the intended use of each template in your internal system (e.g., “Only for appointment confirmations”).
  1. Opt-out management: If users unsubscribe but your system doesn’t update their status, Meta’s Compliance Dashboard may flag your account. If a significant portion of your messages go to unsubscribed users, Meta may restrict your sending limits.
  • Fix: Integrate opt-out tracking with your CRM. For marketing messages, use a double-opt-in process (e.g., “Reply YES to confirm”).
  1. Number reputation issues: If your dedicated number receives complaints (e.g., users report spam), Meta may temporarily suspend it. Shared numbers are more vulnerable to this.

Example scenario: A gym sends daily workout tips via WhatsApp without tracking opt-outs. After several months, a significant portion of users have unsubscribed, but the system continues messaging them. Meta flags the account for non-compliance, and the gym’s message volume is reduced for a period while they clean up their contact list.

The Hidden Costs of Scaling—And How to Plan for Them

The $49/month Starter plan is suitable for basic automation (e.g., booking confirmations, simple FAQs), but most businesses outgrow it within a year. Here’s what drives the cost—and how to avoid unexpected expenses:

  1. Message volume: The Starter plan includes a limited number of messages per month. Exceeding this limit triggers additional fees. For example, sending more messages than allowed may result in charges per extra message.
  • Solution: Upgrade to a higher plan (e.g., Growth ($99/month) for more messages, or Scale ($249/month) for even higher volumes). Plan for additional capacity in your volume estimates to avoid overage fees.
  1. Template management: Each new template requires approval time. If you add multiple templates in a short period, delays can accumulate.
  • Solution: Design all templates before launching. Use a tracking system to monitor their status (approved, pending, rejected).
  1. Compliance overhead: Monitoring opt-outs, message frequency, and quality scores requires ongoing effort. This isn’t just a one-time task—it’s an ongoing process to avoid restrictions.
  • Solution: Automate compliance checks where possible (e.g., use tools to log unsubscribes in a CRM). For larger setups, allocate resources for regular monitoring.
  1. Number porting challenges: If you need to switch numbers (e.g., due to reputation issues), the process can take weeks. During this time, you cannot send messages to existing users.
  • Solution: Avoid shared numbers if you expect growth. If porting fails, Meta may require you to start over with a new dedicated number, adding more time to the process.

Comparison Table: When to Upgrade Plans

Plan Max Messages/Month Best For Hidden Costs to Consider
Starter ($49) Limited Testing, very low volume Potential overage fees if message limit is exceeded.
Growth ($99) Higher limit Small businesses, 1–2 communication channels Delays in template approvals if scaling rapidly.
Scale ($249) Much higher limit Multi-location, high engagement Additional time needed for compliance monitoring.

Example cost scenario for a growing e-commerce store:

  • Initial months: Message volume is low, and the Starter plan covers usage.
  • Later stages: Message volume increases, requiring an upgrade to avoid overage fees.
  • Long-term: Higher message volumes may necessitate further upgrades, increasing monthly costs.

Frequently Asked Questions

### How long does Meta Business Verification take?

Verification typically takes several weeks, but it can extend to over a month for regulated industries (e.g., healthcare, finance) or if documents are incomplete. Begin the process well in advance of when you need the API. If you’re porting an existing number, add extra time for Meta’s review of its usage history.

### Can I use the same template for multiple languages?

No. Each template must be submitted in one language only (e.g., en_GB for British English, es_ES for Spanish). Mixing languages in a single template will result in rejection. For multilingual businesses, create separate templates for each language and manage opt-ins accordingly.

### What happens if Meta rejects my template?

You’ll receive a rejection notice with details on the issue (e.g., missing placeholders, incorrect category). Fix the template and resubmit—there’s no appeal process. To minimize delays, use Meta’s Template Tester before submission to catch errors early. Plan for several days per resubmission.

### Do I need a dedicated number for broadcasts?

Yes. Shared numbers cannot be used for broadcasts (sending identical messages to multiple users). If you plan to use WhatsApp for promotions, re-engagement campaigns, or bulk notifications, you must use a dedicated business number. This requires Meta verification and can take weeks to provision.

### How do I handle users who opt out?

When a user replies “STOP” or unsubscribes via your system, you must remove them from future message flows within 24 hours. Meta tracks opt-out rates, and if a significant portion of your messages go to unsubscribed users, they may restrict your sending limits. Use your CRM or chatbot platform to automatically log opt-outs and suppress those contacts. For marketing messages, include clear opt-out instructions (e.g., “Reply STOP to unsubscribe”).

Want this working for your business?

DialogHive builds AI chatbots for WhatsApp, Instagram, Messenger and websites — see our services, pricing or book a free demo.

Related Posts

Ready to put your customer chats on autopilot?

Get a free demo of DialogHive on WhatsApp, Instagram, Messenger and your website — live in days, not months.