Review requests

Review-Request Automation: Get More Reviews Without Chasing

When the receptionist bookmarks an appointment as completed, a one-question Google review request goes out with the shared disclosure, on the same consent ledger as the rest of the SMS pipeline.

The fastest way to get more reviews is to ask — once, the day after, by SMS, on the SMS-vetted contact list you've already built. Analese reads appointment completion from the calendar and the receptionist, then sends a single one-question review request. Reply STOP and you stop getting them, period. No separate opt-in flow to manage, no third-party review vendor, and no manual work for your front desk.

The fastest way to get more reviews is to ask — once, the day after, by SMS, on the SMS-vetted contact list you've already built. Analese reads appointment completion from the calendar and the receptionist, then sends a single one-question review request. Reply STOP and you stop getting them, period. No separate opt-in flow to manage, no third-party review vendor, and no manual work for your front desk.

What you get

  • One-question Google review request, with the shared disclosure on the first send.
  • Same consent ledger as the rest of the SMS pipeline — STOP, CANCEL, END, QUIT, STOPALL, UNSUBSCRIBE all honored case-insensitively.
  • Server-rendered STOP ack — the system replies with the same STOP_ACK string the rest of the SMS pipeline uses, and never texts that number again.
  • Plan-gated on Team and Multi-location — same gate as the missed-call and appointment texts, so the SMS boundary flips in one place.

How the dispatcher runs

  1. 01The receptionist bookmarks an appointment as completed — through the daily-summary inbox, the dashboard, or the same completion hook that powers appointment verifications.
  2. 02A trigger row flows to /api/review-request/trigger, which checks the customer's plan and the recipient's SMS consent ledger before dispatching anything.
  3. 03A single one-question SMS goes out within minutes — the link points to the Google review flow configured for the business.
  4. 04Reply STOP opts the recipient out across every pipeline that shares the consent ledger — same rule as the rest of the SMS pipeline.
  5. 05Your team tracks review-request throughput in the daily summary email.

A buyer question: why a one-question SMS instead of a vendor?

Most review-request vendors ride as bolt-on dashboard apps with their own consent ledger, separate opt-out flow, and a separate dashboard to monitor. Analese's review-request rides on the same SMS pipeline and consent ledger that miss-call and appointment texts already use. One opt-out covers every text on Team and Multi-location, so you don't have to maintain a separate vendor database to enforce the shared product behavior. The trade-off is that we only do the one-question Google flow (not vendors that ship bespoke review platforms) — for most service businesses, that's the right scope.

A buyer question: what about reply rate?

Reply rates for one-question post-appointment SMS requests are usually in the 8–15% range when sent within minutes of the appointment being marked complete. The window matters: send within the day, not days later. Send to the customer's mobile, not a desk line. Send a one-question text, not a survey. That's the only shape Analese ships today, and it's the shape that hits the floor of the funnel.

Ready to see it work?

See if it fits.

Three plans, side by side. Same receptionist, same SMS pipeline, and a clear monthly allowance: Solo 500, Team 5,000, or Multi-location 25,000 conversations. Pick a tier and pay in the same checkout.

Keep reading

More from the blog. Different topic, same playbook.