Building a Review Request Process Your Whole Team Follows

A store does not have a review problem because customers refuse to write. It has a process problem because the ask lives in one person's head. When that closer is on a test drive, the deal still delivers, the customer still leaves happy, and nobody sends the link. Building a review request process your whole team follows means the ask happens on ordinary Tuesdays, with ordinary reps, without a speech from the owner at the Saturday meeting.

Process is unglamorous on purpose. It is a checklist line, a CRM note, a shared short link, and a manager who looks at last week's deliveries instead of last week's star count. If your current "process" is a poster in the restroom or a spiff for five-stars, the team already knows it is optional. Optional processes die at month-end.

This guide is for managers who need the floor, F&I, and (if you have one) a BDC to run the same play. It covers roles, the minimum artifacts, scripts that do not beg, how to audit without turning reviews into a contest, and how to keep the process legal and platform-safe at a high level.

Design a Review Request Process Around Deals, Not Campaigns

Campaigns are calendars. Deals are daily. Attach the review request to delivery the same way you attach the second key.

One definition of "eligible"

Write down when a deal is eligible for a request:

• Retail delivery is complete (keys, explanation, no open promise sitting on the jacket).
• The customer has not asked to be left alone.
• There is no active complaint you have not addressed.
• You are asking for an honest review of the experience, not a specified star rating.

Wholesale, internal, and incomplete deals are out. If recon or plates are still open, the deal is not eligible yet. Eligibility is a gate, not a vibe.

One owner per deal, visible to the team

Put a name on the jacket or in the CRM:

• Default: the delivering salesperson.
• House deals and manager deals: the manager who delivered.
• Rep off-shift: a named backup, not "the desk."

Associates who only posted the unit or copied photos do not own the ask. They did not earn the conversation. Sales reps who self-queued and sold the car do. Managers who assign associate work should still own house-customer relationships.

One place the link lives

If every rep texts a different Google search, half of the customers land on a competitor or an old address. Create:

• A single short URL or QR that goes to your current review form.
• A printed card at delivery as a backup for customers who do not want a text.
• A note in the CRM template so a backup can send the same thing.

When the Google Business Profile URL changes, one person updates the source. Everyone else copies. That is the entire "technology stack" a small lot needs.

The Artifacts the Floor Will Actually Use

If it is not on the delivery checklist, it will not happen. If it requires a login nobody remembers, it will not happen.

Delivery checklist: three extra lines

1. Open issues remaining? Yes / No. If yes, skip ask.
2. Verbal ask by ________ at ________.
3. Link sent (text/email/card) at ________, or skip reason ________.

Keep it on the same sheet or screen as the rest of delivery. A separate "reputation form" will not be filled out.

Scripts that survive a busy Saturday

Verbal, under thirty seconds:

• Thank them by name and vehicle.
• Explain that local buyers read Google.
• Ask if they are willing to describe the experience in their own words.
• Offer to send the link for later. Do not watch them type.

Text, same day if eligible:

• One thanks sentence.
• The link.
• Permission to ignore it if now is a bad time.

No second message that night. One reminder in a later window only if they were eligible and silent. Stop if they opt out. Capture contact preference. This is not legal advice on messaging consent; set that policy with counsel.

Timing rules the team can remember

Teach the moment separately from the checklist. The full timing logic lives in asking for Google reviews at the right moment after a sale. In training, keep it to: not in F&I, not while issues are open, same day after they are gone, one reminder later if needed.

Train the Review Request Process Like Any Other Floor Skill

A process your whole team follows is trained, role-played, and inspected. It is not announced.

Onboarding block (thirty minutes)

For every new rep and associate who will be near delivery:

• Why we do not ask for a star number.
• Who owns the ask.
• How to send the link from the shared source.
• What to do if the customer is upset or still waiting on something.
• What never to offer (discounts for stars, "I'll knock off $200 if you hit five").

Put it on the same day as Marketplace posting onboarding so reputation and listing hygiene feel like one store, not two hobbies.

Role-play that includes the awkward cases

1. Happy delivery, customer in a hurry.
2. Delivery with a missing second key.
3. Customer who says they never review businesses.
4. Customer who wants to complain about wait time.
5. Manager covering for a rep who is off.

If the only practice is the happy path, the process will be skipped on the deals that most need a human close (the complaint should be handled, not converted into a review ask).

Incentives that do not corrupt the ask

Pay for process compliance if you must: checklist complete, link sent when eligible. Do not pay for star volume. Star spiffs produce hovering, coached language, and reviews that mention being asked for five stars. That is the opposite of a professional profile. For the broader problem of paying for the wrong online behavior, see spiffs and pay plans that reward online lead handling and apply the same logic: reward the work, not a vanity number.

Audit Weekly, Coach the Pattern, Not the Person

Managers do not need a dashboard from a review vendor to start. They need last week's deal list.

Monday review (fifteen minutes)

• Count retail deliveries.
• Count eligible deals with a completed checklist.
• Spot-check three texts for the shared link (not a random Google search).
• Note any review that arrived and whether it describes an open issue you should have closed first.

Share the compliance number in the sales meeting, not the star average. Stars are a lagging result. Checklist completion is the leading habit.

Failure modes to coach

• F&I asking because they "know the customer will forget."
• Reps sending the link from a personal Google page of a different location.
• Skipping anyone who negotiated.
• Asking while a promised detail is unfinished.
• A month-end blast to everyone in the CRM.

Coach the pattern in public. Coach an individual miss in private. If one rep never asks, it is a performance item like any other skipped delivery step.

Keep platform and legal risk in the process document

Include one page that says:

• No incentives tied to a positive rating.
• No asking employees or vendors to pose as retail customers.
• No suppressing negative reviewers by only asking "happy" deals as a hidden policy (you may delay while an issue is open).
• Check Google's current review policies and any state rules on testimonials and advertising.

That page is operational hygiene, not legal advice. Have counsel review it if you advertise with review quotes or run any gift program.

When you later use reviews in ads or social posts, follow turning customer reviews into marketing content ethically rather than screenshotting from the floor group chat.

How PostToMarket Automates This

A review request process fails when delivery day is also the day the floor is still posting yesterday's inventory by hand. PostToMarket does not send review texts. It takes listing work off the people who own the ask, and it cuts the sold-unit and accuracy mistakes that make customers unwilling to review.

Protect the delivery window

• Queues: personal queues, per-rep queues, managers assigning vehicles to associates, reps self-queuing from shared inventory.
• Mobile dashboard so a rep can reorder posting around deliveries instead of dropping both jobs.
• Server-enforced daily post limits and human-like delays in the Chrome extension, one vehicle at a time, so the team is not dump-posting at the hour customers are leaving with keys.

Keep the public story aligned with the deal they just signed

• Mark as sold and archive so the car they bought is not still advertised an hour later.
• AI listing copy from specs, editable before post, and a Facebook photo picker.
• Import history with row-level errors so the price and miles on the listing match the jacket.
• Leads inbox so managers see whether the customer was ignored before they ever arrived.

PostToMarket is not affiliated with Meta. It cannot guarantee a Google review. It can make the review process possible on a busy floor because posting is no longer an all-hands scramble.

Make the Ask Ordinary, Then Leave It Alone

Building a review request process your whole team follows is checklist design, role design, and a Monday audit. Name an owner, gate on eligibility, send one shared link, and stop paying for stars. When the process is ordinary, the profile grows from completed deliveries instead of from whoever remembered.

Clear the operational noise that competes with that process. PostToMarket includes unlimited inventory, bulk CSV and Excel import, AI titles and descriptions, team queues, a leads inbox, and AutoPost. Dealership is $299 per month for up to 13 logins. Starter is $59 per month for a solo operator who is the entire team.

Start your 10-day free trial through secure Stripe checkout. Get posting onto a paced queue so delivery—and the review ask—can happen on time. Cancel anytime.