Inspect the current review and reply
Open the actual review and business response before preparing a correction. Check that staff are discussing the same listing and conversation. In a fictional service business, a reply mentions a Tuesday appointment when the business record refers to Wednesday. Preserve the relevant original wording for the internal review instead of editing from memory. A screenshot or copied draft may show an earlier state. Record what is currently visible and the specific detail the business believes needs attention.
Establish the correction with its owner
Ask the authorised business person to verify the relevant fact and decide what should change. Do not treat a suggested correction from an automated tool as established truth. Keep the scope narrow: correcting a day does not require adding private booking details or rewriting the customer’s account. If the facts remain uncertain, hold the proposed change for review. This administrative process does not decide legal responsibility or promise that a revised reply will change the reviewer’s opinion.
Prepare the complete revised wording
Show the approver the current reply and proposed replacement together. Identify any new statement or commitment so it is not hidden inside a general rewrite. Use only the information the business has approved for a public response. In the fictional appointment example, avoid including the customer’s contact details to demonstrate that the internal record was checked. Make the wording understandable on its own. A correction should address the verified issue without inventing an outcome or promising action that staff have not accepted.
Approve the version that will be used
Record who approved the revised reply and which wording they reviewed. If the text changes materially afterwards, return it for approval. Approval of the original response should not automatically authorise every later edit. Confirm the intended business listing and review reference before any public action. Ask the operator to use the options actually available in the relevant service rather than assuming a particular edit or removal feature exists. If the required action is unavailable, report that limit to the owner.
Verify the public result
After the authorised action, inspect the response in its destination and compare it with the approved wording. Keep prepared, approved, attempted and visibly updated states separate. If the result is uncertain, investigate before repeating the action. Do not claim completion solely because an internal button reported success. Record any difference or delay without inventing an explanation. The owner should know whether the correction is visible, still pending or needs another supported action.
Keep a concise correction history
Record the review reference, reason for correction, approved wording and verification outcome in the business’s approved workspace. Exclude unnecessary customer information. Use the incident to improve drafting instructions if it reveals a recurring problem, then test the change with fictional examples. Avoid converting one correction into a blanket template that misstates other situations. The useful outcome is an accurate current response with a traceable decision, not an assumed improvement in ratings, visibility or the customer relationship.