Customer-centric AI for powersports retail

ResourcesCustomer data

Customer data

Managing the Value of Customer Information: Data Quality Standards for Your Dealership CRM

Dealership customer data quality: a field-by-field data standard, duplicate and merge rules, consent records, who updates what, and a monthly cleanup checklist.

By PSX Ascend Editorial TeamPublished Updated 11 minute read
  • CRM/Sales Process
  • Customer data
  • Data quality
  • Consent

Quick answer

Dealership customer data quality means every record is complete enough to act on, formatted the same way, free of duplicates, honest about consent and kept current by a named owner. Write a short data standard, search before you create a record, capture contact details in conversation, and run the same cleanup checklist every month.

In a 2018 PSX video conversation, Danny James and Larry Bruce talked about the oldest rule in CRM: "garbage in, garbage out." Larry's view was practical. "I wouldn't say there's a good and a bad way or a right or a wrong way, but there is an easy way and an inefficient way to add customer data into a CRM."

This guide turns that conversation into a working standard for the sales manager, BDC lead or CRM administrator who needs customer records the whole store can use.

What customer data quality means at a dealership

A customer record is good enough when anyone in the store can act on it without asking the customer to repeat themselves, which is a large part of the customer experience a dealership delivers. That breaks down into five tests:

  1. Complete: the fields needed for the next step are filled in. For an open lead, that is a working contact method, an owner and a next action.
  2. Consistent: the same kind of data is entered the same way, so search, reports and marketing all work.
  3. Unique: one customer, one record, across sales, service, parts and every rooftop.
  4. Permitted: the record says how the customer wants to be contacted and what they have agreed to.
  5. Current: someone is responsible for updating it when things change, and old data is cleaned or retired.

Records fail in predictable ways: duplicates, phone numbers in five formats, units sold years ago, and notes only the writer can follow. Car retail sees the same problem. In Cox Automotive's 2024 Power of Data study of franchise dealers, "54% of dealers have experienced conflicting data across multiple sources."

The dealership data standard

Write down the fields your store requires, when, in what format and who keeps each current. Keep it short. Adapt this starting point.

Field Required when Format rule Updated by
First and last name Record is created As the customer spells it; no nicknames in the name field Whoever creates the record
Mobile phone Record is created, if given Ten digits, one format store-wide; mark whether it is a mobile Salesperson, BDC, service advisor
Email Record is created, if given Lowercase, checked for obvious typos Salesperson, BDC, service advisor
Preferred channel First conversation Call, text or email, from a fixed list Salesperson or BDC
Text and email permissions Before any marketing message Yes or no per channel, with date and source (form, conversation, deal file) Whoever captured it; changes logged, never overwritten silently
Do-not-contact requests The moment they are made A flag plus the date, never deleted in a merge Anyone who receives the request
Mailing address At the sale, or for service Follow USPS addressing standards (Publication 28) Business office, service advisor
Lead source Record is created From a fixed list (website, OEM, phone, walk-in, event, service, referral) Whoever creates the record, or the integration
Unit of interest First conversation Year, make, model, or at least category Salesperson
Units owned Delivery, service visit or trade appraisal Year, make, model and VIN; remove units sold or traded Business office, service advisor, salesperson at trade
Owner (salesperson) Lead is assigned One named person Sales or BDC manager
Stage and next action Every customer contact A stage from the list plus a dated next step Record owner
Lost reason When a deal does not close From a fixed list, plus a short note with the numbers Salesperson, reviewed by the manager

Two rules sit above the table. No open record without an owner and a dated next action, and no message sent without a recorded permission for that channel.

Larry's point about capture still applies. "Anytime you can avoid manually typing the information is a better way." Scanning a driver's license is fast, but the address on it may be out of date. Danny added a warning that holds today: "I always tell salespeople to not rely on a driver's license for follow-up contact information." Ask for the mobile number and email as part of the meet and greet, and confirm the address at the sale.

Search before you create

Duplicates are the most common data problem, and the cheapest one to prevent. Larry's rule was "It's best practice to search your customer base first," for three reasons he gave in the interview:

  1. Avoid duplicating the customer.
  2. Be informed of the interaction the customer has had with the dealership in the past.
  3. Have knowledge of details about the customer themselves.

Make the search a habit at every entry point, not just the sales floor:

  1. Search by mobile number first, then email, then last name and ZIP code.
  2. If you find a match, update it. Add the new interest or visit to the existing record instead of creating a new one.
  3. If you are unsure, do not guess. Create the record, flag it as a possible duplicate and leave the merge to the person who owns cleanup.
  4. Apply the same rule to integrations. Website, OEM and third-party leads should match existing customers by phone or email before a new record is made.

What cleanup guides leave out

Most data quality advice for dealers, including vendor checklists and trade articles, gives the same three steps: assess the data, prevent bad entry, then clean regularly by merging duplicates and verifying emails. That is sound, but it skips the decisions that cause real trouble at a powersports store.

  • Merges must keep the strictest permission. When two records are merged, the result should keep every do-not-contact flag and opt-out from either record. A merge that keeps the "newer" record's permissions can quietly turn an opt-out back on.
  • Merges must keep the history. Notes, lost reasons, service visits and appraisals from both records belong on the surviving one. Ownership should go to whoever is actively working the customer.
  • One rider, many units. A powersports customer may own a side-by-side, a dirt bike and a personal watercraft. That is one customer with several units, not three customers. Units sold or traded must come off the record, or service and marketing will keep talking about a machine they no longer own.
  • Households are not duplicates. Two riders at one address, or a couple sharing one email, are separate customers. Merging them mixes up units, consent and deal history.
  • The parts counter and service drive create records too. Counter sales and service write-ups are often where duplicates start, because they are entered quickly by people outside the sales process. The standard has to cover them.
  • Seasonal addresses and changing numbers. Riders move, keep a seasonal address or switch numbers. Ask "Is this still the best number?" at every visit, not only when a message bounces.
  • Lost reasons are data too. Larry's list of why deals stall (price, payment, trade value, credit) is only useful if it is captured the same way every time. He wanted those options "made easy for the salesperson to enter into their CRM with the push of a button."

Permissions are data quality, not a marketing afterthought.

Federal telephone rules show why the record matters. Under the FCC's TCPA rules at 47 CFR 64.1200, calls or texts that include an advertisement or are telemarketing, made with an autodialer or an artificial or prerecorded voice, need the called party's "prior express written consent." A customer may revoke consent "by using any reasonable method," and the rule says revocations must be honored "within a reasonable time not to exceed ten business days." For company-specific do-not-call lists, a request "must be honored for 5 years from the time the request is made."

For your data standard, that means:

  • Record each permission separately for text, email and phone, with the date and how it was given.
  • Log changes rather than overwriting them, so you can show when a customer opted in or out.
  • Treat an opt-out in any form (a reply, a call, a remark at the service desk) as data that must reach the record the same day.
  • Never let a merge, import or integration reset an opt-out.

State laws can add more. This is general information, not legal advice; check your own process with counsel. For how to use permitted data in messages customers welcome, see personalized marketing for powersports dealers.

Retention and security

Clean data is also data you keep only as long as you need it, and protect while you have it. The FTC's guide to its Safeguards Rule lists elements such as implementing and periodically reviewing access controls, and securely disposing of customer information "no later than two years after your most recent use of it to serve the customer," unless there is a legitimate business need or legal requirement to keep it. The FTC says whether a business is covered depends on "the types of activities your business undertakes." Ask your counsel whether and how it applies to your store. This is general information, not legal advice. Credit applications are the most sensitive records most stores hold, so before adding a tool that stores them, read our questions for automated form fill software for powersports dealers.

Who can see and export customer data is part of the CRM administrator's job. Our guide to the CRM administrator role at a dealership covers users, permissions and the weekly routine. If you are choosing a new system, get the export terms in writing first; our questions to ask CRM vendors about data export cover format, timing and cost.

Who owns updates

Data stays current only if every role knows which fields are theirs.

  • Salespeople and BDC: contact details, preferred channel, unit of interest, stage, next action and lost reason, updated at every contact.
  • Sales or BDC manager: the owner on every lead, and a review of lost reasons before a customer is let go. Larry's point was that "sales managers need to get notified first so that they can intervene and save the sale if possible."
  • Service advisors and parts counter: contact checks at every visit, units owned (with VIN), and any trade or upgrade interest passed to sales.
  • Business office and F&I: legal name, address and units at delivery, and removal of traded units.
  • CRM administrator: the written standard, duplicate merges, permission changes from imports and the monthly cleanup.

Monthly data cleanup checklist

Run the same checks every month, in the same order, so the numbers can be compared. Use this as the checklist:

  • Records created this month that are missing a working phone or email
  • Open leads with no owner, and open opportunities with no dated next action
  • Phone numbers and emails not in the standard format
  • Bounced emails and numbers reported as wrong or disconnected
  • Possible duplicates: same mobile, same email, or same last name and ZIP code
  • Merges completed, with permissions and history checked on each
  • Opt-outs and do-not-contact requests received this month, and confirmation they are on the record
  • Units sold or traded that still show as owned
  • Lost reasons left blank or set to "other"
  • Records past your retention period, reviewed with management before anything is deleted
  • A note of the three most common problems, and which entry point they came from

Track a few numbers month to month, such as the share of open leads with a working mobile number and the count of duplicates found. Fix the entry point that keeps producing errors rather than cleaning the same mess every month. The same data underpins your customer retention rate: duplicates and stale units make retention look better or worse than it is.

Where PSX Ascend fits

Data quality is a habit first, but software should make the right habit the easy one. As Larry put it, "Make it easy for them, automate much of their sales process - and they'll use it."

PSX Ascend's AI-powered powersports CRM brings customer, communication and historical data into a connected view with less manual entry, across one rooftop or many. The PSX process requires quality notes and accurate dispositions when a sale does not happen, because quality data comes first: AI on a broken process only speeds up the broken process. ALMA, the Automated Lead Management Assistant, then works stalled prospects back to a live conversation with a person, using the context in the record. For the stages and owners that data supports, see the powersports CRM process that makes it work, and for getting staff to follow the standard, our CRM training plan for dealership staff.

You can also see the same AI-powered powersports CRM on our sister site, PSXDigital's AI-powered powersports CRM page.

Sources

Written and editorially reviewed byPSX Ascend Editorial Team

The PSX Ascend Editorial Team covers connected dealership operations, CRM workflows, inventory intelligence, marketing automation, and powersports website performance.

This guide is designed to help powersports dealership teams evaluate real operating workflows. It avoids unsupported performance guarantees and should be adapted to each dealership's people, policies, and technology.

Last reviewed and materially updated .

Questions dealers ask

Frequently asked questions.

Short answers about customer data for powersports dealership teams.

Ask a PSX Ascend specialist
01What is customer data quality at a dealership?

It is how usable your customer records are: complete enough to act on, entered in a consistent format, free of duplicates, clear about what the customer has agreed to, and kept current by a named owner. A good test is whether a colleague could pick up any record tomorrow without asking the customer to repeat themselves.

02What fields should be required in a dealership CRM?

Keep the required list short: name, at least one working contact method, lead source, unit of interest, a named owner, the stage and a dated next action. Add permissions per channel before any marketing message, and units owned, address and VIN at delivery or service.

03How do you prevent duplicate customer records?

Search before you create, by mobile number first, then email, then last name and ZIP code. Update the existing record when you find a match, flag uncertain matches for review instead of guessing, and set lead integrations to match on phone or email before creating new records.

04How often should a dealership clean its customer database?

Merge obvious duplicates weekly and run a full cleanup checklist monthly: missing fields, formats, bounces, duplicates, opt-outs, sold units and blank lost reasons. Track the same few numbers each month so you can see whether entry habits are improving.

05What should happen to consent when two customer records are merged?

The merged record should keep the strictest permission from either record. Any opt-out or do-not-contact request on either record stays in place, along with its date. This is general information, not legal advice.

Put it to work

See how PSX Ascend connects the next customer conversation.

Bring one real lead, inventory, or follow-up workflow into a focused walkthrough with the PSX Ascend team.

Request a demo