Define what counts as a complaint
A complaint is an expression of dissatisfaction that asks for a response, a correction, or a change. It may arrive as an angry email, a short review, or a quiet note in a call. The intake log should capture the ones that create a commitment. A casual suggestion is not the same as a complaint.
Write the definition with two examples and one counterexample. A billing error and a missed delivery are complaints. A request for a new feature may be feedback rather than a complaint. The team needs a shared boundary so the log does not fill with every message.
Decide which channels feed the log. Include email, chat, phone notes, and the client portal. A complaint that arrives in a personal message still needs a record. The channel should be a field, not a reason to leave the issue out.
Capture the first report in plain words
Record what the client said and what they want, using plain language. Avoid internal labels and sarcasm. A short summary is enough if it preserves the facts. Add the client's own words in a quoted field when the tone matters.
Include the date, the channel, the product or service, and the person who received the message. These details help the owner understand the context without reading the whole thread. They also make repeat complaints easier to spot. Add the client reference or account number so the complaint can be matched to the work.
Separate the facts from the assistant's interpretation. A note that says the client is furious is less useful than one that says the client used capital letters and asked for a refund. The facts support a response, while the interpretation may be wrong. Keep both, but label them.
Assign severity and an owner
Use a small severity scale that matches the risk. A safety issue, a legal threat, or a public review needs a faster path than a minor billing question. Write the scale beside the log. The assistant should be able to choose a level without a long debate.
Name one owner for the response, even when several people must contribute. A complaint with three owners often has none. The owner may be a support lead, an account manager, or a specialist. The log should show the name and the time the owner accepted.
Set a response time for each severity level. The time is a promise to the client, not an internal target. Record the promised date and the channel. If the owner cannot meet it, the log should show the revised date and the reason.
Record the response promise
Write the exact promise the client received. A reply that says someone will look into it is not a promise, while a reply that says you will hear back by Thursday is. Record the date and the person who made the promise. The log should match the client's inbox.
Send a short acknowledgment that confirms the next step without admitting fault or guessing an outcome. The assistant can use a template that names the owner and the response time. Do not let the template promise a refund or a fix that has not been approved. The acknowledgment protects the relationship while the decision is made.
Update the log when the promise changes. A new date should be sent to the client, not only recorded internally. A silent delay is worse than a revised date. The log should show both the original promise and the current one.
Review repeat complaints
Group complaints by cause rather than by client. A repeated billing error, a late delivery, or a confusing policy points to a process problem. The largest group is the best place to start. A single dramatic complaint can distract from a pattern that affects many clients.
Read the complaints that were closed quickly and the ones that took longest. A fast close may be a good response or a brushed-off issue. Check the client's later messages for a sign that the problem returned. Speed and resolution are different measures.
Change one process and watch the complaint group for a month. If the billing errors fall after a new invoice check, the fix probably worked. If they do not, the cause may be elsewhere. Record the change and the result in the review note.
Set the assistant boundary
The assistant may log the complaint, acknowledge receipt, gather the facts, and route it to the owner. The owner should decide the remedy, the refund, or the public response. Write that boundary in the role brief. A complaint is not the place for an improvised promise.
Define what the assistant does when the complaint involves a legal threat, a safety issue, or a request for personal data. The default should be to stop, preserve the message, and send it to the named specialist. Do not discuss the substance in the general channel. The fast path should be written before it is needed.
Review the log and the boundary each quarter. A new service or a new client can create a complaint type the old process does not cover. Update the severity scale and the owner list. The log should be a living control, not a form that everyone fills in and no one reads.
Sources
Open the original publisher and confirm the current version, definition, and scope before using a source for a business decision.
Turn the reading into a role brief
Bring the recurring tasks, tools, schedule, access limits, and owner-only decisions. Start with one work sample and one clear review path.
Plan a Philippines-based role