The FCA CONC Line: The UK Car Dealership WhatsApp Stack That Actually Fits

The five rulebooks a UK car dealership actually meets when it turns on WhatsApp

The day a UK new or used car dealership switches its lead, sales, and after-sales flow onto WhatsApp — through a Business Solution Provider, a DMS integration, or an informal team WhatsApp — five separate rulebooks come into play. The FCA's Consumer Credit sourcebook (CONC) at handbook.fca.org.uk/handbook/CONC/ governs any motor-finance conversation with a customer (from initial quote through pre-contract information to affordability assessment), and the FCA's Consumer Duty overlay at fca.org.uk/firms/consumer-duty sets an additional 'good outcomes' obligation. The Consumer Rights Act 2015 (legislation.gov.uk/ukpga/2015/15) — particularly Section 22's 30-day short-term right to reject — governs what happens when a car does not match the description or fails within the first month. The Motor Ombudsman (themotorombudsman.org) is the CTSI-approved Alternative Dispute Resolution scheme for the automotive sector and its Motor Industry Codes of Practice are the sector-specific standard the ombudsman applies. The Advertising Standards Authority (asa.org.uk) polices used-car advertising through the CAP Code, including price presentation and finance representations. And UK GDPR plus PECR at ico.org.uk/for-organisations/direct-marketing-and-privacy-and-electronic-communications control lead-data handling and any WhatsApp broadcast that constitutes marketing. Every section below picks one of these five threads.

Why 'Respond.io alternative' is the wrong lens for a UK dealership

Respond.io is a solid omnichannel messaging platform — WhatsApp, Instagram DM, Facebook Messenger, SMS, email — built for teams that want a shared inbox and template broadcast across those channels. Pricing scales per user and per active contact.

A UK car dealership does not have that shape of problem in isolation. A dealer's WhatsApp conversation is not just a message — it sits on top of a Dealer Management System (DMS) that holds the stock record, the finance-application status, the DVLA history, the customer file, the compliance log, and the CRM. A WhatsApp reply that ignores the DMS and CRM record creates duplicate work, breaks the audit trail, and — on a finance-related conversation — creates a live FCA CONC issue.

What a UK dealership actually needs sits at the intersection of three tools:

• A Dealer Management System (DMS) and CRM that holds stock, customer, finance, and compliance records. Common UK options: Pinewood, Keyloop (formerly CDK Global International), CDK Global, ProMax, iVendi (finance-integration focused), GForces NetDirector, RTC Automotive Solutions, Autoline.
• A WhatsApp lead-and-service rail that carries first-response, appointment booking, walk-around video sends, finance-status updates, and MOT/service reminders — connected to the DMS/CRM so every conversation lands on the customer record.
• A compliance and record-keeping workflow that keeps CONC pre-contract information, adequate explanations, affordability outcomes, and any finance conversation documented for FCA and Financial Ombudsman Service review.

Respond.io's role narrows to the middle rail — the messaging inbox — sitting alongside (not replacing) the DMS/CRM. Realistic UK-market alternatives on that middle rail:

• PMS + WhatsApp built into the DMS: some UK DMS platforms have first-party WhatsApp integration or a preferred BSP partner. Pinewood, Keyloop, iVendi and others publish current partner lists on their own pages.
• Stand-alone WhatsApp BSPs: WATI, Callbell, 360dialog, Twilio — Meta-approved gateway providers on business.whatsapp.com/partners.
• Automotive-specific comms tools: CitNOW (video-messaging for walk-arounds and workshop updates), Autoconvert, WhatsAuto — automotive-first tools with dealer-tailored templates.

FCA CONC and Consumer Duty: what a WhatsApp finance quote must and must not say

A UK dealership that arranges consumer credit for motor finance — whether directly (a dealer's own finance house) or as a credit broker introducing the customer to a lender — needs FCA authorisation. The activity is 'credit broking' (or 'entering into a regulated credit agreement as lender') under the Financial Services and Markets Act 2000 (Regulated Activities) Order 2001. The FCA's Consumer Credit sourcebook (CONC) at handbook.fca.org.uk/handbook/CONC/ sets the rules.

Core CONC requirements that hit WhatsApp finance conversations:

• Pre-contract information (CONC 4) — before a customer commits to a regulated credit agreement, they must receive prescribed pre-contract information (typically SECCI — Standard European Consumer Credit Information). A WhatsApp thread that names a monthly payment number without any pre-contract information trail is incomplete.
• Adequate explanations (CONC 4.2) — the firm must give the customer an adequate explanation of the credit agreement so they can assess whether it is suited to their needs and financial situation. Explanations that are template-only or that skip the specific implications for the customer fail this test.
• Affordability assessment (CONC 5) — the firm must undertake an assessment of the customer's creditworthiness before entering into or significantly increasing a regulated credit agreement. A WhatsApp exchange that jumps to a soft-search offer without affordability data is an early-stage step, not an approval.
• Financial promotions (CONC 3) — any communication that promotes or invites a credit agreement is a financial promotion and must be clear, fair, and not misleading, with representative APR presentation where relevant. A WhatsApp broadcast that shows a headline monthly figure without the representative example fails CONC 3 and CAP Code Rule 15.

Consumer Duty overlay — the FCA's Consumer Duty (PRIN 2A) at fca.org.uk/firms/consumer-duty requires firms to deliver 'good outcomes' for retail customers across products and services, price and value, consumer understanding, and consumer support. It applies to motor-finance conversations end-to-end.

Where WhatsApp workflows walk into a CONC issue:

• Sales-side templates that lead with monthly payment ('from £199/month') without the representative example.
• 'Get approved in 60 seconds' auto-replies that describe soft-search matching as approval.
• Finance quotes issued via WhatsApp without SECCI or pre-contract information having been sent.
• Chat threads that skip affordability questions and move straight to reservation.
• Handoff points where the WhatsApp thread ends but the finance decision is made off-record — Financial Ombudsman Service can and does request WhatsApp records on a finance complaint.

Safe patterns:

• WhatsApp-side finance conversation is 'first response and hand-off' — the actual quote-and-agreement flow moves into the DMS/CRM and the finance provider's compliant journey.
• Templated messages cleared by the firm's Compliance Officer against the current CONC and CAP Code position.
• Every finance-related WhatsApp thread automatically archived to the customer record for audit.
• Consumer Duty file-review captures WhatsApp evidence, not just the finance-house record.

Consumer Rights Act Section 22, the 30-day short-term right to reject, and the WhatsApp reply that lands you at the Motor Ombudsman

The Consumer Rights Act 2015 Section 22 (legislation.gov.uk/ukpga/2015/15/section/22) gives the buyer of goods a 30-day short-term right to reject where the goods do not conform to the contract (satisfactory quality, fit for purpose, or as described). For a car — new or used — Section 22 is one of the most frequently-exercised statutory rights in the UK consumer economy.

Section 22 mechanics:

• 30 days from delivery (or from the point ownership passes, whichever is later) is the window.
• Buyer's remedy is a full refund (deducting a reasonable amount for use for a very short period is limited by the Act — typically no deduction in the 30-day window).
• After 30 days, the buyer moves to the tiered remedy under Sections 23-24: one attempt at repair or replacement, then further refund with reasonable deduction for use.
• Delivery charges are refundable on rejection of the whole order.
• The buyer does not need to prove the defect was present at delivery for the first six months (a rebuttable presumption applies under Section 19(14)).

Motor Ombudsman route — themotorombudsman.org runs the Chartered Trading Standards Institute (CTSI)-approved Alternative Dispute Resolution scheme for the automotive sector. Its Motor Industry Codes of Practice — the New Car Code, the Vehicle Sales Code, the Service and Repair Code, the Motor Industry Code for Vehicle Warranty Products — set the sector-specific standards. Consumers can bring free complaints against member businesses if the internal dispute-handling has not produced a resolution within eight weeks.

Where WhatsApp workflows walk into a CRA Section 22 issue:

• A WhatsApp reply that says 'that's a manufacturer warranty issue, not our problem' when the buyer is within the 30-day window: a documented refusal that becomes evidence of an unfair contract term or a refusal of a statutory right.
• 'We only accept complaints in writing to our head office': overriding the buyer's chosen contact channel is not permissible; a WhatsApp rejection notice is a valid rejection notice.
• A template that offers a repair when the buyer is within the 30-day window: the buyer's Section 22 right is to a full refund; a repair is Section 23 territory.
• Aggressive save-the-sale tactics on a rejection thread: the CMA and Motor Ombudsman both flag friction-added consumer processes.

Safe patterns:

• Written policy that any WhatsApp complaint within 30 days is treated as a potential Section 22 rejection notice; escalated to the dealership's after-sales manager within a working day.
• Templated acknowledgment that names the buyer's right to reject, the process for return, and the refund timeline (typically 14 days from acceptance of rejection under the Regulations 2013).
• Motor Ombudsman signposting in the acknowledgement — this is a Code of Practice requirement for members, and it demonstrates good faith on any subsequent adjudication.
• WhatsApp thread archived to the customer file for evidence at internal review, Motor Ombudsman adjudication, or Small Claims Court.

DVLA, HPI, and the WhatsApp handover thread every UK dealership creates

Every UK-registered car has a V5C registration certificate (the 'log book') issued by DVLA (gov.uk/dvla). When a dealership sells a car, the V5C ownership transfer is a statutory requirement, and the timing and evidence trail matter. In addition, most reputable UK dealerships run a HPI check (Hire Purchase Investigation, part of CDL Vehicle Information Services) or equivalent (Experian AutoCheck, Cazana, Auto Trader's vehicle check) on every used-car intake — the check reveals outstanding finance, stolen-vehicle registration, insurance write-off category (Cat A/B/S/N), and mileage discrepancy.

Where WhatsApp fits in the handover flow:

• Pre-purchase enquiry: buyer asks about the car's history — dealership can share the HPI check summary (or a sanitised version) via WhatsApp with the buyer's consent to receive.
• Reservation and deposit: the reservation confirmation via WhatsApp should include the terms of the deposit, the reservation period, and cancellation rules. A £99-fully-refundable-if-you-change-your-mind reservation is different from a £500-non-refundable deposit, and a WhatsApp thread that blurs the two creates a Consumer Rights Act issue.
• Handover appointment: WhatsApp is the fastest channel for confirming the appointment, the documentation the buyer needs to bring (driving licence for photo ID, proof of address if finance-required, insurance details), and any last-minute changes.
• V5C transfer: the seller (dealership) completes the 'new keeper' section and returns the relevant part to DVLA — increasingly done online at gov.uk/sell-vehicle-to-motor-trader for trade-in and at gov.uk/tell-dvla-vehicle-been-sold for retail sale.
• After-sale: a WhatsApp thread that includes the buyer's confirmation of receipt is a defensible record of delivery date — which starts the 30-day CRA Section 22 clock.

Compliance discipline:

• WhatsApp messages about vehicle history — HPI results, mileage, past repairs — become part of the pre-contract information. A misstatement here is a Consumer Protection from Unfair Trading Regulations 2008 issue.
• Photos of the car sent via WhatsApp before purchase form part of 'as described' under CRA. If the car delivered is materially different from the photos, that is a Section 22 basis.
• DVLA-related information (V5C reference number, previous keeper count, MOT status) is factual and should reflect the source (gov.uk/check-mot-history for MOT, gov.uk/check-vehicle-tax for tax status).

ASA CAP Code, price presentation, and the WhatsApp broadcast Trading Standards will flag

The Advertising Standards Authority (ASA, asa.org.uk) polices marketing communications in the UK through the Committee of Advertising Practice (CAP) Code. The Code applies to WhatsApp broadcasts and social messages as fully as it applies to press ads and TV — it is medium-neutral. Two Code sections are particularly relevant to used-car advertising:

CAP Code Rule 3 (Misleading advertising) — a WhatsApp broadcast that shows a headline price and then reveals significant additional costs (delivery, admin fee, mandatory pack) at the point of sale is misleading. Total-price presentation is the CAP-safe pattern.

CAP Code Rule 15 (Financial products) — any communication that promotes a credit agreement (including a monthly-payment number) must present the representative example prominently and clearly. A 'from £199/month' broadcast without the representative APR, deposit amount, term, and total amount payable is a CAP Rule 15 breach.

Consumer Protection from Unfair Trading Regulations 2008 — the trader-facing rules that Trading Standards enforce. Misleading actions or omissions in a WhatsApp broadcast trigger these.

Digital Markets, Competition and Consumers Act 2024 (DMCC) — new powers for the CMA and Trading Standards to take direct action on unfair practices; drip-pricing and hidden-fee presentations are named targets under the Act.

Where WhatsApp workflows walk into an ASA or DMCC issue:

• 'FROM £8,995' when the actual price at collection is £9,795 after 'admin' or 'preparation' fees.
• 'From £199/month' broadcasts without representative APR, deposit, term, and total amount payable.
• 'Interest-free' finance messaging when there is a hidden margin or fee elsewhere.
• Broadcasts that misrepresent vehicle condition, mileage, or history.
• Countdown / scarcity messaging ('only one left, decide today') without factual basis.

Safe patterns:

• Total-price broadcast defaults with no unnamed add-on fees at collection.
• Finance-specific messaging cleared through the Compliance Officer with CAP Code Rule 15 checklist.
• Templated messages carry a plain-English CAP-Code-compliant representative example when finance is mentioned.
• Broadcast lists managed through an opted-in WhatsApp Business API, not a manager's personal WhatsApp broadcast.

UK GDPR, PECR, and the WhatsApp lead broadcast that lands you at the ICO

The Privacy and Electronic Communications Regulations 2003 (PECR) govern electronic marketing in the UK, and the ICO's direct-marketing guidance at ico.org.uk/for-organisations/direct-marketing-and-privacy-and-electronic-communications treats WhatsApp as electronic mail for these purposes.

Transactional (no PECR consent required): reservation confirmation, deposit acknowledgement, finance-status update, handover-appointment confirmation, MOT-due reminder for a current customer, service-appointment confirmation, part-arrival notice. Contract-performance basis under Article 6(1)(b) UK GDPR covers these.

Marketing (PECR consent required): 'new stock this week', 'end-of-quarter offers', 'we've received a car like your part-ex', 'winter tyre package', general email-style broadcasts about the dealership. These require either explicit prior consent or the ICO's narrow 'soft opt-in' exception.

Soft opt-in for a UK dealership — the three conditions:

1. Contact was obtained during the sale or negotiation of a similar product.
2. Marketing is for the operator's own similar products (a used-car buyer can be marketed a service pack; a warranty-only customer cannot be marketed for a new car under the same basis without fresh consent).
3. Easy opt-out at data collection AND in every subsequent message.

Patterns that work:

• Separate unticked checkbox at handover for 'WhatsApp offers and new-stock alerts'.
• 'Reply STOP to opt out' text in every marketing message, honoured within a working day.
• Timestamped consent records the ICO can inspect on a Section 55 notice.
• Segmented lists (past buyers of a similar model, service customers, finance customers) with soft-opt-in scope respected.

Patterns that fail:

• Adding every past sales enquiry's WhatsApp number to a blast list.
• Marketing dissimilar products (van dealership marketing a supercar) to the same list.
• WhatsApp Groups for promotional broadcasts — group membership makes customer numbers visible to each other, a separate UK GDPR breach.
• Cross-brand marketing between dealership sites without a fresh consent gate.

Maximum PECR fine: £500,000; UK GDPR-adjacent breaches can trigger the higher £17.5m or 4%-of-turnover ceiling. The ICO's public enforcement database at ico.org.uk/action-weve-taken/enforcement/ lists past decisions relevant to sector operators.

Which UK DMS/CRM platforms actually integrate with WhatsApp Business API

The UK Dealer Management System (DMS) and dealer-CRM market has a mix of established enterprise platforms and specialist tools:

• Keyloop (keyloop.com, formerly CDK Global International) — enterprise DMS with strong UK footprint, particularly at franchise dealer groups. Integrated messaging via partners.
• Pinewood (pinewood.co.uk) — UK-origin DMS, strong at UK independent and mid-scale franchise groups. Publishes current integration partner list.
• CDK Global (cdkglobal.com) — enterprise DMS with UK presence in some franchise groups.
• iVendi (ivendi.com) — UK-origin finance-and-sales platform, deep on FCA-compliant motor-finance flows and integrates with major DMS platforms.
• GForces (gforces.co.uk) — UK-origin digital-retail platform, dealer websites and integrated messaging.
• RTC Automotive Solutions (rtcautomotive.com) — UK-market DMS.
• Autoline (auto-line.com) — UK-market classified-listing and dealer platform.

Automotive-specific comms tools with UK adoption:

• CitNOW (citnow.com) — UK-origin video-messaging for walk-arounds and workshop updates. Widely adopted at UK franchise and independent groups.
• Autoconvert / Autoconvert.io — UK-market lead-conversion messaging.
• WhatsAuto — automotive-first WhatsApp template tooling.

BSP layer: WhatsApp Business API integrations sit on top of Meta and a Business Solution Provider — WATI, Callbell, 360dialog, Twilio, Infobip. Meta's official directory at business.whatsapp.com/partners is the source of truth for approved gateway providers.

What to check on the shortlist:

• First-party WhatsApp integration versus Zapier-style bridge — matters at volume, and matters for audit trail on finance-related conversations.
• DMS-CRM sync — every WhatsApp message that touches a customer record needs to land on the customer file (for CONC, Consumer Duty, and CRA audit).
• Finance-conversation compliance overlay — is the platform aware that a monthly-payment reply triggers CONC 3 and CAP Rule 15?
• CitNOW-style video capability — walk-around video is now a table-stakes lead-conversion tool in used-car retail.
• UK-hosted / data residency — UK GDPR position on the messaging archive.
• BVRLA compliance — dealerships that also lease need BVRLA (bvrla.co.uk) membership standards reflected in the messaging templates.