Replying to Google reviews
Replying to reviews changes what the next guest reads. But publishing an automatically generated reply straight out makes the problem you hoped to solve bigger. nalyzed prepares the draft; the decision to publish stays with a person.
A draft is tied to its evidence
A reply draft carries the review and the topic finding it answers. Whoever approves it does not approve without seeing the sentence being answered.
There is no auto-publish
Replies to critical allegations and negative reviews are never published without human approval. There is no setting that removes the step; approval is built into the flow.
Measuring whether the reply worked
After a reply or an operational action, the topic's positive rate in the following period is compared with the previous one. Writing replies becomes a measured action rather than a habit.
Care with personal data
A reply should not carry a booking reference, a room number, a phone number or an email address. Drafts do not include such fields, and personal data in reviews is redacted before analysis.
Method
Every number on this page comes from the analysis pipeline nalyzed runs over publicly visible Google Maps reviews: normalisation, language detection, personal-data redaction, business-type topic classification and aspect-level sentiment. Results are stored with their evidence quote, sample size and confidence score; a result whose evidence does not appear verbatim in the source review is not published. When collection does not finish, coverage is shown as `partial` and no screen claims that every review was analysed.