How Do I Get My Dealership Service Advisors to Sell Maintenance Plans?

The job the maintenance plan is actually hired to do

Before you touch a pay plan, get honest about what a prepaid maintenance plan is doing for the store. It is not an oil-change discount. It is a retention instrument: it converts a one-time visitor into a customer with prepaid visits sitting on your books, and it converts unpredictable customer-pay traffic into scheduled, forecastable hours. That distinction matters, because it determines who inside the dealership should care about the number and how hard you are allowed to push it.

Three separate departments have a stake. Fixed operations wants the recurring visits, because a customer with prepaid oil changes comes back four to six times over the plan's life instead of drifting to a quick-lube. The sales floor wants it because a customer who keeps returning to service is materially more likely to buy their next vehicle from you. Finance wants it because plan revenue is collected up front and recognized as the services are consumed, which smooths the month. When only fixed ops is scored on plan sales, the other two departments free-ride and nobody defends the plan when it gets squeezed out of a busy Saturday write-up.

Now look at the advisor's actual job, minute by minute, because that is where the plan dies. A service advisor on a busy drive is a queue manager. They are greeting, walking the vehicle, writing the concern, checking warranty and recall status, quoting, calling for approvals, handling the two customers who are already upset about yesterday's job, chasing parts, and cashiering. The maintenance plan pitch is a two-to-four minute conversation that requires the advisor to slow down, explain a multi-visit value proposition, and handle a price objection — at precisely the moment they have three people in line.

So the failure is not motivational. It is structural. The advisor is being asked to spend their scarcest resource, uninterrupted attention at write-up, on the line item that pays them the least per minute. If your pay plan rewards total repair order dollars or ticket volume, you have explicitly priced the plan conversation as the worst use of an advisor's time. They are behaving rationally. Every "our advisors just don't sell plans" complaint I have heard traces back to a comp plan that made not selling plans the smart move.

The fix is to change the price of that two minutes. That means three things, in order: make the plan visible on the scorecard so it exists as a measured behavior, weight it high enough that it competes with the easy ticket, and give the advisor a script and a system prompt so the conversation takes ninety seconds instead of four minutes. Skip any one and the other two underperform. Weight without a script produces anxious advisors who mention the plan badly. A script without weight produces a laminated card nobody reads. Visibility without either produces a report that gets emailed and ignored.

There is also a hiring and role-design angle worth naming. Some stores solve this by splitting the role — a dedicated plan or F&I-style specialist who handles the plan conversation while advisors keep the line moving. That works, particularly in high-volume drives above roughly forty repair orders a day per advisor, but it introduces a handoff and a second commission split. Most single-point stores are better off keeping it with the advisor and buying back the time with a shorter, better-rehearsed pitch and a menu that presents the plan automatically at write-up rather than depending on advisor recall.

How the scorecard fits the RevOps stack

The scorecard is not a spreadsheet exercise — it is a small RevOps pipeline, and it fails at the same places every RevOps pipeline fails: data extraction, definition drift, and the last mile to the human. Treat it that way and it survives; treat it as a report and it goes stale in three weeks.

Start with the source of truth. Your DMS — CDK, Reynolds and Reynolds, Dealertrack, Tekion, whatever the store runs — holds the repair orders, the labor operations, the parts lines, and the advisor of record. Plan sales may live in the DMS, in the plan administrator's portal, or in both with a reconciliation gap between them. That gap is the single most common reason a scorecard loses credibility: an advisor sees a plan they know they sold missing from their number, decides the report is wrong, and stops looking at it. Resolve the plan feed before you publish anything.

From there the flow is straightforward: extract repair-order and plan data on a fixed cadence, normalize it so a "recommended service" means the same thing in every store, calculate per-advisor KPI levels, roll those into a weighted composite, and publish the composite somewhere the advisor sees it without asking. Daily is ideal. Weekly is workable. Monthly is a post-mortem, not a management tool, because by the time an advisor learns they are behind, the pay period is over and the feedback loop is broken.

Note the loop back to the DMS at the bottom. That closure is the whole point. A scorecard that only reports is an accounting artifact; a scorecard whose output changes what an advisor says at write-up tomorrow morning is an operating system. When you are evaluating whether your setup is working, the test is not "is the report accurate" but "did anyone's behavior change on Tuesday because of what they saw Monday."

Definitions deserve more care than most stores give them. "Recommended service close rate" can mean closed lines divided by presented lines, closed dollars divided by presented dollars, or closed repair orders divided by inspected repair orders — and those three numbers can differ by twenty points on the same data. Pick one, write it down, and put the definition next to the number on the display. The same goes for hours per repair order (customer-pay only, or all pay types?) and attach rate (per repair order, or per eligible repair order?). Ambiguous definitions get exploited, not maliciously, but because people optimize whatever the number rewards.

The adjacent-system integrations are where this earns extra leverage. Push the plan-sale event into the CRM so the sales department knows which customers hold active plans — that list is one of the highest-converting sources for a trade-in campaign. Feed the inspection-to-close ratio to the technicians, since a badly written inspection recommendation is unsellable no matter how good the advisor is. Send the plan expiration dates to the BDC so someone is calling those customers before the last prepaid visit is consumed. None of this is exotic; it is the same data plumbing any RevOps function builds around a subscription product, applied to a service drive.

Keep the tooling proportional to the store. A single point with four advisors runs fine on a well-maintained sheet fed by a Monday morning DMS export, provided one named person owns the update. A group above roughly five rooftops needs automated extraction, because manual entry across stores collapses within a quarter and the composite loses its authority the first time a store's numbers are visibly a week stale.

Weighting, pay structure, and the ranges that actually work

Weights are the steering wheel, so set them deliberately and revisit them on a schedule. A workable starting matrix for a service advisor covers seven to nine lines: maintenance plan sales, recommended-service close rate, hours per repair order, tire attach, brake attach, alignment and fluid services, customer-pay ratio, CSI or survey score, and sometimes a readiness or certification line. Each gets a weight, each advisor gets a one-to-five level per line, and the composite is the sum of weight times level.

For maintenance plans specifically, a starting weight in the ten to twenty percent range of the composite is reasonable for a store where plans are an established product. If you are launching a plan or trying to reverse a long slide, a temporary bump into the twenty to twenty-five percent range for a quarter is a legitimate forcing function — just announce the end date up front so it reads as a push, not a permanent re-pricing. Anchor the weight to margin where you can: if the plan carries roughly double the gross of a standalone oil change, weighting it at roughly double is defensible and easy to explain on the drive.

The levels need definitions, not vibes. Write out what a level three looks like on each line and what separates it from a four. For plans, that might be expressed as plans per hundred repair orders, with each level a defined band. The specific bands should come from your own trailing ninety days — set level three at the store's current median so half the room starts in the middle, then set five at roughly the top quartile's performance. Bands pulled from a competitor's store or a vendor's slide deck will be wrong for your traffic mix, your price point, and your customer base.

Pay structure is where the matrix gets teeth, and there are three broad models. The first is a composite-gated spiff: advisors keep their existing commission structure, and a separate bonus — meaningful, not token — unlocks only at a composite threshold. This is the lowest-risk way to start because nobody's base earnings move. The second is component commissions, where each KPI carries its own rate: a lower rate on base labor, a higher rate on plans, a middle rate on recommended services closed. This is more powerful and more disruptive, since it changes take-home pay directly. The third is a tiered composite, where the entire commission rate steps up as the composite crosses defined bands.

Whichever you pick, model it against trailing data before you announce it. Run the last three months of actual performance through the new plan and calculate what each advisor would have earned. If your top two advisors come out materially worse, you have a plan that will cost you your best people, and you need to adjust the weights or the rates before it leaves the room. The rule of thumb worth holding: a comp change should let a strong performer earn more by changing behavior, and should only reduce earnings for someone who refuses to change at all.

Budget for the tooling honestly. A spreadsheet costs a few hours to build and roughly an hour a week to maintain, which is real money in a manager's time and is the cost most stores forget. Sales-scorecard and gamification platforms are typically quoted per user per month, and dealer-group pricing usually requires a conversation with the vendor rather than a published rate. Incentive-compensation platforms are enterprise purchases with implementation effort attached, and they only pencil out when comp administration is already consuming a meaningful share of someone's week across many rooftops. Verify current pricing directly with any vendor before you budget — published tiers move, and dealership-specific pricing frequently differs from the generic per-seat rate.

Do not forget the second-order costs. A plan sale creates a future service obligation, so an aggressive plan push loads your shop with prepaid work at a fixed price you set months ago. If your effective labor rate rises and your plan pricing does not, you have quietly sold tomorrow's capacity at yesterday's rate. Review plan pricing on the same quarterly cadence as the weights, and model the shop-loading effect before you triple the attach rate.

Building the shortlist and running the rollout

Evaluate tools against the method, not the demo. The questions that separate a fit from a expensive dashboard are narrow and answerable in a thirty-minute call.

First: can you define your own KPIs and set your own weights, without vendor services work? If changing a weight requires a support ticket, you have lost the ability to re-aim the drive when a plan promotion drops or a parts margin shifts. That agility is most of the value.

Second: does it read your DMS automatically, and how? Ask specifically which DMS platforms are supported, whether the integration is a certified API or a nightly file drop, what the refresh latency is, and whether the plan administrator feed can be reconciled in the same view. A tool that shows yesterday's numbers at noon is fine; a tool that shows last Thursday's is not.

Third: what does the advisor see, on what screen, without logging in? Advisor-facing visibility is where behavior actually changes. A manager-only dashboard produces manager anxiety and no drive-level movement.

Fourth: can it drive pay, or does someone still export to a spreadsheet on the fifteenth? If the composite does not flow to payroll, the composite is advisory, and advisory numbers lose to whatever the paycheck actually rewards.

Fifth: what happens when someone disputes a number? There should be a drill-down from the composite to the individual repair orders behind it. Without that, the first dispute you cannot resolve on the spot costs the scorecard its credibility permanently.

Run a structured pilot before you commit. Four weeks, one store, the existing pay plan untouched — publish the composite and nothing else. You are testing three things: whether the data is trustworthy, whether the definitions survive contact with the drive, and whether visibility alone moves anything. It usually moves something, which gives you the evidence to argue for the comp change in month two.

Sequence the rollout in that order deliberately. Most stores reach for tooling at step one, which is backwards — you cannot automate a matrix you have not defined, and a vendor will happily configure whatever weights you guess at on the kickoff call. Define, publish, prove, then automate.

Expect resistance, and expect it from your best ticket writer. The advisor who has spent three years optimizing for volume has the most to lose from a rule change and the most credibility on the drive. Bring them in during the weight-setting conversation rather than after. When they can see the arithmetic — that two plans a week under the new structure earns more than the volume bonus they are protecting — the objection usually resolves inside two pay cycles. When they find out at the announcement meeting, it hardens into a months-long problem.

Timeline expectations: with the composite published and the spiff wired, behavior typically starts shifting within two to four weeks, roughly one to two pay periods, because advisors learn quickly which lines carry weight. Durable habit — the pitch happening automatically without a manager standing there — usually takes a further month or two of consistent reinforcement. The first week is the noisiest; some advisors will test the system by maxing one line while ignoring the rest, which is exactly what the composite is designed to expose.

What breaks it, and the adjacent plays worth running

The failure modes are predictable enough to design against.

Too many KPIs. Past roughly eight or nine lines, no advisor can hold the matrix in their head, and it stops functioning as a decision aid. If everything is weighted, nothing is prioritized. Cut to the lines that actually move gross and retention.

Stale data. A scorecard updated erratically teaches people that the number does not matter. Pick a cadence you can genuinely sustain — a reliable Monday 9 a.m. refresh beats an aspirational daily one that slips.

Weights that never move. The matrix is a steering wheel, not a monument. If you have not changed a weight in a year, either your business has not changed or you are not paying attention.

Punitive framing. If the composite is only ever discussed when someone is failing, advisors will hide from it. Use it to recognize the advisor who moved from a two to a four on plans as much as to correct the one stuck at one.

Ignoring the upstream. Advisors cannot sell recommended work that technicians did not document. If your multi-point inspection completion rate is weak, or your inspections come back with vague notes and no photos, the advisor's close rate is capped by something outside their control — and scoring them on it is unfair and demotivating. Fix the inspection quality first, or score the technician on documentation alongside the advisor on close rate.

A few adjacent plays are worth running alongside the scorecard, because they raise the ceiling rather than pushing harder on the same lever.

Menu presentation. If the plan appears automatically on the write-up menu with a price and a benefit line, the advisor is confirming rather than remembering. This single change often outperforms a comp adjustment because it removes the recall burden entirely.

Point-of-sale timing. The plan sells better at a moment when the customer already feels good about the value — commonly at delivery of a first paid service, or at vehicle delivery through the sales department. If your only presentation moment is a busy write-up, you are fighting the worst possible conditions. Test a second presentation point and score both.

Sales-department participation. Plans sold at vehicle delivery convert at a different rate than plans sold on the drive, and they arrive with a customer who has not yet formed a service relationship with anyone else. If your dealership does not present the plan in the sales handoff, that is usually the largest untapped volume in the building.

BDC follow-up. A customer with an expiring plan is a warm renewal conversation, not a cold call. Score the BDC on renewal contacts and the advisor on renewal closes, and you have converted a one-time sale into an actual subscription motion.

The through-line across all of it is that this is a RevOps problem wearing a service-drive costume. You are instrumenting a behavior, attaching it to compensation, closing the loop with data, and iterating the weights as the business changes. The same discipline that makes a sales team hit quota makes a dealership service drive sell maintenance plans — the only real difference is that the pipeline runs through a write-up desk instead of a CRM stage.

Related questions

Should I hire a dedicated maintenance plan seller instead?

Consider it above roughly forty repair orders per advisor per day, where write-up time is genuinely scarce. Below that, a specialist adds a handoff and a commission split for volume the advisors could capture with a shorter script and a menu that presents the plan automatically.

How do I score advisors fairly when they have different traffic mixes?

Score rates, not raw counts. Plans per hundred repair orders, close rate on presented lines, and attach per eligible repair order all normalize for volume differences. Raw totals punish the advisor covering the slow shift and reward whoever gets the Saturday rush.

What if my DMS will not export the data I need?

Start with what it does export — repair order counts, labor hours, parts lines — and score fewer KPIs well rather than many badly. For the plan feed, pull directly from the administrator's portal weekly and reconcile manually until an integration exists.

Does gamification actually help or is it a gimmick?

It helps when the point values mirror the matrix weights. It backfires when they do not — advisors will chase whatever the leaderboard rewards, so a game that pays more points for easy tickets will actively undermine the plan push you are trying to run.

How often should I change the weights?

Review quarterly with leadership; change immediately when a promotion launches or a margin shifts. The advantage of owning your weights is overnight re-aiming — a weight you cannot change without a vendor ticket is a weight that will be wrong for months.

FAQ

What is the single biggest mistake dealerships make here?

Rewarding advisors on total repair order dollars or ticket volume alone. That structure explicitly prices the plan conversation as the worst use of an advisor's time, because it pays nothing for the two to four minutes the pitch costs. The advisor who writes five quick tickets in the time it takes to sell one plan looks like the star, and the plan number stays flat no matter how many meetings you hold about it.

How much weight should maintenance plans carry on the scorecard?

Ten to twenty percent of the composite is a defensible starting range for an established plan, with a temporary bump toward twenty-five percent for a quarter when launching or recovering a plan. Anchor it to relative margin where you can — if the plan carries roughly double the gross of the standalone service, roughly double the weight is easy to explain and easy to defend on the drive.

Will my top ticket writer quit over this?

Not if you model the change against trailing data and bring them into the weight-setting conversation before the announcement. Run their last ninety days through the new structure. If a strong performer can earn more by adding two plans a week, show them that arithmetic directly. If the model shows them earning less no matter what they do, the plan is wrong and needs adjusting before it leaves the room.

How long before behavior actually changes?

Typically two to four weeks — one to two pay periods — for the initial shift, once the composite is published and the spiff is wired to it. Durable habit takes another month or two of consistent reinforcement. Expect the first week to be noisy, with some advisors testing the system by maxing one line while ignoring the others.

Can a small store with three advisors use this?

Yes, and it is often easier. The arithmetic is identical with fewer rows, and a small team can run on a maintained spreadsheet fed by a weekly DMS export, provided one named person owns the update. The constraint is not store size; it is whether someone reliably refreshes the numbers and whether the advisors can see them without asking.

Does the sales department have any role in this?

A significant one. Plans presented at vehicle delivery reach a customer who has not yet formed a service relationship elsewhere, and that is usually the largest untapped volume in the building. If the plan only ever gets presented at a busy service write-up, you are running it under the worst possible conditions and blaming the advisors for the result.

Sources

• https://www.cdkglobal.com/ — CDK Global dealer management systems and fixed-operations software.
• https://www.reyrey.com/ — Reynolds and Reynolds DMS and dealership retailing systems.
• https://www.tekion.com/ — Tekion cloud-native dealer management platform.
• https://www.dealertrack.com/ — Dealertrack DMS and dealership technology.
• https://www.nada.org/ — National Automobile Dealers Association, dealership operations and financial benchmarking.
• https://www.autonews.com/ — Automotive News, dealership fixed-operations and retail coverage.
• https://www.cbt.news/ — CBT News, dealership fixed-ops and service-drive management coverage.
• https://www.jdpower.com/business/automotive — J.D. Power automotive research, including customer service index studies.
• https://www.cox2m.com/ — Cox Automotive technology and dealership solutions.
• https://www.quotapath.com/ — QuotaPath commission tracking and quota attainment.

Related on PULSE

• [How Do I Know Where, When, and How Many People to Schedule at Each of My Multi-Unit Retail Locations?](/knowledge/tl0001)
• [How Do I Figure Out How Many People to Schedule Each Day and at What Times for My Single Store?](/knowledge/tl0002)
• [How Do I Know How Many Cooks and Servers to Schedule Each Shift at My Pizza Restaurant?](/knowledge/tl0003)
• [How Many Salespeople Should I Schedule Each Day on My Furniture Store Floor?](/knowledge/tl0004)
• [How Do I Decide How Many Reps to Schedule at Each Store in My Mattress Retail Chain?](/knowledge/tl0005)