The recall data is free. The matching is the product.

Recall outreach is often sold as a data product. The federal data is already public.

NHTSA publishes recall datasets, model-level APIs, annual recall reports and a VIN lookup service supported by major manufacturers. The valuable dealership work begins after that feed arrives.

A recall record is not a customer list

The public feed can tell the group which vehicles are affected. The DMS and service history can tell it which VINs the group sold, serviced or currently associates with an owner. Those are different jobs.

The matching layer has to handle ownership changes, duplicate customers, scrapped vehicles, completed repairs, stale contact data and brand routing. It should record why each VIN matched and when the source data was refreshed.

That transparency matters because recall completion is uneven. NHTSA's annual reporting shows wide variation by campaign, manufacturer, vehicle age and remedy timing. A national average cannot tell a service manager which owners in the local database still need a repair.

Start with a preview, not a campaign

1. Ingest the recall source. Store campaign number, affected vehicle attributes, remedy status and source dates.
2. Match against the owner base. Use VIN first. Keep the last known relationship and service history visible to reviewers.
3. Suppress what should not send. Remove completed repairs, invalid contacts, recent outreach and records without the required consent or business basis.
4. Show a masked preview. Let service leadership inspect counts and examples before any message leaves.
5. Cap the flow. Route by store and appointment capacity. A successful campaign that overwhelms the lane is not successful.
6. Write outcomes back. Appointment, repair order and completion should return to the warehouse.

Keep privacy categories straight

The FTC's dealer guidance distinguishes customer financial information from some general sales, service and recall records. But commingling changes the risk. A database that includes financing details must be protected as customer information, and direct service-provider access creates oversight obligations.

That is another reason to create a limited recall tool instead of handing a messaging vendor broad database access. The tool should expose only the fields and actions required for the recall workflow.

Measure repairs, not messages

Delivered SMS is not the outcome. The operating chain is:

eligible VIN - matched owner - approved contact - appointment - repair order - completed remedy.

Every stage should have a count and a reason for fallout. That makes the workflow improvable and keeps the vendor or channel from grading its own homework.

Recall work is a good first owned activation because the facts are checkable, the public data is documented and the customer value is clear. It also teaches the group the pattern it will use everywhere else: public or internal source, governed match, controlled action, receipted outcome.

What not to automate

Do not let a match silently become a promise about remedy availability. Do not route every VIN to the nearest rooftop without checking franchise and service capacity. Do not treat an undelivered message as proof the owner is unreachable. And do not discard the match history after a campaign ends.

The durable record is the campaign, VIN, owner relationship, contact decision and repair outcome together. That history lets the store try a different channel, avoid repeated outreach and explain exactly why a customer was contacted.