Reviews and Referrals After the Job: A Simple System

Grunlo is field service operations software for landscaping, lawn care, and similar businesses—this article is about reviews and referrals as a repeatable system, not about begging for five stars.

Reviews are not vanity—they are signal: where training pays off, where access assumptions were wrong, and where your estimate language might be creating post-job friction. Referrals, when you use them, are distribution: the best crews still need a simple way for happy customers to send neighbors.

The failure mode is randomness: sometimes you ask, sometimes you forget, sometimes you ask twice because two people on the team “always do it.” Customers experience that as inconsistency—not enthusiasm.

Start with one definition of “done”

Your system should trigger off a stable operational event: job completed (with quality checks you already believe in).

If you ask for a public review while the customer still thinks something is open (billing confusion, missed debris, unclear next visit), you are not collecting feedback—you are collecting conflict.

This connects directly to how you close work and communicate completion: When the schedule breaks and Getting paid faster are siblings here—clarity before applause.

Email vs SMS: two channels, one intent

Email is great for detail and links. SMS is great for “this is the one thing to do now.”

Grunlo can send a job completed email, and—when enabled appropriately for your plan and configuration—can also send a review SMS as a separate message with a link. The behavior, requirements, and setup toggles are documented in Review requests and Leaving reviews.

SMS consent and valid mobile numbers matter—SMS is not a universal pipe. If you are tightening SMS discipline more broadly, read SMS that helps customers.

Make the review page feel like part of your brand, not a detour

Customers should recognize:

• what job they are reviewing
• what “good” looked like for that job
• what happens after they submit

Grunlo’s review flow is designed so customers can submit a star rating and optional comment on a secure page; owners can review reporting in-app (see Help for details).

If you use an external Google Review URL, treat it as a second step, not an ambush—Help describes prompting after an in-app review when configured.

Referrals: keep the incentive honest and legible

Referrals work when neighbors trust the introduction. The mechanics—codes, landing page attribution, qualification rules—are covered in Referral program.

A practical principle: reward outcomes you want repeated (for example, first paid invoice) rather than rewarding noise—your Help doc explains why “first invoice paid” is often the recommended qualification rule.

Portal habits make reviews and referrals easier

When customers already know where to find invoices and upcoming visits, your post-job ask feels like a natural continuation—not a new system to learn. If portal adoption is weak, fix that first: Customer portal adoption.

How Grunlo helps

Grunlo ties post-job follow-up to the same customer record as scheduling and billing—so “review timing” is not a separate shadow workflow run out of someone’s personal phone.

Feature availability depends on your plan (review requests and referrals are called out explicitly in Help). Configure feedback and referrals under Settings → Feedback & Referrals, and SMS types under Settings → Customer Communications—see Review requests.

Key takeaways

• System beats heroics—trigger reviews off a consistent “job complete” standard.
• Channels have different jobs—email carries context; SMS carries a single action when appropriate.
• Consent and data quality are part of CX—failed sends feel like neglect.
• Referrals need clear rules—neighbors should understand what qualifies and what credit means.

Related reading

• Blog: Why customers leave — reputation is downstream of communication and billing trust
• Help: Customer portal overview
• Help: Public landing page (where reviews can surface publicly, depending on setup)