Shopify customer support: Gorgias, WhatsApp and helpdesk setup (India)

For most Indian D2C brands, the right support stack is a WhatsApp Business API app plus a shared inbox to start, and Gorgias only once you cross a few hundred tickets a month across channels. Buy the helpdesk to match your ticket volume and channel mix, not the marketing, because WhatsApp is the channel your customers actually use.

I build and maintain Shopify stores for D2C brands in India, the US, UK, and UAE, and support tooling is one of the first things a founder over-buys. This is the honest version: which tool at which stage, why WhatsApp sits at the centre for Indian stores, how to set up macros and SLAs that hold under a festive rush, and what the whole thing costs.

What problem is a helpdesk actually solving?

Before you pick a tool, name the problem. A helpdesk solves three things at once, and if you only have one of them you probably do not need Gorgias yet.

• Channel sprawl. Tickets arrive on WhatsApp, Instagram DMs, email, and sometimes a phone number, and no single person can watch all four. A helpdesk pulls them into one queue.
• Context switching. Answering "where is my order" means leaving the inbox, opening Shopify admin, finding the order, checking the courier, then coming back. A good helpdesk shows order data inside the ticket.
• Accountability. With volume you need to know who owns which ticket, how fast you reply, and what is still open. That is what SLAs and assignment give you.

If you are a founder answering thirty WhatsApp messages a day yourself, you have none of these problems yet. A shared inbox and a WhatsApp API app are enough. The helpdesk earns its cost when the queue outgrows one person's attention.

Why WhatsApp is the channel that matters in India

In most Western D2C playbooks, email is the support spine and chat is a bonus. In India it is inverted. Customers message a brand the way they message a cousin — on WhatsApp — and they expect a human-speed reply. Order-status questions, size queries, COD confirmations, and returns all start there.

That has two consequences for your stack. First, whatever helpdesk you choose has to treat WhatsApp as a first-class channel, not a bolt-on. Second, WhatsApp on Shopify runs on the WhatsApp Business API, which you access through a provider — Interakt, Wati, or AiSensy are the common ones in India — not through the free WhatsApp Business app on a phone. The API is what lets you send order updates, run broadcasts, and route two-way chat into a shared queue.

The single highest-leverage move in Indian D2C support is not answering faster. It is deflecting the "where is my order" question before it is asked — proactive WhatsApp shipping updates at dispatch, out-for-delivery, and delivered. That is also the biggest driver of repeat purchase behaviour, which is why I treat it as a conversion project, not just a support one. If your store is losing customers after the first order, the why your Shopify store isn't converting post covers the wider picture.

Gorgias vs the alternatives: which tool at which stage

Gorgias is genuinely good — it was built for e-commerce, it pulls Shopify order data into every ticket, and you can refund or cancel without leaving the helpdesk. But it is priced in USD and metered by ticket volume, which makes it expensive for an early Indian store. Here is the honest staging.

App and platform prices move; treat these as planning ranges and verify current pricing on each vendor's site.

A few notes on the options:

• Gorgias. Best-in-class Shopify integration, e-commerce-native macros and automation, all channels in one queue. As of 2026 it starts around $10–20/month and rises to roughly $60–360/month on higher tiers, often metered by tickets — verify on gorgias.com. Right for scaling stores where support is a real cost centre.
• Freshdesk / Zoho Desk. Cheaper, general-purpose helpdesks with solid WhatsApp and email support and India-friendly billing. Zoho in particular has local pricing and GST invoicing, which matters more than founders expect.
• Gmail / shared inbox + WhatsApp API app. The unglamorous starter stack. A shared inbox tool plus Interakt, Wati, or AiSensy covers a store's first year cheaply. Do not skip straight to Gorgias because a competitor uses it.
• Native Shopify Inbox. Free, handles the store chat widget and basic replies. Fine as a supplement, not a full helpdesk.

The mistake I see most is a store doing 200 orders a month paying for a scaling-stage tool because a bigger brand recommended it. Match the tool to your volume. When you outgrow the cheaper stack, migrating up is a day of work, not a crisis.

What does WhatsApp support actually cost?

WhatsApp API pricing has two layers people conflate. There is the provider's software fee (Interakt, Wati, AiSensy) and there is Meta's per-conversation charge that the provider passes through. As of 2026, Meta bills by conversation category, and utility and marketing conversations are priced differently, with some service conversations free within a window — this changes periodically, so verify current rates with your provider and on Meta's WhatsApp pricing page.

For a store sending a few thousand order-update messages a month, the all-in WhatsApp cost usually lands in a few thousand rupees monthly — cheap relative to the tickets it deflects and the repeat orders it drives. The templated messages (order confirmed, shipped, delivered) need Meta approval, which is a one-time setup step your provider or developer handles.

Macros and SLAs: turning support into a system

Software is the easy part. What separates a store with good reviews from one bleeding them is the operating layer on top: macros and SLAs.

Macros are saved replies for repeated questions. In Indian D2C, roughly ten macros cover 80 percent of tickets:

1. Where is my order (with a courier-tracking link)
2. Order confirmation for a COD order
3. Return / exchange process and window
4. Refund timeline and method
5. Size / fit guidance
6. Product availability / restock
7. Cancellation before dispatch
8. Damaged / wrong item received
9. Discount code not working
10. Delivery delay apology + revised ETA

Write these once, in your brand's voice, with the order variables auto-filled. They keep replies fast and consistent, and they let a new support hire sound like you on day one.

SLAs are target response times. For a growing D2C brand, a realistic set is: first WhatsApp reply within one business hour, first email reply within four business hours, resolution within one business day for anything not blocked on a courier. The point of an SLA is not perfection — it is a number you measure against, so support does not silently degrade during a rush. Pair it with proactive shipping updates and your ticket volume drops before the SLA is ever tested.

This system layer is the same discipline I apply to automations elsewhere — see Shopify Flow automations for D2C and abandoned cart automation in India, which share the same "set it up once, let it run" philosophy.

How many tickets should you actually expect?

Planning a support stack without a volume estimate is guessing. A rough rule for Indian D2C: 5–15 percent of orders generate a support contact, weighted heavily toward order-status questions during COD-heavy, courier-delayed periods.

Two things drive the number down hard: proactive WhatsApp shipping updates (kills most "where is my order") and a clear returns page (kills most process questions). Two things drive it up: COD, which invites cancellations and confusion, and courier delays, which you do not control but do absorb the tickets for. If you are planning festive-season readiness, tickets spike alongside orders — build the macros and staffing for the peak, not the average. The Diwali festive Shopify readiness post covers the wider prep.

Where a developer fits in

Most of a support stack is configuration a capable founder can do. Where I get pulled in is the integration and edge work that determines whether the whole thing feels seamless or bolted-on:

• Wiring the WhatsApp API provider cleanly into Shopify so order events (placed, shipped, delivered) fire the right templates automatically, without duplicate or missed messages.
• Building a proper returns/tracking flow on the storefront so customers self-serve before they ever open a ticket — the single biggest deflection lever.
• Custom metafields and theme work so support agents (and increasingly AI answer tools) can see the right product and order context; the metafield strategy for AI-readable stores post explains why that matters beyond support.
• Making sure the support widget and scripts do not tank your page speed — a badly-loaded chat widget is a common Core Web Vitals culprit.

If you want the support layer set up so it deflects tickets instead of just collecting them, that is exactly the kind of scoped work I do — see what a Shopify developer in Delhi handles.

What's next

If your support is sprawling across WhatsApp, Instagram, and email and you are not sure whether you need Gorgias or a cheaper stack, I can set the whole thing up properly — WhatsApp API wired into Shopify order events, proactive shipping updates, macros in your voice, and a returns flow that deflects tickets before they land. See how I work as a Shopify developer in Delhi, or tell me your order volume and channel mix on the project intake and I will give you an honest scope and a fixed number — including telling you if you should just start with the ₹1,000/month stack.

Related reads

• Best Shopify apps for Indian D2C brands — the wider app stack, support tools included.
• Klaviyo vs Omnisend vs Mailchimp for Shopify India — the messaging side of retention.
• Hidden costs of running a Shopify store in India — where support tooling fits in the real monthly total.

Sources

• Gorgias — helpdesk for e-commerce
• Meta — WhatsApp Business Platform pricing
• Shopify — Shopify Inbox