Customer support on WhatsApp: A 2026 playbook for Indian brands

WhatsApp is now the default support channel for most consumer-facing Indian brands. It outperforms email on response time, beats phone on cost-per-resolution, and beats web chat on customer preference (because the customer doesn't need to keep a tab open).

But "we're on WhatsApp" and "we run scaled support on WhatsApp" are very different operational maturity levels. This playbook covers the practical building blocks for the second one in 2026.

The 24-hour service window — the rule that changes everything

WhatsApp's service window is the single biggest concept that separates WhatsApp support from email or web chat. Whenever a customer messages you, a 24-hour window opens. During that window:

• You can send any message — text, image, video, document, list, button — without a pre-approved template.
• The conversation is categorised as a "service conversation" by Meta.
• Meta gives you the first 1,000 service conversations per WABA per month free.

When the 24-hour window expires, you can no longer send free-form messages. To re-engage, you'd have to send a pre-approved template — which usually costs ₹0.115+ as a utility conversation.

What this means for support workflows:

• Try to resolve inside the window. Every minute counts. Customers who don't get a response in the first hour drop the conversation 60% of the time.
• Auto-acknowledge instantly. A quick "Hi, we got your message — an agent will reply shortly" keeps the window warm.
• Use templates strategically. When you must reach back outside the window (e.g. an order issue takes 3 days to investigate), use a utility template like "Update on your order #{{1}}" with a prompt for the user to reply, which re-opens the window.

WBIZ shows the service-window countdown on every conversation in the inbox so agents always know how much time is left.

WhatsApp Business profile — get the basics right

Every WABA-connected number has a public business profile that customers see when they tap your name in chat. Fill all of it:

• Business name — your legal or trading name (the same one you submitted for display name approval).
• Description — 1–2 sentences. What you sell, where you operate.
• Address — your registered or primary office. Maps integration uses this.
• Email — a real, monitored support email. Customers do click through.
• Website — your homepage.
• Hours — actual support hours. Customers calibrate expectations off this.
• Categories — pick the closest Meta category. Affects discoverability.

This takes 15 minutes and is one of the highest-leverage things you can do for trust signal. Brands without a complete profile look like spam to first-time chatters.

Agent assignment — when one inbox isn't enough

A single WhatsApp number serves your entire customer base. The challenge inside your business is making sure conversations land on the right team member without descending into chaos.

Common patterns we see in Indian support teams:

Round-robin assignment

New incoming chat → assigned to whichever agent has the least active conversations. Works for teams of 3–10 with similar capability across agents. WBIZ does this out of the box.

Skill-based routing

Incoming chat → keyword detection or a pre-chat Flow → routed to the team that handles that topic (Returns / Tech / Billing). Best when your team is segmented by expertise.

Tier-based escalation

Chats start with a bot or a junior agent. Complex issues escalate to senior agents. Works at scale (50+ agents) when call volume justifies the layering.

Across all three, the operational rules that matter:

• One conversation, one agent. Hand-offs should be visible to the customer, not silent. ("Vikram from our delivery team will help you from here.")
• Internal notes that the customer doesn't see. Critical for hand-offs. Every modern WhatsApp inbox supports this.
• SLA timers per ticket. If an agent doesn't respond in X minutes, auto-reassign or page a manager.

Saved replies and macros

Most support tickets in any vertical follow a long-tail distribution where the top 30 questions account for 70% of volume. Saved replies are the cheapest productivity boost you can give your team.

Patterns that work:

• Order status — /order in the agent's input → autocomplete → message with order ID variable.
• Refund initiation — /refund → a templated message + an internal note that flags this conversation for accounts.
• Office closed — /closed → a friendly out-of-hours message with the next available slot.

WBIZ's saved reply autocomplete is shared across the team — when one agent writes a great answer, it becomes available to everyone.

Conversation analytics that matter

The metrics that actually drive support quality on WhatsApp:

• First Response Time (FRT) — how quickly an agent picks up. Target: under 2 minutes during business hours.
• Average Handling Time (AHT) — how long a conversation takes to resolve. Trade-off: too short and quality drops, too long and capacity dies.
• Resolution rate inside the 24-hour window — direct cost lever. Higher = lower Meta fees.
• CSAT — collected via a quick-reply survey at end-of-conversation. Yes/no/face-emoji works fine; long surveys kill response rate.
• Topic distribution — what are people contacting us about? Drives self-service investments.

WBIZ's analytics module ships these out of the box.

Scaling beyond one number

If your support volume goes above ~5,000 conversations a month, a single WABA number starts to feel constrained — not technically (Meta scales tiers automatically), but operationally:

• Routing complexity — segmenting by team gets harder when everything funnels into one inbox.
• Brand isolation — a multi-brand company often wants brand-specific WABAs.
• Risk isolation — a quality-rating drop on one number doesn't affect the others.

The 2026 best practice is one WABA number per support brand, plus a separate WABA for marketing. Marketing carries higher policy risk; isolating it from support means a marketing misstep doesn't take your support channel down.

WBIZ's WhatsApp account switcher lets agents move between numbers in one click; routing rules and templates are scoped per number.

What "good" looks like in 2026

A well-run WhatsApp support op in 2026 looks like:

• 24/7 first-response acknowledgement, even if just a bot.
• 90%+ of conversations resolved inside the 24-hour service window.
• Average FRT under 5 minutes during business hours.
• CSAT above 4.4 / 5.
• Cost per resolution 60–70% lower than the equivalent on phone.

None of these are reachable without disciplined inbox design. None of them require enterprise headcount. A 4-person team running on a modern WhatsApp inbox can serve 50,000 customers comfortably.

After-hours coverage without 24/7 staffing

A common worry for smaller teams: customers expect WhatsApp responses around the clock, but you can't justify a night shift. Three patterns work in practice:

• Bot triage with honest expectations. When a customer messages outside hours, an auto-response acknowledges receipt, sets the next-available-agent expectation ("we'll reply by 9am tomorrow"), and offers self-service links. Customer satisfaction stays high because the expectation is set, not violated.
• Tiered escalation rules. Most after-hours messages are not urgent. Bot-triaged "is my order shipped" gets answered automatically. The 5% of genuinely urgent issues (payment failure, allergy emergency for healthcare) are paged to an on-call agent's phone.
• Geographic agent rotation. If your customer base spans timezones (NRI customers in the Gulf, EU diaspora), staff to those windows specifically rather than blanket 24/7 coverage.

Brands that get this right see no measurable CSAT drop versus brands paying for full overnight coverage — and they save 60-70% on staffing.

The brands that win on support in 2026 aren't the ones spending the most. They're the ones who treat WhatsApp as the front door — designed, instrumented, and improved every week.