A client calls about a service problem. The person answering listens carefully, then leaves a message saying the client is unhappy. By the time the delivery lead responds, the client has explained the story twice and nobody knows what they actually asked you to do.
A customer complaint intake checklist should capture the specific failure, its effect, the outcome requested and the next accountable action. It is an admission record for investigation, not an instant verdict on fault or entitlement. Use this approach for ordinary service complaints; route urgent safety, security or legal concerns to the appropriate qualified owner.
Photo by Petr Macháček on Unsplash.
What needs to be understood during the first conversation?
Ask the client to describe the expected service and what happened instead. Record dates, the affected deliverable and any existing reference. Separate their description from your interpretation. “The report did not include the agreed period” is more useful than “the client seems unreasonable”.
Ask what would help them now. They may want a corrected file, an explanation or a discussion about a commitment. Recording that request does not mean you have approved it. Tell the client who will review it and when they can expect the next update, based on actual authority and availability.
A reusable complaint intake card
Case reference, received date and communication channel.
Client, appropriate contact and affected service or deliverable.
Expected outcome, reported failure and immediate operational effect.
Requested resolution, recorded in the client's terms where useful.
Evidence already available and information still needed.
Immediate action allowed, plus decisions requiring approval.
Named case owner, next action and next update time.
Any communication or access needs relevant to handling the case.
Store supporting material in the approved case location. Avoid copying a sensitive client file into several general trackers. If the complaint arrived through a normal request channel, create a clear reference in your shared intake queue rather than relying on a private reminder.
An illustrative case: the wrong reporting period
A client says its monthly report covers the wrong dates and asks for a corrected copy before a board meeting. The intake owner records the affected version, the agreed period, the meeting time and the source of the original instruction. They acknowledge the request without promising an unassessed turnaround.
The service owner checks the evidence and capacity. If a remedy would change another commitment or exceed the recipient's authority, it follows the agreed escalation route. One case owner remains responsible for keeping the client informed while specialists investigate.
Check that intake leads somewhere
At the next update point, the case should have a decision, an owned investigation or a clearly explained dependency. Do not mark it resolved merely because it was forwarded. Review a few cases to find whether intake missed the expected outcome, the requested remedy or the person able to decide.
If complaints keep returning to the founder because nobody can identify the next step, Hili Consulting can help design the intake and ownership around your service workflow.
