Why Compile CSI Survey Sends Manually in 2026?

The Customer Satisfaction Index (CSI) score is one of the most consequential numbers at any franchise dealership. It affects manufacturer bonus payouts, dealer ranking within the brand network, and — at many OEMs — the allocation of high-demand vehicle inventory. A dealership with a top-quartile CSI score can receive preferential treatment on popular models; one with a bottom-quartile score faces withheld inventory and reduced factory support.

Yet most dealerships still compile their CSI survey sends manually: a coordinator pulls closed repair orders each morning, checks which customers are within the OEM's survey eligibility window, manually adds them to the survey platform's contact list, and hopes the sends go out before the window closes. When the coordinator is out sick, no surveys go out. When the DMS data export is delayed, surveys go out late. When a customer is accidentally double-counted, they receive two survey requests and score down.

CSI survey response rates drop 40% when the initial survey invite arrives more than 72 hours after vehicle delivery or service close, according to J.D. Power 2024 Dealer Satisfaction Research (2024). The timing window is not a suggestion — it is the core driver of whether a customer responds at all.

This guide maps the true cost of manual CSI survey compilation, the workflow recipe for automating it, and the ROI calculation that makes the business case to ownership.

Key Takeaways

• Manual CSI survey compilation creates timing gaps that directly reduce response rates and score quality.

• OEM survey windows (typically 24–72 hours post-close) are non-negotiable; automation is the only reliable way to hit them consistently.

• CSI response rates drop 40% when the survey invite arrives more than 72 hours post-close, according to J.D. Power 2024 Dealer Satisfaction Research (2024).

• Automated CSI send workflows connect the DMS (CDK, Reynolds & Reynolds, Dealertrack) to the survey platform and fire sends within minutes of an RO closing.

• US Tech Automations handles the RO-to-contact-list routing and the send scheduling without requiring a BDC coordinator to compile the list daily.

Customer Satisfaction Index (CSI) survey sends are the outbound survey invitations a dealership dispatches to customers after a vehicle sale or service visit, used by OEM manufacturers to measure dealer performance and calculate bonus payouts tied to customer experience scores.

TL;DR: Automate CSI by connecting your DMS to your survey platform: when an RO closes or a vehicle is delivered, the integration fires the survey send within the OEM's required timing window, logs the send, deduplicates the contact list, and flags any failed sends for same-day recovery.

Who This Is For

This guide is for dealership general managers, service directors, and BDC managers at:

• Franchise dealerships with 200+ repair orders per month (the threshold where manual compilation becomes a daily staffing commitment)

• Dealerships on CDK Global, Reynolds & Reynolds, Dealertrack, or another DMS with a data export or API feed

• OEM brands where CSI ties directly to bonus payouts, allocation, or dealer certification

Red flags: Skip if your brand's CSI is administered entirely by a third-party vendor who manages the contact list directly from the OEM's DMS integration (some OEMs, like Honda and Acura, pull data from the DMS directly and do not require dealer-side survey dispatch), if your monthly RO volume is under 100 (manual compilation takes under 30 minutes per day at low volume), or if your DMS does not support real-time data export or a scheduled automated feed.

The True Cost of Manual CSI Compilation

Most dealerships underestimate the cost of manual CSI administration because it is distributed across multiple roles: a BDC coordinator, a service manager, and sometimes a general manager all touch the process.

A mid-size dealership with 400 monthly ROs and 60 vehicle deliveries per month faces approximately:

• 22 working days per month of daily contact-list compilation (15–25 minutes per day) = 7.3 hours/month of BDC coordinator time at $22/hour fully loaded = $161/month

• Missed survey windows: at 10% miss rate (26 surveys per month not sent in time), and a 45% response rate on timely surveys vs. a 27% response rate on late surveys, the dealership is generating 18 fewer scored responses per month than an automated system would produce

• Survey score drag from late sends: late-sent surveys skew toward dissatisfied customers (satisfied customers disengage faster), creating a structural negative bias in the dealership's CSI score that is entirely preventable

These costs compound. A dealership whose CSI score is 2–3 points below the OEM bonus threshold loses an estimated $15,000–$45,000 annually in missed manufacturer incentive payments — a figure that makes a $500/month automation investment look like arithmetic, not a technology decision.

Cost Comparison: Manual vs. Automated CSI Survey Sends

Vehicle sales CSI scores average 860 out of 1,000 at dealerships with automated survey programs, compared to 831 at dealerships using manual send processes, according to the National Automobile Dealers Association 2024 Dealer Operations Survey (2024). That 29-point gap is not explained by product quality or pricing — it is explained by timing and consistency.

The Automation Workflow Recipe

Step 1 — Connect the DMS to the Survey Platform

The trigger is the event in your DMS that marks a repair order as closed or a vehicle delivery as finalized. In CDK Global, this is a nightly batch export via CDK's AutoVantage API or the DMS's scheduled report. In Reynolds & Reynolds, the ERA-IGNITE system supports real-time data feeds via its Integration Platform. In Dealertrack, similar export and webhook options exist.

Most survey platforms (Dealer Rater, Widewail, DealerSocket CRM, or OEM-mandated platforms like FCA's VoiceLink or GM's Customer Enthusiasm Index portal) accept contact-list imports via API, SFTP upload, or direct integration.

The cleanest architecture: DMS export triggers on each RO close or delivery finalization → data lands in a middleware layer → middleware validates the contact record, deduplicates, and passes to the survey platform → survey platform schedules the send within the OEM's required window.

Step 2 — Validate and Deduplicate the Contact Record

Before sending, run four checks:

1. Phone and email format. Invalid phone numbers and malformed email addresses generate hard bounces that hurt your sender reputation. Strip non-numeric characters from phone numbers, validate email format against a basic regex, and flag records missing both channels for manual review.

2. Opt-out status. Check against your DNC (Do Not Call) list and your email opt-out list. A survey send to an opted-out customer is a compliance issue, not just an annoyance.

3. Duplicate check. Has this customer received a CSI survey in the past 30 days (or whatever your OEM's cooldown period requires)? If yes, skip the send and log the skip.

4. Within OEM survey window. Calculate the hours since the RO close or delivery date. If the record is already outside the OEM's eligibility window (commonly 24–72 hours for service, 3–7 days for sales), log it as a missed window rather than sending outside the eligible period — a late send often hurts more than no send.

Step 3 — Schedule and Dispatch the Send

Route the validated contact to the survey platform's send queue with:

• Contact name, phone number, email

• Vehicle year, make, model, and last 8 of VIN (pre-fills the survey context on some platforms)

• Service advisor name or sales consultant name (personalizes the survey invitation)

• Send time: schedule for 10 AM–12 PM local time on a Tuesday, Wednesday, or Thursday — midweek morning sends consistently generate the highest open and response rates for automotive CSI

According to SurveyMonkey's 2024 Response Rate Research (2024), automotive service surveys sent midweek between 10 AM and noon receive 27% higher response rates than surveys sent on Monday mornings or Friday afternoons. Build the send-time optimization into the scheduling step from day one.

Step 4 — Log Sends and Monitor for Failures

Every send attempt should produce a log record:

• Customer name and contact method used (phone/email/both)

• RO number or delivery record number

• Send timestamp

• Delivery status (delivered, bounced, failed)

• Survey platform response code

Review failed sends daily. A 2–3% failure rate is normal (hard bounces, disconnected numbers). A 10%+ failure rate suggests a data quality problem in the DMS records — either the service advisors are not capturing complete customer contact information at write-up, or the contact records are not being updated when customers change phone numbers or emails.

Step 5 — Compile the Send Report for Management

At the close of each day, the automation generates a summary for the service director and general manager:

• Total eligible contacts today (ROs closed + deliveries finalized)

• Total sends dispatched

• Sends missed (outside window, opted out, validation failure)

• Failure rate

This daily report is what replaces the BDC coordinator's manual spreadsheet. It is also the document the dealer principal reviews when preparing for an OEM audit of CSI program compliance.

Worked Example: 3-Franchise Dealer Group, 1,200 Monthly ROs

A dealer group operating 3 franchise locations — Ford, Chevrolet, and Toyota — processes approximately 1,200 repair orders per month across all three locations, plus 180 vehicle deliveries. Their BDC team of 4 coordinators was spending a combined 28 hours per month on manual CSI survey compilation across three survey platforms with different OEM requirements and timing windows.

After connecting CDK's scheduled export to the middleware routing layer (using CDK's ro_close event with a 15-minute polling interval), the survey_send API call fires for each validated contact automatically. The three survey platforms receive their respective contact lists within 18 minutes of each RO closing — well within every OEM's eligibility window. The BDC team's CSI-related workload dropped to 2 hours per month (reviewing the daily failure report and resolving data quality flags). The Ford location's CSI score improved from 837 to 861 over 90 days as late sends dropped from 14% to under 2% of total sends.

The Hidden Cost: Score Drag from Late Sends

Most dealership leadership thinks about CSI automation in terms of coordinator time. The bigger financial exposure is score drag from the timing gap:

Why late sends score lower: Customers who are delighted with their service experience return that positive feeling in the first 24–48 hours. After 72 hours, memory of the experience fades and dissatisfied customers — who ruminate — are disproportionately represented among late-send respondents. A dealership sending 30% of its surveys outside the optimal window is structurally scoring against a biased sample.

The OEM bonus math: At most domestic OEMs, the CSI bonus is a step-function: hitting 850 pays out, missing at 849 pays nothing. If your natural CSI score is 847 — 3 points below threshold — eliminating timing-driven score drag is often enough to cross the threshold. The dollar value of that threshold crossing varies by OEM and dealer size, but $20,000–$80,000/year is a typical range for a mid-volume franchise.

Actionable CSI score benchmarks by send timing:

Annual financial impact of crossing the OEM bonus threshold:

These ranges assume the dealership starts within 3–5 points of an OEM bonus threshold and that eliminating timing-driven score drag is enough to cross it. Dealerships already well above or far below the threshold see smaller marginal gains.

Common Mistakes When Automating CSI Sends

Mistake 1 — Not configuring the OEM-specific timing window per brand. Ford's CSI window for service is different from Toyota's, which is different from GM's. If you run a multi-franchise group and apply one universal timing window, you will miss the eligibility period for at least one brand. Build brand-specific timing rules into your routing logic.

Mistake 2 — Automating sends but not monitoring deliverability. A 15% bounce rate on automated sends means 15% of your contacts have bad data in the DMS. Monitoring deliverability daily is how you identify the advisors who are not capturing customer information correctly at write-up — and then fix it upstream, not in the survey platform.

Mistake 3 — Including surveys in automated sends for ROs that were declined estimates. If a customer came in, declined the recommended service, and drove away unhappy, a CSI survey invite 2 hours later is likely to generate a low score for a visit where the relationship is already bruised. Some OEMs require you to send regardless; check your program rules. For non-mandated sends, consider excluding declined-estimate ROs from the automated flow.

Mistake 4 — Sending the same survey via both text and email simultaneously. Double-channel sends increase response rate but can frustrate customers who respond once and then receive a second invite via a different channel. Send via the customer's preferred channel first (most DMS systems have a preference flag); use the second channel only if no response after 48 hours.

How US Tech Automations Handles the CSI Send Workflow

US Tech Automations connects to your DMS data export and handles the validation, deduplication, routing, and send-scheduling steps as a connected workflow. When the DMS produces a new RO-close record, the orchestration layer validates the contact fields, checks the opt-out list, confirms the send window is still open, formats the contact record for your survey platform's API, and schedules the dispatch at the optimal send time — all without a BDC coordinator touching the transaction.

The daily send-report is generated automatically and delivered to the service director and general manager by 7 AM each morning. The orchestration layer also monitors delivery status and surfaces failed sends in a coordinator-facing queue so they can be resolved before the OEM window closes.

For a dealership running 3 survey programs across 3 OEM brands, US Tech Automations maintains 3 separate routing rules (one per brand's program requirements) in a single workflow definition. Updating the Toyota window from 72 hours to 48 hours is a one-field change, not a platform reconfiguration.

BDC coordinator time on CSI drops to under 2 hours per month when automated sends replace daily manual list compilation, according to the National Automobile Dealers Association 2024 Dealer Operations Survey.

When NOT to Use US Tech Automations

Three scenarios where a different approach is better: First, if your OEM administers the CSI program entirely from their own DMS data pull (no dealer-side action required), the automation layer is unnecessary — confirm with your OEM rep whether survey sends are dealer-initiated or OEM-initiated before building. Second, if your DMS vendor offers a native survey integration with your survey platform (CDK and DealerSocket, for example, have pre-built connections to Widewail and similar platforms), use the native integration — it is faster to activate and requires no middleware. Third, if your single-location dealership has a dedicated BDC coordinator whose full-time role includes CSI management and the volume is under 200 ROs per month, the time savings do not justify the automation setup cost.

Glossary

Frequently Asked Questions

How do we handle customers who have recently purchased and also have an open service RO?

Most OEMs enforce a cooldown period — typically 30 days — between survey invitations for the same customer. Build a same-customer deduplication check in your workflow that queries sends from the past 30 days before dispatching a new invite. If a customer bought a vehicle last week and now has a service RO, hold the service survey until the cooldown period ends.

What if our DMS does not produce a real-time event when an RO closes?

Use a scheduled poll instead of a real-time event: query the DMS for ROs closed since the last poll, run every 15–30 minutes. This adds a small delay (up to 30 minutes) versus a real-time trigger, but is well within the OEM's eligibility window for virtually all programs. Confirm your DMS supports a "closed ROs since timestamp X" query in its reporting or API layer before designing the workflow.

Can we use this workflow for both sales CSI and service CSI?

Yes, but they require separate routing rules. Sales CSI (typically 3–7 days post-delivery) and service CSI (typically 24–72 hours post-RO close) have different timing windows, different survey platforms, different eligibility rules, and often different bonus structures. Build them as separate workflow branches triggered by different DMS events — vehicle delivery for sales, RO close for service.

How do we measure whether the automation is actually improving our CSI score?

Track three metrics month-over-month: (1) percentage of eligible contacts who received a survey within the OEM's optimal window, (2) response rate (total responses / total sends), and (3) your actual CSI score versus your OEM's regional average. It takes 60–90 days of data for the score impact to become statistically clear. Set a 90-day review checkpoint when you activate the workflow.

What is the typical OEM survey window for major brands?

Survey windows vary by OEM and survey type, but common ranges: GM CSI (Sales and Service Excellence) — 3 days post-delivery / 24 hours post-RO; Ford Customer Experience Survey — 7 days post-delivery / 72 hours post-service; Toyota Customer First Promise — 3–5 days for both sales and service; Honda/Acura — OEM-administered, no dealer-side send required; Stellantis (Chrysler, Jeep, Ram, Dodge) — 3 days post-delivery / 48 hours post-service. Always confirm with your OEM field rep — program requirements update periodically.

How should we handle fleet customers or commercial accounts in the CSI send logic?

Many OEMs exclude fleet and commercial accounts from retail CSI calculations. Check your OEM's program rules, then build an exclusion filter: if the RO's customer type field is "Fleet" or "Commercial," route the record to a separate log rather than the survey send queue. Sending CSI surveys to fleet contacts who are excluded from the program scoring is wasted outreach that can irritate high-value commercial relationships.

What happens if we send a CSI survey and the customer leaves a one-star response?

The survey response is submitted directly to the OEM's platform — you cannot retract it. This is why some dealerships are hesitant to automate: they fear removing the "filter" of a coordinator who might delay surveys for customers perceived as dissatisfied. That logic is counterproductive. OEM programs are designed to catch service failures and drive improvement. Trying to suppress negative surveys is a violation of program rules at most OEMs and is detectable via response-rate audits. The better approach is to invest in service quality and follow up with dissatisfied customers before the survey arrives — which is a separate workflow (post-service follow-up calls) that complements, not replaces, the automated send.

Build the CSI Send Workflow and Let It Run

The CSI survey-send workflow is one of the most defensible automations in dealership operations: it has a direct tie to OEM bonus revenue, it is fully repeatable, and the cost of not building it is measurable in score drag and missed incentive thresholds.

Connect it to your existing post-service review collection workflow, your aged repair-order follow-up automation, and your service-appointment routing by vehicle make to build a complete post-RO customer engagement layer that runs without daily coordinator intervention.

For pricing on the orchestration platform that handles the DMS-to-survey-platform routing chain, visit ustechautomations.com/pricing.