How April uses Uniqode
A review code per technician, not per truck.
for portfolio breadth across all Uniqode customers
the code count of a typical account in its industry
The challenge
A local landscape irrigation and low-voltage outdoor lighting contractor runs on two unglamorous mechanics: getting a happy customer to leave a Google review right after the job, and giving a prospect who sees a truck or a mailer a way to request a quote without calling the office. Neither works if it is one shared link for the whole company.
The solution
The account names its review codes by crew member, not by campaign, so a review ask is attributable to the technician who did the job instead of disappearing into an office-wide number. A separate code handles a specific contract-tier upsell response. Both point straight at Google's own review flow rather than an intermediate landing page.
How April puts it to work
One review code per technician
Each crew member gets a distinct code so a customer's review request is attributable to the person who did the job, not lumped into a company-wide total.
Straight to the review flow, no detour
The large majority of custom URLs resolve directly to Google's own review page, cutting the request down to a single scan.
A dedicated code for a contract-tier upsell
One code is built specifically for prospects responding to a plan upgrade offer, kept separate from the review-generation set.
Rolled out as a fleet, not a pilot
The large majority of the account's codes were created in a single month, reading as a deliberate technician-by-technician rollout rather than gradual, uncertain adoption.
Features used
04 · The outcome
The codes were rolled out in a single batch, the account's busiest month by far, and have kept working reliably since, which is the whole ask in the account's own review.