01 / Completed service
An approved staff form or supported booking event starts the request.
Newzchain Studio / US businesses
Ask for a review.
Keep it simple.
Send a short review request, one reminder and a clear opt-out, with a simple view of requests sent and clicked.
A clear handoff
02 / Request and reminder
A direct review link, one reminder, then the sequence stops.
03 / Staff visibility
See requests sent and clicked; respect consent and opt-outs.
A short request, then stop
After a completed job or service, customers receive a short review request with a direct link to the business’s review page. One reminder can follow after the agreed interval, then the sequence stops. The message should identify the business and make participation optional.
For example, a catering team can mark an event complete in a staff form. The system sends the approved email and records the send status. A reminder is sent only under the agreed rules; duplicate staff entries must not create repeated requests. We define the event that starts the sequence before connecting any provider.
See requests sent and clicked
A simple dashboard can show requests sent, delivery status where available and recorded link clicks. These measures describe the request process. A click does not prove that a customer posted a review, and a request does not guarantee a rating.
Staff need a clear way to correct an address, stop a sequence and identify failed delivery. We agree access permissions and the records the business needs, rather than adding an unrestricted customer database. Third-party review platforms control their own review publication and moderation.
Ask consistently and respect permission
Every customer is asked under the same completed-service rule. The workflow does not filter out unhappy customers, offer incentives for reviews or send only satisfied customers to a public review link. Private feedback can have its own route, but it must not become a gate that prevents someone from leaving a public review.
Texts go only to customers who agreed to receive them. Every text includes an opt-out and the workflow respects that choice. The business supplies lawful contact permissions and an accurate sender identity. We review provider and platform requirements before setup; automated requests should not bypass them.
Choose a supported starting point
A staff form can be the simplest launch route: an authorised team member records a completed service and the permitted contact channel. A QR card can invite the customer to open the review route directly. Where supported, a booking-software connection can trigger a request after a defined completion event.
Email is the initial channel. SMS launches only after the required carrier registration is approved and consent/opt-out handling is ready. A carrier approval or supported API must not be assumed from the price alone. We test duplicates, opt-outs, missing permissions and delivery failures with synthetic contacts.
Defined setup and monthly support
$299 setup + $79–$149/month. The agreed scope defines the starting event, email template, one reminder, dashboard and usage boundaries. Approved email/SMS provider charges and custom integrations are separate.
We do not promise review counts, star ratings or search positions. The service helps carry out an approved request process. It does not write customer reviews, create fake accounts or alter reviews left by other people.
Frequently asked questions
How can I get more Google reviews responsibly?
Ask customers consistently after completed work, make the review link easy to find and keep participation optional. Do not filter, incentivise or invent reviews.
Can we ask only happy customers?
No. The workflow asks every customer under the same rule and does not use sentiment to gate the public link.
How many reminders are sent?
One reminder under the agreed timing, then the sequence stops.
Does a click mean a review was posted?
No. The dashboard distinguishes request activity from review publication.
Can it use our booking software?
Where the software supports a reliable completion event and approved access. Custom integration is separately scoped.
Is SMS available immediately?
The initial launch is email-first. SMS requires approved carrier registration and working consent and opt-out handling.