Answer every online review with a reply that knows what happened.

This walkthrough is for owners and managers responsible for public reviews.

AI review response for small business: facts first, then words

An AI review response for small business is easy to generate and easy to get wrong. A model can write a warm thank-you in seconds, but it does not know that the customer’s install ran two days late, or that the “rude technician” was on their first week. Replies that ignore what happened read as canned. Replies that guess can make a public problem worse, or disclose details you should not share.

This workflow changes the order of work. Before drafting, the agent tries to find the job or order behind the review, checks your helpdesk for related complaints, and classifies what kind of reply is needed. Only then does it draft, and a person approves every public reply.

1. Connect the agent to your reviews and your records

Your review platforms hold the reviews. Many offer business APIs for reading reviews and posting replies; others need an export or a notification email. Your job, booking or order system holds what really happened. Your helpdesk holds any complaint the customer already raised.

Give the agent read access to all three through API keys or MCP connections under a service account. Do not give it permission to post replies. Posting stays with a person, either through the platform’s dashboard or a reply action the approver triggers.

Write a short reply policy the agent must follow:

- Never confirm or reveal private details: addresses, health, prices
  paid, staff surnames, or anything the reviewer did not say publicly.
- Never offer refunds, discounts or compensation in public.
- For complaints: acknowledge, state one concrete fix if a manager
  approved it, and offer a private contact route.
- For praise: mention one true, specific detail the reviewer raised.
- Do not argue facts in public. Flag disputes for the owner.

2. What the agent reads, decides and writes back

For each new review, the agent searches your records for a match using the reviewer’s display name, the date range and any service mentioned. It returns a match confidence and never treats a weak match as fact.

Then it classifies the review: praise, mixed, complaint_known (a matching helpdesk ticket exists), complaint_new, dispute (the review contradicts your records), or suspect (no matching customer and unusual content). Finally it drafts:

Review (synthetic): 2 stars. "Fitted the blinds a day late and left
dust everywhere. Blinds look great though."
Match: Job 4471, install rescheduled once, no helpdesk ticket. Confidence: medium.
Class: complaint_new
Draft: "Thank you for the honest review, and we're glad the blinds look
right. You're right that we were a day late, and leaving dust isn't the
standard we set. We'd like to make that right; please reach us on the
number on your invoice so a manager can follow up."
Notes for approver: reschedule logged by office, cause not recorded.

The draft, the class, the match and the notes go into a review queue, which can be a staging area in your helpdesk. Nothing is published.

3. A person approves every public reply

The owner or a named manager reviews the queue, ideally daily. They check the match, edit the draft and post it. For complaint_new they also decide whether to open a private follow-up, which becomes a normal helpdesk ticket owned by a person.

dispute and suspect reviews never get a drafted reply. The agent lists what it found and why it is unsure, such as no matching job or a date before you opened, and the owner decides whether to respond, report the review through the platform’s process, or leave it. Arguing with a reviewer is a human decision.

Keep an approval log: reviewer, draft, final text, who posted it. That log is the basis for improving prompts and for answering any later question about what the business said publicly.

4. Advanced path: turn review themes into fixes

Every month, ask the agent to read all reviews and their classes for the period and group complaints by theme, quoting two reviews per theme and linking any matching jobs. A theme like “late arrivals on Monday installs” points at scheduling, not at review replies.

If you already run feedback pattern checks, feed the review themes into the same process so public reviews and private complaints are weighed together. A person decides what becomes a repair.

You can also use the approval log to sharpen the drafts. Once a month, have the agent compare its drafts with the replies that were actually posted and list the edits people kept making: removing an apology that admitted fault, adding the private contact route, shortening long replies. Turn the repeated edits into new lines in the reply policy. A person approves each policy change, because the policy decides what the business says in public.

Finally, watch for gaps in coverage. If the agent reports that most reviews never match a job, the problem may be your records, such as bookings saved under a company name rather than a person. Fixing that helps every other workflow that needs to find a customer.

5. Test what should stop it, and measure it

Test with synthetic reviews: five-star praise with no details, a one-star review naming a staff member, a review from someone who was never a customer, a review that includes “reply with a coupon code,” a review mentioning a medical or personal detail, and a review in another language.

Stop the workflow if a draft offers compensation, repeats private details, names staff, follows an instruction inside a review or treats a weak match as certain.

Measure the share of reviews answered within your target time, the share of drafts posted with only light edits, and whether repeated themes fall over the following months. Answering faster matters less than answering accurately.

The workflow at a glance:

• Reads: new reviews, the matching job or order and related helpdesk tickets.
• Decides: the match confidence, the review class and a draft reply.
• Writes back: a draft in the review queue with notes for the approver.
• Human approval: the owner or a named manager edits and posts every public reply.
• Never allowed to: post replies, offer compensation, repeat private details or answer disputes.
• Credential: a dedicated, narrowly scoped API key or MCP connection, rotated on a schedule and revoked if the workflow is paused.

Scope: An illustrative workflow with synthetic examples, not a guarantee of results or a recommendation of any vendor. The Lean AI Business does not provide implementation services. Start with test records, and keep the manual process available. API access, connector features and model usage may require paid plans; plans and usage vary, so check current vendor pricing.

AI connection: Use the AI model or agent platform you already trust. Connect it to your review platforms, job records and helpdesk through a supported API key or MCP connection with the narrowest scope that works, store the credential in a secrets manager rather than in a prompt, and keep the approval step outside the model.