Check the fact and the action separately.
When hours, contact details or destination links disagree, start with the public business-details check. Confirm the underlying fact, compare equivalent fields and identify who can correct each surface. An edit submitted for review is not yet a verified public change.
When the words imply different next steps, use the website promise check. Follow one action from the page through the form and confirmation. The useful result is agreement about what actually happened: an estimate request should not quietly become a confirmed visit.
Choose between asking for a review and answering one.
Use the review-invitation guide before preparing a voluntary Google review request. It covers a neutral process, the right destination and checks that avoid pressure or duplicate invitations.
If a review is already public, use the public-response guide. Decide what can be said publicly, what needs investigation and who owns any private follow-up. A posted reply does not establish that the customer's concern is resolved.
Finish the practical work behind the wording.
For a public fact, record what is now visible and what is still pending. For a customer concern, keep the private action owned without publishing job details in the response. If the question is what customers found confusing, use private customer feedback rather than turning every comment into a public-review request.
These checks are useful without buying anything. If they expose a recurring gap between a request and the team handling it, bring one example to a Local Growth Call. The conversation can explore the path without assuming that another tool is the answer.
Put the guidance to work.
Use the instructions before filling in a worksheet. These downloads are blank and do not submit information to JetSynapse.