Support process

WhatsApp customer support for a team

The number is already the support line. The missing piece is a queue the team can run: open, pending, resolved, a label, and a saved reply. Not a new phone. Not “five people sharing a PIN.”

AED 499 / 999 / 1,999 per workspace / month · 7-day trial on Ziina

Not a full ITSM helpdesk. The product page is the WhatsApp shared inbox.

Already the support line

WhatsApp is the queue. The team still needs a process.

If customers already write WhatsApp for order questions, appointment changes, and “where is my invoice,” you do not need a new channel. You need the habits a mailbox already has: a status, a label, a reusable answer, and a place the next agent looks first.

Support teams copy those habits onto email without thinking. On WhatsApp they often copy them onto one person’s phone. The unread badge becomes the ticket list. There is no pending. There is no resolved. Yesterday’s promise lives in a scrollback no one else can search.

This page is not five employees on one handset. It is not how to assign a chat. Those jobs have URLs. This one is the care process: open / pending / resolved, labels, saved replies — for a team that already treated WhatsApp as support and outgrew a personal inbox.

Three states

Open, pending, resolved — honest enough for a shift

Open means the customer is waiting or the work is still live. Pending means you sent the last public message and you are waiting on them, a warehouse, or a clinician. Resolved means the next person should not treat the thread as new. That is the whole model. We do not ship an ITSM SLA clock, a CMDB, or change tickets. The shared inbox page says the same thing.

Teams get in trouble when “done” lives in one head. The person who sent “we will confirm tomorrow” goes home. The morning agent sees an unread tick and writes a second, different promise. Status does not make that impossible. It makes the lie visible: pending is still pending.

Open

Live work. The customer is waiting, or you have not finished the reply.

Pending

You wrote. You are waiting. The next shift should not “start over.”

Resolved

Closed enough to leave the pile. Reopen it if they write again.

Filters the next agent trusts

Labels and saved replies are the daily tools

Labels mark the work you actually filter: billing, first contact from an ad, waiting on a supplier, VIP. Twelve unused labels are worse than two that change what the next agent does. They are not medical records, not a CRM sync, and not a report we invent.

Saved replies are the answers you already trust — hours, return window, how to send a receipt. A person still picks one and sends it. That is live. AI suggested replies — a draft the model writes — are coming soon. Autonomous answering is coming soon. We mark both. We do not sell them as live on a support page.

Search is for the promise someone made last Tuesday. Notes are for the sentence the customer should not see. Mentions pull a specialist without opening a side group. All of that is the same workspace once WhatsApp Business is connected. Instagram and email can sit in the same queue later. You do not have to connect every channel on day one.

Limits

A support inbox, not a campaign suite or a helpdesk suite

InboxBay connects to WhatsApp Business. It does not replace it and is not a BSP. If you need broadcasts, chatbots, and a WhatsApp-led campaign platform, read InboxBay vs WATI and stay on WATI if that is the job. If you need a contact-metered messaging suite, read InboxBay vs respond.io. We do not invent their prices.

The stack is a Chatwoot MIT core plus an InboxBay overlay. Hosted demo: demo.inboxbay.work. Plans: Starter AED 499, Growth AED 999, Business AED 1,999 per workspace / month, 7-day trial on Ziina. Meta still bills template and marketing messages. Automations and round-robin are live on Growth. Suggested replies are not.

Labor versus those list prices, from the hours and hourly AED you type: WhatsApp team cost calculator. No industry-average constants.

InboxBay is not a full ITSM helpdesk. Open / pending / resolved, labels, and saved replies are the support process we actually ship on WhatsApp.

FAQ

Straight answers

Can a support team use WhatsApp as the customer line?

Yes — many already do. The gap is process: open, pending, resolved, a label the next agent can filter, and a saved reply for the question you answer every day. A shared inbox is that process on the number customers already saved.

What do open, pending, and resolved mean here?

Open: the customer is waiting or the work is still live. Pending: you replied and you are waiting on them or on a supplier. Resolved: the next shift should not treat it as new. These are conversation statuses, not an ITSM SLA module we do not ship.

Are saved replies the same as AI answering?

No. Saved replies are text you already approved. A person still sends them. AI suggested replies and autonomous answering are coming soon and are not sold as live.

Is this “five employees, one phone”?

No. That ops problem has its own page. This page assumes WhatsApp is already the support line and asks how the team runs a queue: status, labels, saved replies.

Does InboxBay replace a helpdesk?

No. It is a shared inbox — assignment, notes, status, labels — not a full ITSM helpdesk with SLAs, a CMDB, or change tickets. The shared-inbox page states the same limit.

How much does the support workspace cost?

Starter AED 499, Growth AED 999, Business AED 1,999 per workspace / month, 7-day trial on Ziina. Not per agent. Meta WhatsApp fees are extra and not marked up.

Who pays Meta’s WhatsApp message fees?

Meta bills WhatsApp per delivered template or marketing message. Conversation-based pricing was deprecated as of 1 July 2025. InboxBay does not collect or mark up Meta’s fees. You keep the WhatsApp Business number.

Keep reading
Ready when you are

Run the queue
you already have.

Start the demo. Connect the WhatsApp Business account customers already write. Status, labels, and saved replies are live.

demo.inboxbay.work · Login and Start free go to the same workspace