Asking for reviews can feel awkward. Ask too early and it sounds like you care more about the score than the job. Ask too often and the customer feels hassled. Do not ask at all and the only people who leave reviews are the ones who are angry enough to remember.
A good review request is plain. It comes after the work is finished, gives the customer a simple path, and asks for honest detail rather than a perfect score.
Finish the job before asking
Do not ask for a review while the customer is still waiting on cleanup, a certificate, a receipt, a defect fix or a final answer. The review request should come after the job is actually complete from the customer’s point of view. If you ask too early, the customer may feel pressured to praise work they have not fully checked. Finish first, then ask.
Send the request close to completion
Timing matters. Send the request while the job is still fresh, usually within a day or two of completion. Wait too long and the customer forgets the details. Send it too soon and it feels pushy. A simple message after the final invoice, handover or completion photos is usually enough. The customer still remembers what happened and can write something useful.
Ask for an honest review, not five stars
Do not ask for a five-star review. Ask for an honest review of the work and the experience. Customers can smell score-chasing. A request for honesty sounds more confident and produces better reviews. If the job went well, the score will usually look after itself. If something was bumpy but resolved properly, the review may be more credible than a perfect line with no detail.
Make the request specific
A useful prompt helps the customer write. Ask them to mention the kind of job, communication, timing, cleanliness, quote accuracy or how the issue was handled. Do not script the review. Just help them think about what mattered. "If you are happy to leave a review, mentioning the leaking shower repair and how the timing went would help future customers" is better than a generic plea.
Use one clear link
Do not send customers through a maze. Give one review link, one short request and no long explanation. If they have to search for your profile, create an account they were not expecting, or choose between several platforms, many will give up. The request should be easy to act on in the moment. Friction kills normal satisfied reviews.
Do not reward the review
Gifts, discounts, cashbacks and incentives can distort reviews and create regulatory trouble. They also make the review look bought. If you want to thank customers, thank them for the job, not for a score. The review should be a record of their experience, not a transaction. Customers who felt respected are more likely to leave the kind of review that helps anyway.
Do not nag
One request is normal. One polite reminder after a few days can be fine. More than that starts to feel needy. If the customer does not leave a review, let it go. You are building a review record across many jobs, not extracting a review from every person. A business that pesters customers for reviews can undo the goodwill the job created.
Use bad jobs as feedback first
If the job had problems, ask for feedback before asking for a public review. "I know the timing slipped on this one. Is there anything you want us to sort before we close it out?" That gives the customer a path to raise issues. Asking for a review while unresolved frustration sits under the surface is asking for trouble. Fix what can be fixed first.
Put the agreement in one place
For how to ask for a review without sounding desperate, the useful record is usually short: what was agreed, who agreed it, when it was agreed, and what it does to price or timing. Keep that in one message, quote, invoice note or job file entry. Scattered details across calls and texts are where honest people start remembering different things. One written record gives both sides a calmer place to return to if the job later gets tense.
Keep the proof with the job
Save the quote, photos, messages, payment record, invoice and any approval tied to the issue. The proof does not need to be dramatic. It just needs to be findable. A customer can use it to explain a concern clearly. A tradie can use it to show what was done and why. The person with the clean record usually has the easier conversation when something is questioned later.
Make the later review factual
If the experience later becomes a review, write about behaviour and records, not just mood. Say whether the quote was clear, access was handled, messages were answered, changes were written down, payment terms were plain, and problems were fixed. That helps the next person reading the review. It also gives the business useful feedback instead of a public argument with no detail behind it.
Reset the scope when facts change
Jobs change when hidden damage appears, a customer changes their mind, parts are unavailable, weather moves the date or access is harder than expected. The safe move is to reset the scope before work continues. Write what changed, what it costs, what it does to timing and who approved it. That small pause is usually cheaper than arguing about an invoice after the work is already done.
A good review request is not desperate. It is short, honest and timed after the job is complete. Ask once, make it easy, invite useful detail and do not chase a perfect score. The review record you want is built from steady, fair requests across normal jobs.