Track Referral Partner Introductions and Follow-Up

Outcome: a permission-aware referral loop that records the request, connector decision, introduction, follow-through, outcome, and respectful close-the-loop update.

Use this workflow when a trusted customer, adviser, investor, operator, community member, or partner may connect two people. A known relationship is a possible path, not consent to use it. Finta can help organize warm-introduction pathways and related follow-through, but it is not a referral commission, partner portal, deal-registration, or channel-attribution system.

Inputs

• The requester, target, and possible connector
• A specific reason the introduction may benefit both sides
• Current identity and relationship evidence
• The connector's preferred request channel and sharing boundary
• Approved context that may be forwarded
• The relevant CRM contact, opportunity, or partnership record
• Any legal, privacy, conflict, or program requirement

Referral event ledger

Track the loop as events instead of compressing it into one ambiguous status.

Do not convert this ledger into an unsupported commission or revenue-attribution claim. If a formal program administers rewards or registered referrals, keep that program as the authoritative system.

Run the workflow

1. Verify the identity, current role, and relevance of the requester, target, and connector.
2. Write a one-sentence mutual-value hypothesis. If the introduction primarily benefits the requester, revise the ask or stop.
3. Ask Aurora to gather permitted relationship, CRM, meeting, message, task, and document context through supported tools.
4. Inspect any available Finta Network path. Treat it as a research lead, not permission, relationship strength, or proof that the connector will make the introduction.
5. Prepare a connector-first request that makes declining easy. Include only approved, forwardable context.
6. Have the relationship owner review the connector, timing, disclosure, and draft before sending.
7. If the connector agrees, record the introduction event and create the smallest useful follow-up task. Do not bypass the connector or add new recipients without permission.
8. Record the outcome from evidence, then close the loop with the connector at an appropriate level of detail.

Aurora prompt

Review this proposed referral using the permitted CRM, Network, meeting, message, task, and document context available to you. Verify the three parties, explain why the path may be relevant, identify stale or conflicting evidence, and prepare a connector-first introduction request for review. Make the request easy to decline and include only context marked as forwardable. If an introduction occurs, propose follow-up tasks and a concise close-the-loop update. Do not infer consent, relationship strength, confidentiality permission, or commercial attribution. Do not send a message, add a recipient, or make a commitment without approval.

Aurora can inspect supported records, synthesize context, research public information, prepare drafts and tasks, propose changes, and complete eligible actions within available tools and permissions. Human review remains necessary for identity, appropriateness, disclosure, and consequential external communication.

Worked example

A founder wants an introduction to the operations leader at a regional employer. Finta Networks shows that an adviser appears connected to the leader. Recent CRM history confirms the founder spoke with the adviser last month, but it does not establish how well the adviser knows the target or whether the adviser is comfortable making an introduction.

Aurora assembles the permitted context, flags that uncertainty, and prepares a short request explaining the employer-specific value of a conversation. The draft asks whether the adviser knows the target well enough to consider an introduction and makes clear that declining is fine. It includes a three-sentence forwardable note but omits a confidential customer example.

The founder reviews and sends the request. The adviser agrees, edits the forwardable note, and makes the introduction. Finta records the pathway as in progress, creates a follow-up task after the recipient responds, and later records the outcome as a useful discovery conversation rather than attributed revenue. The founder sends the adviser a brief thank-you and outcome update that reveals no confidential detail.

Completion checks

• All three parties have verified identities and current roles.
• The mutual-value hypothesis is specific and credible.
• The connector explicitly chose whether to participate.
• Only approved, forwardable context was shared.
• The introduction and outcome are separate events.
• Follow-up has a clear owner and respectful stop condition.
• The connector received an appropriate close-the-loop update.
• No consent, commission, or revenue attribution was inferred.

Safe stops and limitations

Stop when identity, relationship freshness, connector comfort, information-sharing permission, conflict, or recipient relevance is unclear. A network import may show an old or indirect edge. Communication sources can be incomplete. A declined or unanswered request should not trigger repeated outreach or an attempt to bypass the connector.

Finta tracks introduction pathways with operational statuses, but it does not verify personal trust, guarantee a response, administer referral payouts, or prove that later revenue was caused by the introduction.

Sources

• Finta Networks
• Finta CRM
• Finta Aurora
• Finta warm-introduction workflow
• Salesforce referral data model
• Microsoft referral resource

Make warm introductions easier to operate well

Keep the path, permission, follow-through, and outcome connected. Explore Finta for referral partner management.