A complaint is a conversation, not a writing contest.

A customer says the repair did not hold. Another says the delivery arrived with the wrong item. Your first instinct may be to explain what happened, defend the team, or promise to fix everything immediately. Take a breath first. A polished reply cannot rescue a response built on half the story.

For a busy owner, the useful first move is a short complaint worksheet: what the customer said, what the business can confirm, what remains unclear, who can decide the next step, and when the customer should hear back. An assistant can prepare that worksheet from the records you choose. It should not decide who is at fault or send a message in your name.

The customer still needs a real person who can listen and make a fair decision. The assistant helps that person arrive prepared.

Collect the customer's words before your explanation.

Write down the issue as the customer describes it. What happened from their point of view? What result were they expecting? Is there a safety concern, an urgent service interruption, or a deadline? If you do not know, ask. Do not let a tidy internal note flatten the part that matters most to them.

Then gather only the relevant business records: the original order or scope, appointment notes, photos the customer has chosen to share, a delivery record, and any messages about a change. Give the assistant a bounded set of material and ask it to separate three columns: customer account, confirmed record, and open question. A disagreement between the columns is a reason to investigate, not a reason to choose the version that favors the business.

Use only approved tools and relevant records; leave unnecessary personal details out. For a legal, safety, discrimination, or other sensitive issue, stop the routine drafting flow and involve the appropriate person or professional.

Make the next decision visible.

The worksheet needs an owner, not just a status. Put a name beside the next action: the field lead checks the repair notes; the shop manager checks the order; the owner decides whether a refund, return visit, or different remedy is appropriate. Note what must be verified before that decision. No assistant should invent a policy, warranty term, discount, or appointment slot to fill the blank.

Set a realistic time for the next human update. That update can be an acknowledgment even when the resolution is not yet known: the concern was received, a named person is checking it, and the business will return with an answer at the time it actually can meet. Have that person verify the timing and send the message. A promise you cannot keep makes the problem harder.

The Australian Government's business guidance recommends listening, keeping a record of promises, gathering relevant documents, and following up after a complaint is resolved. Those are useful service habits, not a substitute for checking the obligations that apply to your own business and location.

Illustrative example: a return visit after a plumbing repair.

This is illustrative, not a PeakAgent customer story. Imagine a plumbing company receiving a message that water has appeared under a sink two days after a repair. The owner first makes sure a person handles the possible active leak promptly. The assistant is not asked to diagnose it or tell the customer the situation is safe.

From the approved work order and the customer's message, the assistant prepares a short sheet: the repair performed, the customer's description, the date of the visit, what the notes actually say, and missing details such as whether the water is still flowing. It leaves cause and responsibility open. The service lead checks the record and speaks with the customer before deciding the next step.

Only then might the assistant draft a plain acknowledgment for the lead to edit: we hear the concern, we are checking the job details, and here is when we will contact you again. The lead confirms that the proposed time is real and sends the final message. The point is a faster grasp of the facts, not a machine-made diagnosis or promise.

Illustrative example: the wrong item at a neighborhood shop.

This second example is illustrative too. A neighborhood hardware shop receives a note saying a special-order fixture is the wrong finish. The order record has a product code, but the customer's photo and an earlier email suggest there may have been a change that was not captured in the final order.

The assistant lays out the dated trail without declaring either side wrong. It flags the mismatched code and email, lists the item the customer says they expected, and asks whether the supplier has confirmed availability of the alternative. The manager checks the original paperwork and the shop's actual return terms. The assistant may prepare two draft explanations for review, but it cannot choose a remedy, authorize a refund, or order a replacement.

The manager speaks with the customer, decides under the applicable terms, and records what was agreed. Later, the team can check whether its special-order confirmation step needs improvement.

Use a five-line worksheet you can inspect.

You do not need a new system to test this. Start with five lines: the customer's concern in their words; the confirmed facts and where they came from; the questions still open; the person who owns the decision; and the next update time, approved by that person. Add a sixth line for any promise actually made, with its owner and date. Keep the original message available so a summary cannot replace it.

Try a first pass on one past, appropriately handled complaint using permitted information. Compare it with the source. Did it miss the customer's point, turn a guess into a fact, or suggest an unauthorized remedy? Correct the instructions before trying another; keep the human process if the worksheet is not dependable.

For a public review, take extra care: your reply is visible to more people than the customer, and private details do not belong in it. The U.S. Small Business Administration advises courteous, specific responses to negative reviews rather than personal or defensive ones. A human should decide what is appropriate to say publicly and what belongs in a direct conversation.

The takeaway: understand first, then answer.

Try the worksheet on one real issue this week. Let an assistant sort the approved information into facts and open questions, then have the owner or manager listen, verify, decide, and approve every outward message. That is a small, useful win: less scrambling for context and more attention for the customer in front of you.

The service-practice guidance behind this approach comes from the Australian Government's customer-complaint guide at https://business.gov.au/people/customers/handle-customer-complaints and the U.S. Small Business Administration's negative-review guidance at https://www.sba.gov/blog/2018/2018-10/essential-steps-handle-negative-reviews/. Check your own local rules and written terms for any remedy or formal obligation.

If you want help setting up a reviewable first pass for one recurring customer-care task, you can try a PeakAgent assistant free for up to 30 days. Bring the process you already use. You and your team remain the people who listen, decide, and speak for the business.