Read the actual review and context
Give the approver the review text, relevant listing and proposed response together. Avoid relying only on an automated summary, which may omit the detail the customer wants addressed. Distinguish what the reviewer said from information the business has independently confirmed. A fictional comment about a delayed callback should not become a statement that the entire service failed. If the context is unclear, route the draft to the appropriate owner rather than filling gaps with an assumed account of what happened.
Check every factual statement
Verify any claim about contact attempts, staff actions or completed follow-up against the business record. Do not say the team has investigated or resolved the issue if that work has not occurred. Keep uncertain details out of the public reply. The response can acknowledge the topic raised without inventing a finding. If a draft refers to a private conversation, ask whether that reference is appropriate and necessary. Do not publish personal or account details merely to demonstrate that the business has checked its records.
Review promises and next steps
Any commitment needs an owner and an achievable process behind it. A draft should not offer compensation, a deadline or a specific remedy unless the authorised person has approved that action. A useful next step might direct the reviewer to the established contact route for further discussion. Confirm that route is correct and staffed as expected. Avoid claiming a reply will remove the review, change its rating or improve a ranking. The approval concerns the message and follow-up the business controls.
Approve the complete final version
Show the final text and the exact destination account or listing. Keep the approver identity and decision linked to that version. Do not interpret silence, opening a preview or an expired request as approval. If someone changes the wording or adds a commitment after approval, return it for review. A fictional manager might approve a neutral invitation to contact the office but decline a later-added promise of a refund. Those are materially different messages even if most of the paragraph is unchanged.
Verify publication separately
Keep drafted, approved and published as distinct states. After the authorised publication step, check that the intended response appears under the correct review and that its text matches the approved version. If the result is uncertain, inspect the destination before repeating the action. A tool reporting success is not the same as seeing the correct public response. Keep a failed or pending publication visible for follow-up. Do not mark the underlying complaint resolved merely because the business has posted a reply.
Review corrections and approval delays
Track drafts returned for factual changes, unclear ownership or unsuitable wording. Read examples before expanding automated drafting scope. Repeated corrections may point to an incomplete tone brief or missing business context. Keep a backup approver for absence and a route for cases needing more careful review. Test the process with fictional positive, mixed and negative comments. The objective is accurate, authorised public communication, not simply the fastest possible approval or the largest number of replies published.