SHARED TEAM INBOX

One inbox, your whole team in it — on WhatsApp and Messenger.

A real-time shared inbox for teams that outgrew the WhatsApp Business app. Everyone works one live queue, conversations get assigned to agents or routed to named team inboxes, and role-based visibility means each agent sees exactly the threads they should. WhatsApp and Facebook Messenger side by side on the official Cloud API — with 0% markup on Meta’s charges.

app.whatsmark.io/inbox
Chats Calls Soon
Search conversations…
AS
Aarav SharmaLead

Thank you for messaging us…

15:38
PP
Priya Patel

📷 Image

03:542
RM
Rohan Mehta

Hy

14/07
SI
Sneha IyerVIP

↗ Template: order

13/07
AS
Aarav Sharma
Today
AS

Hi

15:34

Connect WhatsApp Business

Welcome Aarav

Thank you for messaging us. How can we help you?

15:38

Type a message
4096

Start on WhatsApp, expand when you are ready

Built for WhatsApp first — Messenger and Instagram when you need them.

WhatsMark runs your marketing, sales, and support on WhatsApp today. Add Messenger and Instagram to the same shared inbox and automations whenever you want — no new tool, no re-platforming.

WhatsApp
WhatsApp

Broadcasts, chatbots, templates, and a shared team inbox — on the official Cloud API.

Live
Facebook Messenger
Messenger

Campaigns, instant templates, and automation straight from your Facebook Page.

Live
Instagram
Instagram

DM automation and campaigns for Instagram — landing soon.

Coming soon

Sound familiar?

Three things every D2C team already lives with

Support is running on personal phones

Five people, five phones, five copies of the WhatsApp Business app. Nobody can see what a colleague already replied. The customer who messaged at lunch gets re-pinged at 4 PM by someone who didn't know. There's no way to assign a chat, hand it off, or see who's on what.

Conversations walk out when an agent leaves

When Anjali resigns, her phone leaves with her — and so does the entire history with 4,200 customers. The next hire picks up cold, and customers hate being asked to "explain again from scratch". A shared inbox keeps every thread with the business, not the handset.

Every extra agent and every message costs you twice

Most WhatsApp tools charge per agent seat and mark up Meta’s per-conversation fees on top. Add a hire and you pay another seat; send a campaign and you pay a margin on every conversation. WATI charges per user; many BSPs quietly pad Meta’s rates. WhatsMark keeps seats on your plan and adds 0% markup — you pay Meta directly.

The four pieces

What you actually need to run WhatsApp marketing at scale

One real-time inbox for WhatsApp + Messenger

Every WhatsApp and Facebook Messenger conversation lands in one live queue. New messages, assignments, and read receipts update instantly over websockets — no refresh, no polling. Filter by status, assignee, or unread, and each agent signs in with their own login. The customer sees one number, one brand.

Assign to agents, route to named teams

Assign any conversation to one or more teammates in a click, or route it to a named team inbox — Sales, Support, Billing. The conversation header logs every handoff: who took it, who reassigned it, and when. The new assignee inherits the full thread, so the customer never re-explains.

Role-based visibility, built in

Owners and admins see everything; every other agent sees only the conversations assigned to them or shared with their team. It’s enforced on the query itself — not just hidden in the UI — so no customer thread is ever exposed to an agent who shouldn’t see it. Ideal for sales teams protecting their leads, clinics, and multi-desk support.

Reply faster — canned replies, AI assist, templates & Flows

Drop in saved canned replies by shortcut, rewrite or translate a draft with one-click AI assist, and send an approved WhatsApp template or an interactive WhatsApp Flow straight from the composer — with full photo, document, and voice-note media in-thread.

Scenario 01 / Festive-peak support (e-commerce)

Scale the roster for the Diwali rush — one queue, clean handoffs.

A D2C beauty brand adds agents for the four-week festive window. Everyone works the same shared inbox instead of five personal phones. Reception assigns each incoming chat to an agent, or routes it to the English or Hindi team inbox; edge cases get handed to senior CX with a single reassignment, and every handoff is on the record. Seats scale with your plan — five on Professional, more via the Extra Team Members add-on, unlimited on Reseller.

  • One shared queue — no more five agents on five personal phones
  • Assign chats to agents, or route to named team inboxes (English desk, Hindi desk)
  • Hand tricky cases to senior CX in one click — every reassignment logged
  • Canned replies for the repeat festive questions — sizing, COD, delivery ETAs
9:41
WhatsMark
WhatsMark.io

online

Hi, do you have the rose gold gift set in stock? Want to order 3 for Diwali gifting.

11:02 AM

🔁 Routed to Hindi Desk team inbox — festive queue.

11:03 AM ✓✓

Hi Priya! Yes, rose gold gift set is in stock. For 3 sets we can also apply the festive bundle discount — want me to share the checkout link?

11:05 AM ✓✓

Yes please, and what’s the COD delivery time to Pune?

11:06 AM

🔁 Reassigned to Meera · Senior CX — customer asking about interstate COD limits, routing for approval.

11:08 AM ✓✓

Hi Priya, Meera here. COD is available up to ₹5,000 per order — your 3 sets qualify. Delivery to Pune is 3–4 working days during the festive rush.

Confirm COD Order
Pay Online Instead

11:11 AM ✓✓

Scenario 02 / Billing dispute (SaaS)

Hand a dispute to billing without losing the thread

A B2B SaaS customer messages about a duplicate charge. Tier-1 documents it in a note on the customer’s contact, then reassigns the conversation to the Billing team inbox. Billing picks it up from the same shared queue — with the full history and the note already attached — confirms the refund, and replies. The customer sees one clean answer; three people collaborated behind it, and every handoff is logged.

  • Reassign to a Billing or Finance team inbox — the thread and its history travel with it
  • Document the case in a contact note your team sees and the customer never does
  • Role-based visibility keeps the conversation scoped to the people working it
  • Forward inbound messages and delivery events to your own systems via signed webhooks
9:41
WhatsMark
WhatsMark.io

online

Hey — I've been charged twice for the May invoice. ₹14,999 deducted on May 3 and again on May 4.

10:14 AM

Thanks for flagging, Karan. Pulling up your billing history now.

10:15 AM ✓✓

🔁 Reassigned to the Billing team — duplicate charge confirmed on account HA-2207: two successful captures, same amount, 24h apart. Refund approval needed.

10:17 AM ✓✓

Confirmed the duplicate on our side. A refund of ₹14,999 is initiated to your registered card and will reflect in 3–5 working days. Sorry for the trouble.

10:32 AM ✓✓

Scenario 03 / Lead protection (sales team)

One sales number, every rep walled to their own leads — no poaching, no peeking.

A sales team fields inbound WhatsApp enquiries on one shared number. Each new lead is assigned to a rep — by region, by product, or on a round-robin rotation. From then on, a rep's inbox shows only the leads assigned to them: another rep's conversations, and those leads' phone numbers, simply don't appear in their queue. It's enforced on the query itself, not just hidden in the UI, so a rep can't scroll into a colleague's deal or lift a lead's number from the inbox. The sales manager and owners see the whole floor and can reassign in a click.

  • Assign each inbound lead to a rep — by hand, or auto via round-robin / next-online agent
  • Each rep's inbox shows only their own leads — other reps' threads and numbers never appear
  • Query-enforced visibility, not UI hiding — no peeking at a colleague’s deal
  • Managers and owners see every lead and can reassign or step in anytime
9:41
WhatsMark
WhatsMark.io

online

Hi, I saw your ad for the enterprise plan. Can someone share pricing for 50 seats?

3:20 PM

🔁 Auto-assigned to Rhea · West region — round-robin.

3:20 PM ✓✓

Hi Arjun, this is Rhea from WhatsMark. Happy to help — for 50 seats you’d be on our Enterprise tier. Can I ask which city you’re based out of?

3:22 PM ✓✓

Bangalore. We’re a 200-person team, evaluating a few vendors.

3:23 PM

Got it — I’ll send over the Enterprise deck and a slot for a 15-min call this week. This lead is now scoped to me, so you’ll always reach the same rep on this thread.

Book a Call
Send Pricing PDF

3:25 PM ✓✓

What your customers see

Templates that show how teams really collaborate — assignment, handoffs, escalations.

Real WhatsApp threads — drop them straight into your account or use them as starting templates.

Assign → hand off to senior CX
9:41
WhatsMark
WhatsMark.io

online

Hi, the kurta I ordered (ORD-9912) has a stitching defect on the left sleeve.

11:02 AM

I'm sorry to hear that, Aanya. Could you share a photo of the defect so I can raise the replacement?

11:03 AM ✓✓

[image attached]

11:05 AM

🔁 Assigned to Vikram · Senior CX — genuine defect, photo confirms; within the 14-day window. Replacement from Hyderabad; flagged supplier batch SUP-227 (fourth complaint this week).

11:06 AM ✓✓

Confirmed — a replacement is shipping from our Hyderabad warehouse, arriving in 3 working days. The defective piece will be picked up at the same time. Apologies for the slip.

Track Replacement
Talk to Senior CX

11:08 AM ✓✓

Tier-1 → billing team handoff
9:41
WhatsMark
WhatsMark.io

online

Hey — I've been charged twice for the May invoice. ₹14,999 deducted on May 3 and again on May 4.

10:14 AM

Thanks for flagging, Karan. Pulling up your billing history now.

10:15 AM ✓✓

🔁 Reassigned to the Billing team — duplicate charge confirmed on account HA-2207: two successful captures, same amount, 24h apart. Likely the May 3 retry that did not catch the May 4 success. Refund approval needed.

10:17 AM ✓✓

Confirmed the duplicate on our side. A refund of ₹14,999 is initiated to your registered card and will reflect in 3–5 working days. We've patched the retry logic that caused it. Sorry for the trouble.

10:32 AM ✓✓

Reception → doctor handoff
9:41
WhatsMark
WhatsMark.io

online

Hi, I'm getting sharp chest pain on the left side since this morning. Should I come in today?

8:48 AM

Good morning. I'm assigning this to Dr. Mehra (cardiology) right now — please don't wait for a routine slot. One moment.

8:49 AM ✓✓

🔁 Assigned to Dr. Mehra · Cardiology — Sunita Rao (UHID 4422), 52F, sharp left-side chest pain since morning. Feb 2026 ECG on file. Reception suggests an urgent slot.

8:49 AM ✓✓

Dr. Mehra here. Please come directly to OPD-3 — I will see you ahead of my scheduled list. Bring the Feb ECG printout if you have it. If the pain worsens before you reach, call 108.

Confirm Coming In
Share Location

8:51 AM ✓✓

By the numbers

Specific, defensible, no fabricated stats.

Agents on one number

1 → unlimited

Free 1 · Professional 5 · Reseller unlimited — add seats with the Extra Team Members add-on

Channels in one inbox

WhatsApp + Messenger

One real-time queue across both, on the official Meta Cloud API

Markup on Meta charges

0%

You pay Meta's conversation rates directly — from ₹0.30 in India — nothing added

FAQ

Common questions, honest answers

Don't see your question? Email me at mailto:[email protected] — I read and answer every one personally.

It's a workspace where multiple agents share access to one WhatsApp Business number through the official Cloud API. Conversations land in a single real-time inbox, get assigned to specific agents or routed to named teams, and stay visible to the right people through role-based access. The customer sees one number and one brand; your team sees a structured queue with a full assignment history.

Yes — that's exactly what the WhatsApp Cloud API enables, and exactly what the regular WhatsApp Business app does not. With WhatsMark, every agent signs in with their own credentials and conversations route via assignment. The Business app is single-login and manual; once your support team has more than one person on WhatsApp, you can't share a login, you can't route, and you can't see who handled what. The Cloud API plus a shared inbox like this is the supported path.

The Business app is built for one phone, one user. The shared team inbox is built for multi-agent teams: one real-time queue, per-conversation assignment, named team inboxes, role-based visibility, canned replies, AI reply assist, and both WhatsApp and Messenger in the same screen. The Business app maxes out at a few linked devices with no admin layer, no routing, and no visibility controls — anything past two agents needs the Cloud API path.

Assign any conversation to one or more agents in a click, or route it to a named team inbox such as Sales, Support, or Billing. Every assignment and handoff is recorded — who did it, the change, and the timestamp — and the new assignee inherits the full thread, so the customer never re-explains. New incoming conversations can also be auto-assigned: pick a strategy per workspace — round-robin (rotate evenly through the team), next online agent, or a fixed team member — or leave it off and assign everything by hand. (Skill-based and language-based routing aren’t part of the product today.)

Add internal notes on a contact that your whole team can see but the customer never does — order IDs, context, a reminder for a new hire. They persist across every conversation with that contact. Role-based visibility then controls who sees which threads: owners and admins see everything, while each agent sees only the conversations assigned to them or shared with their team. It's enforced on the query, so a thread is never exposed to an agent who shouldn't see it.

Today, via our developer tools: WhatsMark forwards signed webhooks for 30 Meta event types (inbound messages, delivery, read, and more) to any endpoint, and the REST API exposes Conversations and Messages — enough to sync a transcript into most helpdesks. Native one-click connectors for Zendesk, Freshdesk, and Intercom are on the roadmap, not shipped yet.

You pay a flat platform plan, not a rising per-seat bill. Each plan includes team members — 1 on Free, 5 on Professional, unlimited on Reseller — and you can add more seats anytime with the Extra Team Members add-on. On top of that, WhatsMark adds 0% markup to Meta's per-conversation charges, which you pay Meta directly on your own Meta Business Account. So your cost is a predictable plan fee plus Meta's own rates — not a per-user ladder with a hidden margin like many BSPs.

The Reseller plan is built for scale — unlimited team members, unlimited WhatsApp numbers, unlimited bot flows, and a custom domain for your workspace. Today, agencies typically run each client as its own WhatsMark workspace, fully isolated. Full multi-client sub-account management from a single master dashboard is on our B2B roadmap; ask us where it stands if that’s central to your setup.

Not ready to start today?

Get the WhatsApp automation starter kit —
the flows every business should run.

No spam — just the starter kit in your inbox.