5 Service-Due Reminder Steps 2026 (Step-by-Step)

To automate chase service-due reminders from RO history is to read closed repair orders for mileage, date, and operation codes, compute the next due service, and run a logged outbound chase until the customer books or opts out. The category decision is which dealer system of record you trust for that history — a DMS, a service CRM, or a scheduler — and whether that system can chase without a BDC agent re-typing the last oil-change date.

TL;DR: CDK Global and Reynolds and Reynolds win when the RO is already their object and you will not fight the DMS. Tekion wins when you want a cloud-native RO. Xtime and myKaarma win when the gap is appointment-making and two-way text, not the accounting ledger. DealerSocket and VinSolutions win when the chase has to live next to sales CRM. Orchestration is a later conversation, after the five steps below actually have a data source.

5 steps that turn RO history into a chase

Step 1 — Pick the RO fields that are allowed to mean “due”

You need a closed date, a mileage (or hours), and an operation or opcode that maps to a service interval. If any of those three is missing on a meaningful share of ROs, stop. A reminder that guesses 5,000 miles from a wash RO will train customers to ignore you.

Write the interval in one place: 5,000 / 7,500 / 10,000 miles or 6 / 12 months, per make and opcode, not in a technician’s head. The chase is only as honest as that table.

Step 2 — Compute next-due once, store it, do not re-invent it in the SMS

Store next_due_date and next_due_miles on the vehicle record. Recompute when a new RO closes. If two departments send two dates, the customer will pick neither.

This is also the step where you suppress sold vehicles, auction units, and customers who opted out. A chase that hits a wholesale unit is not persistence. It is a data leak.

Step 3 — Choose the channel the service lane already answers

Phone, SMS, email, and app push are not interchangeable. If your advisors live in Xtime or myKaarma, the chase should book a slot in that scheduler, not dump a “call us” email into a personal Gmail.

Two-way SMS only counts if the inbound text lands on the vehicle or customer record. A group chat on someone’s phone is not a system.

Step 4 — Chase on a schedule, then stop

A typical pattern is day 0 (due), day 7, day 21, then stop or move to a different offer. Infinite reminders are how you earn spam complaints and a quiet block.

Stop immediately on a new appointment, a new RO, an opt-out, or a sold flag. Stopping is a feature. It is not a lack of hustle.

Step 5 — Log the send, the skip, and the book on the same RO/vehicle

If CSI, a manufacturer audit, or a general manager asks “who was reminded about that 30,000-mile service,” the answer must be a record, not a BDC memory. Skip reasons matter as much as sends: bad mobile number, do-not-contact, already appointed, vehicle sold.

US Tech Automations can be configured, as a proposed capability, to run step 5 as a writeback: take the scheduler’s booked event or the inbound SMS, match it to the vehicle, and close the chase on the DMS record. Prerequisites are DMS or scheduler API access and a named service employee who can correct a mismatched VIN. That is a design, not a live rooftop.

Adjacent work after the chase is not this article. Reviews belong in post-service review collection. Finance paperwork belongs in finance-contract document chase. A broader reminder landscape is in vehicle service reminders for dealerships. A sibling spelling of this chase is service-due reminders from RO history.

Decision criteria for RO-reminder stacks

We scored seven dealer-facing products on whether they can own the five steps, not on whether they can print an RO. Pricing is “contact vendor” unless the product publishes a useful public card; dates below are as of 2026-09-01.

There are about 16,700 franchised U.S. dealerships, according to NADA (checked September 1, 2026). Most of them already paid for a DMS that can theoretically do this; the gap is usually the chase, not the ledger.

Feature matrix

CDK and Reynolds win the “RO is our object” test. Xtime and myKaarma win the “customer can actually book” test. DealerSocket and VinSolutions win the “BDC already lives here” test. Mixing all three without a stop rule is how a customer gets four texts about the same oil change.

The 7 products

CDK Global

CDK is a full dealership DMS covering service, parts, and accounting for a large share of U.S. rooftops. Best fit is a store whose closed ROs already live in CDK and whose service director will not entertain a second ledger. Limitation: the chase layer is often a bolted scheduler or CRM, and implementation is a program, not a weekend. Go-live for anything that touches RO flow is 12–26 weeks. Primary evidence: CDK (checked September 1, 2026).

Disqualify CDK as the reminder product when your actual pain is two-way text and online booking. Keep CDK as the RO source either way.

Reynolds and Reynolds

Reynolds is the other legacy DMS many service lanes still close on. Best fit is a Reynolds store with clean opcodes and a parts/service accounting team that already trusts ERA. Limitation: same gravity as CDK — you do not “add reminders” without touching a heavily customized environment. Implementation is 12–26 weeks for meaningful service-lane change. Primary evidence: Reynolds and Reynolds (checked September 1, 2026).

Pick Reynolds when it is already the truth. Do not pick it to get a modern SMS product. You will still pair it.

Tekion

Tekion is a cloud-native automotive platform meant to replace a patchwork of DMS and CRM. Best fit is a group already on a Tekion journey, or a rooftop willing to treat the RO as a cloud object. Limitation: you do not dip a toe; you migrate. Implementation is 10–20 weeks for service to trust it. Primary evidence: Tekion (checked September 1, 2026).

Tekion wins when the current CDK/Reynolds reminder is a report nobody opens. It loses when the group just needed Xtime on top of a stable DMS.

DealerSocket

DealerSocket (now in the Cox Automotive / Dealertrack orbit depending on the module you own) is a dealer CRM that service and BDC teams use to chase customers. Best fit is a store whose reminder problem is people, not accounting: the RO exists, but nobody systematically texts it. Limitation: RO completeness still depends on the DMS feed. Implementation is 6–14 weeks. Primary evidence: DealerSocket (checked September 1, 2026).

If the DMS feed drops opcodes, DealerSocket will chase garbage politely. Fix the feed first.

VinSolutions

VinSolutions is a Cox Automotive CRM used heavily on the sales side, with service follow-up in many rooftops. Best fit is a BDC that already lives in Vin and wants service-due as another campaign type. Limitation: it is not the RO system of record. Implementation is 6–14 weeks. Primary evidence: VinSolutions (checked September 1, 2026).

VinSolutions wins when sales and service share a customer record. It loses when service advisors will not leave their scheduler.

Xtime

Xtime is a Cox Automotive service-scheduling and customer-communication layer that sits on the DMS. Best fit is a store whose advisors already book in Xtime and whose reminder should become an appointment, not a speech. Limitation: garbage in from the DMS is still garbage out. Implementation is 4–10 weeks. Primary evidence: Xtime (checked September 1, 2026).

Xtime is often the right “chase” buy when CDK or Reynolds already owns the RO. That pairing is normal, not a failure of either product.

myKaarma

myKaarma focuses on payments, two-way text, and customer experience in the service lane. Best fit is a rooftop whose customers already text the store, and whose reminder should ride that thread. Limitation: it is not a DMS; next-due still needs RO history from somewhere. Implementation is 3–8 weeks. Primary evidence: myKaarma (checked September 1, 2026).

myKaarma wins the customer-thread test. Pair it with a DMS. Do not ask it to be the accounting system.

Pricing and TCO

Stacking a DMS, a CRM, and a scheduler is common. Price the stack, not the logo you saw at NADA. A reminder project that requires a DMS replacement is no longer a reminder project.

Key Takeaways

• Five steps: honest RO fields, stored next-due, a channel advisors use, a stop rule, and a log on the vehicle.

• Franchised U.S. dealerships: ~16,700 according to NADA — most already have a DMS; few have a clean chase.

• CDK and Reynolds win as RO sources; Xtime and myKaarma win as booking/text layers; DealerSocket and VinSolutions win as BDC CRMs.

• Do not chase sold units, wholesale units, or opted-out numbers.

• Infinite reminders are a CSI problem, not a persistence trophy.

• If opcodes are junk, fix the RO before you buy another outbound tool.

Who this is for

This explainer is for service directors, BDC managers, and dealer-group ops people who can point at a closed RO and still cannot say when that VIN is due next.

It fits rooftops on CDK, Reynolds, Tekion, or a Cox stack (Xtime, VinSolutions, DealerSocket) where the current chase is a monthly list.

Red flags: skip a new tool if your scheduler already texts due customers from stored next-due; skip it if closed ROs lack opcodes and mileage; skip it if nobody will own stop rules for sold vehicles.

Worked example

A rooftop with 28 technicians closing 1,100 ROs a month at a $465 average RO can map last oil-change date and mileage from the DMS, set a 5,000-mile / 6-month next-due, and treat a customer “next Tuesday at 7” text as Twilio’s com.twilio.messaging.inbound-message.received event (see Twilio Event Streams) so the chase closes when Xtime books the slot. That is 1,100 ROs of history, a $465 reason to ask again, and a 6-month clock that should not live in a service advisor’s notebook.

US Tech Automations can be configured, as a proposed capability, to sit between the DMS export and the Twilio/Xtime layer: compute next-due, send only if the VIN is still in inventory and not appointed, and write the inbound text onto the vehicle. Prerequisites are a DMS extract or API, a sender, and a person who can fix a mismatched mobile number. No live rooftop is claimed here.

Benchmarks

Automotive technician median wage: $47,770 according to the U.S. Bureau of Labor Statistics (May 2023 data). A technician waiting on a bay because the due customer was never asked is that wage sitting idle. The same occupational outlook page put 2022 employment for the job at 779,400 positions, according to BLS, which is why a dirty due-list is not a boutique problem.

Small businesses citing time strain: 44% according to the NFIB 2024 Small Business Economic Trends survey. Independent rooftops feel it as a BDC working a stale list.

US small businesses: 33 million-plus according to the SBA Office of Advocacy (checked September 1, 2026) 2025 Small Business Profile. Most will never buy CDK. A franchised dealer still needs the same five steps.

Workflow-tool ROI inside 12 months: 62% of surveyed small businesses, according to Goldman Sachs (checked September 1, 2026) 10,000 Small Businesses (2024). Treat that as directional self-report, not as your service absorption forecast.

What “clean RO history” means before you buy a chase tool

Pull 100 closed ROs from last month. Count how many have mileage, a usable opcode, and a customer mobile that still matches the vehicle. If fewer than 80 of 100 have all three, you do not have a reminder-software problem. You have an RO-completion problem, and Xtime will not invent the missing opcode.

Then pull 20 sold vehicles and see whether they still appear on the current due list. If they do, your stop rule is already broken, and a new CRM will just text the new owner’s predecessor.

Only after those two counts should you sit in an Xtime or myKaarma demo. Ask them to book from a due record and show the inbound SMS on the vehicle, not in a shared iPhone. Ask CDK or Reynolds to show where next-due is stored so two departments cannot compute two dates.

Service directors who skip this homework buy a second outbound channel and keep the same dirty list. The five steps above are the homework. The vendors are the last mile.

Manufacturer CSI programs will not give you credit for texts that went to sold units or to a driver who is not the customer of record. Log the skip. The log is how you survive the audit, not how you decorate a dashboard.

Frequently Asked Questions

What does “chase from RO history” actually use?

It uses closed repair-order date, mileage, and opcode to compute next-due, then runs outbound contact until the VIN is appointed, repaired, sold, or opted out.

Can CDK or Reynolds do this without Xtime?

They can store history and often next-due; they usually still need a scheduler or text layer if the goal is a booked appointment the advisor will honor.

Why do service texts duplicate sales texts?

Because CRM campaigns and service schedulers both read the customer and neither checks the other’s lock; one vehicle-level stop rule is the fix.

Is Tekion required to modernize reminders?

No. Many rooftops get a clean chase by pairing the current DMS with Xtime or myKaarma. Tekion is a platform change, not a reminder feature.

How do we keep sold vehicles out of the chase?

Suppress on a sold or wholesale flag before send, recompute nightly, and log the skip; do not rely on staff memory.

Should we keep chasing after three no-replies?

No. Stop or change the offer. Infinite reminders train blocks and hurt CSI.

Common mistakes

• Using open ROs instead of closed ROs as history.

• Mapping every opcode to a 5,000-mile oil change.

• Letting sales and service run separate cadences on the same VIN.

• Texting a number that belongs to a driver who is not the customer of record.

• Measuring success as texts sent instead of appointments kept.

• Buying a new DMS to solve a missing stop rule.

When the appointment is booked, close the chase on the vehicle so CDK or Reynolds does not send a fourth text. That writeback is the entire last mile. See US Tech Automations if you later want that step scoped on top of the DMS, and plans if you want it priced. Until the five steps have a data source, stay inside the DMS and scheduler you already own.