Why your tint shop needs automated review requests (and how to set them up)

Why reviews decide who calls you

Almost nobody chooses a tint shop from a website. They search "window tint near me", look at three map results, and pick on two things: how many reviews you have and what the recent ones say. That is the whole funnel for a local install business.

It is not folklore, either. Google's own guidance on local ranking lists prominence as one of three factors alongside relevance and distance, and says review count and rating feed into it: More reviews and positive ratings can help your business's local ranking. (Google Business Profile Help: Tips to improve your local ranking on Google.) So reviews are doing two separate jobs at once — they help you appear in the pack, and they win the click once you are there.

Recency matters in a way shop owners underrate. A profile with a healthy count and nothing new in eight months reads as a business that may have gone quiet. A steady trickle — a few every month, forever — beats a one-off push where you asked forty customers in a week and then stopped. It also looks more like what it is: a shop that keeps doing good work.

The right moment to ask

There is a window, and it is narrow. Ask after the customer has paid and seen the car — walked around it, sat in it, noticed how much cooler it is, shown somebody. That is peak enthusiasm. In practice for a tint shop that means a couple of hours after pickup, the same day.

The two common mistakes are on either side of that window:

• Too early: asking at the counter while you are handing over keys. The customer is holding a card, thinking about parking, and being watched by the person asking. They say "sure, absolutely" and never do it.
• Too late: a week later. The tint is normal now. Whatever they felt in the sun on the drive home has gone, and your message is just another notification.

Two tint-specific caveats. First, if you hand over with cure-time instructions, do not send the request before the film has settled — a customer messaged during the haze-and-tiny-water-pockets phase may write a review about a problem that was never a problem. Waiting until the same evening, or the next morning for a full install, avoids that neatly. Second, only ask once the job is paid. A request that goes out before the invoice is settled is a strange thing to receive, and it tangles two conversations.

One follow-up is fair, three days later, if there was no review and the first message did not bounce. Then stop. Nobody's third reminder ever earned five stars.

What to actually say

Short, specific to their car, signed by a person, and with the link right there. The link matters more than the prose — every extra tap loses people, so send the direct review link rather than telling them to search for you.

Four things are doing the work in there. The vehicle ("the Model 3") proves a human wrote it. The time estimate lowers the perceived cost of saying yes. The escape hatch — reply here if something is wrong — routes problems to you instead of to your profile, which is legitimate because you are offering it to everybody, not only to the people you suspect are unhappy. And the name at the end makes it a message from Luis rather than from a system.

What to leave out: "5-star", "positive", any mention of a discount, and any ask for particular wording. Those cross the line covered in the next section.

Google's rules, in plain language

The relevant policy is Google's Maps user-generated content policy, and it is worth reading once so you know exactly where the edge is (Prohibited & restricted content). Three rules matter for a shop:

1. Never gate by rating. Asking "how did we do, one to five?" and only showing the review link to the people who said four or five is review gating. The policy prohibits selectively soliciting positive reviews from customers. Send the same request to everyone who paid.
2. Never incentivise. No discount, no free tint on the visor strip, no entry into a draw, no free wash for a review. The policy specifically prohibits offering incentives such as payment, discounts or free goods and services in exchange for reviews — and that includes paying to have a negative one removed.
3. Do not manufacture a burst. Handing your phone or a shop tablet round so ten customers post in one afternoon, or setting your staff a target number of reviews, is the pattern the policy's rating-manipulation section is about. It also risks the reviews being filtered out, so you take the risk and get nothing.

What you are allowed to do, and what this whole guide is about, is ask every customer, plainly, for an honest review of a real experience, and give them a link. Steady, automatic, un-targeted. That is both the compliant approach and the one that actually works, because it scales to every job instead of to the ones somebody remembered.

When you get a bad one

You will. Aim to have enough recent reviews that one bad one is a data point rather than a headline, and then answer it properly. Reply publicly, once, within a day or two:

1. No defensiveness in the first sentence. Thank them for saying it, name the specific problem so other readers can see you understood it.
2. Say what you are doing about it. Re-do the panel, refund the section, change the process. Something concrete.
3. Move the argument off the profile. Leave a direct way to reach you — a phone number or an email — and stop replying in public after that.

Do not argue facts in a thread, do not imply the customer is lying, and do not offer money to have it taken down — that last one is itself against the policy above. It is worth remembering who the reply is for: not the reviewer, who has usually made their mind up, but the next twenty people reading your profile while deciding whether to call. A calm, specific, slightly boring reply to a one-star review sells better than a perfect profile with nothing on it, because it shows what happens when something goes wrong.

The one time to use Google's reporting flow is a review that breaks their content rules — a competitor, someone who was never a customer, abuse, or spam. Report it, then get on with your day; do not build your week around it.

Tracking requests against new reviews

The only honest measure is requests sent versus new reviews landed, month by month. Not your star average, which moves too slowly to tell you anything, and not your total count, which only goes up.

Compare the first two before you touch the wording. Most shops that think their requests do not convert are actually sending far fewer than they think.

Set a baseline for a month, change exactly one thing — the timing, or the wording, or sending the link instead of a search instruction — and look again next month. This is also the reporting shape PeelBoard uses: requests sent against new reviews, rather than a vanity star average.

Making it automatic

Everything above collapses if a human has to remember it. Here is the whole setup, and it is a fifteen-minute job:

1. Get your direct review link from your Google Business Profile — the short link that opens the review box straight away, not your profile page.
2. Write the two messages from the templates above, in your own voice, with your name and your link.
3. Trigger the first one off the job being paid, not off the job being finished. Paid is the clean signal and it is the one that matches the moment.
4. Set the delay to a couple of hours, and shift it to the next morning for jobs that finish late so nothing lands at 9pm.
5. Send it to everybody who paid. No screening, no filtering, no exceptions.
6. Check the two numbers — requests sent and new reviews — once a month.

In PeelBoard this is the review request text that fires automatically after a paid job, out of the same 500 texts a month that send your appointment confirmations and reminders. Set it once and it keeps asking every customer, on every job, on the day — which is the only version of this that survives a busy month.

Related reading