Designing Multi-Brand WhatsApp Business Deployments using a Single Genesys Cloud Org

How-To-Articles
1

Designing Multi-Brand WhatsApp Business Deployments using a Single Genesys Cloud Org

What This Guide Covers

This masterclass details the architectural design and configuration of a Multi-Brand WhatsApp strategy within a single Genesys Cloud organization. By the end of this guide, you will be able to manage multiple WhatsApp Business Accounts (WABAs)-each with its own distinct branding, phone number, and template library-while maintaining a unified agent experience and efficient cross-brand reporting. This is essential for conglomerates or BPOs serving diverse clients from a centralized platform.

Prerequisites, Roles & Licensing

Multi-brand WhatsApp requires careful coordination with Meta’s Business Manager and Genesys Cloud administrative settings.

  • Licensing: Genesys Cloud CX 1, 2, or 3 with WhatsApp digital channel enabled.
  • Permissions:
    • Messaging > WhatsApp > View/Edit/Add
    • Routing > Queue > View/Edit
    • Integrations > Integration > View/Edit
  • Infrastructure:
    • Multiple verified WhatsApp Business Phone Numbers.
    • Access to the Meta Business Manager where the numbers are registered.

The Implementation Deep-Dive

1. Provisioning Multiple WhatsApp Integrations

Genesys Cloud allows you to add multiple WhatsApp integrations within the same org. Each integration corresponds to a unique phone number.

Configuration Step:

  1. Navigate to Admin > Message > WhatsApp Configurations.
  2. Click Add New Integration for each distinct brand.
  3. Follow the “Embedded Signup” flow to link the specific Meta phone number to that integration.

Architectural Reasoning:
Do not try to “Share” a single WhatsApp integration across brands using logic in the Architect flow. WhatsApp is inherently number-based. If a customer messages “Brand A,” the reply must come from “Brand A’s” number for the session to remain valid and for the branding (logo/name) to appear correctly on the customer’s device.

2. Segmenting Traffic using Participant Data

Once you have multiple integrations, you must ensure that agents know which brand the customer is interacting with.

Implementation Pattern:
In your Inbound Message Flow:

  1. Use the Get Message Details action to identify the Integration ID or To Address (the WhatsApp number).
  2. Use a Switch block to branch based on the number.
  3. Use the Set Participant Data action to tag the interaction (e.g., AttributeName: Brand_Name, Value: Brand_A).
  4. Route the call to a brand-specific queue or use Skills-Based Routing to find an agent qualified for that specific brand.

3. Managing Brand-Specific Message Templates

WhatsApp requires pre-approved Message Templates for outbound proactive notifications.

The Trap:
Mixing templates from different brands in the same library. Agents might inadvertently send a “Brand B” welcome message to a “Brand A” customer.
The Solution: Use a Naming Convention for templates (e.g., brand_a_shipping_update, brand_b_shipping_update). In the agent script, filter the template selection based on the Brand_Name participant attribute collected in Step 2.

4. Implementing Cross-Brand Isolation (Divisions)

If your brands are managed by different teams or BPOs, you must enforce security isolation.

Implementation Step:
Assign each WhatsApp integration and its corresponding queue to a specific Division.

  • Brand A Integration & Queue → Division: Brand_A_Div
  • Brand B Integration & Queue → Division: Brand_B_Div

This ensures that a supervisor for Brand A cannot see the WhatsApp settings or real-time metrics for Brand B.

Validation, Edge Cases & Troubleshooting

Edge Case 1: The “Shared” Meta Business Manager

  • The failure condition: You cannot add “Brand B” because it is owned by a different Meta Business Manager (BM) than “Brand A.”
  • The root cause: Genesys Cloud’s embedded signup flow works best when all numbers are in the same BM.
  • The solution: Use the Meta BM Partnership feature. The owner of the Brand B BM must grant “Manage” permissions to your main BM. Once the partnership is established, the numbers will appear in your embedded signup list.

Edge Case 2: Template Approval Latency

  • The failure condition: You’ve created a template for a new brand launch, but it’s stuck in “Pending” for 48 hours.
  • The root cause: Meta’s automated review system flagging content that doesn’t align with the “Business Category” of the WABA.
  • The solution: Ensure each WABA has its own Profile Categories correctly set in Meta Business Manager. A “Retail” template will often fail approval if the WABA is categorized as “Health/Medical.”

Official References