The ask, after the job, without gating anyone out

This page is about the workflow that asks: when it fires, who it skips, what it sends, and how consent is handled. What happens to the reviews afterwards, the responses and the reputation they build, is part of local search and lives at review management.

A satisfied customer finishes the service, thanks your team, and moves on with the day. Writing a public review is rarely the person’s next urgent task, so the business needs a consistent request that arrives after the qualifying service, identifies the business, and makes the destination clear. Automation supplies the consistency. It does not manufacture goodwill or control what the customer writes.

What we build

• A completed servicethe trigger comes from the operating record, not from memory
• Eligible?a real customer, a valid contact, no opt-out, no duplicate
• The same chance to leave a public review, for every eligible customerthe ask is short and honest, with the direct destination
• The customer choosesa public review, or none

Review gating

Not built

• A satisfaction question first
• Happy customers sent to Google
• Unhappy customers sent to a private form

It filters the public sample and breaks platform rules. A private feedback route can exist, but it never replaces the public option.

Ask every eligible customer

Eligibility comes from a completed service record and approved exclusions, not from a satisfaction score used to decide who sees the Google link. The rules can exclude duplicate records, opt-outs, canceled work, test contacts and cases without a completed service, and they are documented and applied consistently. Picking who gets asked distorts the result, and it breaks the platforms’ rules.

Timing the request

The best moment is when the customer can fairly evaluate the completed service, and the completion event comes from the operating record: a finished appointment, a closed job, a delivered project, or another approved status. Some services need a short delay so the customer can see the result. Others support a request soon after completion while the details remain familiar. Timing is chosen from the service process and then reviewed against response and delivery data.

Message and follow-up

The request is short. It identifies the business, asks for an honest review, and provides the direct destination. It does not tell the customer what rating to choose or supply praise for them to copy. Follow-up is limited and stops when a review is recorded where observable, an opt-out is received, the contact becomes ineligible, or the sequence reaches its approved end. The workflow does not misrepresent that posting on Google needs a Google account, and it never publishes a review on the customer’s behalf.

Service concerns are handled elsewhere

Review requests do not replace a response process for service concerns. A complaint needs a neutral route into the business and a named owner, and a public negative review needs a calm, factual reply. Both are part of review management, which begins where this page ends.

What gets measured

• Completed services reviewed for eligibility
• Eligible customers entering the sequence
• Requests attempted
• Delivered, or failed
• New reviews in the period

A new review cannot always be tied to one request. The customer may use another device, search for the profile later, or review without clicking the tracked link. Reporting separates what was seen from what is assumed.

Its place in your growth system

Customer Continuity creates the request process, and the resulting reputation can support Market Visibility.

Next step

Bring your completion statuses, current review request, Google profile, opt-out process, and staff response rules. We will check eligibility, timing, policy risk, and ownership before deciding what to automate.