WhatsApp for Sales and Customer Support: A Team Playbook

Using WhatsApp for sales and customer support works best when the same team, the same number and the same customer history serve both. A buyer who asked about a product on Monday and has a delivery problem on Friday shouldn't have to explain themselves twice. This playbook sets out the process (roles, stages, scripts, response targets and reviews) that turns a busy WhatsApp number into a dependable sales and support channel, using a shared inbox on the WhatsApp Business API.

Key takeaways

• Split work by stage, not by phone: new lead, qualified, quote sent, won, then support.
• Set response targets you can actually meet, and use automation to cover the gaps (welcome, away, AI).
• Write scripts for the 10 conversations you have every day, and save them as quick replies.
• Use labels and a pipeline so every lead has a next step and an owner.
• Review first response time, resolved chats and won deals every week.

Why WhatsApp works for both sales and support

• Customers already use it, so there's no new app and no login.
• It's asynchronous. The customer replies when they're free, and so do you.
• It's rich. Photos, voice notes, documents and in-chat forms let you show and collect what a call can't.
• History stays in one place. On a shared inbox, the full thread belongs to the business, not to an employee's phone.

The catch: WhatsApp feels personal, so slow or careless replies feel worse than a slow email. Process matters.

Step 1: Set up roles and routing

In ReploChat you can restrict which labels a manager sees, so a branch team only sees its own chats. See our article on the shared WhatsApp team inbox.

Step 2: Define your stages with labels

Use labels for stages that matter for action, and keep the list short:

1. New lead: first contact, not yet qualified.
2. Qualified: you know what they want, their budget or size, and their city.
3. Quote sent: a price or proposal has gone out. This is the label that should start a follow-up sequence.
4. Won / Lost.
5. Support and Complaint for after-sale issues.

For deals with real value (furniture, property, courses, B2B orders), also put the opportunity on the Kanban Pipeline and drag it through stages. The sales pipeline guide shows how, and the WhatsApp CRM guide explains how labels, fields and the pipeline fit together.

Step 3: Response targets and coverage

Pick targets that match your staffing, then automate the rest:

• Instant: a welcome message on the first message of every new chat.
• Within minutes during hours: answers to simple questions, either from an agent with quick replies or from the AI assistant using your business profile.
• Out of hours: an away message that gives your next opening time. The AI assistant can keep answering factual questions and hands anything it can't handle to the team for the morning.

Away message sample:

Thanks for messaging! We're closed now and back at 10:00 AM tomorrow. You can still ask about prices, sizes or delivery here and get an instant answer. For anything else, our team will reply first thing.

Step 4: The sales playbook

Qualify fast

Ask two or three questions before you quote. You can ask them in chat, with a chatbot's question nodes, or with a WhatsApp Flow form.

Happy to help! To give you the right price:
1) Which size or model are you looking at?
2) Which city should we deliver to?
3) When do you need it?

Quote clearly

Here's your quote, {name}:
• 3-seater sofa, Oak frame, Grey fabric: Rs 89,000
• Delivery to Islamabad: free
• Ready in 10–12 working days
Payment: 30% advance by bank transfer, balance on delivery. Shall I reserve it for you?

Then add the label Quote sent.

Follow up without nagging

A follow-up sequence that stops when the customer replies works well here. For example: a check-in after 1 day, a reason to act after 3 days, and a polite last message after 7 days. Ready-made copy is in WhatsApp follow-up message templates.

Handle the common objections

Close and confirm

Confirm in writing (item, price, delivery date, payment), mark the deal Won, and move it on the pipeline. For online stores, the Shopify and WooCommerce integrations send order confirmations and COD confirmation buttons automatically.

Step 5: The support playbook

Triage in the first reply

Sorry to hear that, {name}. Could you send your order number and a photo of the issue? We'll sort it out today.

Use notes, not side chats

When support needs a warehouse or finance colleague, write a private note with an @mention inside the chat. The context stays with the customer record.

Snooze instead of forgetting

Waiting for a courier update? Snooze the chat until tomorrow morning so it comes back to the top.

Close the loop

All sorted, {name}: your replacement left our warehouse today and should reach you by Thursday. Anything else we can help with?

Then resolve the chat. If the customer writes again, it reopens automatically.

Prevent the ticket

The best support message is the one that answers the question before it's asked. Proactive utility templates such as "order shipped" and "out for delivery" cut "where is my order?" chats. Templates you can adapt are in WhatsApp template message examples.

Handover rules between sales and support

Most friction happens at the moment a buyer becomes a customer. Agree on these rules once and write them down:

• Who owns the chat after the sale? A common rule: the salesperson owns it until delivery, then support takes over any issues.
• How is the handover marked? Change the label from Won to Support and reassign the chat, with a note that summarises the order and anything promised.
• What did sales promise? Put delivery dates, discounts and special requests in a note, so support doesn't contradict them.
• When does support pass back to sales? When a happy customer asks about a new purchase, label the chat New lead and reassign it.

Sample handover note:

@Ali order #10521 placed: 3-seater sofa, grey, Rs 89,000, 30% advance received. Promised delivery by 14 Nov and free cushion covers. Customer prefers calls after 6 PM.

Training a new agent in one day

1. Morning: read 20 resolved chats from each stage to learn the tone and common questions.
2. Late morning: learn the labels, quick replies and the 24-hour rule. Practise sending a template to a chat whose window has closed.
3. Afternoon: handle live chats with a senior agent reviewing replies through notes.
4. End of day: go over what they found hard, and add any missing quick replies.

Step 6: Ten quick replies every team needs

1. /hours: opening hours and location
2. /delivery: delivery areas, times and charges
3. /cod: cash-on-delivery terms
4. /bank: bank transfer details
5. /return: return and exchange policy
6. /size: size guide (with an image from the media library)
7. /order: "please send your order number"
8. /thanks: an order thank-you
9. /sorry: an apology plus next step for complaints
10. /human: "I'm passing you to my colleague who handles this"

Tone guidelines for the whole team

• Write the way a helpful shop assistant speaks: short sentences, plain words, no jargon.
• Use the customer's name once per conversation, not in every message.
• One or two emojis are fine. A row of them looks unprofessional in a complaint.
• Never leave a customer on "let me check" for hours. Snooze the chat and give a time: "I'll update you by 4 PM."

Step 7: Review every week

Thirty minutes every Monday with reports:

• Average first response time overall and per agent.
• Chats replied to and resolved per agent.
• Busiest hours: adjust shifts or extend AI coverage.
• Pipeline movement: deals stuck in Quote sent for more than a week.
• Top 5 questions agents answered by hand. Add them to quick replies or the business profile.

Industry notes

• E-commerce: COD confirmation and delivery updates matter most. See WhatsApp for e-commerce.
• Real estate: qualify on budget, area and timeline, then hand off to the agent for that area.
• Clinics and salons: collect appointment requests with a Flow form and confirm by message. Use date reminders for check-ups.
• Education: answer fee and admission questions with AI, and collect enquiries with a lead form.

FAQ

Can I use WhatsApp for customer service legally?

Yes. Customers who message you can be answered freely for 24 hours. For proactive messages, use approved templates and make sure customers opted in.

How fast should we reply on WhatsApp?

As fast as you can reliably manage during business hours. Use a welcome message and the AI assistant to give an immediate first answer, and set a team target for the human reply.

Should sales and support use different numbers?

Not necessarily. One number with labels and assignment keeps the customer's history together. Separate numbers make sense for separate brands or branches.

Can the AI handle support completely?

It can answer factual questions from your business profile and hands over when it's unsure or when the customer asks for a person. Complaints and judgement calls should stay with people.

How do I track which chats became sales?

Use stage labels and the pipeline. Mark deals Won, and compare with chats and campaigns over the same period.

Put this playbook to work on one shared number. Start a free ReploChat trial or see plans on pricing.