All answers
How it works

What CRM fields should we use to track warm introductions?

Track warm introductions with stable target and connector identities, account, source group, dates, approval and delivery statuses, owner and outcome. Link the introduction to an opportunity where appropriate. Keep relationship evidence and permissions accessible without copying unnecessary sensitive information into broad CRM fields; one free-text connector name is a start, not a complete reporting model.
October 8, 2026

Use a minimal operational record

Capture who requested the introduction, who may connect, whom they are introducing and the business purpose. Record approval, introduction sent, meeting held and qualification separately.

Associate rather than duplicate

Use contact, account and opportunity identifiers. Preserve the partner or customer organisation independently from the individual connector. Attach evidence references where permitted.

Apply consistent attribution

Store sourced versus influenced classification and the relevant dates. Allow multiple contributions without giving each full opportunity credit. Keep the commercial policy documented outside the field list too.

Confirm implementation details

The right CRM object or custom record depends on your architecture and reporting needs. Test permissions, updates and ownership changes before rolling out.

This is a suggested data model, not a claim about Orbb's current writeback fields. Confirm the integration scope and who is responsible for entering or synchronising outcomes in your deployment.

Related questions

Orbb researches the relationships your company already has — across customers, employees, investors and partners — then runs the introduction end to end, from finding the path to the meeting in the calendar.
See it on your own accounts