WhatsApp is where everything happens between a gym and its members: a question about class times, a photo of a payment receipt, and also a complaint about a cold shower or a locker that won't close. That works perfectly for a quick question. It breaks down the moment the message is a complaint that needs follow-up, because the conversation itself has no status, no owner, and no closing date.
A support ticket is not extra complexity layered on top of WhatsApp — it is the same idea with three things that were missing: who owns this complaint, what state it is in right now, and when it closed and with what resolution. Those three things alone are the difference between a complaint that gets solved and one that disappears.
Why a complaint dies in WhatsApp
The problem is not staff carelessness — it is the structure of the tool itself. Three patterns repeat in every gym that runs support through an ordinary chat:
- No named owner: three staff members see the same message in the group, and each assumes someone else will reply.
- "Replied to" and "resolved" are two different things, and an ordinary chat thread makes no distinction between them.
- No lasting record: a staff member switches phones or leaves the job, and the thread holding the complaint's entire history disappears with them.
The ticket lifecycle: from open to closed
A member opens a ticket from their own account instead of a message that vanishes into a busy group chat, and it moves through three clear states instead of one vague one called "seen".
| State | Means | Who moves next |
|---|---|---|
| Open | Arrived, and nobody has started working it yet | The staff member responsible for that category |
| In review | A staff member is working it, possibly waiting on the member for a detail | The same staff member, or the member if a reply is awaited from them |
| Closed | The resolution is documented and the member has been told explicitly | Nobody — until a new ticket is opened |
Categorizing and assigning: no ticket without an owner
Categorizing a ticket when it opens — complaint, suggestion, or technical issue — decides who sees it first. A billing complaint routes to whoever handles financial exceptions, and a broken-equipment report routes to whoever tracks the equipment log, instead of both landing on the same person and waiting their turn in the same queue.
The number worth tracking: response time, not ticket count
The number of tickets opened this month says nothing about service quality — a busy gym opens more tickets than a quiet one, with no relation to which one serves its members better. The number actually worth tracking is time to first response: how long a member waited before hearing anything, regardless of when the ticket was actually closed.
Closing the loop: how a complaint becomes a renewal
Fixing the problem silently is not enough — tell the member explicitly that their complaint was resolved and how. A member who knows their feedback landed and produced a real action is far more loyal than one the gym went quiet on, even if the underlying issue got fixed either way.
And review ticket categories once a month looking for a pattern: six tickets about the air conditioning in one month are not six separate problems for the duty manager to solve one at a time — they are a maintenance or replacement decision that deserves to reach you directly.