The useful context is already in the CRM tab
A follow-up draft often begins with a lead that is already open. Asking the employee to copy the lead into LotPro loses time and creates another chance to select the wrong vehicle or stage. The better handoff is narrower. Carry the context needed to start the message, then leave the CRM record where it is.
On a supported page, Companion can now open a template draft from the selected CRM lead or vehicle. The draft receives targeting metadata for stage, target, source, and event. The message remains a reusable template rather than becoming a copy of one customer record.
A handoff should show its assumptions
The editor makes inherited targeting visible. Staff can review it, change it, or clear it while keeping the template text. That matters because a CRM label can be useful context without being the final audience decision. The interface should expose the assumption instead of quietly turning it into a rule.
- Recognize the supported CRM page first
- Carry only the fields needed for the draft
- Show inherited stage, target, source, and event filters
- Let staff clear targeting before saving
It still stops before autonomous outreach
The handoff prepares work. It does not send email or SMS by itself. Staff review the content, targeting, and next action. DriveCentric currently has the broadest adapter coverage, while AutoHub support is narrower and page-specific.
This remains a preview workflow. A page redesign can change what Companion recognizes, and a missing field should stop the handoff rather than invite a guess. The right test is whether the employee can explain why this template opened for this lead before using it.