Google Review Cards For Auto Dealerships

Why dealerships are a distinct review-programme case

Auto dealerships look like premium retail from the outside, but the business runs two completely different customer flows under one roof (sales delivery and service pickup) with separate staff, workflows and handoff moments. A generic retail review-card plan fits neither, and the dealership also layers OEM manufacturer scoring on top, which changes both the stakes and the compliance lines.

• Sales delivery: a high-stakes, once-a-decade transaction. The customer has spent hours at the dealership, signed paperwork, and is picking up a car they feel emotionally invested in. The review moment is very strong if it lands well, and sales reviews tend to be long, substantive and heavily influential for other new-car shoppers comparing dealers.
• Service pickup: a frequent, lower-stakes transaction. The customer drops off, the car is fixed, the customer pays at the cashier and drives away. The review moment is shorter but repeats every visit. Service generates the bulk of total review volume across the year because the customer base cycles through service two to six times for every one sales interaction.
• The two flows share a Google Business Profile in most rooftops, which means both sales and service reviews land on the same rooftop profile. This is a feature (consolidated review count that strengthens local-pack ranking) but creates measurement complications (no clean separation of sales vs service review velocity without URL-level tagging).
• OEM scoring overlay: most manufacturers run CSI (Customer Satisfaction Index) for service and SSI (Sales Satisfaction Index) for sales, fed partly by post-visit surveys. These scores tie to dealer bonuses, allocation and stair-step programmes. Dealer principals often treat the Google review programme as complementary (the surveys drive OEM bonuses, the reviews drive local visibility) but the two systems cannot contradict each other publicly.
• Dealer-group structure: multi-rooftop groups often hold several OEM franchises under one parent. Each rooftop has its own Business Profile, its own general manager, and often its own internal culture. The group-level template and admin layer has to accommodate variation between rooftops, not force an identical workflow onto every one.
• EV and hybrid transitions: as dealerships shift toward battery-electric inventory, the delivery moment is longer (charging setup, range education, mobile-app pairing) and the service moment is different (fewer routine service visits, more infrequent high-stakes battery-related visits). The prompt timing has to shift with the vehicle mix.
• Recall and warranty dynamics: recall repairs and warranty-claim visits are often emotionally negative. The customer is inconvenienced, and a review ask in that context reads tone-deaf. The programme's default should bias toward skipping prompts during recall visits and warranty disputes, catching those customers only at their next clean interaction.

Per-rooftop URL routing and dealer-group admin

Dealer groups with multiple rooftops follow the same multi-location URL discipline as other verticals. The specific addition is that many dealerships want the URL to log whether the tap came from sales or service, even if it lands on the same profile. This dual-path routing is what makes per-department measurement possible without splitting the underlying Google profile.

• Subdomain pattern: review.dealergroup.com/rooftop-northside-sales, review.dealergroup.com/rooftop-northside-service, etc. The redirect logs the source path and then 301s to the rooftop's single Google review URL. The chain-owned subdomain survives profile URL changes and OEM-mandated profile renames without card reprints.
• Central admin: one admin panel mapping rooftop and department to Place ID. Growing dealer groups often acquire rooftops; this admin is also the migration workflow for new-acquisition rooftops entering the group.
• OEM franchise agreements: some OEMs specify how the Business Profile is named and categorised. Work within OEM rules; do not invent parallel profiles that confuse the customer or create OEM-compliance exposure. Profile ownership is a frequent pre-sale negotiation point in dealer acquisitions, and the purchase agreement should explicitly cover review-asset transfer.
• Rooftop closure and consolidation: when two rooftops merge, decommission the losing rooftop's redirect so old cards do not drive traffic to a stale profile. Residual cards circulate in customer glove boxes for years; a live redirect to a deprecated profile is worse than a clean 404.
• Fixed operations vs variable operations: service and parts (fixed ops) and sales (variable ops) may belong to different general managers. Align the URL strategy with the GM structure so attribution lands in the right place and neither GM can dispute the other's numbers.
• Multi-brand holdings: groups holding multiple franchises (Toyota, Honda, Ford at a campus) may have three profiles at the same physical address. Each profile needs its own subdomain row and its own redirect; mixing cards between brands at a shared service drive is a common mistake on campuses with shared quick-service lanes.
• Used-car-only stores: some groups operate used-vehicle-only satellite stores under the parent group umbrella. These usually have their own Business Profile and their own routing path, distinct from the flagship new-car rooftop.
• Routing audit: quarterly, tap each rooftop's cards from a distant IP and confirm the destination profile is live, owned by the group, and shows the correct rooftop. DNS and Place ID drift silently breaks 1–2% of cards per year in groups over ten rooftops.

Sales delivery: the high-stakes review moment

The new-car or used-car delivery moment is the strongest review-card opportunity in the entire vertical. It earns a dedicated workflow, premium materials and a carefully sequenced handoff that involves the salesperson, the F&I manager and often a delivery specialist. Most dealers under-invest in this moment because service volume feels more urgent; the dealers who get it right see sales-side reviews that heavily influence local-pack conversion.

• Delivery bay handoff: the salesperson walks the customer through the new car's features and hands over the keys. The review card is part of the key handoff kit along with the owner's manual pocket and registration paperwork. Dedicated delivery specialists (a role growing at larger dealer groups) handle this moment specifically and convert noticeably better than multitasking salespeople.
• F&I exit moment: after the finance and insurance paperwork is signed, the F&I manager hands over the folio plus the review card. Conversion is high because the customer has just made a large commitment and the relief-point emotion is strong. The F&I prompt is also a natural compliance-safe moment because there are no incentives or discounts being traded.
• EV-specific delivery: electric-vehicle deliveries take longer (charging app pairing, home-charger discussion, range education). The review prompt fits at the end of the EV walkthrough, after the customer has just been educated for 30–45 minutes. Conversion is disproportionately strong because the customer feels looked-after.
• Post-delivery SMS: 24–48 hours after delivery, a short text with the review URL. Supplements the physical card; captures customers who walked away without tapping. The BDC (Business Development Center) usually owns this motion at group scale.
• Photograph moment: some dealerships take a photo of the customer with the new car and text it with the review prompt. Higher conversion (often 20–30% of deliveries), more production overhead, and the photo itself becomes content the customer shares, creating organic social lift alongside the review.
• Trade-in emotional layer: the sale often involves trading in the customer's previous car, which carries emotional weight. A delivery handoff that acknowledges the trade-in (not just the new car) generates warmer reviews. Train sales staff to mention the trade-in explicitly in the delivery conversation.
• Substrate choice: premium. A plastic reception-style card undermines the six-figure transaction. Metal-look or premium PVC with heavy soft-touch laminate is appropriate. The folio the card sits inside matters almost as much as the card itself. A branded folio lifts perceived quality of the entire delivery experience.
• Script: 'If your buying experience went well, a Google review helps the next customer find us.' Delivered by the salesperson at key handoff and by F&I at folio handoff. Mentions 'buying experience', not 'service', which keeps the sales review separate from service reviews the customer may write later.

Service pickup: the high-volume review moment

Service pickup is where most of the review volume comes from because the interaction repeats several times a year per customer. Getting the prompt right at scale matters. The service-advisor handoff is the single highest-leverage moment, and the dealers who treat it as a trained workflow (rather than an afterthought on a busy Friday) see 3–5× the review velocity of dealers who print cards and hope.

• Service advisor handoff: the advisor walks the customer through the service ticket, takes payment (or routes to cashier), and returns the keys. The review card is part of the key handoff. This is the highest-converting service moment because the advisor is the relationship anchor and the customer is about to drive away satisfied.
• Cashier counter: if the dealership has a separate cashier, a small card or sticker at the counter supplements the advisor handoff. The cashier moment is shorter and less relational, so conversion is lower, but it catches customers whose advisor forgot to mention the card.
• Courtesy shuttle / loaner return: the customer returns a loaner, waits briefly for their car, and is a captive audience. A tabletop stand in this area converts steadily without staff effort. Loaner-return placement is one of the few 'set-and-forget' placements that works reliably.
• Quick-service lane (oil change, tire rotation): many dealers run express lanes separate from the main service drive. These customers have shorter interactions (45 minutes) and do not meet a service advisor. A stand at the quick-service checkout plus a sticker at the express-lane exit catches these visits.
• Post-service text: a short text 2–4 hours after pickup asking for the review. Most effective when the service advisor's photo is in the message. Open rates for service-advisor-named texts run 50–70% versus 25–40% for generic texts.
• Mobile service visits: dealers offering mobile service (technician visits the customer's home or office) have a different prompt architecture. The technician hands over a card at the end of the visit along with the paperwork. Conversion is very strong because the customer just received white-glove service at home.
• Substrate choice: mid-range. Service pickup runs higher volume than sales delivery, so the cost has to support the refresh cadence. Standard PVC with a durable laminate is the workhorse; upgrade the advisor-handed card, keep the waiting-lounge and cashier placements at baseline spec.
• Script: 'If service went well today, a Google review helps us out.' Shorter than the sales script because the interaction is shorter. Avoid prompts during warranty-claim disputes or recall repairs where the customer is inconvenienced; those are not review moments.

Separating sales and service in the measurement layer

Sales and service reviews land on the same Google Business Profile, but a dealer group needs to know whether sales or service is driving volume. The routing layer is what makes this possible, and the reporting infrastructure built on top of it is what turns the review programme from a marketing expense into a measurable operations layer.

• Source tagging in the redirect: the sales URL and the service URL hit the same redirect endpoint, which logs which path triggered the tap before forwarding to Google. The log captures rooftop, department, timestamp, and optionally which staff member's card was tapped (if the card carries a staff parameter).
• Dealer management system (DMS) integration: match review taps against the DMS customer record so the group knows whether the reviewer just bought a car, just had service, or both. CDK, Reynolds and Reynolds, Dealertrack and Auto/Mate all expose APIs that support this matching if the group's IT team prioritises the integration.
• Reporting: weekly report per rooftop showing review velocity by source. Use this to coach sales teams or fixed-ops teams separately. Monthly roll-up at group level for the dealer principal; quarterly review against OEM CSI/SSI trends.
• Google review copy analysis: most reviews mention either the salesperson's name or the service advisor's name. A simple NLP scan of review text classifies reviews even without the URL routing, and dealers who run this analysis catch naming patterns that the redirect data cannot show (most-named advisor, most-praised sales specialty).
• OEM reporting: many manufacturers now require dealers to report customer experience metrics tied to reviews. The per-source routing makes this reporting cleaner and defensible; dealers who rely on guesswork tend to under-report sales-driven reviews (which are often longer and harder to classify with simple rules).
• Advisor-level leaderboards: with staff-parameter routing, the group can maintain per-advisor tap leaderboards. Publish monthly at each rooftop; pair with non-cash recognition. Trailing advisors often benefit more from coaching on the handoff moment than from motivation alone. The leaderboard identifies who needs help.
• Review-volume-to-CSI correlation: over time, pair the group's Google review velocity with OEM CSI scores. Rooftops where the two diverge (high CSI, low review velocity) are under-prompting; rooftops where they converge are running the programme correctly. The divergence analysis is one of the most useful KPIs a dealer principal can add.
• Response-time metric: track how quickly the group responds to each review (goal: under 24 hours). Fast, thoughtful responses lift the profile's perceived attentiveness and correlate with future review volume. Centralise responses to a small team trained in both the sales and service voice.

Format choice by department and surface

Each dealership department needs a format tailored to its physical layout and customer flow. A single universal card almost always underserves at least one department. The cost of running five different formats across a rooftop is tiny compared with the review volume the right placement unlocks.

• Sales showroom: premium handheld card, held by sales and F&I. Not placed on showroom furniture. It gets lost in the showroom's visual noise and competes with OEM brochures, brand displays and colour-swatch kits. Keep it in the salesperson's hand or in the delivery folio.
• Delivery bay: a branded folio with the review card included. The folio dignifies the card and keeps it with the paperwork the customer takes home. A folio costs 3–5× a standalone card but keeps the card in rotation as the customer refers to the paperwork weeks later.
• F&I office: desk card or small stand at the F&I manager's desk. The F&I conversation is the last room before delivery; a card on the desk that the manager reaches for at folio handoff fits naturally.
• Service drive-through: small NFC sticker on the service advisor's desk or a stand at waiting-area eye-level. Customers may drop off and rush; the prompt has to catch them on return. Desk-level placement converts better than wall-mounted signage because the advisor can gesture to it during the handoff.
• Service waiting lounge: tabletop card or stand. The customer is a captive audience for 30–60 minutes; the prompt competes with WiFi, coffee and phone use. Placement near the coffee station works well because the customer physically approaches that area.
• Loaner return area: tabletop stand. The customer waits briefly; the placement converts steadily without any staff involvement.
• Cashier counter: small stand or sticker. Transactional moment, short dwell, works as supplement to the advisor handoff. The cashier should not deliver a verbal prompt (that is the service advisor's job) but the sticker catches customers whose advisor handoff was rushed.
• Quick-service exit: sticker on the payment kiosk or tabletop card at the service-writer stand for express-lane customers. These customers do not meet a traditional service advisor, so self-serve placement is the only prompt they will see.

DMS, CRM and OEM reporting integrations — technical hooks for dealership review infrastructure

A dealership review programme that lives only on printed cards leaves most of its potential on the table. The DMS holds the transaction record, the CRM holds the customer contact chain, and the OEM reporting system holds the scoring that ties to bonuses. Wiring the review redirect into these three systems is what turns reviews into coachable per-advisor, per-salesperson data and what lets the dealer principal see the programme in the same dashboards that drive operational decisions.

• CDK Drive integration: CDK's Fortellis API marketplace exposes RO (repair order) and deal-close events. A nightly batch or near-real-time webhook pulls closed ROs and delivery events, matches them against review redirect logs by phone number or VIN, and flags matched reviews in the CDK customer record. Fortellis requires a developer account and a signed API key; typical setup is two weeks of joint work between the group's IT team and a certified Fortellis developer.
• Reynolds and Reynolds ERA-IGNITE and Focus: Reynolds' Certified Interface licensing controls third-party data access. The ReynoldsCertified programme requires the developer partner to carry a licence (many review vendors do not), so dealer groups on Reynolds often build a thin middleware that reads the nightly CSV extract rather than paying for a full Certified Interface. The CSV export includes RO close time, advisor ID and customer phone, which is enough to match against review logs.
• Dealertrack DMS: Dealertrack exposes the DealTrack OpenTrack API with RESTful endpoints for service and sales events. OAuth 2.0 with a dealer-scoped client credential. The integration is lighter-weight than CDK or Reynolds because Dealertrack's API surface is smaller and more modern.
• Auto/Mate and PBS DMS: smaller dealer groups often run Auto/Mate or PBS. Both support nightly SFTP or scheduled REST exports; neither has the deep event catalogue of the big three. The programme typically runs on matched-timestamp logic against the SFTP extract, with a 24-hour lag.
• CRM integrations: VinSolutions, DealerSocket, Elead, ProMax: these CRMs drive the BDC's SMS/email follow-up motion. VinSolutions' Automotive CRM API, DealerSocket's RevenueRadar API and Elead's DealerCRM REST all support post-visit message triggers. The BDC template embeds the per-rooftop review URL; the CRM logs the message status (sent, delivered, clicked) alongside the customer record.
• OEM reporting: Toyota TDMS, Ford FSDR, GM DSPP, Stellantis DealerCONNECT: OEMs increasingly ingest third-party review metrics alongside their own CSI/SSI surveys. Stellantis DealerCONNECT, for instance, includes a Digital Reputation Module that pulls Google review volumes and star trajectories; the dealer must enable the feed and grant read access from the group's Google Business Profile.
• Google Business Profile API: the profile API (mybusiness.googleapis.com/v1) exposes review read and respond endpoints. Most groups run a daily pull that caches reviews into the group's central reporting warehouse (Snowflake, BigQuery or a Postgres data mart). This cache feeds dashboards and the response-time SLA measurement; it also allows sentiment and topic modelling on review text, which the Business Profile UI does not surface.
• Data-privacy layering: matching phone numbers across DMS, CRM and review redirect logs qualifies as CCPA/CPRA personal-information processing in California. Run the match through a hashed-phone-number key (SHA-256 of the E.164-normalised number) rather than raw phone numbers, and retain the match in a warehouse-only table that customer-facing staff cannot query directly.

OEM CSI/SSI programme interplay and review-gating compliance for dealerships

Dealership review programmes sit at the intersection of OEM-mandated scoring, FTC endorsement rules, and Google's own review-gating policy. Most dealer principals focus on CSI and SSI because those tie to bonuses; most review vendors focus on Google star counts because those tie to local-pack ranking. Running both systems without a compliance framework exposes the group to OEM chargebacks, FTC enforcement action and Google profile de-indexing. The interplay rules are not obvious and need explicit programme governance.

• Toyota CSI: Toyota Dealer Management System (TDMS) scores service CSI monthly with a threshold typically around 97+ for Executive Board bonus eligibility at Toyota Motor Sales USA. The CSI survey is fielded independently of Google reviews; the two do not replace each other, but a dealer with strong Google reviews and weak CSI has a handoff-consistency problem worth investigating.
• Honda SSI: Honda's Sales Satisfaction Index ranks dealers within zone and nationally, with top-decile performers eligible for Master Circle and President's Awards. Honda does not mandate Google review volume but increasingly tracks it as a secondary indicator; SSI and Google review trajectories should trend together for dealer credibility.
• Ford Blue Oval Certified: Ford's CX certification programme requires dealers to meet specific customer-experience thresholds across CSI, SSI and digital reputation. Ford FSDR (Ford Sales and Service Data Reporting) now includes Google-review-velocity inputs for certified dealers.
• GM Dealer Standards for Performance Program (DSPP): GM's stair-step programme includes CSI, SSI and — since 2024 — digital reputation metrics drawn from Google, Cars.com and DealerRater. Dealers receive per-store digital reputation scorecards monthly.
• Stellantis Voice of the Customer: Stellantis runs CSI/SSI under its Voice of the Customer (VOC) framework. The VOC dashboard in DealerCONNECT now pulls public review data alongside VOC survey responses; low VOC and high Google scores trigger investigation for possible review gating or survey manipulation.
• FTC Endorsement Guides (16 CFR 255): FTC updates effective 2023 tightened disclosure rules on incentivised reviews, fake reviews and review gating. Dealers who offer gift cards, service discounts or entry into raffles in exchange for reviews are in FTC-enforcement territory. The revised rules authorise civil penalties up to $51,744 per violation (as adjusted for inflation through 2026); the FTC has brought enforcement actions against small-business operators in the $50K-$500K range.
• Review gating via SMS pre-screening: the common vendor pattern of 'text Yes if you had a great experience, we'll send you the review link' is technically review gating and violates both FTC guidance and Google's Prohibited Content policy. Google has de-indexed Business Profiles for this pattern. Replace it with a universal post-visit prompt that links to the Google review regardless of the customer's satisfaction, and handle dissatisfied-customer escalation through a separate private channel.
• State AG enforcement: New York, California and Washington Attorneys General have brought actions against review-manipulation schemes in automotive retail. New York AG vs Lifestyle Lift (2009) established the public-deception precedent; California AG has brought similar actions against marketing vendors operating in the automotive and dental verticals.
• OEM compliance audits: OEMs periodically audit dealers suspected of review manipulation. Audit signals include sudden review-velocity spikes inconsistent with transaction volume, clustered reviews from the same IP range, and review text with AI-generated patterns. Groups running a clean programme should document the workflow (card-only prompt, no gating, no incentive trade) to defend against audit triggers.

Per-rooftop launch checklist — 10 items before the cards arrive at the store

The checklist below is the structured version of what experienced dealer-group operations leads run through before the review-card programme goes live at a new rooftop. Each item is a typical failure mode we have seen at multiple groups; running through the list at a 30-minute pre-launch meeting catches 80% of the issues that would otherwise surface in the first month.

• Per-rooftop Google Business Profile claimed and verified, with administrative access mapped to a named manager who is not the franchisee owner personally (so transitions do not lose access). Place ID captured in the central admin spreadsheet.
• Sales and service URL paths configured in the central redirect: review.dealergroup.com/rooftop-X-sales and review.dealergroup.com/rooftop-X-service, both 301-redirecting to the rooftop's single Google review URL with ?src= tagging for attribution.
• DMS integration tested: CDK Drive, Reynolds and Reynolds, Dealertrack or Auto/Mate webhook fires on RO-close and deal-close events; phone-number hash matches against review-redirect logs within 24 hours.
• Sales delivery folio printed and stocked in the F&I office: branded folio plus 50-100 review cards plus the staff script printed on a laminated insert.
• Service drive cards stocked at every advisor desk plus a backup countertop stand in the waiting lounge and a sticker at the cashier counter (if separate cashier).
• BDC SMS templates updated: 24-48 hour post-delivery and post-service text including the per-source URL and the customer's salesperson or service-advisor name.
• Quick-service-lane and loaner-return placements specified: tabletop stand at the express-lane checkout, sticker on the loaner-return waiting area.
• OEM CSI/SSI score baseline captured for the previous quarter: required to defend the programme if the brand-marketing team or OEM rep questions whether reviews are pulling resources from the survey-driven scoring.
• Recall and warranty-dispute prompt-suppression rule documented: staff knows to skip prompts on recall visits, warranty-claim visits, and any service interaction where the customer has expressed dissatisfaction.
• Pilot exit criteria written before launch: 4x sales-delivery review velocity, 3x service-pickup velocity, no CSI/SSI degradation, no incentive or gating violations in the staff script. Six-week pilot duration covering at least one service-month closeout.

Common dealership programme mistakes — seven failure patterns and their fixes

The patterns below are the ones we see across dealer-group rollouts that under-perform. Each is invisible in the planning document and obvious only after the first quarter of live operation. Memorise them and the rollout review meeting becomes shorter because most diagnoses end up pointing at one of the seven.

• One generic card for sales and service: the most common dealership mistake. Sales delivery is a high-stakes, once-a-decade transaction; service pickup is a frequent, lower-stakes transaction. One generic card fits neither well. Fix: two tailored formats with separate URLs and separate measurement, even though both ultimately route to the same Google profile.
• Service advisor handoff treated as optional: advisors with high RO volume drop the prompt under pressure and review velocity stalls. Fix: prompt is part of the advisor's documented handoff motion, observed in the GM's weekly walk, with monthly per-advisor leaderboards published in the service department.
• Prompts during recall or warranty-dispute visits: the customer is inconvenienced or actively unhappy. The ask reads tone-deaf and damages the relationship for future interactions. Fix: explicit prompt-suppression rule for recall (NHTSA-flagged VINs) and warranty-claim visits; catch these customers at the next clean interaction instead.
• Card placed in the waiting lounge as the primary service prompt: customers in the lounge are absorbed in coffee, WiFi, phones and TV. Conversion is low. Fix: advisor handoff at key return is the highest-converting moment (60-75% of total service reviews); the lounge stand is supplementary.
• Sales delivery without F&I reinforcement: the salesperson mentions the card at key handoff but the F&I manager forgets at folio handoff, so the customer hears the ask once and leaves without acting. Fix: prompt is part of both the salesperson's delivery script and the F&I manager's folio handoff; combined delivery converts 1.5-2x single-deliverer.
• Per-rooftop URL routing broken silently: a profile merger after an OEM rebrand or an acquired-rooftop's Place ID never gets updated in the central admin. Cards keep printing with the wrong URL. Fix: quarterly routing audit, tap-test every rooftop's cards from a different IP.
• BDC follow-up template references the wrong vehicle or wrong advisor: customer ignores the message because the personalisation is wrong. Fix: BDC template is auto-populated from the DMS at message-send time, not maintained manually; verify the merge fields against a sample monthly.

Pilot, measurement and refresh rhythm

Dealership pilots need to test sales and service in parallel at the same rooftop, then scale across the network with a consistent data model. Six-week duration is the minimum because service month-end cycles create operational swings that shorter pilots miss, and model-year-end sales cycles create similar distortions on the sales side.

• Pilot selection: one representative rooftop (mid-volume is ideal, not the group's flagship). Test sales delivery and service pickup in parallel for six weeks. The flagship rooftop often has non-representative staffing and disproportionately senior teams, which makes its pilot results hard to scale to smaller rooftops.
• Metrics: reviews per 100 deliveries (sales), reviews per 100 service ROs (service), and reviews per 100 service visits (for quick-service lanes). Segment by source via the URL routing. Track per-advisor and per-salesperson attribution where possible.
• Exit criteria: sales delivery review velocity lifts to at least 4× baseline; service review velocity lifts to at least 3× baseline; OEM CSI/SSI trajectories hold or improve; no complaints from staff about the prompt cadence. A pilot that meets volume targets but damages CSI is not a successful pilot.
• Replacement cadence: showroom and F&I cards every 6 months because dwell is short and cards stay in the folio. Service department cards every 3 months because service staff handle them dozens of times a day. Loaner-return stands last a year; quick-service-lane stickers need 90-day replacement because of heavy hand traffic.
• Seasonal variation: model-year end (August/September for most OEMs) spikes sales volume, quarter-end sales pushes spike deliveries, and winterisation service volume spikes in October. Print sales folios ahead of the August/September window and service stock ahead of October.
• Rooftop rollout: after the pilot, roll out one rooftop per month. Faster rollouts lose training consistency; slower rollouts lose momentum. Pair each rooftop rollout with a dedicated launch week where a group-level trainer visits and coaches sales and service staff on the handoff.
• Audit: quarterly per-rooftop audit of review velocity by source, card wear and stock levels. Laggard rooftops get coaching before replacement cards. A rooftop whose service velocity trails the group average by more than 30% almost always has a service-advisor handoff problem, not a card problem.
• BDC integration: once rooftops are running, fold the post-delivery SMS and post-service SMS into the BDC's existing call-and-text scripts. Consistent follow-up from the BDC across sales and service adds 20–35% to review volume versus physical cards alone.

FAQ