Industries
Restaurants & Food
Take restaurant orders, table bookings and payments in one WhatsApp chat. Auto-reply to common questions and cut support costs with ChatMitra.
Real Estate
Use WhatsApp automation to capture property leads, qualify them automatically, and follow up fast. See how real estate agents close more with ChatMitra.
Travel & Tourism
Use the WhatsApp Business API to capture travel leads, send itineraries, confirm bookings, and keep travellers updated. See how agencies grow with ChatMitra.
Banking & Finance
Run secure KYC, send account alerts and payment notifications on WhatsApp. Cut support load and stay within Meta's rules with ChatMitra.
Beauty & Cosmetics
Sell your catalog, recover carts and win repeat orders on WhatsApp. Auto-reply to product questions and send launches to opted-in customers with ChatMitra.
Education
Answer admission enquiries, fee and timetable questions, and keep parents updated — all on WhatsApp. Cut admin load and costs with ChatMitra.
EduTech
Capture course leads, qualify them and onboard learners on WhatsApp. Automate replies and cut lead-qualification cost with ChatMitra's no-code chatbot.
Events & Webinars
Handle event registrations, reminders and RSVPs in one WhatsApp chat. Cut no-shows, automate FAQs and keep attendees updated with ChatMitra.
Freelancers & Consultants
Capture leads, send proposals and chase invoices in one chat. WhatsApp automation for freelancers and consultants with ChatMitra — from ₹0.20 a chat.
Health & Wellness
Book appointments, send reminders and answer client questions in one WhatsApp chat. Auto-reply to routine queries and cut support costs with ChatMitra.
Home Decor
Share your home decor catalog, take orders and send delivery updates on WhatsApp. Automate FAQs and cut support costs with ChatMitra.
IT Services
Use the WhatsApp Business API to qualify leads, run support over chat, and wire WhatsApp into your stack with webhooks. How IT companies scale with ChatMitra.
Marketing Agencies
Use WhatsApp automation to capture leads, run campaigns and manage multiple client brands from one account. How agencies scale on WhatsApp with ChatMitra.
Offline & Retail
Turn shop footfall into a WhatsApp list. Share catalogs, add a QR-to-chat at the counter and bring buyers back — with ChatMitra from ₹0.20 per chat.
Spas & Salons
Use the WhatsApp Business API to take spa and salon bookings, cut no-shows with automated reminders, and rebook regulars. How salons grow with ChatMitra.
Automotive
Use the WhatsApp Business API for automotive dealerships to qualify buyers, book test drives and send service reminders — automated, on one chat, with ChatMitra.
All Industries
Browse every industry guide
Automation & Chatbots

WhatsApp Ticketing System: How to Turn Chats into Tickets

When a WhatsApp inbox needs tickets, how the ticket lifecycle fits Meta's 24-hour window, helpdesk options compared, utility templates and costs in ₹.

Nikunj Gohil
Written byNikunj Gohil
Read time 19 min
Posted on
WhatsApp Ticketing System: How to Turn Chats into Tickets
Summarise this post with:

Short on time? Read this first

  • A WhatsApp ticketing system gives each customer issue its own record, with an owner, a status and a due time, so problems raised in chat aren't lost in a long thread or answered twice.
  • You need one when several people answer the same number, when issues take more than one conversation to fix, or when you have to prove response times. A single person answering a handful of chats a day doesn't.
  • Plan around Meta's 24-hour customer service window. Your first-response target must be well inside it, and any update after it closes needs an approved template, which Meta charges for (₹0.115 per utility message in India since 1 October 2026).
  • There are three ways to run tickets: a shared inbox with a tag routine, a helpdesk with a native WhatsApp channel, or your WhatsApp platform connected to a helpdesk. They differ in cost per agent, setup effort and where replies land.
  • ChatMitra's inbox has no ticket IDs, assignment or SLA timers. Teams use tags, pins and notes as lightweight tickets, and move to a helpdesk when volume or reporting needs outgrow that.
On this page 0

    A WhatsApp ticketing system turns each customer issue that arrives on WhatsApp into a tracked record, a ticket, with an owner, a status and a due time. The customer just chats. Behind the scenes, your team can see who is handling the damaged parcel, which refund is waiting on the warehouse and which complaint is about to break your promised response time. Without it, issues drift down a busy inbox, get answered twice or not at all, and nobody can say how long customers wait.

    This guide is for support leads and business owners whose WhatsApp has outgrown “whoever sees it first replies”. It covers when you need tickets and when you don’t, how a ticket’s life fits WhatsApp’s 24-hour rule, the three ways to set one up, the templates and costs involved in India, and how to run a lightweight version in a shared inbox before you pay for a helpdesk.

    Key takeaways

    • A chat is a conversation; a ticket is one problem. One customer's WhatsApp thread can hold several tickets over time.
    • You need tickets once several people share a number, issues span more than one conversation, or you must report response times.
    • Set your first-response target well inside Meta's 24-hour window. Updates after it closes need a template, which costs money.
    • Pick between a tagged shared inbox, a helpdesk with a WhatsApp channel, or a connector. Check where customer replies land before you choose.
    • Measure first response time, resolution time, reopen rate and messages per ticket, not just "chats answered".

    What is a WhatsApp ticketing system?

    A WhatsApp chat is one long, continuous thread per customer. A customer who bought from you three times may have asked about delivery in March, reported a defect in June and requested an invoice copy last week, all in the same thread. A ticketing system separates those into distinct issues, each with its own record:

    FieldWhat it holdsWhy it matters on WhatsApp
    Ticket IDA unique reference, such as #4821Lets the customer and your team refer to one issue inside a long thread
    OwnerThe agent or team responsibleStops two agents replying to the same message
    StatusNew, open, waiting on customer, waiting on us, resolvedShows what needs action now, not just what's unread
    Priority and categoryUrgent or normal; refund, delivery, defect, billingRoutes work and shows which problems recur
    Due time (SLA)When the next reply or the fix is promisedHas to fit inside Meta's 24-hour reply window
    History and notesMessages, internal notes, linked orderThe next agent picks up without asking the customer to repeat everything

    “Unread” and “replied” describe the chat. “Waiting on the warehouse until Thursday” describes the issue. That difference is the whole point of tickets.

    Do you need a ticketing system?

    Not every business does. A shop owner answering 15 chats a day on one phone needs quick replies and an away message, not tickets. Use this checklist instead of guessing:

    SignWhat it looks likeWhat it means
    Double repliesCustomers get two different answers from two agentsYou need ownership
    "Did anyone reply to her?"Agents ask each other in a separate groupYou need status
    Forgotten promises"We'll call you tomorrow" and nobody doesYou need due times and a waiting status
    Multi-day issuesRefunds, replacements and repairs that need other teamsYou need tickets that outlive one conversation
    No numbersYou can't say how long customers wait or what they complain aboutYou need categories and reports
    Several channelsThe same customer also emails and callsYou need one record across channels, usually a helpdesk

    If one or two signs apply, a disciplined shared inbox will usually do. If four or more apply, or the last one does, budget for a helpdesk.

    The life of a WhatsApp ticket

    A ticket moves through the same stages in any tool. What’s specific to WhatsApp is the message you’re allowed to send at each stage, because free-form messages are only allowed for 24 hours after the customer’s last message.

    StageWhat happensWhat the customer gets on WhatsApp
    1. NewA message arrives that isn't part of an open issueAn instant acknowledgement, ideally with the reference and expected reply time
    2. AssignedAn owner and category are setNothing extra; don't send "assigned to an agent" filler
    3. In progressThe agent asks questions or investigatesFree-form replies inside the window
    4. Waiting on customerYou need a photo, an order number or a decisionOne clear question. If they go quiet past 24 hours, a utility template reminder
    5. Waiting on us or a third partyWarehouse, courier, technician or financeA dated promise ("by Thursday"), then an update, by template if the window has closed
    6. ResolvedThe fix is doneA summary of what was done and how to reopen
    7. Closed or reopenedNo reply for an agreed period closes it; a related reply reopens itOptional feedback request about this specific issue
    Green chat bubbles riding a conveyor belt past four stations labelled New, Open, Waiting and Resolved, with the line Every issue moves through the same stages
    A ticket's status says what the issue needs next. Unread and replied only describe the chat.

    Two rules make this work. Only a person or a clear rule changes a status, never “the chat was read”. And a customer reply to a resolved ticket within a few days reopens it rather than creating a new one, so your reopen rate stays honest.

    The 24-hour window and your SLA clock

    Meta’s customer service window opens when a customer messages you and lasts 24 hours from their latest message. Inside it you can send any message. Outside it, you can only send an approved template. This one platform rule shapes how you set service levels on WhatsApp.

    First response time must sit well inside the window. A four-hour first-response target leaves 20 hours to follow up freely. A 22-hour target leaves almost nothing, and if your answer needs a follow-up question you’ll be sending a template. Most teams set a first-response target in business hours (for example, 2 hours from 9 am to 7 pm) and an out-of-hours promise in the away message.

    Long tickets cross the window. A replacement that takes four days will outlive at least one window. Plan the update messages as templates before you need them, so agents aren’t stuck when the window closes.

    Every reply counts toward cost. Since 1 October 2026, Meta charges for service messages after 1,000 free per business number each month, and utility templates are charged even when you send them inside an open window. In India both cost ₹0.115 per message. Ticket handling that takes eight messages instead of four doubles the Meta part of the bill.

    An hourglass marked 24h whose falling sand is about to bury a small chat bubble on the lower floor, with the line Reply well before the window closes
    Meta's 24-hour window starts with the customer's last message. Your response target has to finish well inside it.

    Here is what Meta’s charges look like for a team handling 1,500 WhatsApp tickets a month on one number in India:

    ItemAssumptionMessagesMeta charge
    Free-form replies5 replies per ticket inside the window7,500 (6,500 after the 1,000 free)₹747.50
    Template updates30% of tickets need one update after the window closes450₹51.75
    Feedback requestsSent by template after resolution to every ticket1,500₹172.50
    Total9,450₹971.75 a month

    Meta's India rates effective 1 October 2026: ₹0.115 per service message after 1,000 free per number each month, and ₹0.115 per utility template. Excludes tool and platform fees.

    Meta’s charges are rarely the expensive part of ticketing. Per-agent helpdesk licences usually are, which is why the choice of setup matters more than message counts.

    Three ways to run tickets on WhatsApp

    1. Shared inbox with a tag routine2. Helpdesk with a WhatsApp channel3. WhatsApp platform connected to a helpdesk
    How it worksAgents work in a WhatsApp team inbox; tags, pins and notes act as ticket fieldsThe helpdesk connects to WhatsApp directly; every message becomes or joins a ticketMessages arrive in your WhatsApp platform; an integration creates or updates helpdesk tickets
    Ticket IDs, SLAs, assignment, reportsManual, by conventionBuilt in (by plan)In the helpdesk
    Where agents replyThe inboxThe helpdeskDepends on the integration; check before you buy
    Cost driverInbox planPer-agent helpdesk licence plus WhatsApp chargesBoth tools plus the integration
    Best forSmall teams where WhatsApp is the main channelTeams that also run email and phone supportBusinesses that use WhatsApp for marketing and sales too, and only want support issues in the helpdesk
    Main riskRoutine slips when the team is busyCost per agent; marketing tools live elsewhereTwo inboxes, and replies that land in the wrong one
    A road splitting into two lanes signposted Shared inbox and Helpdesk, with a green chat bubble choosing between them, with the line Pick the route your volume needs
    Most small teams start in a shared inbox. Volume, other channels and reporting needs decide when to move to a helpdesk.

    Helpdesks with a WhatsApp channel compared

    If you choose a helpdesk, check four things for WhatsApp specifically: which plan includes the channel, which plan adds SLA policies and automatic assignment (they’re often a tier higher), how Meta’s message charges are billed, and how the tool handles the 24-hour window. Here’s how five common options compared when we checked their pricing pages and help centres on 15 October 2026:

    HelpdeskLowest plan with WhatsAppSLA policies and auto-assignmentMeta's message charges
    FreshdeskGrowth, US$19 per agent a month billed annually (up to 50 WhatsApp numbers)Multiple SLA policies and round-robin or load-balanced assignment from Pro, US$55 per agent a month billed annuallyBilled through Freshworks with a 20% markup on Meta's cost
    ZendeskSuite Team, US$55 per agent a month billed annually (US$69 monthly)Routing by agent status and capacity on Suite Team; SLA policies from Suite Professional, US$115 per agent a month billed annuallySeparate from Zendesk's fees; the WhatsApp account stays in your Meta Business Manager
    Zoho DeskStandard, ₹800 per user a month billed annually (1 WhatsApp channel)4 SLAs on Standard; round-robin load-balanced assignment from Professional, ₹1,400 per user a month billed annuallyPaid from prepaid WhatsApp credits bought in Zoho
    HubSpot Service HubProfessional, ₹8,330 per seat a month on an annual commitment; the WhatsApp integration is listed as "up to 1,000 messages per month"SLAs in Professional; skill-based routing and conditional SLAs from Enterprise, from ₹12,500 per seat a monthPaid to Meta; up to 25 numbers per WhatsApp Business account
    Gorgias (ecommerce)All helpdesk plans; priced by tickets, not agents, from US$40 a month for 50 ticketsSLA policies on all helpdesk plansMeta bills Gorgias; WhatsApp conversations are billed to you as helpdesk tickets, with no separate Meta bill

    Prices exclude taxes and are the list prices shown on each vendor's site on 15 October 2026; Freshdesk, Zendesk and Gorgias showed US dollars and Zoho Desk and HubSpot showed rupees. Plans and limits change often, so confirm on the vendor's site before you buy.

    Three patterns stand out:

    • The features that make ticketing worth paying for often sit one tier above the WhatsApp channel. Freshdesk and Zendesk both include WhatsApp on their entry plans but keep multiple SLA policies (Freshdesk) or SLA policies at all (Zendesk) for the next tier. Price the plan you’ll actually need, not the cheapest one that lists WhatsApp.
    • Per-agent pricing changes the maths. For a team of eight, the difference between US$19 and US$55 per agent is nearly US$3,500 a year. A ticket-priced tool such as Gorgias suits small ecommerce teams with many agents and modest volume; per-agent tools suit large volumes handled by a few people.
    • Check how Meta’s charges reach your bill. Some helpdesks add a markup, some deduct prepaid credits, some fold them into ticket pricing, and some leave billing with Meta. Since 1 October 2026 every reply beyond 1,000 a month per number has a price, so a markup on Meta’s cost now applies to support replies too.

    Most of these helpdesks also show agents when the 24-hour window is about to close; Zendesk, for example, displays a countdown and switches to template replies after it expires.

    Setting up WhatsApp in a helpdesk, step by step

    The screens differ by vendor, but the order of work is the same:

    1. Choose the number. Use a number that isn’t already connected to another WhatsApp Business Platform provider, or plan a migration. A number can only be on one provider’s API at a time, and moving it takes coordination with both.
    2. Connect through the helpdesk’s signup flow. Most helpdesks use Meta’s embedded signup: you log in with Facebook, pick or create the Meta business portfolio, and verify the number by SMS or call. Keep the WhatsApp Business account in your own business portfolio so you can leave the vendor later.
    3. Verify your business with Meta. Unverified accounts have low messaging limits for business-initiated messages, which matters for ticket updates after the window closes.
    4. Submit your ticket templates. Acknowledgement, waiting-on-customer, update and resolved templates, as in the table below. Approval can take minutes or days, so do this before launch.
    5. Set ticket rules. Decide when a new message joins an open ticket and when it starts a new one, which group gets WhatsApp tickets, and the business hours your SLA clock uses.
    6. Set the SLA targets. A first-response target in business hours that sits well inside 24 hours, and a resolution target per category.
    7. Test end to end. From a personal phone, open a ticket, let the window lapse, receive a template update, reply, and confirm the reply lands on the same ticket.
    8. Announce the number. Put it on invoices, order emails, packaging and your website, and say which number handles support if you also use one for sales.

    If you’re moving an existing support number from a WhatsApp platform to a helpdesk, export or archive the chat history first: most migrations move the number, not the old conversations.

    How to run lightweight tickets in a shared inbox

    Most small teams can get 80% of a ticketing system from a shared WhatsApp inbox and a written routine. Here’s a setup that works in any inbox with tags and notes, with the steps for ChatMitra.

    1. Define status tags. Create a small, fixed set and agree that every open issue carries exactly one:

    • t-new: arrived, nobody has taken it.
    • t-open: someone owns it and is working on it.
    • t-waiting-customer: we asked the customer something.
    • t-waiting-us: we’re waiting on stock, a courier, a technician or finance.
    • t-resolved: done; remove the tag after your reopen period.

    2. Add an owner tag. One tag per agent, such as owner-priya. An agent claims a chat by adding their tag before replying. Anyone who sees another owner’s tag leaves the chat alone.

    3. Add a category tag. Keep it to five or six: refund, delivery, defect, billing, how-to, other. These become your monthly report.

    4. Write the reference in the note. Use a simple ID convention such as date plus number, #1015-03, and keep a one-line log in the contact’s note: “#1015-03 defect, replacement promised by Thu 17 Oct; courier AWB pending.” When the customer writes again in a month, the history is there.

    5. Pin what’s urgent. Pin chats with a promise due today. Unpin when it’s kept.

    6. Run two short sweeps a day. Filter by t-new and assign everything. Then filter by t-waiting-us and check every promise date. Ten minutes at opening and ten before closing catches most dropped issues.

    7. Automate the first tag. If your inbox supports rules, tag messages that contain clear keywords, such as “refund” or “damaged”, as t-new plus the category, so they’re easy to find even before anyone reads them.

    In ChatMitra:

    • Filters: the chat list filters by All, Unread or Replied, and by included or excluded tags, so “show me every t-waiting-us chat that isn’t owner-priya” is two clicks.
    • Pins and notes: chats can be pinned and marked unread, and each contact has tags and a note.
    • Auto-tagging: on Pro, an Auto Reply rule can add a tag when a message matches a keyword, a phrase at the start of the message or a pattern.
    • Read status is shared: in ChatMitra, once one agent opens a chat it’s read for everyone, so agents should rely on owner tags, not the unread dot.
    Two bowls seen from above, one with chat bubbles scattered at random and one with the same bubbles in neat rows under coloured tags, with the line Same messages, sorted by tags
    A fixed set of status, owner and category tags gives a shared inbox most of what a ticketing tool does.

    Where this stops working. Tag routines depend on discipline, and they don’t give you due-time alerts, automatic assignment, reports on response times or one record across email and phone. When you need those, or when more than about five people answer the same number, move to a helpdesk or connect one.

    Connecting your WhatsApp platform to a helpdesk

    If you already use a helpdesk for email, or want to keep marketing and sales on your WhatsApp platform while support works in the helpdesk, you can connect the two. Before you build it, answer five questions:

    1. Where do customer replies land? If an agent replies from the helpdesk but the customer’s answer arrives in the WhatsApp platform, your team works in two places. The cleanest setups route support conversations to one tool only.
    2. Who owns the 24-hour window? The tool that sends the reply must know whether the window is open and fall back to a template when it isn’t.
    3. Which templates exist? Ticket acknowledgements, updates and closure messages must be approved in your WhatsApp account before the helpdesk can use them.
    4. How are tickets matched? Decide when a new message joins an open ticket and when it creates a new one. A common rule: join the open ticket if there is one, otherwise create a new ticket.
    5. Which number belongs to which tool? A separate support number for the helpdesk, printed on invoices and order messages, avoids most routing problems.

    With ChatMitra, the developer API (on paid plans) sends messages and webhooks report events such as incoming messages to your own systems, so a workflow tool can create a helpdesk ticket when a support keyword arrives. Replies to messages sent through ChatMitra still arrive in ChatMitra’s inbox, not on the helpdesk ticket, so give template updates a link button to the ticket or the helpdesk’s customer portal.

    Let automation do the triage, not the resolving

    Automation earns its place in ticketing before a person sees the issue. Use it to collect what the agent will need, so the first human reply can solve the problem instead of asking questions:

    • Acknowledge instantly, with an honest time. “Thanks, we’ve got your message. Our team replies between 9 am and 7 pm, usually within two hours.” It sets expectations before the customer starts chasing.
    • Ask for the identifier up front. A button menu (“Order issue”, “Payment”, “Something else”) followed by “Please send your order number” saves a round trip on most tickets.
    • Ask for evidence when it’s always needed. Damaged-item tickets need a photo; billing tickets need the invoice number. Ask once, in the first automated message.
    • Tag by the button the customer tapped. That gives you the category without an agent reading the message.
    • Hand over, then step back. Once a person replies, pause the bot for that customer so it doesn’t answer on top of the agent.

    Keep refunds, complaints and anything involving money or safety with people. A bot can open a ticket; it shouldn’t close one on its own.

    WhatsApp templates for ticket updates

    These templates are original examples for common ticket stages. Meta classes a template as utility when it is non-promotional and specific to the customer’s own order, account, service or transaction; its own examples include a case moving to the next step. Adding an offer or a cross-sell makes it marketing, which costs more (₹0.8631 per message in India) and needs marketing opt-in.

    StageExample templateLikely category
    Acknowledgement after hoursHi {{1}}, we've received your message about order {{2}} and logged it as {{3}}. Our team will reply by {{4}}.Utility
    Waiting on customerHi {{1}}, to continue with request {{2}} we need a photo of the product label. Reply here with the photo when you can.Utility
    Update after the window closesHi {{1}}, an update on request {{2}}: your replacement was dispatched today. Tracking number: {{3}}.Utility
    ResolvedHi {{1}}, we've marked request {{2}} as resolved: {{3}}. If anything is still wrong, reply to this message within 7 days and we'll reopen it.Utility
    Feedback on this requestHi {{1}}, you contacted us about request {{2}} this week. How did we do? Tap a button below.Utility, because it's about a specific interaction
    Feedback plus discount"How did we do? Rate us and get 10% off your next order."Marketing, because of the offer

    Meta’s guidelines say a generic or promotional feedback request won’t be approved as utility; tie it to the specific order or conversation. For survey wording, see our guide on how to ask customers for feedback, and for template rules in general, our WhatsApp utility templates guide.

    Tricky cases and how to handle them

    • Two issues in one message. “My order is late and the last one was the wrong size.” Split them into two tickets with two references, and answer both in the same reply.
    • A new issue in an old thread. If the earlier ticket is closed, create a new one; don’t reopen a ticket from last month because the customer wrote in the same chat.
    • The customer writes on another number. People message from a family member’s phone or a second SIM. Ask for the order number or the reference and add a note linking both contacts.
    • Voice notes and photos. Treat them as part of the ticket. Note what the voice note said in the ticket or note, so the next agent doesn’t have to play it again.
    • Sensitive data. Never ask for full card numbers, PINs or passwords on WhatsApp, and tell customers you won’t. In India, the Digital Personal Data Protection Rules apply most of their obligations from 13 May 2027; decide now how long you keep chat and ticket data and how you delete it on request.
    • A customer who goes quiet. Send one reminder, by template if the window has closed, then resolve the ticket with a note on how to reopen. Chasing three times is how support messages start to feel like spam.
    • Escalations to other teams. When finance or the warehouse must act, the ticket stays with the support owner. The customer should never be told “that’s another department”.

    Ticket setups by business type

    BusinessCommon categoriesTypical first-response targetWhat usually crosses the 24-hour window
    D2C or ecommerce brandWhere is my order, damaged item, return or exchange, refund, COD payment1–2 business hoursReplacements and refunds that wait on the courier or payment gateway
    Appliance or electronics service centreInstallation, repair visit, warranty claim, spare partsSame business dayTechnician visits and part orders, so plan visit-date templates
    Clinic or diagnostic labAppointment changes, report requests, billingWithin opening hoursReports that take days; keep medical advice out of chat and route to a clinician
    Education or coachingFees, batch timings, certificates, technical accessSame business dayCertificates and fee reconciliations
    SaaS or subscriptionLogin, billing, bug reports, feature questions1–4 business hours by planBugs waiting on engineering; give a dated update, not silence

    The targets above are starting points, not industry standards. Set yours from your rota, publish it in your away message, and measure against it.

    How to measure a WhatsApp ticketing system

    Track a few numbers weekly, by category:

    • First response time (median and 90th percentile, in business hours). The 90th percentile shows the customers you’re failing.
    • Resolution time from new to resolved.
    • Share of tickets resolved inside the first 24-hour window. This is the most WhatsApp-specific measure: it tracks both speed and template cost.
    • Messages per ticket. A rising number usually means unclear first answers or missing information, and it raises Meta charges.
    • Reopen rate. Tickets reopened within your reopen period. High rates mean “resolved” was declared too early.
    • Backlog by status. How many tickets are waiting on customers versus waiting on you. A growing “waiting on us” pile is an operations problem, not a support one.
    • Satisfaction from the feedback request, read alongside the comments.

    If your tool can’t report these, a weekly export and a spreadsheet will. Count tickets by category tag and you’ll find the two or three problems behind most of your volume, which is worth more than any tool.

    Common mistakes

    • Treating every message as a new ticket. “Thanks!” and “ok” shouldn’t open tickets. Set a rule for what creates one.
    • Closing tickets because the chat went quiet. Wait for your agreed period, and tell the customer how to reopen.
    • Setting an SLA you can’t keep at weekends. Promise what your rota can deliver, and say it in the away message.
    • Letting the bot answer while an agent handles the ticket. Pause automation for that customer when a person takes over, or the bot may reply on top of your agent.
    • Asking the customer to repeat themselves. Write the context in the ticket or note before any handover.
    • Putting offers in update templates. It turns a utility message into marketing and risks rejection.
    • Buying a helpdesk before fixing the routine. A tool won’t fix unclear ownership; it just records it.

    Where ChatMitra fits

    ChatMitra is a WhatsApp Business Platform provider with a shared team inbox, templates, broadcasts and automation. For ticketing, here’s what it does and doesn’t do today:

    NeedChatMitra today
    Shared inbox for the teamYes. Unlimited agent logins with per-number, per-section permissions
    Status and ownerBy tags, with include and exclude tag filters, plus Unread and Replied views
    Notes and historyA note and tags on each contact, and the full chat history
    Auto-taggingAuto Reply rules can add a tag on a keyword match (Pro)
    Ticket IDs, assignment, SLA timers, ticket reportsNo
    Agent shown on each messageNo; agents can sign their replies
    Bot pause during a human conversationYes, per customer, for 30 minutes up to until you turn it back on
    Helpdesk connectionThrough the developer API and webhooks (paid plans), with a workflow tool
    PriceMeta's charges plus ₹0.20 per conversation (one customer, 24 hours) on Starter and Pro; Pro is ₹999 a month with 1,000 credits; no per-agent fee

    That makes ChatMitra a good fit for the shared-inbox approach, and for teams that want marketing, sales and simple support on one number without paying per agent. If you need SLA policies, assignment rules and ticket reports, use a helpdesk for support and connect it. See pricing and Auto Reply.

    Summary

    A WhatsApp ticketing system gives each customer problem an owner, a status and a due time, so nothing gets lost in a long chat thread. You need one when several people share a number, issues span days, or you have to report service levels. Set response targets well inside Meta’s 24-hour window, prepare utility templates for updates after it closes, and remember that every message has a small cost in India since October 2026. Start with a tagged shared inbox and a twice-daily sweep, and move to a helpdesk, or connect one, when you need SLA timers, assignment and reports. Whatever the tool, the routine matters more than the software.

    For the wider picture of support on WhatsApp, read our guide to WhatsApp for customer service.

    Sources: Meta, Pricing on the WhatsApp Business Platform and INR rate card (effective 1 October 2026) and template categorization guidelines (updated 15 September 2026); Freshworks, Freshdesk pricing, connecting WhatsApp to Freshdesk and WhatsApp pricing model; Zendesk, pricing, adding WhatsApp channels and WhatsApp templates in the Agent Workspace; Zoho, Zoho Desk pricing and plan comparison; HubSpot, Service Hub pricing, connecting WhatsApp to the help desk and WhatsApp integration limits; Gorgias, pricing, WhatsApp setup and billing and SLA policies, all checked 15 October 2026; MeitY, Digital Personal Data Protection Rules, 2025. ChatMitra product behaviour as verified in ChatMitra's code (October 2026).

    Clear answers

    Frequently Asked Questions

    It's a way of tracking each customer issue that arrives on WhatsApp as a separate record, a ticket, with an ID, an owner, a status such as open, waiting on customer or resolved, a priority and a due time. The customer keeps chatting normally on WhatsApp; the ticket exists on the business side so the team knows who is handling what and nothing is forgotten.

    No. The WhatsApp Business app has labels, quick replies and greeting and away messages, but no ticket IDs, statuses, assignment or response-time tracking, and it runs on a limited number of linked devices. Ticketing needs the WhatsApp Business Platform (API) and a tool built on it, either a shared inbox or a helpdesk with a WhatsApp channel.

    You can send free-form replies only within 24 hours of the customer's last message. If a ticket stays open longer, for example while you wait for a replacement part, any update after the window closes must be an approved template. A non-promotional update about the customer's own request fits Meta's utility category; in India it costs ₹0.115 per message since 1 October 2026.

    Three costs add up: your tool's fee, usually charged per agent per month for helpdesks; your WhatsApp provider's fee if it's separate; and Meta's message charges. In India, Meta gives each number 1,000 free service messages a month, then charges ₹0.115 per service message and ₹0.115 per utility template. A small team with a shared inbox can run lightweight tickets for little more than the inbox fee; a full helpdesk adds a per-agent licence.

    Use a team inbox with a clear tag routine if WhatsApp is your main channel, one team handles it and issues are usually solved in one or two conversations. Use a helpdesk if you also handle email and phone tickets, need SLA policies, auto-assignment and reports, or other departments must work on the same issue.

    Only if you send it. A helpdesk can include the ticket ID in its first reply or in a utility template such as "We've logged your request as #4821". Sharing it helps when the customer contacts you again or on another channel, and it gives your team a reference to search.

    Yes. Inside the 24-hour window you can ask in a normal message. After it, use a template. Meta classes a feedback request as utility only when it's about a specific order or interaction, such as "You chatted with us about order 4821. How did we do?"; a generic or promotional survey is marketing.

    Not a full one. ChatMitra's shared inbox lets a team filter chats by Unread or Replied, tag and pin chats, filter by tags and keep a note on each contact, which is enough for a lightweight ticket routine. It has no ticket IDs, assignment, SLA timers or ticket reports, so teams that need those connect a helpdesk.

    Nikunj Gohil

    ChatMitra

    Nikunj Gohil writes for the ChatMitra blog about the WhatsApp Business API.

    Ready to try WhatsApp Business API?

    Start free on the Starter plan — free subscription. Pro is ₹999/month with a 15-day trial when you need automation.