Where will users work?
Confirm standalone access, authenticated handoff or an embedded interface.
CRM INTEGRATION
A useful connection needs more than a contact import. Define what moves, how it matches, and which system owns the next step.
CONNECTION SCOPE
| Information | Intended direction | What must be verified |
|---|---|---|
| Contact & relationship context | CRM → campaign workspace | Stable IDs, source, ownership and refresh frequency |
| Campaign activity | Delivery provider → workspace → CRM | Sends, deliveries, bounces, opens and clicks; event matching and delay |
| “No email” restrictions | Honor across connected systems | Opt-outs, bounce restrictions and protection against re-import |
| Replies & meetings | Verified mailbox/calendar → relationship record | Identity, owner, attribution and pause/resume rules |
| Next actions | Agreed workflow → CRM | Assignment, due date, completion and duplicate prevention |
This is a connection specification for evaluation, not a claim that every mapping is live for every CRM. The internal BKLM environment is the initial pilot; broader CRM adapters require separate validation.
CRM FIT DISCUSSION
Confirm standalone access, authenticated handoff or an embedded interface.
Define ownership, duplicate matching, retries and the system of record.
Agree on a test contact, an event trail, expected update timing and administrator visibility.