Running customer conversations through a single mobile phone creates an obvious problem: only one person can reply at a time, and the whole business depends on whoever holds that handset. Stitch, the WhatsApp business communication platform, replaces that setup with a shared inbox where team members log in with an email and password rather than a SIM card, so several people can read, assign and reply to the same WhatsApp number at once. This guide walks through how to set that up, from initial configuration to team assignment rules.
A main business number you want customers to message on, ideally your existing landline rather than a personal mobile
Access to complete WhatsApp's business verification process, which takes approximately one day
A list of the team members who need login access, and a rough idea of how you want chats divided (by branch, team, or individual)
Awareness of message capacity limits: once verified, businesses can initiate up to 1,000 conversations per day
With those in place, the setup itself follows a straightforward sequence of configuration steps.
Decide which number your customers will actually message. Stitch recommends using your main business landline for WhatsApp communications rather than introducing a new number, which simplifies customer interactions because customers keep contacting the number they already know. Some businesses run two main numbers into one shared inbox, for example a UK number and a US number, depending on where their customers are based. How a Multi-City Property Management Company Unified International Teams on One WhatsApp Number illustrates how this works for firms operating across different regions.
Note: If you plan to route different departments through different numbers rather than one shared number, you can provision additional inboxes for £49 each after the first setup, or provision separate numbers per branch, which is covered in Step 4.
Before your shared inbox can operate at scale, WhatsApp requires business verification. This process takes approximately one day to complete. Verification matters beyond compliance: it directly determines how many conversations your team can initiate, since verified businesses can send up to 1,000 conversations per day, a limit unverified accounts don't reach.
Once verification is confirmed, you're ready to move from a single-user setup to a genuine team inbox.
This is the core of what makes a shared inbox work: your team logs in using email and password credentials, not by scanning a QR code on a personal phone. This structure removes the single point of failure that comes from routing all communication through one person's mobile device, since multiple users can access and respond to messages from the same number simultaneously.
It also addresses a common compliance concern directly. Because communications are managed centrally through the platform rather than through personal devices, businesses have an easier time demonstrating GDPR compliance for customer messaging. Conversations stay attached to the business, not to an individual's phone, and persistent chat history means every interaction is stored and accessible for continuity even if the original replying agent is unavailable.
Sub-step 3a: Set access permissions. You can restrict which chats individual users see, filtering by branch, team, or individual assignment, which keeps sensitive conversations visible only to the people who need them.
Sub-step 3b: Confirm your team size fits the platform's supported scale. One configuration supports up to 10-11 users across two branches, which gives a useful benchmark for how a small-to-mid-sized team's setup typically looks.
Once your people are in the inbox, decide how incoming messages get distributed. Stitch allows the creation of teams so that chats can be assigned to specific users or teams based on the nature of the inquiry, which improves response efficiency compared with every message landing in one shared queue.
There are two common assignment models worth understanding before you configure yours:
Auto-assign to sender: incoming messages are automatically routed based on who the customer previously spoke to, which keeps continuity for repeat conversations
Team-based assignment: messages are routed to a team rather than an individual, useful when inquiry volume is high or when the responding agent doesn't need to be the same person each time
If one team's workload grows to the point where a single inbox isn't enough, for example when a business wants to separate a general enquiries team from a specialist team like repair progression, the alternative is provisioning a second WhatsApp number rather than overloading one inbox with mismatched assignment rules.
Multi-branch or multi-location businesses need a slightly different structure than a single-location team. Each branch can have its own WhatsApp account, so customer communications for one location stay separate from another, and users can filter messages based on their role to see only the inquiries relevant to them. This is particularly useful where staff are assigned to specific branches and shouldn't be fielding enquiries meant for a different one.
For businesses where staff need clearer separation between personal and business use, dedicated WhatsApp Business accounts linked to DDI (direct dial-in) numbers are the recommended structure, keeping personal WhatsApp accounts entirely separate from the business inbox. The team inbox supports multiple WhatsApp accounts within the same platform and allows switching between them, so this doesn't require separate logins for separate tools.
With people and teams in place, add automation on top rather than relying purely on live replies. Businesses can set up automated replies to incoming messages that give customers options to choose from, which streamlines the initial inquiry process before a human agent picks up the conversation. This also covers out-of-hours coverage: automated replies and follow-up questions ensure customers receive timely information even when agents aren't available, which matters because WhatsApp messages can be responded to at any time, unlike live chat, which demands an immediate response.
Automated capture of a customer's mobile number at this stage also strengthens lead management and follow-up, since the number becomes part of the record the team can act on later.
A shared inbox is only as useful as the channels feeding it. A website widget lets visitors initiate a WhatsApp conversation directly from your site, and is designed specifically to capture mobile numbers for future engagement. Some businesses extend this further with dynamic QR codes, for example on physical signage, that direct customers straight to a WhatsApp chat about a specific product or property.
If your business already runs a CRM, connect it before rolling the inbox out fully. Messages sent and received through the shared inbox can be automatically synced into a CRM such as REAPit, keeping the full communication history organised and accessible without manual logging. For estate agents, setting up a shared WhatsApp team inbox with Reapit CRM ensures that all property enquiries are tracked against the correct contact records. This matters most for teams managing high enquiry volumes, where template messages with call-to-action buttons, for booking a viewing or requesting more information, can also be built directly into the workflow to speed up common actions.
Roll out in phases. Start with basic team messaging on WhatsApp Business accounts before introducing automation or AI assistants, giving your team time to get familiar with the shared inbox first.
Expect a fast initial setup, but plan for variables. Setup can be as quick as 40 minutes, though the real timeline depends on client readiness and how far along your Meta business environment configuration already is.
Keep personal and business numbers separate from day one. Staff who want to retain a personal WhatsApp account alongside their business one can do so, provided the business communications route through the dedicated DDI-based account.
Don't over-provision numbers early. Additional inboxes cost £49 each after your first setup, so it's worth confirming your team-assignment structure (Step 4) before deciding you need a second number.
Use media features to keep conversations self-contained. The platform supports voice notes, photos and videos, so agents can share the same range of media customers expect from a personal chat, without switching tools.
"Messages aren't reaching the right team member." Check your assignment configuration from Step 4. If you're using auto-assign to sender and a customer's history has changed hands (for example, a different agent), messages may still route based on that history, so a team-based assignment model may fit better for high-turnover queues.
"Two teams are working out of the same inbox and it's getting crowded." This is a sign you may need a second number rather than more automation on one number. Provisioning an additional number for a specific team, such as a repair progression team separate from general enquiries, keeps queues distinct at the source.
"We're not seeing the message volume we expected." Confirm business verification has completed. Verification is what unlocks the 1,000-conversation-per-day threshold, so an unverified account will hit a lower ceiling regardless of how well the inbox itself is configured.
"Staff are unsure whether to use their personal WhatsApp or the business one." Revisit Step 5. Dedicated DDI-based WhatsApp Business accounts are the recommended structure precisely to remove that ambiguity, letting staff keep a personal account separate from the one tied to the shared inbox.
Setting up a shared WhatsApp inbox comes down to a handful of decisions done in the right order: pick the number, complete verification, bring your team in through login credentials rather than mobile devices, configure assignment rules that match how your business actually splits work, and layer in automation once the team is comfortable. Done this way, the result is a WhatsApp inbox that survives staff turnover, holidays and busy periods, because no single phone or person is the bottleneck. From here, the natural next step is connecting the inbox to your existing CRM and reviewing your assignment rules after the first few weeks of real usage, adjusting team structures as actual message volume reveals where the bottlenecks are.
