Direct answer: A prioritized review queue of active relationships that lack an accountable next step, owner, or date.
Execution mode and verification status
Reviewed operating recipe. The workflow creates a candidate queue from the records and evidence a reviewer can access; it does not claim a proprietary priority score or trigger automatic outreach.
The outcome this workflow produces
A prioritized review queue of active relationships that lack an accountable next step, owner, or date.
| Input | What to verify | Output |
|---|---|---|
| CRM contacts | Active scope and owner | Candidate review set |
| Email and calendar evidence | Latest verified interaction | Recency context |
| Pipeline state | Stage meaning | Priority and next step |
Run the workflow
- Define which pipeline stages should always have a next step.
- Filter out archived, passed, duplicate, and explicitly paused relationships.
- Identify contacts with no open task, dated commitment, or scheduled meeting.
- Apply a human review rubric for fit, relationship strength, recency, and current timing.
- Assign a human owner to review each candidate and choose the appropriate action.
Worked example
Example: Jordan is in an active investor stage, the latest visible meeting was twelve days ago, and no open task, dated commitment, future meeting, or pause reason exists. Jordan enters the review queue. Sam is omitted because the record contains an explicit wait-until-October decision.
Expected review receipt
- The candidate contact and current stage are visible
- The latest accessible interaction is shown
- The missing-next-step checks are listed
- The reviewer can assign, dismiss, pause, or pass with a reason
Decision checklist
- Paused relationships are excluded
- The latest interaction is visible
- No task already covers the same commitment
- Priority is based on fit and timing, not activity volume alone
- The owner can dismiss the recommendation with a reason
Where Finta helps
In a supported, permissioned setup, Finta can organize the relevant CRM record, relationship history, user-provided or connected-source evidence, and next-action workspace for the same review. Aurora can prepare a recommendation or draft; a person remains responsible for checking the evidence and approving consequential changes or communication.
Human approval boundary
A person decides whether each relationship is active, assigns the owner, and approves outreach; inactivity alone must not trigger an automatic send.
Failure states and safe stops
- Inbox or calendar evidence is unavailable
- A duplicate record hides an existing task
- The relationship is intentionally paused
- The record owner or stage meaning is unclear
Limitations
- Missing email or calendar access can make a relationship look inactive.
- A next step should not be invented when the correct decision is to stop pursuing.
- Relationship strength does not replace mandate or thesis fit.
Sources and related Finta resources
Last reviewed: August 30, 2026. Re-verify product behavior, permissions, and the approval boundary before publication and after a material workflow change.
