A customer messages your boutique about a torn dress, on Instagram, at nine at night. Someone replies "sorry, we will check", and the thread goes quiet: no name recorded, no promise kept, nothing anyone else on your team could pick up if she writes again. Three weeks later she messages your website chat asking why nobody ever got back to her, and the honest answer is that the complaint never lived anywhere except one person's memory.
The Complaint That Lives in One Head
Most small teams handle complaints the same way they handle everything else: by memory and goodwill. Someone reads the message, feels bad, promises to sort it, and moves on to the next chat. That works fine when exactly one person answers every message, every day, forever.
It stops working the moment a second person joins the WhatsApp, a shift changes, or the same customer writes back three weeks later on a different app. Nobody lied when they said "I didn't know about that". In a very real sense, they didn't, because the complaint never existed anywhere except inside one person's head.
Why It Falls Through
Enquiries rarely arrive in one place. The same complaint can start on WhatsApp, continue as an Instagram direct message, and finish as a comment under a post, each one answered by whoever happened to be free at the time.
Staff turnover makes it worse. A weekend hire who replies to a complaint on a Friday might not be on shift when the customer follows up on Monday. If the note only lived in her head, the business loses the whole thread the moment she clocks off.
- Answered once, then forgotten as soon as the chat moves on
- Split across WhatsApp, Instagram and the website with no shared record
- Picked up by whoever is free, not whoever can actually fix it
- Never followed up once the first apology is sent
If a complaint is really just a question nobody finished answering, the arithmetic looks a lot like a missed WhatsApp enquiry.
A complaint you can't find again is a complaint you haven't actually closed, no matter how sorry you were in the moment.
What One Lost Complaint Actually Costs
Take Hanan, who runs a salon with four staff in Qurum (a composite example). A customer had a mild allergic reaction to a hair dye and messaged on Instagram. Two different staff replied over three days, neither aware the other had answered, and nobody logged a follow up call. The customer left a public review before anyone rang her back.
What actually broke that pattern for Hanan is simpler than it sounds, and it comes a little further down. First, the honest cost of what happened before she fixed it.
| What it cost | Hanan's salon (composite example) |
|---|---|
| Average spend per visit | OMR 18 |
| Visits she would likely have kept this year | 5 |
| Lifetime value that walked away | OMR 90 |
| Refund issued after the public review | OMR 15 |
| Staff hours spent firefighting the review | 2 hours |
| Total visible cost | OMR 105, plus 2 hours, before counting the review itself |
Four Things Every Complaint Needs
Once you accept a complaint is a job and not just a chat, the fix is almost boring. It needs four things, and none of them require new software.
- Captured: written down somewhere the whole team can see, not just remembered by whoever replied first.
- Owned: one name attached to it, even if that name is just "whoever answers WhatsApp today".
- Closed: someone actively marks it done, instead of letting the thread go quiet.
- Told: the customer hears the outcome, even when the outcome is "we can't refund it, but here's what we can do".
Now every complaint has a name attached to it, and it doesn't disappear just because the shift changed.
You Do Not Need Enterprise Software
None of this needs a helpdesk built for a call centre floor. For a two or three person team, a shared note, a WhatsApp group with one line per complaint, or a plain spreadsheet with four columns (who, what, owner, status) covers it completely. The habit matters more than the tool.
Where it gets harder is once complaints arrive across three different apps and nobody remembers to check the spreadsheet at eleven at night. That is the point where turning the chat itself into a ticket, the moment it is raised, closes a gap a shared note cannot. Chatbot.OM's Automated Support Tickets do exactly that, on WhatsApp and the website, so a complaint is logged and tracked to closure without anyone typing it in twice.
What This Means for You
Pick one place, today, where every complaint gets written down: a notebook by the till, a shared note on your phone, anything that is not one person's memory. Decide who owns a complaint the moment it lands, and agree that "closed" means the customer actually heard back, not just that an apology was sent.
If complaints keep arriving on channels nobody is watching at night, that is your cue to look at something that catches them automatically, rather than hoping everyone remembers to check.
Do I need real ticketing software for a two person team?
No. A shared note or a simple spreadsheet with four columns does the job until you are handling more than a handful of complaints a week.
Who should own a complaint if there is no manager on shift?
Whoever answers it first, until they hand it to someone with the authority to close it. The point is that one name is always attached, never nobody.
The Bottom Line
A complaint that only lives in someone's head is a complaint you will end up solving twice: once for the customer, and once for your own reputation. Writing it down costs two minutes. Not writing it down can cost the customer, and sometimes the next ten who read her review.
Practical information, not legal advice. Rules and dates were checked on 17 September 2026; verify current official positions before acting.
