Running WhatsApp customer support as a team

In Turkey, customers don't email. They message on WhatsApp. Product questions, shipping updates, refund requests, invoice copies, all of it lands on one number. In a small business that number usually lives on one person's phone, and as the business grows the same scene repeats: the phone travels around the office, two people answer the same customer, someone says "I thought you had it", and three messages go unanswered overnight.

The problem isn't the team. It's that a tool built for personal messaging is being used for work that needs a queue.

How far the WhatsApp Business app gets you

The Business app is genuinely good for a one-person operation. Catalogue, quick replies, labels, several linked devices. It holds up for two people.

It cracks at the third, because questions start that the app has no answer for:

• Who picked this one up? The app doesn't know. Everyone sees everything and nobody owns anything.
• What did we tell this customer last time? There's history, but it isn't searchable, and if they also wrote from your website, that thread lives somewhere else entirely.
• How do I leave my colleague a note? You don't. A separate WhatsApp group gets created for notes the customer shouldn't see, and context splits in two.
• What happens when someone leaves? If the number is on their phone, so is the history.

None of this is a missing feature. It's just not what the app is for.

Why the Business API is overkill for most teams

The next step up is the WhatsApp Business Platform, the API. It's the right answer at enterprise scale, but for a small team the cost is higher than it looks:

• Meta requires an application and business verification.
• Any message you send before the customer writes first has to go through template approval.
• Billing is per conversation. If you're used to a flat monthly cost, forecasting gets harder.
• You usually go through a solution partner (a BSP), so there's one more party in the chain.
• Once your number moves to the API, you can't keep using it in the WhatsApp app on your phone.

For a business handling 50–200 messages a day, that's more work than it solves.

A third option: your number as a linked device

WhatsApp's linked devices feature lets one number be used from several places. WhatsApp Web has worked this way for years. The same mechanism can connect your number to a shared inbox: you scan a QR code, and messages arrive in the inbox as well as on the phone.

Your number doesn't change, there's no application, and there's no per-conversation fee. The only thing that changes is that messages now form a queue.

What the queue actually fixes

Four things resolve themselves the moment conversations have owners:

1. Ownership. Someone claims the conversation and their name is on screen. Two people answering the same customer stops.
2. Handover. A pricing question goes to sales, a refund to accounts, with the history attached.
3. Internal notes. "This customer had the same problem last month, go gently" sits inside the conversation, not in a separate group chat.
4. Closing. An answered conversation leaves the list. What's on screen at the end of the day is work that's genuinely waiting.

Add canned responses on top. Shipping times and refund policy are answers you write dozens of times a day; behind a shortcut, your agents' attention goes to the questions that actually need thinking.

Why it matters that web chat sits in the same place

In most businesses, customers arrive through both doors: they open the chat while browsing, then message on WhatsApp the next day. If those are two separate apps, your agent starts from zero on the second conversation and the customer repeats themselves.

When both identities merge into one contact, that repetition ends. In Lunachat, web chat and WhatsApp share one inbox, and the contact card shows both histories side by side.

What to watch out for

The linked-device route isn't a cure-all. Pick it knowing its limits:

• The phone needs to come online regularly. The session survives for a while with the phone off, but it isn't fully independent.
• It isn't for bulk messaging. WhatsApp's own rules don't allow broadcast blasts, and doing it can get your number restricted.
• Moving to the API later is a migration. You don't need to plan for it now, but know it's a one-way door.

Where to start

Setup is one step: scan a QR code from the panel with your phone. The full walkthrough is on the WhatsApp integration page.

If you also want chat on your site, two lines of script do it. We've written separate steps for WordPress, Shopify, Wix and any custom site.