CRM INTEGRATION

Keep the campaign connected to the person.

A useful connection needs more than a contact import. Define what moves, how it matches, and which system owns the next step.

CONNECTION SCOPE

Confirm the data in both directions.

InformationIntended directionWhat must be verified
Contact & relationship contextCRM → campaign workspaceStable IDs, source, ownership and refresh frequency
Campaign activityDelivery provider → workspace → CRMSends, deliveries, bounces, opens and clicks; event matching and delay
“No email” restrictionsHonor across connected systemsOpt-outs, bounce restrictions and protection against re-import
Replies & meetingsVerified mailbox/calendar → relationship recordIdentity, owner, attribution and pause/resume rules
Next actionsAgreed workflow → CRMAssignment, 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

Get precise before implementation.

Where will users work?

Confirm standalone access, authenticated handoff or an embedded interface.

What happens on a conflict?

Define ownership, duplicate matching, retries and the system of record.

How will you know it worked?

Agree on a test contact, an event trail, expected update timing and administrator visibility.