Case Study

Case Study: Car Dealership Lead & Service Automation

We built a connected set of automations for a car dealership with a service department: a cleaner CRM pipeline fed by every lead source, internet lead response with test drive booking, service and inspection reminders with declined-work follow-up, digital inspection estimates approved by phone, and warranty claim pre-checks with recall outreach. Salespeople get warm leads, advisors spend less time on status calls and the warranty administrator sees gaps before claims go out.

Business type
Car dealership with sales, service and parts departments
Team involved
Dealer principal, sales manager, BDC, service advisors, technicians, warranty administrator
Systems connected
DMS, dealer CRM, inspection tool, stock feed, Twilio, n8n
Delivery
Scrum, 1-week sprints, about 8 weeks to full launch

The challenge

Where the practice started

Leads from marketplaces arrived as plain emails, phone-ups were rarely logged and duplicates piled up between the CRM and DMS. Weekend leads often waited until Monday.

Service reminders went out once, declined work was never followed up and advisors spent hours on "is my car ready?" calls.

Advisors rewrote technician notes into estimates by hand, and approvals were recorded inconsistently.

Warranty claims were checked by hand and rejections were reworked slowly; recall outreach relied on manufacturer letters.

Goals

What the project had to change

  • Every lead in the CRM with a source, vehicle and next step.
  • Every internet lead answered within minutes with real stock details.
  • Service reminders and declined-work follow-up that run on their own.
  • Clear estimates approved by phone, with a record of every decision.
  • Warranty gaps caught before submission and recall customers invited to book.

What we built

What we built, as one connected system.

01

CRM pipeline clean-up

We normalised every lead source into ADF, logged phone-ups, matched leads to stock and DMS customers, and set cadences with manager escalation and weekly reports.

Service details
02

Internet lead response

Leads get a specific reply within minutes with live stock details and test drive slots, trade-in photos are collected, and salespeople receive warm hand-offs.

Service details
03

Service reminders

Nightly due lists from the DMS, reminder sequences with booking links, declined-work check-ins and a lapsed-customer call list for advisors.

Service details
04

Inspection estimates and updates

Technician notes and photos become plain-language draft estimates the advisor edits; customers approve by phone and get progress updates.

Service details
05

Warranty checks and recalls

Claims are checked against the administrator's requirement lists before submission, rejections are summarised, and customer vehicles are matched to open recalls for outreach.

Service details

Architecture

How the dealership's workflows connect

Lead sources Web, ADF, calls DMS Stock, ROs, service Recall data NHTSA API n8n Five workflows AI steps Drafts, checks Dealer CRM Leads, tasks Texts and emails Twilio, email Sales and BDC Warm leads Service team Advisors, warranty Log and reports Weekly summary
  • Input
  • Logic and services
  • AI step
  • Data
  • Output
  • People

How it flows

  1. 1 Lead sources, the DMS and public recall data feed one n8n instance.
  2. 2 Five workflows update the CRM, send texts and emails, and use AI to draft estimates and check claims.
  3. 3 Sales and BDC work warm leads; advisors and the warranty administrator work their own lists.
  4. 4 Every step is logged, with a weekly summary of the agreed measures.

How it behaves

How the system behaves day to day

What each person sees and what runs in the background, including what happens when something goes wrong.

What customers see

  • A specific reply within minutes about the car they asked about
  • Service reminders with a booking link
  • Clear estimates with photos to approve by phone
  • Progress updates until collection
  • Plain recall notices with booking links

What staff see

  • Warm leads with stock and customer history
  • Draft estimates and recorded approvals
  • Lapsed-customer call lists and warranty gap alerts

What the automation does

  • Replies, reminds, drafts and checks on schedule
  • Applies consent and opt-outs across every workflow
  • Logs every step and alerts managers on failures

Edge cases and fallbacks

A buyer asks about finance
Handed to the business manager; no automated finance answer.
Extra work found mid-repair
A new estimate goes out for approval before work continues.
A customer opts out in one workflow
One shared opt-out list stops texts from every workflow.
The DMS is unreachable overnight
Reminder runs are skipped and retried, never sent from stale data.
Twilio or n8n has an outage
Leads stay in the CRM with call tasks and managers are alerted.

Integrations

What we connected

All integrations

CDK Global (Fortellis)

Dealer management system

Customers, vehicles, repair orders and service data.

APIs through the Fortellis marketplace, priced by consumption; access approved by CDK.

VinSolutions

Dealer CRM

Leads, tasks and customer records.

ADF lead delivery; deeper API access confirmed per project.

ADF XML lead feeds

Lead standard

Website, marketplace and OEM leads in a format dealer CRMs accept.

Auto-lead Data Format XML by email or HTTP post.

NHTSA recalls API

Vehicle data (US)

Open recall campaigns by make, model and year.

NHTSA public API, free and without a key.

Twilio

SMS and voice

Lead replies, reminders, approvals, updates and the AI agent's phone line.

Twilio Programmable Messaging and Voice APIs.

Google Business Profile

Reviews and local search

Review requests after sale or service and booking links.

Google Business Profile settings and APIs.

n8n

Automation platform

Runs the workflows, self-hosted or on n8n Cloud.

Your own n8n instance; we hand over every workflow.

How we delivered it

Week by week, one workflow at a time.

Each workflow went live on its own after a shadow run and a sprint demo, so the team got used to one change before the next.

Delivery timeline

Typical time to launch: about 8 weeks, then support

  1. 01

    Discovery

    Week 1

    We sat with sales, BDC, service and warranty staff, mapped each flow and agreed consent rules, data flows and Safeguards Rule vendor documentation.

  2. 02

    Design and access

    Week 2

    ADF mapping, cadences, templates approved by managers, DMS API access through the vendor programme, Twilio number and A2P 10DLC registration.

  3. 03

    Sprint 1: CRM pipeline

    Week 3

    Built lead normalisation, matching and cadences; shadow-ran against the existing setup.

  4. 04

    Sprint 2: lead response

    Week 4

    The pipeline went live. Built instant replies, stock lookup, test drive booking and trade-in collection.

  5. 05

    Sprint 3: reminders

    Week 5

    Lead response went live. Built service reminders, declined-work follow-up and the call list.

  6. 06

    Sprint 4: inspections

    Week 6

    Reminders went live for one type. Built estimate drafting, phone approvals and progress updates.

  7. 07

    Sprint 5: warranty and recalls

    Week 7

    Approvals went live. Built claim pre-checks, rejection summaries and recall matching.

  8. 08

    UAT and handover

    Week 8

    Each department ran acceptance tests; we switched everything on, handed over the run book and trained the teams.

  9. 09

    Support

    Ongoing

    Weekly check-ins during stabilisation, then monthly care.

Who does what

What the team does, and what automation does.

Automation does

  • Normalises and matches leads and runs cadences
  • Replies to internet leads and books test drives
  • Sends service reminders and declined-work check-ins
  • Drafts estimates and sends approval links and updates
  • Pre-checks warranty claims and matches recalls

The team does

  • Salespeople and BDC work warm leads and confirm appointments
  • Advisors edit estimates and call lapsed customers
  • The warranty administrator fixes gaps and submits claims
  • Managers review weekly reports

Advisor or manager decides

  • Sets vehicle prices and trade-in values
  • Handles finance through authorised staff only
  • Decides repair recommendations with the technician
  • Approves advertised offers

Compliance handled

Privacy, consent and safety, built in.

Safeguards Rule vendor oversight

Every vendor that touches customer data was documented within the dealer's written information security program.

Source: www.law.cornell.edu

Texting rules in the US

Promotional texts only to customers with prior express written consent; opt-outs honoured across every workflow.

Source: www.law.cornell.edu

A2P 10DLC registration

The sending number was registered before any texts went out.

Source: www.twilio.com

Written estimates and approvals

Every approval is recorded against the repair order, in line with written-estimate rules such as California's.

Source: www.bar.ca.gov

No finance or pricing by automation

Finance, trade-in values and negotiation are handled by authorised staff only.

Outcomes

What changed for the practice

  • Every lead lands in the CRM with a source, vehicle and next step.
  • Internet leads get a specific reply within minutes, day or night.
  • Service reminders and declined-work follow-ups go out on their own, and lapsed customers reach an advisor.
  • Customers approve clear estimates by phone, and every decision is recorded.
  • Warranty gaps are caught before submission, and recall customers are invited to book.

What we track

The measures the practice watches.

Lead response

Time to first reply and appointment set rate by source.

Show and close

Show rate and close rate for internet leads.

Service retention

Bookings from reminders and declined work booked later.

Approval speed

Time from inspection to approval and approval rate per item.

Warranty recovery

First-time rejection rate and recovery after resubmission.

Cost estimate

What a project like this costs

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Process mapping, data flows, wording and the backlog for all five workflows.

    $1,000 – $2,000

  • CRM pipeline module

    Normalisation, matching, cadences and reports.

    $700 – $1,600

  • Lead response module

    Replies, stock lookup, booking and trade-in collection.

    $500 – $1,300

  • Reminders module

    Due lists, sequences, declined work and call list.

    $700 – $1,700

  • Inspection module

    Estimate drafting, approvals and updates.

    $800 – $2,000

  • Warranty and recall module

    Claim checks, summaries and recall outreach.

    $800 – $2,000

  • Integrations

    DMS, CRM, inspection tool and Twilio.

    $200 – $400

  • Testing, UAT and launch

    QA, user acceptance testing, launch and training.

    $300 – $1,500

  • Total project estimate

    $5,000 – $12,500

Optional monthly care after launch is quoted with your proposal. Typical range for a project of this scope: five workflows at our fixed per-workflow range. Every dealer gets its own fixed quote after a free call.

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, and about $1.15 a month per local number (Twilio's published US pricing), plus A2P 10DLC fees.
  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
  • DMS API access: Billed by the DMS vendor under its programme.
  • AI usage: Pay-per-use model fees, usually small at dealership volumes.

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
Get a fixed quote

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 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. 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. 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. 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

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

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

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

Free 20-minute call

Want this built 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.

Book a free 20-minute call