WhatsApp for Customer Support: Setup, Automation & Best Practices (2026)

WhatsApp is the support channel customers actually open, reply to, and trust — and since November 2024 it is also the cheapest, because replies inside the 24-hour service window carry no Meta charge. Customers already live in WhatsApp; routing support there means no app to download, no hold music, no email that gets buried.

For Indian small businesses the economics are decisive. Phone support needs staff on calls; email is slow and ignored; SMS is one-way and pricey. WhatsApp gives you a two-way, threaded, media-rich conversation where a bot handles the routine 70% and a human picks up the rest. And the conversation history stays in one place, so the next agent has full context.

This guide walks through everything you need to run support on WhatsApp properly: how the free service window works, setting up a shared team inbox, automating with keyword bots, defining SLAs, escalating to humans, and measuring satisfaction. We close with best practices that separate a delightful support experience from a frustrating one.

When a customer messages your business, a 24-hour customer service window opens — and inside it, your replies carry no Meta charge at all. This is the single most important fact in WhatsApp support economics, and it has been true since Meta's November 2024 pricing change.

Here is how the window works:

• A customer sends you any message — a question, a "hi", a button tap. The 24-hour timer starts.
• Within those 24 hours you can send unlimited free-form replies with no template and no Meta charge. These are Service messages.
• Each new customer message resets the timer to a fresh 24 hours.
• If 24 hours pass with no customer message and you need to reach out, you must use an approved template, which carries Meta's category charge.

The practical upshot: as long as you respond promptly while the customer is engaged, support costs you almost nothing on the Meta side. Inbound messages are free, and your replies in the window are free of Meta charge. PayPerWA's ₹0.20 platform fee applies only to automated outbound messages we send on your behalf — a live agent's manual replies in the window simply flow through.

Setting up support starts with connecting a dedicated WhatsApp Business API number — ideally separate from your marketing number so support conversations stay clean. PayPerWA's embedded signup links your number to Meta's Cloud API directly, with no BSP in the middle.

1. Choose a support number. Use a number not already on a personal WhatsApp account. A dedicated support line keeps reporting and SLAs clear.
2. Complete embedded signup. Connect the number to your Meta WhatsApp Business Account through PayPerWA — it takes minutes.
3. Set your business profile. Add your logo, business hours, address, and a clear "About" line so customers trust the chat.
4. Publish a click-to-chat link. Put a wa.me link and QR code on your website, invoices, and packaging so customers can start a conversation in one tap.

Once connected, every inbound message lands in your team inbox. Builders who want to wire support into their own systems can use the API.

A shared team inbox is where multiple agents handle one WhatsApp number together without stepping on each other — the foundation of scalable support. Instead of one phone passed around the office, every conversation is visible, assignable, and trackable.

A good support inbox gives you:

• Assignment. Route a chat to a specific agent so two people do not reply to the same customer.
• Internal notes. Agents leave private notes on a thread the customer never sees.
• Labels and status. Tag conversations as open, pending, or resolved, and filter by topic.
• Full history. The next agent sees every prior message, so the customer never repeats themselves.
• Canned replies. Save common answers as quick-insert snippets to respond in seconds.

With the bot handling first contact and the inbox handling the human handoff, a two-person team can comfortably manage hundreds of daily conversations.

An auto-reply keyword bot answers the routine questions instantly, day or night, so customers get help in seconds and agents only see what truly needs a human. Meta permits business-automation bots like this — what it restricts in 2026 are general-purpose AI assistants, not structured business flows.

Start with these automations:

1. Welcome message. The instant a customer messages, greet them and show a menu: "1. Order status 2. Talk to support 3. Hours and location."
2. Keyword replies. Trigger answers on words like "timing", "price", "refund", or "track".
3. Order-status lookup. Ask for an order number and return live tracking from your backend.
4. Off-hours auto-reply. Outside business hours, set expectations: "We are closed now and will reply by 10 AM. For urgent issues, reply URGENT."
5. Catch-all fallback. If the bot does not understand, offer "Talk to a human" rather than looping.

For a complete walkthrough, read our guides on auto-reply and keyword automation and building a chatbot without coding.

Here are the highest-value support automations, what triggers each, and whether it incurs a Meta charge. Notice how many are free because they live inside the service window.

Only the last row leaves the free window. Everything else costs nothing on Meta's side; PayPerWA's ₹0.20 fee applies solely to automated outbound messages.

An SLA — service level agreement — is your promise on how fast you respond, and on WhatsApp customers expect minutes, not hours. Setting clear targets keeps your team honest and your customers calm.

Sensible starting SLAs for a small business:

• First response: bot replies instantly; a human picks up within 15 minutes during business hours.
• Resolution: simple queries closed same day; complex ones within 24-48 hours with status updates.
• Off-hours: auto-reply immediately, human follow-up by the start of the next business day.

Pair SLAs with routing rules: send billing questions to one agent, technical issues to another, and high-value customers to your most senior person. Because each customer message resets the 24-hour window, fast replies also keep your support inside the free zone.

Good escalation is invisible to the customer — the bot hands off to a human with full context, and the customer never has to repeat themselves. A clumsy handoff, where the bot loops or the agent asks "what is your issue?" again, is the fastest way to frustrate someone.

Build escalation like this:

1. Always offer an exit. Every bot menu should include "Talk to a human" so customers are never trapped.
2. Detect frustration. If a customer repeats themselves or types phrases like "this is not helping", route to an agent automatically.
3. Pass the context. Hand the agent the full chat plus any data the bot collected (order number, issue type).
4. Set expectations. Tell the customer "Connecting you to an agent — typical wait is under 5 minutes."
5. Return control gracefully. When the agent resolves the issue, the bot can take over again for the CSAT survey.

CSAT — customer satisfaction score — tells you whether your support actually helped, and WhatsApp makes it trivial to collect right after a conversation closes. A single in-chat rating gets far higher response rates than an emailed survey.

Track these metrics:

• CSAT: after resolving a ticket, send "How did we do? Reply 1 (poor) to 5 (great)." Watch the average over time.
• First-response time: how long until a human first replies.
• Resolution time: how long from open to resolved.
• Bot deflection rate: share of conversations the bot fully handles without a human — the higher, the cheaper.
• Reopen rate: how often a "resolved" issue comes back, signalling rushed fixes.

If the CSAT survey goes out while the customer is still inside the 24-hour window, it costs nothing on Meta's side too.

The businesses that win on WhatsApp support follow a handful of disciplines that turn a chat channel into a competitive advantage.

• Reply fast, stay in the window. Speed delights customers and keeps replies free of Meta charge.
• Let the bot handle volume, the human handle nuance. Automate FAQs; reserve agents for judgment calls.
• Never trap a customer in a bot. Always offer a human exit.
• Keep a human tone. Even automated replies should sound friendly, not robotic.
• Use a separate support number. Keep marketing and support distinct for clean reporting and trust.
• Respect opt-outs and privacy. Never push marketing through the support line.
• Review transcripts weekly. Find the questions the bot misses and add them.

Ready to set up support? Create a free PayPerWA account, see what is included on the features page, and check transparent costs on pricing and the rate card. Comparing tools? Visit our comparison page.