Every complaint owned, tracked, and actually answered.
Read this before anything else: AcornReply is not regulated-complaints software. There is no statutory case management, no audit workflow, and no complaints register built for a compliance regime. If a regulator inspects how you handle complaints, you need a compliance product and this is not it. What AcornReply does is make sure customer complaints arriving by email get an owner, a status and a real answer.
Complaints are the emails you cannot afford to lose.
A complaint left unanswered for four days becomes a refund, a public review, or a customer who never writes again. A personal inbox or a plain shared mailbox tells you none of what you need: whether the thread is still open, who owns it, or whether the customer ever got a real answer.
Nobody can say whether it was resolved.
The reply went out from one person's own inbox, so a week later there is no way to tell whether the customer was satisfied or simply gave up.
Two people reply, or nobody does.
With no owner, an angry email gets two contradictory answers or none at all. Both leave the complaint worse than it arrived.
Tone slips exactly when it matters most.
Complaints get answered late, under pressure, by whoever is free. That is precisely when a rushed sentence turns a fixable problem into a public one.
The history disappears.
When the same customer writes again three months later, the earlier complaint and whatever you promised are not in front of whoever picks the thread up.
What AcornReply does with a complaint.
It gives a complaint the three things a plain mailbox cannot: an owner, a status, and a written history that outlives the person who handled it.
Every complaint is one thread with a status and an owner.
Open, snoozed or resolved, assigned to a named person. You can see at a glance what is still unanswered and who is holding it.
Nothing is closed silently.
A thread becomes resolved only when a person marks it resolved, and a new reply from the customer reopens it automatically. Closing a complaint by forgetting about it is not available.
The reply is drafted, so the tone holds under pressure.
AcornReply drafts the answer from your own policies and past replies in a consistent voice. You edit and send, which is what keeps a rushed sentence out of the one thread where it would cost you most.
Resolved threads keep their history.
When the customer comes back, the whole complaint is on the thread: what happened, what was promised, and who promised it.
The complaint you would rather not repeat.
A customer writes on a Friday about a charge they did not expect. It lands assigned, drafted from your refund policy, and open. Nobody is around until Monday, so it is still open on Monday morning rather than buried under sixty newer emails. It gets answered, marked resolved, and when the same customer writes in April the whole story is right there.
Your first reply, in five minutes.
Sign up, forward your support address, paste five past replies. The next inbound message arrives with a draft already written.
Frequently asked questions
What is complaint management software?
Software that captures a customer complaint, gives it an owner and a status, tracks it until a person resolves it, and keeps the record afterwards. In regulated industries the same phrase means something stricter: a statutory complaints register with audit trails and mandated response deadlines. Those are two different categories of product.
Does AcornReply meet regulatory complaint-handling requirements?
No. There is no statutory case management, no audit workflow, no regulator-shaped complaints register and no mandated response-deadline tracking. AcornReply is a customer support inbox with owners, statuses and history. If a regulator audits your complaint handling, buy a compliance product instead.
How do you track whether a complaint was resolved?
Each thread carries a status and an assignee. Resolving is a deliberate action by a person, and an inbound reply from the customer reopens the thread automatically, so a complaint cannot quietly close itself while the customer is still waiting.
Related
- EscalationWhat it means to move a complaint past the person who took it.
- CSATThe measure most teams use to tell a resolved complaint from a quiet one.
- Stop missing support emailsThe structural fix for anything that slips through a personal inbox.
- Support ticketThe unit of work a complaint becomes once it has an owner and a status.