Multi-branch companies running WhatsApp for customer communication face a specific structural problem: each branch, region, or trading entity typically needs its own WhatsApp Business Account (WABA), but staff, managers, and compliance teams need one place to see and control all of them. Below, Stitch, the WhatsApp business communication platform, answers the questions multi-branch operators and IT leads most often ask about running several WABAs from a single setup.
Yes. Organizations can manage multiple WhatsApp Business Accounts under one Stitch organization, so a multi-branch business does not need a separate login or separate tool per location. Each branch can have its own WABA, letting multiple staff members access and manage communications for that branch without losing context on prior conversations. This structure means a regional entity keeps its own dedicated WhatsApp number and message history while still sitting inside one consolidated management layer. For a group with several trading names or physical locations, this avoids the alternative of juggling separate phones or separate WhatsApp Business app installs per site.
Each branch typically operates its own WABA rather than sharing a single number across locations. This is deliberate: keeping a distinct WABA per branch preserves a clean, branch-specific conversation history and makes it possible to apply different permissions, teams, and workflows to each one. Where a business wants a single shared number instead, one WhatsApp Business Account can still be connected to multiple users and devices, so smaller multi-site operations that prefer one number can do that within a single WABA. The right structure depends on whether branches need to be reported and audited separately or run as one combined operation.
Setting up an additional WhatsApp Business Account follows the same onboarding and integration process used for the first account, connecting the number to the platform before it goes live for the team. Once connected, that branch's WABA can be linked to its own CRM or integration independently of what other branches use. A branch running a different CRM system, for example, can have its WABA tied to that system while another branch's WABA connects to a different one entirely. There is a setup fee for adding further WABA accounts beyond the first, which businesses should budget for when planning a multi-branch rollout.
Setup is one part of the picture; how users and permissions are handled across those accounts is the next question most operations teams ask.
User management is controlled at the platform level, letting a business decide which team members can access which conversations. Permission settings are flexible: administrators can be given visibility across all chats, while regular users are restricted to only the chats assigned to them. This means a head-office operations lead can be set up to see activity across every branch's WABA, while a branch-level agent only sees the conversations relevant to their location. Chats can also be assigned to individuals or to teams and reassigned as needed, which supports handover between staff without losing conversation history.
Pricing scales with both the number of WABAs and the number of users attached to them. As a reference point, five users on one WhatsApp Business Account is estimated at £150, while five users spread across five separate WABA accounts is estimated at £200. Stitch's pricing starts from £99, with user tiers available for up to 5, 10, or 20 users and customised pricing above that. There are no annual commitments, so a multi-branch business can start with a smaller number of accounts and scale up branch by branch as needs grow.
Yes. Chats can be tagged for grouping and filtering, for example by labelling conversations as "opportunity" or "customer," which helps teams sort activity within their own branch's inbox. The platform supports filtering by unread or assigned chats and allows broadcasting messages to a tagged group, so a branch manager can message a specific segment of contacts without affecting other locations. Chat management works on an inbox-and-archive model similar to a ticketing system, which keeps each branch's conversation queue distinct even though everything sits under one organization.
Access controls answer who can do what, but compliance and audit leads will also want to know how activity gets tracked over time.
Centralising WhatsApp communication through a managed platform, rather than relying on personal WhatsApp accounts, directly addresses data privacy and compliance exposure, since personal accounts carry known risks under regulations such as GDPR. Understanding how UK GDPR and data residency rules apply to WhatsApp business messaging is essential for multi-branch operators who must maintain strict data standards. Stitch's platform provides an audit trail for conversations, which supports compliance and accountability requirements across the business. For a multi-branch operator, this means each branch's WABA generates its own record of who handled which conversation, viewable centrally rather than scattered across individual staff phones.
Conversations stay attached to the branch's WABA rather than to an individual's personal device, so context is not lost when staff change. Because chats can be reassigned between users or teams, an outgoing staff member's open conversations can be handed to a colleague without losing the message history that came before. This is a structural benefit of managing WhatsApp through a business account rather than the free WhatsApp Business app, which is limited to single-user access and does not support this kind of handover.
Yes, each WABA can be linked to a different CRM or integration independently of the others, so one branch might connect its WABA to one CRM while a separate branch connects to a completely different system. A single WABA, however, cannot natively integrate with multiple CRMs simultaneously without custom API development. For visual, day-to-day use, a Chrome extension is also available that integrates with web-based CRMs, letting staff message a contact directly from the CRM screen by clicking or highlighting a phone number. Businesses needing deeper backend integration across systems can pursue custom API development, which involves developer involvement and additional cost.
With compliance and integration covered, the remaining questions tend to focus on the practical mechanics of running the accounts day to day.
Yes. Basic automation, sometimes called a virtual assistant, uses keyword-based bot flows to guide customers through menus and route chats to the right team, and this can be configured per WABA. Separately, AI assistance is available as a custom-built chatbot trained on a company's own FAQs and workflows, capable of handling inquiries and even booking meetings. These are distinct capabilities: automation is rule-based, while AI bots require training and customisation, so a multi-branch operator can decide whether each branch needs simple menu-driven automation, a fully trained AI assistant, or both.
Yes. Voice-to-WhatsApp integration converts unanswered calls into WhatsApp chats by having the phone system play a queue message prompting the caller to press a number to start a WhatsApp conversation. A floating WhatsApp widget can also be embedded on a company website and customised with its own menu options and bot flows, which can be configured to route enquiries to the correct branch. This requires an existing phone system capable of queue messaging and dialling out; it is not available for mobile-only setups, so branches running only mobile phones would need a compatible phone system in place first.
Bulk broadcasting can be carried out within each branch's own account by scraping phone numbers from CRM pages into the platform for that WABA. Because tagging and filtering operate at the WABA level, a branch can broadcast to its own tagged customer groups without that message reaching contacts belonging to a different branch's account. This keeps marketing and update messages relevant to the branch they originate from, which matters for both customer experience and message-template cost control, given that marketing template messages are charged per conversation window.
Typical monthly template fees for a small business range from £3 to £15, with marketing template conversations charged at 3.7p each. Multiplied across several branch WABAs, these per-conversation costs sit on top of the base user-tier pricing and any per-WABA setup fee. Because there are no annual commitments, a multi-branch business can add WABAs incrementally as branches come online rather than committing to the full estate of accounts upfront.
A multi-branch operator planning several WABAs should scope the number of branches, users per branch, and any CRM integrations needed per location before onboarding, since these directly determine account structure and cost. The onboarding process itself follows the same account setup and integration steps regardless of how many WABAs are ultimately connected. Businesses with more complex integration needs, such as connecting one WABA's data to multiple systems at once, should flag this early, since it requires custom API development rather than being available out of the box.
Running WhatsApp across multiple branches does not have to mean multiple disconnected tools: with a dedicated WABA per branch, centralised user permissions, and a shared audit trail, a multi-branch business gets both local control and organisation-wide oversight in one structure.
