Library / Guides / Ask for the review after the work

Guideservices

Ask for the review after the workA QR at the register in a panic is not a review system.

Reviews compound local search and trust. Most teams ask at the worst moment: checkout, a bad invoice, day zero of a job that is not done. The system is: completed work triggers a polite ask, unhappy people get a private path first, and the CRM knows who was asked. Interns send the test. CEOs stop treating Google as a lottery.

00

In plain words

Intern through CEO

Trigger: job complete, visit complete, move done — not estimate, not checkout panic.

  1. 01

    Trigger: job complete, visit complete, move done — not estimate, not checkout panic.

  2. 02

    Unhappy? Private recovery first. Do not spray a 2-star into public because your automation is blunt.

  3. 03

    Track who was asked. Do not ask weekly forever.

Who

Same lesson. Three jobs.

Read your row

Intern

What you actually do

Run steps 01 and 02 this week. Do not add a feature. A stage or a date that means the work is done.

Operator

What you protect

Protect the sequence. Unhappy? Private recovery first. Do not spray a 2-star into public because your automation is blunt.

CEO

What you refuse to fund

Do not fund more traffic or more seats until the scoreboard in this lesson is a number you will defend. Track who was asked. Do not ask weekly forever.

Steps

Do this in order

Why, then done when
  1. 01

    Define complete

    A stage or a date that means the work is done.

    Why: If complete is a feeling, the ask will fire wrong.

    Done when: A test completed job can trigger.

  2. 02

    Ask once, politely

    SMS or email with a direct link.

    Why: Staff nagging at the desk is inconsistent and awkward.

    Done when: The ask exists without a hero.

  3. 03

    Filter unhappy

    A 'how did we do' that routes 1–3 internally.

    Why: Public review automation without a filter is how you scale complaints.

    Done when: A low score creates a task, not a Google tab.

  4. 04

    Log the ask

    So you do not repeat.

    Why: Repeat asks are how you look hungry.

    Done when: Asked-on date on the contact.

  5. 05

    Review the rate

    Asks vs reviews vs recoveries.

    Why: Otherwise you will not know if the system runs.

    Done when: A monthly number.

Home services

Ask after the job is complete and the site is clean — not while the ladder is still in the driveway.

Why

Questions people actually ask

Pushback is normal

Why not ask everyone at checkout?

Checkout is payment stress. The work may not be done. You will get silence or a rating of the queue, not the job.

Apply

Use-case pages for this leak

GoHighLevel

Working notes

GHL Engine Checklist

The minimum CRM, pipeline, and nurture spec before you add more pages. Request the file. It arrives by email — not a public dump, not a drip of slogans.

Request the notes ↗
Next

If the leak is expensive, talk.

Email and WhatsApp stay open. A call is for installing the system.