Car Dealership Survey Template
Send a dealership customer satisfaction survey that matches the actual journey your customer had -- Sales/F&I/Delivery, Service (RO close), or Test Drive/Lead follow-up. This template includes routing, recommended email/SMS timing, NPS/CSAT/CES scoring, and a simple close-the-loop workflow so low scores turn into real fixes (not just a report).
Trusted by 5000+ Brands
When to Send a Dealership Survey (3 best moments)
24-72 hours after delivery (Sales + F&I + Delivery)
Goal: Catch breakdowns in pricing/fees transparency, F&I pressure, delivery quality, and salesperson follow-through while you can still recover the relationship.
Default: Starter send window: 24-72 hours after the delivery event in your CRM/DMS (adjust after your baseline). Use email if you want longer comments; use SMS if your survey is under 2-3 minutes (starter target).
Customize: Route to the Sales version so customers only see Sales/F&I/Delivery questions (not Service items).
Same-day or next-day after RO close/pickup (Service)
Goal: Measure whether the repair was done right, the advisor communicated clearly, and the customer understood timing and charges.
Default: Starter send timing: trigger at RO close (or pickup) and send same-day or next-day (adjust after your baseline). Default to SMS for fast transactional response; use email if you need detailed verbatims.
Customize: Route to the Service version and include only the relevant options (loaner, shuttle, pickup/drop-off, waiting room).
Within 2-24 hours after a test drive/appointment (Lead follow-up)
Goal: Diagnose why a prospect did or did not move forward (availability, trade appraisal, pricing clarity, follow-up speed).
Default: Starter send window: within 2-24 hours of the appointment outcome in your CRM (adjust after your baseline). Use SMS if you want an immediate quick answer; use email if your BDC asks for more detail.
Customize: Route to the Lead/Test Drive version and skip any delivery/service questions.
Choose the Right Metric: NPS vs CSAT vs CES (Dealership Edition)
| Metric | What it measures | Best dealership use | Scoring basics | What to do next | Downside if used alone |
|---|---|---|---|---|---|
| Quick setup (use this default) | Goal: improve Sales/F&I/Delivery and Service experiences with consistent tracking. | Default: Starter approach: use CSAT for each transaction (Sales or Service), and add NPS on a monthly/quarterly pulse (adjust after your baseline) for relationship trend. | Customize: Pick 1 primary metric per journey, then keep it stable for trending. | Add 1 driver + 1 "Why?" comment prompt so you know what to fix. | One number without drivers turns into arguing, not fixing. |
| NPS | Relationship loyalty: "How likely are you to recommend?" | Track overall store/roof health across Sales + Service (starter cadence: monthly/quarterly; adjust after your baseline). | 0-10 scale. Promoters = 9-10, Passives = 7-8, Detractors = 0-6 (see Net Promoter Score scoring definitions). | If Detractor: assign an owner and call within 24 hours (starter SLA); tag the theme (fees, wait, communication, quality) and log the outcome in CRM. | Too high-level for day-to-day fixes; can hide whether Sales or Service is driving the score. |
| CSAT | Transactional satisfaction: "How satisfied were you with..." | Best default for delivery and RO close because you can tie results to a specific advisor/salesperson and day. | Usually 1-5 (or 0-10). Define what counts as a save-needed score (example starter threshold: 1-2 on a 5-point scale; adjust after your baseline). | If CSAT is low: call same-day/within 24 hours (starter SLA), fix the specific breakdown (update cadence, write-up wait time, delivery checklist), and follow up after the fix. | Can drift upward over time; needs a consistent driver question to keep it actionable. |
| CES | Friction/effort: "How easy was it to..." | Use for scheduling, status updates, pickup, and issue resolution where effort drives defection. | Often 1-7 (lower effort is better). Define what counts as high-effort (example starter threshold: 5-7 on a 7-point effort scale; adjust after your baseline). | If effort is high: simplify the process (faster callbacks, proactive status texts, clearer pickup steps). CES is built for reducing avoidable work (see HBR's Stop Trying to Delight Your Customers). | Does not directly tell you if the customer liked the outcome; pair with quality/resolve questions. |
Pick 1 primary metric per journey (example: CSAT after delivery and RO close; CES for scheduling/updates). Then add (a) 1 driver question per stage (wait time, transparency, communication, quality) and (b) 1 "Why?" comment prompt using open-ended questions so you can tag root causes and assign fixes. Keep the same core questions over time so you can monitor trends, not just one-off spikes (see ISO guidance on customer satisfaction monitoring and measuring).
How to Use This Dealership Survey (Routing + Cadence + Minimal Edits)
- Pick the journey you are measuring (Sales vs Service vs Lead)Goal: match questions to the transaction you can fix. Default: run 3 routed versions (Sales/F&I/Delivery, Service RO close, Test Drive/Lead). Customize: rename role labels (salesperson, finance manager, advisor) and add your roof/store name.
- Route with branching so people only see relevant itemsRoute based on the event that triggered the send (delivery vs RO close vs appointment). If the customer did not buy, send the Lead version; if they did, send Sales. This single decision prevents mixed feedback that your managers cannot act on.
- Trigger sends from real events (CRM/DMS) and keep timing tightTrigger off delivery posted, RO closed, or appointment completed. Use 1 primary channel plus 1 reminder (starter rule; adjust after your baseline and consent rules) and stop after a response. Follow general survey best-practice rules from AAPOR's Best Practices for Survey Research.
- Set a cadence that avoids over-contactDefault to either (a) every transaction, or (b) a consistent sampling approach (example starter rule: every 2nd RO close per advisor per day; adjust after your baseline) so your trend is stable. If you blast every touchpoint, response drops and comments get worse -- survey fatigue is real (see evidence on response decline in survey fatigue and response rates).
- Make minimal edits, then launchEdit only what changes by rooftop: store name, department names, and local options (loaner, shuttle, pickup/drop-off). Keep your metric question and 1 driver question stable so month-over-month reporting stays clean.
| Journey | Send window | Primary channel | Reminder rule | Routed version |
|---|---|---|---|---|
| Sales + F&I + Delivery | 24-72 hours after delivery (starter window; adjust after your baseline) | Email (default) or SMS if under 2-3 minutes (starter target) | 1 reminder at 48-72 hours if no response (starter rule; adjust after your baseline) | Sales |
| Service (RO close/pickup) | Same-day or next-day after RO close (starter timing; adjust after your baseline) | SMS (default) | 1 reminder next-day; stop after response (starter rule; adjust after your baseline) | Service |
| Test Drive / Lead follow-up | 2-24 hours after appointment outcome (starter window; adjust after your baseline) | SMS (default) or Email for longer detail | No reminder unless the lead is still open; if you remind, do it once within 24 hours (starter rule; adjust after your baseline) | Lead |
| Default (if unsure) | Next business day (starter fallback; adjust after your baseline) | SMS for Service, Email for Sales | 1 reminder max (starter rule) | Route by event type |
- Keep it short: target 2-4 minutes (starter target); add optional modules with routing instead of a long one-size-fits-all survey.
- Prevent double-contact: if you already triggered an RO-close survey, do not also send a generic monthly survey to the same customer that week (starter rule; adjust after your baseline cadence).
- Minimize data collection: do not ask for unnecessary sensitive data, and confirm you have permission-to-contact for SMS. Use your team's security and privacy best practices as the default rulebook.
Results and Action Plan: Close the Loop on Low Scores (and Fix Root Causes)
- Set alert thresholds you will actually act on: Starter thresholds: alert on NPS Detractors (0-6), CSAT 1-2 out of 5, or high-effort CES (top end of your effort scale). Adjust after your baseline and set separate thresholds for Sales vs Service if one area runs consistently higher/lower.
- Assign a follow-up owner by journey: Route Sales issues to the Sales manager (or desk) and Service issues to the Service manager. Default: your CX lead monitors the queue and reassigns if the wrong department was selected.
- Call fast, then log it: Starter SLA: call same-day or within 24 hours of a low score (adjust after your baseline and staffing). Log contact attempts and the resolution in your CRM (refund, redo, advisor coaching, explanation of fees, parts ETA update) so the fix sticks.
- Tag verbatims into a small set of operational themes:
- Pricing/fees: add-ons, F&I products, surprise charges, estimate accuracy
- Wait time: write-up line, technician cycle time, delivery delays
- Communication/updates: no callbacks, unclear status, missed pickup coordination
- Quality/issue resolution: problem not fixed, repeat visit, new issue created
- Optional: staff professionalism, digital experience (online scheduling, texts)
- Report the cuts that drive action (not vanity averages): Default cuts: roof/location, department (Sales vs Service), new vs used, advisor/salesperson, appointment type, channel (walk-in vs scheduled), and day/time. Customize: add write-up lane, technician team, or delivery specialist if that is how work is assigned.
Start with high-frequency negative themes (wait time, communication, surprise fees, not-fixed-right). Then pull the top 2 drivers by department and set a 2-week owner and due date (starter sprint length; adjust after your baseline), for example: "Service updates: advisor sends 2 proactive texts per RO by 2 pm" (example play; tailor to your process and customer preferences).
Sample Size and Reporting Rules for Dealership Teams (Avoid Bad Comparisons)
Goal: help Sales and Service managers trust the results enough to act. Default: do not rank advisors/salespeople/roofs until each has consistent volume; trend month-over-month instead of reacting to a single week. Customize: set a minimum-N rule per role (advisor vs salesperson) based on your store volume.
- Use small N for learning, not ranking: If an advisor has 6 surveys this month, read the comments and fix obvious breakdowns, but do not publish a leaderboard.
- Set a minimum before comparisons: Starter minimum: require at least 30 responses in a time window before comparing people or small teams; use 60+ if you want more stable rankings (adjust after your baseline and decision stakes).
- Use rolling windows: Starter window: a rolling 60-90 day view for advisor/salesperson performance so one bad Saturday does not dominate the story (adjust after your baseline volume).
- Check uncertainty before you act on a delta: Use confidence intervals or a significance check when you compare teams, especially if volumes differ. For background on statistical quality standards used in U.S. federal surveys, see the OMB Statistical Programs & Standards overview at OMB statistical survey standards and guidance, and align your approach with AAPOR's Best Practices for Survey Research.
Get help with the math (without slowing down ops)
Use sample size guidance to set minimum-N rules, align your sampling approach to your store volume, and use statistical significance checks before you call a week-to-week change a real improvement.
Default reporting rule that prevents fights
Only publish team comparisons when every team meets minimum N in the same time window. If one advisor has 80 surveys and another has 12, report them separately: one gets a trend line; the other gets coaching notes and verbatims.
Frequently Asked Questions
Should I use one survey for Sales and Service, or separate surveys?
Use 1 master template with routing (or 2 separate versions) so Sales customers never see Service-only questions and Service customers never see delivery/F&I items. Default to branching based on the trigger event (delivery posted vs RO close) because mixed, unrouted surveys create noisy scores and unclear ownership.
When is the best time to send a dealership survey after purchase or service?
Starter timing: send the Sales/F&I/Delivery survey 24-72 hours after delivery, and send the Service survey same-day or next-day after RO close/pickup (adjust after your baseline and operations). For test drives/appointments, send within 2-24 hours so you capture the reason they did not move forward while it is still specific.
Email or SMS -- which gets better response for dealership surveys?
Default to SMS for RO-close and other fast transactional feedback when your survey is short, and use email when you want longer comments or clearer permission-to-contact controls. As a starter rule, use 1 primary channel plus 1 reminder and stop after a response, then adjust based on your baseline response and opt-out rates.
How long should a car dealership customer satisfaction survey be?
Keep the core survey to 2-4 minutes (starter target): 1 primary metric (NPS or CSAT, plus CES when you are targeting effort), 1 driver question, and 1 "Why?" comment prompt per journey stage. If you need more detail, add optional modules via routing instead of making everyone answer everything.
How do I score NPS, CSAT, and CES and decide what to improve first?
Score NPS by grouping 0-6 (detractors), 7-8 (passives), and 9-10 (promoters); score CSAT using your chosen low-score threshold (example starter threshold: 1-2 out of 5); and score CES by flagging high-effort responses (all adjust after your baseline). Then prioritize fixes by the most frequent negative themes (wait time, communication, surprise fees, not-fixed-right) and the drivers most tied to low scores in Sales vs Service.
Can I compare advisors or salespeople with small response counts?
Avoid ranking people with low counts because a few surveys can swing the score. Use a minimum-N rule, use a rolling window (starter: 60-90 days; adjust after your baseline), and apply confidence intervals or a significance check before you claim one advisor is better than another.
Related Survey Templates
FREE TO START -- NO CREDIT CARD REQUIRED