The first 60 seconds
Before a single car is discussed, before a job is booked, the customer has already formed a judgement — from how they were greeted, or whether the phone was even answered. This is the moment the experience is won or lost, and it applies to every customer: sales, service, parts, enquiry, walk-in. Get this wrong and nothing downstream recovers it.
ASomeone through the door
- Acknowledged within seconds — eye contact, a nod, "I'll be right with you" — even if you can't serve them yet. Being seen is what matters.
- Never left standing unnoticed. A waiting customer with no acknowledgement is the fastest way to sour a visit before it starts.
- Greeted by name where they're expected — a reserved space, a name on a screen, "we've been expecting you."
- Offered a seat and a refreshment. Small, human, and it signals the whole visit will be taken seriously.
- Someone owns them until they're handed over — never passed between people who each assume someone else has it.
BSomeone ringing in
- Answered promptly, within an agreed number of rings, warm and professional — the caller can hear a smile.
- Unanswered calls redirected to a staffed line, never left to ring out or drop to a voicemail nobody checks.
- Callbacks returned — a promised call that never comes is a broken promise the customer remembers.
- The caller's need captured once and routed to the right person, not bounced around the building.
- Any message is owned — logged, passed on and followed up, not left on a sticky note.
What good looks like
Two journeys, side by side — the sales customer and the aftersales customer — because the basics that make them feel valued are the same, even when the steps differ. Neither is the default; both deserve the full treatment.
Stage 1 · Preparation & first contact
SSales
- Enquiry responded to fast, by the customer's preferred channel
- Appointment confirmed ahead of time; details and any offers ready
- Customer greeted by name, space reserved, personal touch
- Stated needs and preferences noted before they arrive
AAftersales
- Booking taken promptly; details, history and campaigns captured once
- Pre-appointment confirmation sent; mobility arranged in advance
- Pre-call made where useful — remind, confirm, pre-empt questions
- Workshop capacity held for the day; nothing left to chance
Stage 2 · The meeting / check-in
SSales
- Listen first — understand what they want, not what's easy to sell
- Reflect their preferences back so they know they've been heard
- Options presented clearly, honestly, at their pace
- Next steps agreed and confirmed, no pressure
AAftersales
- Symptoms consulted on properly — a conversation, not a guess
- Work scope, estimate and payment agreed and understood
- Completion time and contact plan set, in plain language
- Everything summarised and confirmed before they leave
Stage 3 · While we have the customer / car
SSales
- Kept informed at every step — nothing goes quiet
- Promises made are promises kept, to the letter and the timing
- Small details remembered — the name, the reason, the preference
- The extra mile: a coffee, a walkaround, genuine attention
AAftersales
- Health check done and presented honestly, with evidence
- Contact before any additional work — never spend their money unasked
- Updated proactively if timing slips — silence reads as neglect
- Safety-critical (red) work always raised; any decline recorded
Stage 4 · Handover
SSales
- Handover made to feel like an occasion, not a transaction
- Everything promised present and correct
- Car presented properly — clean, ready, at the front
- Clear on what happens next and how to reach you
AAftersales
- Work explained in plain language before the invoice
- Advisory work not done today clearly flagged for next time
- Car returned clean and brought to the front door
- Next service and follow-up confirmed
Stage 5 · Follow-up
SSales
- A genuine check-in after the sale — not just a survey request
- Feedback invited warmly and acted on
- Account-review contact planned through ownership
- The relationship kept warm for the next purchase
AAftersales
- Sample of jobs quality-checked before the customer judges them
- Low scores followed up fast — within the recovery window
- Verbatim read, not just the number
- Did the fix hold? A follow-up where it adds value
Brilliant basics — the ones that fall away when it gets busy
Attention to detail is the discipline underneath all of these. None need a budget or a system — they're the everyday details that should happen without being noted — and they're exactly what slips first under pressure. Written down and owned, they hold.
Site readiness — before anyone arrives
- Customer parking available — sales or service, spaces kept free and obvious, not filled with stock
- Staggered service slots — not twenty customers all arriving at 8am with work to get to
- Technicians ready at opening to take the waiting jobs straight away
- A standby technician or product expert on the floor for questions — the way the best retailers staff a dedicated expert
- Forecourt cars ready to sell: clean, priced, plated, fuelled for a demonstration — charged for EV models
Walk, don't point
- Every customer acknowledged on entering, regardless of department — nobody's "not my customer"
- Never "it's over there" — walk the customer to their destination
- Introduce them by name to the person who'll be helping them
- Comfortable waiting: refreshments, clean facilities, wifi that works
Weather-proofing — think ahead of the forecast
- Snow or ice? The cars we're selling are ice- and snow-free should a customer want to drive one
- Poor weather due and a customer collecting? Park the car in the workshop overnight — nobody de-ices their own new car
- In icy months, courtesy cars inside too, so they can be brought round ready for use
Courtesy cars — checked every night or first thing
- No warning lights, no software update due
- Fuel or charge in it — a customer on their way to work never sets off on empty
- Clean inside and out — it carries your name while they drive it
- One named owner for the daily check (Tab 4)
The valet, explained — and checked
- "Would you like your car cleaned?" means nothing — we know what that looks like; the customer doesn't. Say it plainly: a wash and hoover
- Before collection, check the clean happened — no marks or dirt left from the workshop
- Settings and personal items respected: seat, mirrors and radio as they left them; protective covers removed
Pre-handover — the 24–48 hour check
- Vehicle going out? Check it 24–48 hours before handover, not on the morning
- No warning lights; no software updates due
- All preparation and optional accessories fitted
- Fuelled or charged before valet and handover — not squeezed in after
The booking, priced right
- The price quoted at booking is the price the customer signed up for — full stop
- Say plainly what it includes — and what it doesn't (parts, fluids, MOT, sundries)
- Check it's the same price showing on our system before the customer arrives — not discovered at checkout
- Any additional costs the customer may not be aware of, raised at booking — never on the invoice. Unexpected cost is a top defection driver (Tab 5)
The courtesy car — qualified, not just allocated
- Is the customer actually aware of the courtesy arrangement — and any terms (fuel, excess)?
- Qualify the need, don't assume: manual or automatic? Big or small? Big boot for work kit? Work or personal use?
- EV asked, never assumed: must it be electric to match their car — or must it not be, because they've no charger at home?
- Record the answers so the right car is ready on the day — listening, captured and acted on
The handover: someone's exciting day
What's routine for us is somebody else's exciting day — for many customers, one of the biggest purchases of their life. Make it feel that way:
- →Build the excitement — preview photos and videos as the car is prepared; every request completed before the day
- →Ask what handover they want — paperwork completed beforehand so the day is purely the experience? Quick, or comprehensive? Any specific features to cover?
- →Set the car up as theirs — apps and profile with their approval, favourite radio stations added, everything ready to drive
- →Efficient where it counts — paperwork prepared and marked for signature; the car brought round and ready before they arrive; keys handed over with a personal touch
- →Offer a secondary handover — a follow-up session for the features nobody absorbs on day one, diarised there and then
- →Agree the contact plan — when we'll be in touch, and what it looks like for the customer and for us
- →Introduce a manager at handover — the customer should know who runs the place that just took their money
- →Walk them to service and introduce an advisor by name — their point of contact from day one, and the retention relationship started before they've left the building
Communication
The single biggest decider of how the experience is led. Not the fix, not the price — how well people are kept informed. It works in two directions: with the customer, and internally between the people delivering the service. And there's a balance to strike: too little communication and too much both cause harm, in different ways.
With the customer
Most complaints aren't about the work — they're about the silence around it. The failures are almost always the same short list:
- × Calls not answered, or left to ring out
- × Callbacks promised and never returned
- × Promises made and not kept — a time, a price, a call
- × Going quiet when something changes or slips
- × Surprises at handover — work or costs never mentioned
The fix is unglamorous and total: answer, return, keep the promise, and never let the customer wonder what's happening. Proactive beats reactive every time — the update you give before they have to chase is worth ten given after.
Internally — with the team & stakeholders
Customer-facing communication only works if the communication behind it does. When internal communication breaks down, the customer feels it — even though they never see the cause.
A morning stand-up, a clear handover note, one owner per customer — small disciplines that keep the whole site aligned.
The balance: too little, right, too much
More communication isn't automatically better. Over-communication has its own failure mode — it buries the signal, confuses priorities and dilutes direction. The skill is the right amount, to the right people, at the right time.
Too little
- Customer left wondering
- Team unsure who owns what
- No direction or accountability
- Frustration and dropped balls
- Problems surface too late
The right amount
- Clear, timely, relevant
- One owner, one message
- Proactive, not chased
- Right people, right moment
- Everyone knows the plan
Too much
- Signal lost in the noise
- Priorities blurred
- Direction diluted
- Meeting and message fatigue
- People stop reading it
Email, conversation or meeting? Choose the channel
With the sheer volume of meetings and emails in a working day, it's easy to lose the wood for the trees. Most communication failures aren't about the message — they're about the channel. Before you write the email, ask: could I go and speak to this person instead?
Walk over / pick up the phone
- The query needs a back-and-forth
- It could be misread in writing
- There's frustration or emotion in it
- Two minutes of talking beats ten of typing
- You need the answer now
Send the email
- A record is genuinely needed
- Several people need identical detail
- It's reference material, not a question
- It's non-urgent and can queue
- Attachments or data must travel with it
Call the meeting
- Genuine alignment across several people
- A decision that needs live debate
- A set operating cadence (e.g. daily prep)
- Not: anything a conversation or a shared note could settle
A working rule: if an email chain reaches three replies, stand up and go and talk. The chain is telling you it was the wrong channel.
Meeting discipline
Meetings are fundamental to alignment — and they quietly lose their importance the day they become a checklist. A status read-around that nobody needed to attend isn't alignment; it's a shared note with chairs.
The senior-level questions worth asking before anything lands in a diary: do we actually need a meeting about this? Could a direct conversation with the two stakeholders who matter settle it faster and better? What decision or alignment will the meeting produce — and if the answer is "none," it's a message, not a meeting.
And the manager's mirror: what are we asking of our teams? Every meeting we call and every email we generate is time taken from customers. Between departments, are we bombarding each other — volume dressed up as diligence? The daily preparation meeting (Tab 4) exists precisely so a dozen smaller check-ins don't have to.
When it goes wrong internally: accountability, not email
Internal respect isn't tested when things go well — it's tested when they don't. Take the most familiar failure in the building — a vehicle promised out that was never properly planned — and follow the ripple:
Count the cost of one piece of poor planning: the handover customer, the diagnosis customer whose fix just stalled, every customer whose prepped car slipped down the queue, and every department — admin, prep, workshop, aftersales, valet — bent out of shape for the day. Not two customers at risk; every department affected, and several customers with them. The most expensive interruptions land on the most skilled people, because they're the ones who can't be substituted.
Who takes accountability? Not as a blame exercise — as a sequence: someone owns the customers first (all of them, immediately: honest communication, a plan, a gesture where warranted), and only then does the root cause get worked — in a conversation, not a thread. Whose planning failed, why, and what changes so it can't repeat. The department that caused it leads the fix; every department that absorbed it is heard, because their day paid for it.
This is the Ownership principle under pressure: the unowned failure, like the unowned task, is the one that never gets fixed. And it's why the daily preparation meeting exists — every one of those interruptions is visible 24–48 hours out to a team that plans together.
Conflict between departments
Frustration between departments is expected — sales and aftersales pull against each other in every dealership on earth. How we deal with it is what's key. And the default is almost always the worst option: the strong-tone email, managers cc'd, grievance on the record. It escalates the temperature, hardens positions, and fixes nothing the customer will ever feel.
Never send the strong email. Fix the customer, have the conversation face to face, log the root cause. If it still needs escalating, escalate the problem and the proposed fix — not the emotion. That's the difference between a complaint and leadership.
A team, not a team of individuals
Ownership: who does what
The unowned task is the one that doesn't happen. "Someone should offer them a coffee" means no one does. Excellence in the basics comes from naming responsibility — so the waiting customer is greeted, the refreshment is offered, the car reaches the front door, and the pre-call is made, every time, because someone owns it.
The daily preparation meeting
The single best tool for making ownership stick is a short, structured daily preparation meeting — ten to fifteen minutes, same time every morning, with every function represented: management, workshop control, service advisors, technicians and parts.
The agenda runs three horizons, and every line has a named owner: yesterday (outstanding actions and customer issues, jobs completed vs carried over and why — parts, time or authority — and the causes of any comebacks, logged for root-cause analysis); today (absences and their effect on hours, first-aid and safety cover confirmed for the day, courtesy cars, collections and deliveries, sales-job urgency, valet resource, hours available to sell, foreseeable problems); and the next 24–48 hours (hours available, MOTs, additional-work calls needed, parts ordered and due, and the same look-ahead for mobility and resource).
That's it. No slides, no minutes beyond the action column — just every owner saying what they own, out loud, in front of the people who depend on it. It's the internal-communication rhythm from Tab 3 made concrete: the customer never sees this meeting, but they feel it in every kept promise that follows.
The cost of getting it wrong
The basics aren't soft. Every enquiry is bought and paid for, and every poor experience has a price — in leads wasted, customers lost and lifetime spend gone elsewhere. The figures below are illustrative — specified by UK automotive leaders for the insights reported, with named third-party studies (Deloitte, Gartner, Medallia, Zendesk) cited where the figure comes directly from them. They are the frame, not your scorecard: your own site figures will vary, so read the direction of travel and enter your own numbers.
Every enquiry costs money — before anyone's sold anything
Speed and communication are the sales channel
Poor aftersales is the #1 named reason customers don't come back
Listening vs hearing: the silent defection
There's a difference between hearing a customer — letting their words pass — and listening: capturing what they said and acting on it. The gap is where loyalty quietly leaks away.
In practice: a customer says they need the car back by three, or prefers a call not a text, or mentioned a noise last visit. Not capturing it — or capturing and ignoring it — tells them they weren't really heard. It rarely produces a complaint. It just produces a customer who doesn't come back, and never says why. Listening, recorded and acted on, is the cheapest loyalty tool there is.
SLAs & Standards
"Good service" is unmeasurable until you define the minimum. Generic, sensible service-level standards for each touchpoint — the floor below which the experience is failing. Defaults to start from; tighten to your own ambition.
First contact & response
| Touchpoint | Standard (default) | Why it matters |
|---|---|---|
| Walk-in acknowledgement | Acknowledged within seconds; never left unnoticed | The first impression the whole visit is judged on |
| Inbound call | Answered within a set number of rings; unanswered redirected to a staffed line | Unanswered calls are the top complaint — and paid-for customers lost |
| Callback | Every promised callback returned, same day where possible | A broken callback promise is remembered |
| Online / lead enquiry | Responded to within minutes where possible; within 1 business day at most | Fast response dramatically lifts conversion |
Preparation & timeliness
| Standard | Default | Why it matters |
|---|---|---|
| Pre-appointment confirmation | Every booking confirmed ahead of time by the customer's channel | Removes uncertainty; reduces no-shows |
| Service pre-call | Made where it adds value — remind, confirm, pre-empt | Preparation the customer feels as professionalism |
| Running late — customer | Customer asked, politely, to let us know if they'll be late | Protects the day's schedule for everyone |
| Running late — us | We respect the customer's time and don't cost them theirs; proactive contact if we'll slip | Their time is as valuable as ours — a two-way courtesy |
| Readiness | Space reserved, name known, car readied in advance | The visit runs itself when prep is owned |
During, handover & recovery
| Standard | Default | Why it matters |
|---|---|---|
| Additional work | Contact and authorisation before any work not booked | Legal and trust line — never crossed |
| Progress update | Proactive contact if timing changes — never go quiet | Silence reads as neglect |
| Promises kept | Every promised time, price or call delivered as stated | Trust is built on kept promises, lost on broken ones |
| Handover | Work explained, invoice clear, car clean and brought to the door | The last minutes shape the memory of the whole visit |
| Low-score / complaint | Followed up within 48 hours; complaint acknowledged within 1 business day, plan within 3 | Fast recovery re-wins customers a slow reply loses |
Numbers left as "a set number" deliberately — set the specific figure to your opening hours, staffing and ambition, then hold to it. A written standard you meet beats an aspirational one you don't.
The Sense-Check
A self-audit you run before the customer judges you. Walk the checklist on a sample of visits, tick honestly, and watch the score. It covers the whole journey — the first 60 seconds, communication, ownership and follow-through — not just the workshop.
Visit-level sense-check
Recognised Frameworks
The established models behind the practical steps — generic, methodology-only, so you can explain why a standard exists, not just enforce it.
The service core process
The industry-standard spine of a service visit — every touchpoint hangs off one of these stages.
First-time fix & repeat repairs
First-time fix (FTF) — jobs resolved on the first visit with no return-to-workshop — is one of the biggest hidden cost drivers there is. Its inverse, the repeat repair, costs far more than the redo.
The discipline behind a high FTF: diagnose to root cause, follow the guided fault-finding process fully, use technical bulletins where they apply, and quality-check before handover.
Customer satisfaction measurement
| Overall satisfaction | The headline score across a touchpoint (sales, used, aftersales) |
| Verbatim comments | The free-text — what to fix. Worth more than the number alone |
| Urgent-alert follow-up | Low scores flagged for fast callback — the recovery window |
| Theme analysis | Grouping comments to see recurring issues across many responses |
| Driver analysis | Which factors most move the score — where to spend effort |
Where loyal customers come from
Working with AI: the 4Ds
AI is now part of how dealership work gets done — drafting, summarising, analysing. Used well it buys back time for the human moments this playbook is about; used carelessly it creates polished mistakes at speed. The SMART approach is the 4Ds, applied here to customer-excellence work:
The SMART AI guide series covers the 4Ds in full, from first principles to applied practice.
Objection & Recovery
What to say when it doesn't go smoothly. Generic, adaptable phrasing — a guide, not a word-for-word script, so you communicate clearly and keep your own voice.
The recovery model
Customers forgive problems far more readily than they forgive feeling ignored or blamed. This sequence leads with listening, not defending.
Common deflections
Recovering a poor experience
My Standards Tracker
Your live RAG view of where the site stands against its own standards. Enter each standard, set its status and owner, and see at a glance what's holding and what's slipping. Starts with a set drawn from the tabs — rename, delete or add your own.
| Standard | Area | Status | Owner |
|---|
Review on the same cadence every month. The point isn't a perfect scorecard on day one — it's watching red move to amber to green as the basics bed in.
Team safety & welfare
A team that doesn't feel safe cannot deliver anything else in this playbook. Safety isn't an HR folder — it's a leadership standard, planned into the rota, rehearsed like any process, and designed for everyone by being tested against the hardest case: a colleague alone, with a stranger, off site. If the answers below aren't instant, the site isn't ready.
The rota is a safety document
Every rota should be checked for one thing before it's published: do we have adequate safety resource on site for the personnel working? That means first-aid cover on every shift, no avoidable lone working at open and close, and eyes on the quiet windows — early starts, late finishes, thin Sundays — where a colleague could find themselves alone with a problem.
Named ownership: the rota compiler builds it in; a manager signs it off. If cover can't be met, the rota changes — not the standard.
Emergency readiness: first aid & defibrillator
Four questions every person on site should be able to answer without looking anything up:
UK employers must assess their first-aid needs; these questions are how a professional site answers that assessment in practice. Make "who's our first-aid cover today?" a standing line in the daily preparation meeting.
The abusive customer: a protocol, not an improvisation
Frustrated customers are part of the job; abuse is not. Every site needs an agreed protocol that everyone knows before they need it:
The alert matters most. Is there a panic alarm — and does everyone know where it is and when to use it? If not an alarm, an agreed code phrase that discreetly summons a manager without escalating the customer ("could you pull the Henley file for me?"). No colleague is ever left alone with an escalating customer, and no colleague is required to absorb abuse to keep a deal or a job ticket alive — walking away with a manager's backing is the professional standard. Serious incidents are recorded, and repeat or threatening behaviour is escalated or banned.
Test drives: one route, every time, everyone
The test drive is the highest-exposure moment in the building: a colleague, alone, in a moving vehicle, with someone they met minutes ago. The controls are simple and they are mandatory for every drive — male or female, no exceptions, because a rule with exceptions protects no one:
- →A designated, risk-assessed route used for every test drive. Everyone on site knows where the car is and when it's due back; any deviation is itself a signal.
- →Every drive logged out and back — who's driving, with whom, which car, expected return. Someone on site owns watching the clock.
- →Licence checked and copied before the drive — identity known before anyone shares a car.
- →The route is not negotiable with the customer. "This is our test-drive route" is a professionalism signal, not an apology.
Lone-worker protocols & panic alerts
Design for the hardest case and everyone is covered: a female colleague, on her own, with a male customer she's never met. The protocols that make that moment safe:
- →The site always knows — no unaccompanied appraisal, drive or off-site visit that isn't logged with a return time and a named person watching it.
- →A panic alert that works in the real moment — a phone SOS/lone-worker app or discreet device, plus the agreed code word to base that triggers a call-back or intervention without alerting the customer.
- →The right to swap or say no, without justification — any colleague uncomfortable with any customer can hand over or take a second person, no questions, no career cost. Discomfort is data.
- →Environment designed in — visible desks, colleagues in sight lines, customer seated where the colleague chooses, keys retained until checks are done.
- →Open and close in pairs — always two people — and the walk to a lit car park never done alone.
These aren't "female protocols" — they're professional protocols that happen to be tested against the scenario with the least margin for error. A site where the newest, smallest, most junior colleague is demonstrably safe is a site where everyone is.
Lock-up & opening: the two-person walk-round
Closing and opening are done in pairs, to a checklist — because a missed door, an unlocked car or a screen left on isn't discovered until it's a problem. The walk-round covers:
Security
- All doors and entrances locked and checked
- Customer cars in the car park locked
- All cars in the compound locked
- Forecourt vehicles locked
- No keys left in pockets or drawers — every key accounted for and secured in the key system
Data & screens
- All computers locked or shut down — no live sessions overnight
- No customer details visible — desks, printers, whiteboards and screens cleared of anything a visitor could read first thing at opening (a GDPR check, done nightly, not annually)
- Job cards and paperwork filed, not left out
Same discipline at opening: two people in, walk-round done, before the doors open to customers. The morning check catches anything the night missed.
Workshop safety
- →No workshop staff working solely — never one technician alone in the workshop, whatever the hour. Ramps, vehicles and high-voltage systems are not lone-worker territory.
- →Ramp and equipment checks — ramps, lifting gear and tools checked on a set cadence so everything in use is safe and in good working order, with faults tagged out of service immediately, not worked around.
Leading the standard
Everything in this playbook lives or dies on one truth: culture is what leadership walks past. Every unacknowledged customer a manager walks by, every strong-tone email that goes unchallenged, every safety question left unasked — that becomes the real standard, whatever the document says. This is the executive layer.
Model it visibly
The team copies what they see, not what's briefed. Leaders greet the waiting customer first, walk people to their destination, pick up a ringing phone, and ask the safety questions before anyone else does. A Head of Business who does the brilliant basics personally makes them unarguable; one who delegates them makes them optional.
Coach the gap, not the person
A sense-check miss is a process or coaching point, never a public verdict. Praise on the floor, coach in private, and always ask before telling: what got in the way? Most dropped basics have a system cause — a rota, a handover, an unowned task — and the person closest to the miss usually knows the fix.
The tracker is a development syllabus
Every amber or red on My Standards should convert into a named coaching conversation with a date — not a note. Over a quarter, the tracker becomes each person's development record: what they've mastered, what they're working on, who's ready to teach it to others. Standards that are coached, stick; standards that are audited only, slide.
Empower the gesture
Brilliant basics need permission-free ownership. The refreshment, the walk-over, the small goodwill gesture within an agreed limit — if the team has to ask, it won't happen at pace. Set the limits once, publicly, then get out of the way. The 90/10 principle only works when the 10% doesn't need a signature.
Lead the safety, lead the trust
The leader asks first: who's our first-aid cover today, is the drive log running, has the walk-round happened? And the deeper layer — psychological safety: the team can raise a problem, admit a miss, or say no to a customer situation without it costing them. A colleague who fears the conversation more than the risk will take the risk. That's on leadership.
Recognise the behaviour, not just the number
Catch people doing it right and name it in the prep meeting — the walked-over customer, the kept promise under pressure, the conflict settled by conversation. Behaviours that get seen and celebrated repeat; behaviours that only avoid punishment shrink to the minimum. What gets recognised is what you'll get more of.
Process, ownership & the chain
Customer experience is the most process-dependent thing you do — a hundred small moments that either happen reliably or don't. The chain is what makes them reliable.
The process that IS the experience
Acknowledgement, communication, ownership, follow-through — these feel like personality, but they're process. "Every caller greeted within three rings," "every customer updated before they chase," "every complaint owned to resolution" are processes, and the experience is simply what's left when they're followed. The site that's brilliant with customers isn't staffed by nicer people; it runs the moments as disciplines, every time, especially when busy.
The measures that tell the truth
CSI, response times and complaint-resolution aren't scores to defend — they're the experience made visible. A dip isn't a number to explain to the OEM; it's the chain telling you a moment-process slipped, and pointing you at exactly which one to tighten.
Accountability — clarity, not blame
Every person owns their moments — the greet, the update, the handover, the follow-up call. When experience slips, the accountable conversation is "which moment did we miss, and how do we make it reliable" — never "who upset the customer." Blame makes people defensive and customers feel it; ownership makes people proud of their moments and customers feel that too.
Customer excellence with AI
AI is a strong assistant for the communication work in this playbook — drafting updates, theming feedback, turning meeting notes into actions. But the relationship stays human: AI speeds the writing; it never replaces the walk-over, the phone call or the apology delivered in person. The 4Ds framework — the same one that underpins the whole SMART AI series — keeps the balance right.
The 4Ds, applied to customer work
1Delegation — what to hand over
- Hand to AI: first drafts of customer updates and complaint responses, theming a month of verbatim feedback, turning prep-meeting notes into an action list, tidying an SLA document
- Keep human: the conversation itself, the apology, the judgement call on a goodwill gesture, anything where the customer needs to feel a person — because they can tell
2Description — how to brief it
- Set the tone explicitly: warm, plain English, no jargon, honest about what went wrong
- Give the context: what was promised, what happened, what you can actually offer
- Name the channel — a text, an email and a letter read differently
- Say what it must NOT do: no promises the site can't keep
3Discernment — how to judge the output
- Check every fact and promise in the draft is true and deliverable — AI will cheerfully offer a courtesy car you don't have
- Read it as the customer would: does it sound like a person who cares, or a template?
- If it's a recovery message, test it against the model: acknowledge, own, understand, put right, follow up
4Diligence — your responsibilities
- Customer personal data never goes into public AI tools — no names, registrations, contact details or account information. Anonymise first, always
- That's a legal line (UK GDPR), not a style preference
- The person who sends the message owns every word of it — AI-assisted or not