Capture target, connector, owner, approval status and next step in an accessible workflow. Use stable identities so duplicate records do not create parallel contact.
A pending introduction may justify pausing an automated sequence to that person. Other stakeholders may still need relevant outreach. Avoid a universal rule that an entire account must use only one channel indefinitely.
Use the same problem and account understanding across introductions, events and direct engagement. Do not imply personal endorsement in a sequence simply because a connector agreed to consider a request.
When a request ends or becomes unsuitable, update the status and choose the next approach. Respect declines and preferences rather than treating every pause as temporary permission to resume.
Orbb can support relationship-led coordination. Confirm current integration and suppression behaviour directly; a useful operational policy does not mean a specific native connector already implements it automatically.