Ask every customer, once, at the right moment.

Happy customers rarely leave a review because nobody asks them. We set up one short request after each finished job, in your words, sent to everyone alike. What they write is up to them.

What we build, and what we refuse to.

Reviews are only worth something if they are real. These rules are not optional settings.

We do

  • Send the same request to every customer after a finished job
  • Use wording the owner wrote or approved, in their languages
  • Link straight to your Google profile, one tap
  • Stop after one reminder, and never message someone who said stop
  • Alert you when a review comes in, good or bad
  • Draft replies for you to approve before anything is posted

We don't

  • Offer discounts, entries or gifts in exchange for reviews
  • Ask happy customers and quietly skip unhappy ones
  • Write, buy or post reviews, for you or about competitors
  • Ask staff, friends or family to review the business
  • Post replies without a person reading them
  • Promise a rating. What customers write is theirs.

Based on Google's published review policies. Plain language, not legal advice.

Triggered by the job, not by memory.

Illustration of a job ticket stamped done on a clipboard, with a single paper plane carrying a small star lifting off from it.
  • 1. The job is marked doneIn your CRM, job tracker or invoicing tool. That event, not someone's memory, starts the request.
  • 2. A short wait you chooseThe request arrives after the customer has seen the result, not while the van is still outside.
  • 3. One messageBy text or email, depending on how that customer prefers to hear from you.
  • 4. One reminder at mostThen the customer is left alone.
  • 5. New reviews arrive as an alertWith a drafted reply for you to edit and post.

The request is sent once per job, even if the job is reopened or the invoice is printed twice. It is the same rule we built into a different automation: trigger on the job itself, never on a button someone might press again.

Illustration of a laptop showing a new review alert card with an empty reply box waiting for the owner to write.

Where it fits

How we'd build it

Not built for a client yet. It is a small workflow on top of a CRM or job tracker you already have: a "job done" event, an approved message with your review link, a stop rule, and an alert to you. The duplicate-proof trigger comes from LabelBot, our shipping automation at a dental lab, which checks before acting so a reprint never repeats an action.

What we need from you

  • Manager access to your Google Business ProfileThrough a login you can remove.
  • Your "finished" momentWhen a job counts as done in your business.
  • The message, in your voiceWe will keep it under three lines.

About asking for reviews.

Can we offer a discount for leaving a review?

We will not build that. Paying or rewarding customers for reviews breaks Google's review policy and can break consumer-protection rules. The request is a plain ask, the same for everyone. This is a plain-language summary, not legal advice.

Can we only ask the customers who were happy?

No. Asking only the customers you expect to be happy, sometimes called review gating, is against Google's rules. Every finished job gets the same request. If someone is unhappy, you hear about it and can fix it in the open.

Will you reply to reviews for us?

We draft replies for you to approve, edit or throw away. A reply to a review is public and speaks for you, so a person always posts it.

Plenty of happy customers, few reviews? Let's ask them properly.

A free call to find the right moment in your work to ask.