Customer Operations
Review and referral: ask everyone, at the right moment
Ask when the job is really finished
Review requests usually go out on a timer: an hour after the visit, whatever happened. Sometimes that's while the invoice is in dispute, the part is still on order, or a complaint is open. Asking then is awkward at best.
A review and referral system asks at the moment the job is actually finished, from the job's real state. It asks every customer the same way, with a direct link to the review form and an easy way to reply privately. What happens next depends on the reply, and anything unhappy goes straight to a person who can put it right.
When it asks, and when it waits
Three replies, three next steps
J-551 · A.B.
- request
- sent Tue 09:00, the morning after payment
- reply
- ★★★★★ “great work, very tidy”
- next
- thank-you sent; referral invitation a week later with A.B.'s own link
- referral
- tracked, so a booking from it credits A.B.
J-548 · C.D.
- request
- sent Mon 09:00
- reply
- none
- next
- one reminder on Thursday, then nothing more
- record
- asked once, reminded once
J-553 · E.F.
- request
- sent Wed 09:00
- reply
- ★★ “technician was 40 minutes late”
- next
- operations manager calls the same day; support case opened
- review link
- not withdrawn; E.F. can still post a review
The rules it won't break
Everyone is asked
Same words, same link
Every eligible customer gets the same request. Timing rules decide when, never who.
Problems reach a person
The same day
An unhappy reply opens a case and a call. The review link stays where it was.
Referrals follow thanks
Not the other way round
Referral invitations go to customers who've already told you they're happy, and every referral is tracked.
Is a review and referral system the right fit?
Good fit
- Reviews and referrals matter to how you win work.
- Requests go out inconsistently, or at the wrong moment.
- Unhappy customers sometimes slip past without anyone calling them.
Avoid when
- The job and invoice records don't say when work is really finished. Fix that first.
- You complete a few jobs a month and ask each customer in person.
How we'd approach it
01
Understand
As much as the problem needs
We map how the work runs today: who does what, which systems hold the records, and where it breaks.
02
Design
Decided before it's built
Ownership, rules, integrations and exceptions, agreed with you and written down with acceptance criteria.
03
Build
Connected to what you use
We build the scoped system, connect it to the tools you already run, and test it on the cases that matter.
Questions about review and referral systems
Can we ask only the happy customers?
No. Google's review policy doesn't allow selectively asking for positive reviews, and the reviews are worth more to future customers when they aren't filtered. Everyone eligible is asked the same way; what changes is how you respond to their reply.
Which review sites do you send people to?
The ones that matter for your business, usually your Google Business Profile. The link goes straight to the review form.
How often is a customer asked?
Once per job, with at most one reminder, and not more than once every six months.
Do referrals need a reward programme?
Not necessarily. The system tracks who referred whom, so you can thank people however suits your business.
Ask every customer, at the right moment
Tell us how reviews and referrals are asked for today. We'll show you what a request sent at the right moment would look like.