Relationship intelligence can connect to a CRM, but data ingestion, in-CRM display and writeback are separate capabilities. Ask what the current integration actually does and where users complete requests. For Orbb, confirm supported systems and permissions for your deployment; do not assume a connector writes relationships into records or eliminates every separate interface.
Separate three integration questions
- Reads: which accounts, contacts and activities can the provider access?
- Displays: where does the team see relationship research and next actions?
- Writes: which fields, objects or activities are created or updated, if any?
A read-only integration can support useful research without writing back. Conversely, automated writeback needs permission, mapping and data-quality controls.
Demonstrate the actual workflow
Use your own CRM record. Show how a rep finds a target, sees supporting evidence, requests an introduction and tracks the outcome. Test what happens when the connector declines or the account owner changes.
Keep reporting coherent
Agree stable identifiers and responsibility for activity and opportunity updates. Avoid filling the CRM with every inferred connection. Store the actionable summary and preserve deeper evidence where access is appropriately controlled.
For Orbb, request current integration documentation rather than relying on a broad list of logos. Confirm what is included in the engagement and what requires custom implementation.
The objective is a workable account process with reliable records, not simply adding another connected system.
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