--- title: "How a Shared Inbox for WhatsApp, Instagram and Email Works" description: "How a shared inbox for WhatsApp, Instagram and email works for sales and support teams: assignment, ownership, templates, history and the KPIs to track." canonical: "https://omnichannels.ai/blog/shared-inbox-whatsapp-instagram-email/" language: "en" updated: "2026-10-10" publisher: "BroadNet Technologies" brand: "OmniChannels.ai" category: "support" primaryQuery: "shared inbox for whatsapp instagram and email" keywords: ["omnichannel shared inbox", "team inbox whatsapp", "instagram dm shared inbox", "conversation assignment rules", "customer service window whatsapp", "shared inbox kpis"] published: "2026-10-10" author: "OmniChannels.ai Editorial Team" reviewer: "BroadNet Messaging Solutions Team" readingMinutes: 8 answer: "An omnichannel shared inbox puts WhatsApp, Instagram Direct and email conversations into one queue that a whole team can work. Each conversation has one owner at a time, a status, a visible history and channel-specific rules such as WhatsApp's 24-hour customer service window. Teams set assignment rules, saved replies and approved templates, then track first response time, resolution time and backlog per channel." takeaways: ["A shared inbox works when every conversation has exactly one owner and one status at any moment; shared visibility without ownership produces duplicate or missed replies.", "WhatsApp and Instagram limit free-form business replies to a window after the customer's last message, so the inbox must show how much of that window remains.", "Outside the WhatsApp customer service window, a business can only start the conversation again with a pre-approved message template.", "Sales and support can share one inbox if queues, tags and assignment rules keep their work separate while history stays visible to both.", "Measure first response time, resolution time, reopen rate and unassigned backlog per channel, because customers expect different speeds on chat and email."] faq: - q: "What is the difference between a shared inbox and a shared email account?" a: "A shared email account lets several people log into one mailbox, so nobody knows who is answering what. A shared inbox adds assignment, ownership, internal notes, statuses and collision warnings, and it can combine chat channels such as WhatsApp and Instagram with email. The result is one queue with a clear owner per conversation and a full history for whoever picks it up next." - q: "Can sales and support use the same omnichannel inbox?" a: "Yes, as long as the inbox separates their work. Use distinct queues or tags for sales and support, route by entry point or keyword, and let both teams see the full customer history. Agree on handover rules, for example that a pre-sales question becomes a support ticket after the order is placed, so ownership never sits with two people." - q: "What happens when the WhatsApp 24-hour window closes?" a: "Once 24 hours pass since the customer's last message, the business can no longer send free-form messages on WhatsApp. To restart the conversation it must send an approved message template, which Meta may charge for by category and recipient market. The window reopens when the customer replies. A good inbox shows the remaining time so agents prioritise those conversations." - q: "How many agents can share one WhatsApp number?" a: "With the WhatsApp Business Platform (API), a single business phone number can be connected to an inbox tool that many agents use at once; the limit depends on the inbox software and your plan, not on the phone. The WhatsApp Business App is different and is designed for a small number of linked devices, which is why growing teams usually move to the API." - q: "Should email live in the same inbox as WhatsApp and Instagram?" a: "Usually yes for customer-facing teams, because customers switch channels and agents need the full history. Keep different targets, though: chat customers expect replies within minutes, while email is often measured in hours. Use separate service level targets and views per channel inside the same inbox rather than separate tools." sources: - title: "Send messages and customer service windows — WhatsApp Cloud API, Meta for Developers" url: "https://developers.facebook.com/docs/whatsapp/cloud-api/guides/send-messages" - title: "WhatsApp Business Platform pricing — Meta for Developers" url: "https://developers.facebook.com/documentation/business-messaging/whatsapp/pricing" - title: "Messaging API — Instagram Platform, Meta for Developers" url: "https://developers.facebook.com/docs/instagram-platform/instagram-api-with-instagram-login/messaging-api" --- # How a Shared Inbox for WhatsApp, Instagram and Email Works Canonical: https://omnichannels.ai/blog/shared-inbox-whatsapp-instagram-email/ Language: en Publisher: OmniChannels.ai by BroadNet Technologies This guide is for support managers, sales leads and CX directors who are moving from personal phones, a shared Gmail login or separate channel apps to one team inbox. By the end you will know how a shared inbox for WhatsApp, Instagram and email actually works, which rules to set before go-live, and which numbers tell you it is working. ## What is an omnichannel shared inbox? An omnichannel shared inbox is one workspace where conversations from several channels arrive in a single list that a team works together. Each conversation keeps its channel, its full message history and one assigned owner. The difference from "everyone logs into the same account" is control. A shared inbox adds: - **Assignment**: a conversation belongs to one agent or one team queue. - **Status**: open, pending (waiting on customer or another team), resolved. - **Internal notes**: comments only colleagues can see. - **History**: every message, attachment, note and assignment change in order. - **Channel rules**: for example, the WhatsApp customer service window and template requirement. ## How do conversations flow through a shared inbox? Every message follows the same lifecycle regardless of channel: arrive, route, assign, reply, resolve, and possibly reopen. The channel changes the rules at each step, not the steps themselves. | Step | WhatsApp (Business Platform) | Instagram Direct | Email | |---|---|---|---| | Arrives as | Message to your business number | DM to your professional account | Mail to a support or sales address | | Free-form reply allowed | Within 24 hours of the customer's last message | Within the standard messaging window (see Meta docs) | Any time | | Restarting later | Approved message template only | Limited; check Meta's message tag rules | Any time | | Typical customer expectation | Minutes | Minutes to hours | Hours | | Rich content | Media, documents, buttons, templates | Media, story replies, quick replies | Attachments, HTML | Because the rules differ, the inbox should show the channel and, for WhatsApp and Instagram, the time left in the window on every conversation card. ## How should assignment and ownership work? Assign every conversation to exactly one owner, and make ownership visible to everyone. Most teams combine automatic routing for new conversations with manual reassignment for exceptions. ### Common assignment models | Model | How it works | Best for | Watch out for | |---|---|---|---| | Manual pick-up | Agents claim from an unassigned queue | Small teams, mixed skills | Easy tickets get cherry-picked | | Round robin | New conversations rotate across online agents | Uniform support queries | Ignores agent workload and skills | | Load-based | Goes to the online agent with fewest open items | Busy support desks | Needs accurate status hygiene | | Skill or language-based | Routed by language, product or channel | Arabic/English teams, specialists | Too many queues starve each other | | Account ownership | Returning customers go to their account manager | B2B sales, VIP clients | Breaks when the owner is off shift | ### Ownership rules worth writing down 1. One owner per conversation at all times; "unassigned" is a queue, not a state to leave things in. 2. The owner keeps the conversation until it is resolved or formally reassigned with a note. 3. When an agent goes offline, their open chat conversations return to the queue; email can stay with the owner. 4. A returning customer within a defined period (for example seven days) goes back to the previous owner if they are online. 5. Collisions are blocked: the inbox shows when a colleague is viewing or typing. ## How do templates and saved replies differ? Saved replies are your own reusable text that agents insert and edit freely. Message templates are WhatsApp-specific messages pre-approved by Meta, required whenever you message a customer outside the 24-hour window. - **Saved replies** speed up common answers such as delivery times, return policy or opening hours. Keep them short, write them in both Arabic and English if you serve the GCC, and review them quarterly. - **WhatsApp templates** have a category (marketing, utility or authentication), variables, and optional media and buttons. Meta reviews them, and pricing is set per template category and recipient market. Do not print exact rates in internal playbooks; link to Meta's current rate card instead. - **Email signatures and snippets** follow your normal email standards. According to Meta's pricing documentation, from 1 October 2026 Meta charges WhatsApp service messages after the first 1,000 free per business phone number per month, and charges utility templates sent inside the customer service window. Confirm the current rules in Meta's pricing documentation before you build templates into routine replies. ## Why does conversation history matter so much? History lets any agent continue a conversation without asking the customer to repeat themselves. It should show messages from every channel for that customer, internal notes, previous owners and outcomes. Two practical requirements make history useful: - **Contact matching.** A WhatsApp number, an Instagram handle and an email address are three identities. Link them to one contact when you have evidence (the customer confirms, or a CRM record holds all three) rather than guessing. - **Searchable notes.** Notes like "refund approved by finance, ref 4471" save the next agent a phone call. ## How do you set up a shared inbox? A go-live checklist 1. **Connect channels.** WhatsApp Business Platform number, Instagram professional account, and each email address via SMTP/IMAP or forwarding. 2. **Define queues.** At minimum: sales, support, and a language split if you run Arabic and English teams. 3. **Pick an assignment model** per queue from the table above. 4. **Write ownership rules** (the five above) and share them with every agent. 5. **Create saved replies** for your top 20 questions, in each language. 6. **Submit WhatsApp templates** for follow-ups you expect to send after the window closes, such as order updates or appointment reminders. 7. **Set service level targets** per channel, for example first response in minutes for chat and in hours for email. 8. **Train on statuses**: when to mark pending versus resolved. 9. **Run a one-week pilot** with one team before moving everyone. ## Worked example: a Dubai furniture retailer A synthetic retailer, "Nakheel Home", sells online and in two showrooms. Before the change, sales staff answered WhatsApp on personal phones, Instagram DMs were checked by marketing, and support used a shared email login. They set up one inbox with three queues: - **Sales** gets Instagram DMs and WhatsApp messages that arrive from a "Shop on WhatsApp" link, routed to Arabic or English agents by the language of the first message. - **Support** gets email and WhatsApp messages containing an order number. - **Showroom** is a small queue for appointment requests, owned by two coordinators. A customer asks on Instagram about a sofa, then sends her order number on WhatsApp a week later about delivery. Because her contact links both identities, the support agent sees the earlier sales chat, replies within the window, and adds a note for the delivery team. When the delivery date moves after the window has closed, the agent uses an approved utility template to notify her. ## What are the common mistakes and limits? - **Shared visibility without ownership.** Two agents answer the same customer, or nobody does. - **Ignoring the window.** Agents type a long reply on WhatsApp after 24 hours and it cannot be sent as a free-form message. - **One target for every channel.** Email backlog makes chat numbers look bad, or chat speed hides slow email. - **Merging contacts too aggressively.** Two people sharing a family phone are not one customer. Merge only on confirmed evidence. - **Assuming the API does everything the app does.** Some consumer features behave differently on the API; check Meta's documentation for each feature you rely on. - **Instagram limits.** Messaging through the API requires a professional account and app permissions, and the reply window and message tags are governed by Meta's policies, which change. ## Which KPIs show the shared inbox is working? Track a small set per channel and per queue, weekly: | KPI | What it tells you | |---|---| | First response time (median) | Whether customers are acknowledged quickly | | Resolution time (median) | How long issues actually take | | Unassigned backlog | Whether routing and staffing keep up | | Reopen rate | Whether "resolved" really means resolved | | Window expiries without reply | WhatsApp or Instagram conversations lost to the clock | | CSAT | How customers rate the outcome | Use medians rather than averages, because a few very old conversations distort averages. ## How OmniChannels.ai helps OmniChannels.ai, powered by BroadNet Technologies, provides an [Omni Inbox](/platform/unified-inbox/) with WhatsApp, Telegram, Email and Instagram tabs, so agents can reply with media, attachments and approved WhatsApp templates from one place. WhatsApp Business API onboarding runs through Meta Embedded Signup, Instagram DMs connect directly, and email works through SMTP/IMAP. Templates support variables, media and buttons with approval tracking, and the interface works in Arabic and English. See how it fits your [customer support](/solutions/customer-support/) team.