Opportunity flow
Track warm paths through momentum, request, introduction, and outcome.
Request intro
Turn a ranked connector recommendation into an intro request with enough context to be useful.
Track requests
Follow intro status, delays, and response patterns instead of treating a request as a black box.
Intro outcomes
Feed success and failure back into connector reputation and ranking.
Best practices
Keep requests honest, contextual, and worthy of the connector’s effort.
Core workflow
- discover or save a promising path
- decide whether the path is ready or still warming up
- create a request from a strong path
- monitor whether the connector engages
- track the result and learn from it
- use outcomes to improve future ranking
Opportunity Flow
Opportunity Flow is the best view when you are managing several warm paths at once. Use it to see path strength, mission fit, current status, last update, next step, and recommended moves.Request Intro
The compose flow should prefill the target, the suggested connector, and enough context to help the user move quickly without losing nuance.Track Requests
Tracking matters because connector performance changes over time. A request record should help users understand not just whether something was sent, but whether it was accepted, ignored, delayed, converted, or stalled.Intro Outcomes
Intro outcomes are one of the best sources of truth for future ranking. They should feed back into connector reputation, reliability, and context-fit scoring.Best practices
- prefer the strongest credible connector, not just the closest one
- give the connector enough context to decide
- do not spam weak paths
- use outcomes to refine future ranking