AI-to-CRM handoff: open the right customer record

A staff member finishes reviewing an AI call or text and decides the customer needs a person. The next step usually happens in the dealership CRM. That is where notes, tasks, and sales history live.

The trouble starts with the search box. Customers share names. Phone numbers change. A household may use one email address. A rushed lookup can land on a different person, an old duplicate, or a record that belongs to a sister store.

The consequence is quiet but real. Notes get attached to the wrong profile. A manager sees activity on a record that has nothing to do with the conversation just reviewed. The customer who needed attention still has nothing logged against their own record.

An AI-to-CRM handoff should close that gap. Our view is narrow on purpose: a CRM shortcut is useful only when it resolves the correct customer within the current store. Clicking it is not proof that anyone completed follow-up.

TrafficDriver's Work in CRM button is built around that rule.

Operational walkthrough: how Work in CRM picks a record

It starts from the store you are signed into

When a customer view loads in the dashboard, the page asks the server which CRM records belong to that customer. The server takes the dealership from the signed-in account, not from anything the page sends. It only looks at customers saved under that dealership. Demo accounts do not receive CRM links.

For a group with several rooftops, this matters. A customer from one store cannot pull a dealership CRM customer record from another.

Stored CRM IDs are checked before a link appears

TrafficDriver does not guess a match by name or phone number. It starts from CRM IDs already saved on the customer, and each ID must pass two checks.

First, the ID must exist among that dealership's CRM customer records. Second, the ID must map back to exactly one local customer in the same dealership. If two local customers carry the same CRM ID, neither gets a link for it. An ambiguous match is treated as no match.

Supported CRMs and button states

Links are built only for three CRM providers: VinSolutions, eLead, and CDK Global. Each uses a fixed profile address for that provider rather than a free-form URL.

The button reflects what the check found:

• Unsupported CRM. The button is hidden.
• No verified link. The button shows but is disabled and labeled as not linked.
• Lookup unavailable. The button is disabled and labeled temporarily unavailable, so a failed check never looks like a customer with no record.
• One verified link. Work in CRM opens that profile in a new tab.
• Several verified links. A Choose CRM record menu lists each record so staff can pick the right one.

What the button does not do

The new tab relies on the staff member's own CRM login. TrafficDriver does not sign anyone into the CRM and cannot guarantee that a given user has access to that record.

It also does not merge duplicate profiles, send outreach, confirm that a message was delivered, or record that follow-up happened. Opening a record is navigation. The work, and the note that shows it happened, still belong inside the CRM.

Practical takeaway for managers

Treat Work in CRM as a direct route to the right record, not as a completion signal. A few habits help:

• When the button says not linked, treat it as a data question. Do not search by name and pick the closest match.
• When Choose CRM record appears, pick the profile that matches the conversation, then flag the extra profile for cleanup in the CRM.
• Measure follow-up from CRM activity itself. A click only shows that someone opened a page.

For a routine around reviewing AI conversations before this handoff, see our weekly voice AI review guide.

Frequently asked questions

Does Work in CRM log staff into the dealership CRM?

No. It opens the verified customer profile in a new tab, and the staff member uses their own CRM login. TrafficDriver does not sign anyone in and cannot guarantee that a user has access to a given record.

Why is the Work in CRM button disabled for some customers?

A disabled button means TrafficDriver could not verify a CRM record for that customer in the current store, or the lookup was temporarily unavailable. Each stored CRM ID must exist in the dealership's CRM and belong to exactly one local customer there before a link appears.

Which CRMs does the AI-to-CRM handoff support?

Links are built for dealerships configured with VinSolutions, eLead, or CDK Global. For any other CRM, the button is hidden rather than pointing to a guessed address.

Does clicking Work in CRM count as completed follow-up?

No. Clicking opens a record. It does not send outreach, prove delivery, or log a task. Follow-up is complete when the work is recorded in the CRM itself.

Have a customer in your store that shows as not linked? Bring that example to a walkthrough with our team, and we will go through how the record check treats it.