Customer service

AI-drafted Google review replies

Review reply automation notices each new review on your Google Business Profile and prepares a draft response that reflects what the reviewer wrote. The draft is sent to Slack, where a person approves, edits or rejects it before anything is published.

An example of how the studio would build it. No live services are connected.

From a new review to an approved reply.

  1. Step 01

    Review posted

    A new review appears on your Google Business Profile, and its rating, text and date are read.

  2. Step 02

    Reply drafted

    Claude drafts a specific, polite reply in your tone that responds to what the reviewer actually said.

  3. Step 03

    Sent to Slack

    Post the review and the draft to a Slack channel, with options to approve, edit or reject.

  4. Step 04

    Person decides

    A team member approves or edits the draft, while critical reviews are flagged for the owner to answer personally.

  5. Step 05

    Reply published

    Post the approved reply to your Google Business Profile and record who approved it.

The result

Every review gets an answer.

No reply is published without a person’s approval. Replies never include customer details or booking information, even when the reviewer mentions them.

Before we connect it.

Where this is useful

Useful for businesses that receive reviews regularly but reply inconsistently, or only to the negative ones. A sensible first version drafts a reply for every review and leaves publishing to a person, who approves each one from Slack.

What we need to connect

  1. 01Access to your Google Business Profile, with permission to read reviews and post replies.
  2. 02A Slack channel for approvals and a list of the people allowed to approve.
  3. 03Examples of replies you like, your tone and the topics a reply should never mention.

What needs careful handling

A public reply should never confirm someone was a customer or reveal details about their visit. Critical reviews deserve a person’s attention, so their drafts are held until the owner decides on a response. Reviews can be edited or removed after they are posted, so the workflow rechecks the review just before publishing a reply.

Questions people ask.

Will the replies sound generic?

They shouldn’t. Each draft responds to what the reviewer actually wrote, uses your tone and avoids stock phrases. The approval step is also a chance to add a detail only you would know.

Can it reply to negative reviews automatically?

Not in this design. A critical review is flagged in Slack for the owner, with a calm suggested draft as a starting point. A person decides what is said and when.

All automation examples