Integration means more than “we connect”
Ask what the integration reads, what it writes, how often it syncs, and which events stop automation. A vendor logo on a slide does not tell you whether the appointment is visible to the desk or whether the customer gets contacted twice.
Map the data contract
Document every field the AI receives and creates. Separate required data from convenient data. Customer financial information, service history, recordings, and free-form notes deserve different access and retention rules.
- Source system and field
- Read or write permission
- Purpose and business owner
- Retention and deletion rule
- Failure and retry behavior
Test operational edge cases
Use a sold vehicle, duplicate lead, wrong phone number, do-not-contact record, transferred lead, manager takeover, and appointment change. Confirm the systems converge on one truth.
Give the manager a reconciliation view
The pilot report should reconcile vendor activity to CRM outcomes. If 90 appointments exist in the vendor dashboard and 61 exist in the CRM, the missing 29 are an implementation problem, not a reporting footnote.
Sources + further reading
This field note synthesizes the sources below with Dealer AI Partners’ implementation framework.
Educational information only. Dealership workflows involving customer data, communications, credit, recording, privacy, or employment should be reviewed with qualified legal, compliance, security, and technology advisers.