Ask, receive, reply: the review loop, closed

The loop as a whole. A request goes out when a job finishes, the review arrives where you will see it, and answering happens in the same place.

Watch

A finished job sending a review request, and the reply being written 35s

What it does

What it does

The request sends itself

Finishing a job or marking an invoice paid can send the ask. Nobody has to remember, which is why it stops happening otherwise.

Reviews arrive where you work

Google and Facebook reviews land in the software rather than in an email you skim. You can see the day one appears.

You reply without leaving

The reply is written and posted from the same screen, so answering a review is a minute's work rather than a login hunt.

How it works

How it works

  1. Connect the review profiles you care about, Google first.
  2. Pick the moment the ask goes out: job closed, invoice paid, appointment done.
  3. Requests send on their own from then on, by text or email.
  4. New reviews appear in one list, and you answer them there.

Worth knowing

Worth knowing

  • Asking everyone means asking unhappy customers too. That is the point, and you should be ready to answer one badly.
  • Google decides what it publishes and when. A request sent is not a review posted, and some never appear.
  • It cannot remove a bad review. It gets you to it quickly, so your answer sits underneath it.

Related

Related

How review requests get sent
The request side in full: channels, timing, QR codes and drafted replies.

Reviews in one place
The review inbox itself, Google and Facebook side by side.

Workflow automation
What else the end of a job can trigger.

Connect your Google profile

Log in, connect your review profiles, and choose the moment the request should go out.

Log in See pricing at LaunchLocal