Separate the complaint, business records and confirmed facts. Review privacy and authority before publishing evidence or promising a remedy.
A complaint appears in a review section, and a support agent considers posting an order screenshot. It may add context while also disclosing an address, telephone number or details the customer never made public. More detail is not necessarily more helpful when the records still conflict.
Establish evidence status and disclosure scope first. This review method uses Google Business Profile’s official reply advice to illustrate platform communication boundaries.
Separate allegations, records and confirmed facts
A customer account, a system status and a verified event are different evidence states. Place the complaint, order record, support messages and owner confirmation on a timeline, naming each source. A system status establishes what the system recorded; the actual service history may still need evidence.
Turn conflicts into precise questions: which timestamp came from the warehouse, which from the carrier, and whether another delivery location was described. Remove unsupported assumptions about motives. State the confirmed scope rather than completing either party’s story.
Decide disclosure separately from record access
Possessing a record does not justify publishing it in full. Inspect names, telephone numbers, addresses, order identifiers, private messages and other identifying details in both text and attachments. Keep internal evidence controlled rather than assuming one redaction makes the whole record suitable for publication.
Google advises against disclosing reviewers’ private information or personal attacks and suggests private contact for complex matters. Hong Kong’s PCPD also warns that publicly available personal data is not unrestricted for further use. A customer’s partial disclosure is not blanket permission for the business to add more.
Source: Official guidance 1 · Official guidance 2
State what is known and what the team can do
Structure a short response around known facts, the remaining question and the next contact channel. Acknowledge verified differences. Do not promise refunds, compensation or responsibility decisions that an authorised owner has not confirmed.
In a hypothetical delivery dispute, a business could say that it is checking the delivery record and invite the customer to a confirmed private channel for necessary details. That is not a template for every complaint: the issue, contact route and completed actions must match the matter.
Source: Official guidance
Retain a brief final review record
Check sources, privacy, authority and the final version. Each definite statement and remedy should lead to evidence or an approver. The publisher should confirm that the released wording matches the approved response.
Continue tracking the actual follow-up: material received, facts established and the owner of the next update. Keep “replied” separate from “resolved”. A reporting status should never turn an unresolved factual conflict into certainty.
| Review | Action |
|---|---|
| Facts | Trace every definite statement to evidence |
| Privacy | Remove unnecessary personal details from copy and images |
| Promises | Confirm authority for any proposed remedy |
| Version | Match the release to the approval |
Bring the complaint link, a redacted timeline and reply draft to PowerFront to agree a general facts-and-response review scope.