Service and MOT reminders that bring cars back to your workshop
We build a workflow that reads service due dates, mileage intervals and declined work from your DMS or shop system, checks MOT due dates from the DVSA MOT history API in the UK, sends reminders by text or email with a booking link, follows up declined recommendations politely and passes lapsed customers to an advisor for a call. A typical build costs $1,000 to $2,500 and takes about four weeks.
The problem
Why service and MOT customers drift away
Service reminders depend on accurate due dates and contact details. Many shops send one reminder, if any, and customers who miss it simply book wherever is convenient.
Declined work is the other leak. A technician recommends brakes or tyres, the customer says "next time", and nobody follows up until the next visit, if there is one. In the UK, MOT reminders compete with the free reminder DVSA offers drivers, so the garage's message needs to be timely and make booking easy.
What we build
What our service reminder software includes
Due list from your system
Service due by date or mileage, inspection or MOT due and declined work, read from the DMS or shop system each night.
MOT due dates from DVSA
For UK garages, MOT expiry checked through the DVSA MOT history API under your own registration.
Reminder sequences
A reminder and up to two follow-ups by text or email, with a booking link or call-back option and stop rules.
Declined-work follow-up
A polite check-in about recommendations the customer postponed, with the technician's notes in plain language.
Lapsed customer list
Customers who did not respond go to an advisor call list, ordered by how overdue they are.
Monthly summary
Reminders sent, bookings made and declined work recovered.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Due list built
Each night the workflow reads due dates and declined work.
-
02
Automated
Reminder sent
Customers get an approved reminder with a booking link.
-
03
Automated
Follow-up
No booking triggers one or two polite follow-ups, then stops.
-
04
Advisor review
Advisor calls
Lapsed customers and questions go to a service advisor.
-
05
Advisor or manager decides
Repair advice
What work a vehicle needs is decided by a technician and explained by the advisor, never by the reminder.
How it behaves
How service reminders behave
What the customer sees
- A reminder when service or MOT is due, with a booking link
- A plain follow-up on work they postponed
- A call from an advisor instead of endless messages
What staff see
- A daily lapsed-customer call list
- Declined work coming back as bookings
- A monthly reminder summary
What the automation does
- Reads due dates and declined work nightly
- Applies channel preferences and opt-outs
- Stops as soon as a booking appears
Edge cases and fallbacks
- Customer books by phone mid-sequence
- The nightly check sees the booking and stops reminders.
- Vehicle sold by the customer
- Advisor marks the record and it is excluded.
- DVSA returns no MOT data
- The reminder uses your own records or goes to the call list.
- Shop system unavailable
- That night's run is skipped and retried, never sent from stale data.
Architecture
Service and MOT reminders at a glance.
- Input
- Logic and services
- Output
- People
- Data
How it flows
- 1 Each night the workflow reads due dates and declined work, and MOT dates for UK vehicles.
- 2 Contact rules apply channel preferences, opt-outs and quiet hours.
- 3 Reminders go out with a booking link, with up to two follow-ups.
- 4 Lapsed customers go to an advisor call list, and every step is logged.
Project planner
How the project runs, phase by phase.
Service, inspection & MOT reminder automation project plan
Typical time to launch: about 4 weeks, then support
-
01
Discovery
2 to 3 days
Systems, due-date data quality, current reminders and booking options.
-
02
Design
2 to 3 days
Sequences, stop rules, declined-work wording and call list format.
-
03
Build
1 to 2 weeks
Data access, DVSA lookup, messages, booking links, call list and log.
-
04
Shadow run
About 1 week
Lists built daily while messages go to a test inbox for advisors to check.
-
05
Launch
1 to 2 days
Start with one reminder type, then add the rest.
-
06
Support
Ongoing
New reminder types and wording.
What it runs on
Real products only, connected through the access each vendor provides. See all integrations
Cost estimate
What it costs, line by line.
-
Discovery and design
Data, sequences and wording.
$200 – $400
-
Build
Due lists, reminders, follow-ups and call list.
$500 – $1,300
-
Integrations
Shop system or DMS, DVSA and messaging.
$150 – $400
-
Testing and shadow run
Daily lists checked by advisors.
$100 – $250
-
Launch and training
Switch-on and walkthrough.
$50 – $150
-
Total project estimate
$1,000 – $2,500
Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. DVSA API registration is free but your own; messaging and n8n are billed to you directly.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- Twilio SMS (US): About $0.0083 per message segment each way plus carrier fees (Twilio's published US pricing).
- n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
What pushes cost up
- Systems without an API, or with integration access that must be requested from the vendor
- Writing data back into your core system rather than only reading from it
- Several locations, brands or very different processes to support
- Custom apps, dashboards or a voice line on top of the workflows
What keeps cost down
- One location and one clear process to start with
- Cloud software with a documented API
- Using tools you already pay for instead of adding new ones
- Approved wording and sample data ready at the start
Privacy and consent
Rules we design for, with the sources.
UK: DVSA MOT history API
Access requires registering with DVSA on behalf of your business; the legacy API was deprecated from 1 September 2025 and keys unused for 90 days are revoked.
Source: documentation.history.mot.api.gov.ukUS: reminders vs marketing texts
Service reminders and promotional offers are treated differently; promotions need prior express written consent and every message honours opt-outs.
Source: www.law.cornell.eduUK: marketing by text and email
Offers to past customers rely on consent or the PECR soft opt-in, with a way to refuse in every message.
Source: www.legislation.gov.ukFree tools
Try these first, free.
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
- 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
- 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
- 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.
How scope stays under control
- Product backlog
- Every feature, fix and question in one prioritised list you can see at any time.
- Acceptance criteria
- Plain-language conditions for "done" on each item, agreed before work starts.
- Change requests
- New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
- User acceptance testing (UAT)
- Before launch your team tests the real workflow against the acceptance criteria and signs off.
Tools we use
Project manager / Scrum master
Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.
Business analyst
Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.
Automation engineer
Builds the n8n workflows, integrations, AI steps and error handling.
Backend developer
Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.
Frontend / mobile developer
Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.
QA engineer
Tests every workflow against the acceptance criteria, including edge cases and failure paths.
DevOps engineer
Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.
Who does what at each phase
- Free call
- Project manager, business analyst
- Understand the problem, check it is worth automating and outline a rough range.
- Discovery
- Business analyst, automation engineer
- Map the current process, systems and data, and agree success measures.
- Design
- Business analyst, automation engineer, backend developer
- Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
- Sprints
- Automation engineer, developers, QA
- Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
- UAT and launch
- QA, DevOps, project manager
- Your team tests and signs off, we switch on, monitor closely and train the team.
- Support
- Automation engineer, DevOps
- Stabilisation window, then optional monthly care with monitoring and changes.
A point of contact
One person who can answer questions and approve decisions, with about an hour a week during the project.
Access
Admin or API access to the systems involved, created as separate accounts with the least access needed.
Sample data
Real but non-sensitive records (or de-identified ones) so we can design and test against reality.
Approved wording
Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.
Vendor agreements
Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.
Time for testing
A few hours from the people who will use the system, for the demos and user acceptance testing.
Working system
Workflows, integrations and any apps running in your accounts, under your keys.
Documentation
Workflow specification, data-flow map, run book and exported workflow files.
Training
A walkthrough for the team and a short recorded video for new starters.
Handover
All access, credentials and code handed over; you can keep us or take it in-house.
Stabilisation window
Fixes for anything that does not meet the agreed acceptance criteria after launch.
Support options after launch
No plan
You run it yourselves after the stabilisation window and contact us when you need a change.
Monthly care
Monitoring, error alerts, small changes and updates each month, with an agreed response time.
Priority care
Faster response times for business-critical workflows and a monthly review call.
How a project moves through our team
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
FAQ
Service, inspection & MOT reminder automation questions, answered.
Your shop system may already send basic reminders. We add what it lacks: multi-step sequences, declined-work follow-up, MOT data from DVSA and an advisor call list.
Yes, for UK garages, using MOT due dates from the DVSA MOT history API under your own registration, plus your booking link.
Short and specific: vehicle, what is due, a booking link and a way to reply. We write the wording with you and keep offers out of pure reminders.
Yes, with a polite check-in that explains the recommendation in plain language. It never pressures or invents urgency.
Shopmonkey has a public API with webhooks, Tekmetric offers API access through an approval process, and dealer DMS service data comes through vendor programmes such as Fortellis. We confirm before quoting.
Reminders sent, bookings from reminders, declined work booked later and lapsed customers recovered by advisors.
Free 20-minute call
Want this for your automotive?
Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.
More for automotive
All servicesDealership & automotive CRM automation
Every website, marketplace, phone and walk-in lead in one dealership CRM pipeline, matched to stock and the DMS, with follow-up tasks, appointment tracking and reports by source and salesperson.
From $1,000 · About 4 weeks Details
Internet lead response & test drive booking
Reply to every internet lead within minutes, day or night, with live stock details, offer test drive slots, collect trade-in photos and pass a warm lead to the salesperson.
From $1,000 · About 3 to 4 weeks Details
Digital vehicle inspection, estimates & progress updates
Turn technician notes and photos into clear estimates customers approve on their phone, send progress updates while the car is in the workshop and log approvals and declines.
From $1,000 · About 4 to 5 weeks Details