
To use WhatsApp Business for sales and support, start with the free Business app if one or two people handle chats, and move to the Business Platform (API) through an approved provider when you need several agents, a shared inbox, automation or CRM integration. Collect clear opt-in, use approved message templates for first contact, reply quickly, and always give customers a route to a human.
Key takeaways
- The Business app suits very small teams; the Business Platform (API) suits teams that need shared access, automation and integrations.
- Availability, rules and fees are set by the provider and change over time, so check the current documentation before you plan.
- Get explicit opt-in before messaging, and keep promotional broadcasts rare and relevant.
- Connect WhatsApp to your CRM and helpdesk so conversations become tracked leads and tickets rather than lost chats.
- Automation should handle simple, repetitive questions and hand over to a person smoothly.
Why does WhatsApp matter for customers in India and similar markets?
In India and many other markets, WhatsApp is already where people talk to family, shops and service providers. Customers are comfortable sending a quick message, a photo or a voice note, and many prefer it to filling in a web form or waiting on a phone line. For a business, that means lower friction at the exact moment someone is interested or has a problem.
It also changes expectations. A WhatsApp chat feels personal and immediate, so customers expect a faster reply than they would from email. Plan for that before you promote your number.
WhatsApp Business app vs Business Platform (API)
These are two different ways to use WhatsApp for a business, and choosing the wrong one is a common early mistake.
The WhatsApp Business app
This is the free app you install on a phone. It offers a business profile, a catalogue, quick replies, labels and simple away messages. It works well for a shop, a freelancer or a small clinic where one or two people reply from a single device. The limits show up quickly: no real team workflow, no deep integration, and limited automation.
The Business Platform (API)
The Business Platform is accessed through an approved provider or directly, depending on current rules. It connects WhatsApp to software, so many agents can share one number, conversations can be routed, and your CRM or helpdesk can read and write messages. It is built for automation, notifications and integrations rather than for typing on a phone.
Availability, features, message categories and pricing are set by the provider and by WhatsApp's own policies, and they change. Treat any article, including this one, as a starting point and read the current documentation before committing.
What are the best use cases for sales and support?
- Enquiries. Click-to-chat links on your website, ads and QR codes let people ask a question in one tap.
- Order updates. Confirmation, dispatch and delivery messages that customers actually read.
- Appointment reminders. Reminders and easy rescheduling reduce missed visits for clinics, salons and service businesses.
- Catalogues. Show products or services with photos and short descriptions inside the chat.
- Support. Customers send a photo of a fault or an order number and get help in the same thread.
- Follow-up. A polite check-in after a quote or demo, where the customer has agreed to hear from you.
How do opt-in and message templates work?
Customers should agree to receive messages from you before you start. In practice that means a clear tick box or a clear statement at the point of capture, such as "Send me order updates on WhatsApp", not a pre-ticked box buried in terms. Keep a record of when and how each person agreed.
When you want to start a conversation with someone, the platform generally expects you to use pre-approved message templates, while free-form replies are allowed within a limited window after the customer writes to you. The exact window, categories and approval process are defined by the provider and can change, so read the current rules and design your flows around them.
Good template habits: write in plain language, say who you are in the first line, use variables such as name or order number, keep one purpose per template and include a simple way to stop receiving messages.
How should you set up a shared inbox and routing?
Once more than one person answers, you need structure. A shared inbox lets several agents see the same conversations, assign ownership and leave internal notes. Routing rules decide where a new chat goes: by topic, language, product line or whether the sender is an existing customer.
A simple setup:
- Assign every conversation to one named owner.
- Use tags such as sales, billing and delivery issue.
- Set working hours and an away message that states when to expect a reply.
- Define when a chat is escalated, and to whom.
- Close conversations explicitly so your reporting is meaningful.
How do you connect WhatsApp to your CRM and helpdesk?
A conversation that lives only in a phone is invisible to the rest of the business. Integration fixes this. Sales chats should create or update a lead in a CRM and lead management system, with the full message history attached. Support chats should become tickets in a helpdesk and support portal, so priority, status and ownership are tracked like any other request.
For custom connections, such as pulling order status from your own system, an API integration is usually the route. Our article on connecting your tools through APIs explains the basics, and the same thinking applies to helpdesk processes that scale.
Where do automation and chatbots fit?
Automation is most useful for the first thirty seconds of a conversation: greeting, collecting a name and reason, answering common questions such as opening hours or order status, and routing the chat to the right person. Anything that needs judgement, empathy or an exception should go to a human.
Rules for responsible automation:
- Say clearly that the customer is talking to an automated assistant.
- Offer a visible option to reach a person at any time.
- Hand over the full context so the customer does not repeat themselves.
- Test with real past questions before going live.
- Review transcripts weekly and fix gaps.
Our guide to AI chatbots for customer support covers what tends to work and what does not.
What tone and etiquette work best?
WhatsApp is informal, but your business is still being judged. Greet by name, keep messages short, answer the actual question first and avoid long blocks of text. Use voice notes and images sparingly, and do not send messages late at night unless the customer started the conversation. Never forward customers' messages or numbers to others.
How should you handle privacy and data?
Chats contain names, phone numbers, addresses and sometimes sensitive details. Decide who can read them, how long you keep them, and where they are stored when exported to other tools. Tell customers how you use their data in your privacy policy, and ask for sensitive information through a safer channel if it is not needed in chat. Rules about consent and data protection differ by country and sector and change over time, so ask a qualified professional about your specific obligations.
How do you measure whether it is working?
Track a small set of measures that matter to the business:
- First response time and time to resolution.
- Share of conversations that end with a lead, sale or solved issue.
- How many chats are handled by automation and how many need a person.
- Opt-out and block rates after broadcasts, as a sign of relevance.
- Customer feedback after a closed conversation.
Common mistakes to avoid
- Sending broadcasts to a purchased or scraped list with no opt-in.
- Using one personal phone for the whole team.
- Automating everything and hiding the human option.
- Leaving chats unassigned so nobody owns the reply.
- Failing to record consent or to honour opt-outs.
- Promoting the number before you can answer promptly.
A worked example
Imagine a small physiotherapy clinic that takes bookings by phone and loses calls during treatments. It adds a click-to-chat link on its website and a QR code at reception. Patients who opt in receive an automatic greeting, choose a reason, and are routed to the front desk inbox. Appointment reminders go out as approved templates, and replies such as "reschedule" create a task for staff. All chats are linked to the patient record, and anything clinical is moved to a call. The clinic reviews response times every month.
FAQ
What is the difference between WhatsApp Business app and WhatsApp Business API?
The app is a free phone application for very small teams with basic tools such as a catalogue and quick replies. The API, or Business Platform, connects WhatsApp to software so many agents, automation and integrations can work on one number. Features and rules for both are set by the provider and can change.
Do I need customer consent to message people on WhatsApp?
You should get clear opt-in before sending business messages, and keep a record of it. Platform policies and local laws on consent differ and change over time, so check the current rules and ask a qualified professional about your situation.
Can I use WhatsApp for customer support?
Yes. Many businesses use it for order queries, troubleshooting and follow-ups. For a team, a shared inbox connected to a helpdesk and support portal keeps every chat assigned, tracked and measurable.
Should I use a chatbot on WhatsApp?
A chatbot can handle simple, repeat questions and route chats, which saves staff time. It should say it is automated, offer a way to reach a person, and be tested on real past questions first.
Related reading
- CRM Data Hygiene and Pipeline Stages That Actually Work
- Helpdesk Software: Build a Support Process That Scales
- AI Chatbots for Customer Support: What Works, What Backfires
- Marketing Automation for Small Teams: Workflows That Work
Next steps
Write down the three conversations you most want WhatsApp to handle, such as enquiries, order updates and reminders. Decide whether the Business app is enough or whether you need the API, then design your opt-in wording and first three templates. If you would like help planning an integration with your CRM or helpdesk, contact us and we will talk it through.



