> ## Documentation Index
> Fetch the complete documentation index at: https://docs.introw.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Referrals

> Turn partner introductions into tracked CRM pipeline with off-portal referrals, first-touch attribution, auto status updates, and automated referral fees.

export const Headless = ({children, intro = true}) => {
  const [copied, setCopied] = useState(null);
  const copy = event => {
    const row = event.target.closest("li");
    if (!row) return;
    const text = row.textContent.trim();
    try {
      navigator.clipboard?.writeText(text);
    } catch {}
    setCopied(text);
    setTimeout(() => setCopied(null), 1600);
  };
  return <>
      {intro ? <p>
          Introw is <strong>headless</strong> by design: run everything here in plain language from Claude, ChatGPT,
          Slack, Teams, or your own CRM through Introw's <a href="/features/developer/mcp">MCP server</a>, with every
          action written straight back to your CRM source of truth. The portal is one surface, never the only one.
        </p> : null}

      {children ? <div className="not-prose" data-prompts="block">
          <div data-prompts="head">
            <span>{copied ? "Copied" : "Try it from your LLM"}</span>
          </div>
          <div data-prompts="rows" onClick={copy}>
            {children}
          </div>
          <a href="/headless/prompts" data-prompts="more">
            See all prompts
          </a>
        </div> : <Card title="See the headless motion" icon="wand-magic-sparkles" href="/headless">
          The agentic motion - lifecycle deep dives and a Claude Code skill library that run your partner program from
          Claude, ChatGPT, Slack, and your CRM.
        </Card>}
    </>;
};

export const Rail = ({children}) => <div className="not-prose" data-overview="rail">
    {children}
  </div>;

export const Impact = ({children}) => <div className="not-prose" data-overview="impact">
    {children}
  </div>;

export const Personas = ({children}) => <div className="not-prose" data-overview="personas">
    {children}
  </div>;

export const Pains = ({children}) => <div className="not-prose" data-overview="pains">
    {children}
  </div>;

> A referral program lives or dies on friction and trust. Introw lets partners refer a named deal from wherever they already work, keeps them updated automatically as your team runs the sale, and pays referral fees and revenue share without a spreadsheet, so referrers keep referring.

## The problem it solves

<Pains>
  | Without Introw | With Introw |
  | - | - |
  | Referring means logging in | A link, an email, an assistant |
  | It goes silent after the intro | Updates arrive as it moves |
  | Credit gets disputed | Attribution is set at the source |
  | Fees are worked out by hand | Calculated from the closed deal |
</Pains>

## Impact

A referral partner has one question: will my intro be honoured. Answering it with automatic updates and a payout they can trace is what turns one referral into a habit.

<Impact>
  for your business

  * **In your CRM**
    A referral lands as an attributed lead, and once partner-qualified it becomes the opportunity, account and contact your team works
  * **No new tool**
    Partners refer from a link, your site, their inbox, or an AI assistant, never from a forced portal
  * **Trustworthy**
    Conflict screening runs before anything credits, and payouts reconcile to the CRM deal that earned them

  for your partners

  * **Self-serve**
    They refer, follow the deal on a shared pipeline and see what they earned, without emailing anyone
  * **Enabled**
    Automatic progress updates mean they can answer their own prospect about where things stand
  * **Efficient**
    A few details at the moment they think of it, rather than a form after a login

  [A day in the life of a referral partner](/days-in-the-life/referral-partner)
</Impact>

<Personas>
  * **Partner Managers** - referrers who stay warm
  * **Your own reps** - clean pipeline to work
  * **Referral partners** - status and earnings, unasked
</Personas>

## How this area works

Referrals is the motion where a partner makes a warm introduction and your team closes the deal. A referral usually enters as a **lead**: a warm intro to a named prospect. The partner submits it off-portal through a link, an embedded form, an email, or an AI assistant - no login, only a few details. It is attributed to the referring partner from the first touch.

A warm intro becomes tracked pipeline and an automatic reward.

**Where this sits in a setup.** The [referral track](/tracks/referral) is this area end to end, and the [affiliate track](/tracks/affiliate) is the same motion when the reward is per click rather than per introduction.

<Rail>
  * ![A referral form in the builder, asking who is referring and who is being referred, with each field mapped to a CRM property.](https://assets.introw.io/docs/features/referrals/lead-sharing/shots/lead-form.png)

    [**Lead Sharing**](./lead-sharing)

    Refer from a link, a site, an inbox or an assistant.

    [How to · 2 guides](./lead-sharing/technical)

  * ![The Channel Conflict Analysis automation on a registration form, screening a referred deal against the CRM before it is accepted.](https://assets.introw.io/docs/features/referrals/channel-conflict/shots/analysis.png)

    [**Channel Conflict**](./channel-conflict)

    Screened against your pipeline before it credits.

    [Read more](./channel-conflict)

  * ![A deal opened from the shared board, with its CRM properties, the partner attributed to it and the conversation both companies work in.](https://assets.introw.io/docs/features/co-selling/shared-pipelines/shots/deal.png)

    [**Shared Pipeline**](/features/co-selling/shared-pipelines)

    A live view of the deals they sourced.

    [How to · 7 guides](/features/co-selling/shared-pipelines/technical)

  * ![The deal-update notification as the referring partner receives it, showing what changed on the deal they shared.](https://assets.introw.io/docs/features/referrals/deal-updates/shots/signal.png)

    [**Deal Progress Updates**](./deal-updates)

    The referrer hears as your team moves it.

    [How to · 1 guide](./deal-updates/technical)

  * ![The Reward step of a commission plan, setting whether a referrer earns a fixed fee or a percentage and how often it pays.](https://assets.introw.io/docs/features/referrals/rewards/shots/reward.png)

    [**Referral Rewards**](./rewards)

    A fee or revenue share, paid on the closed deal.

    [How to · 1 guide](./rewards/technical)
</Rail>

Then the referral is treated as **partner-qualified**: the partner marks it qualified, or your team accepts it. Introw goes further and creates the full deal context - the opportunity, its account and the contact. Now it's real, worked pipeline, still attributed. As your direct team moves the opportunity forward, update notifications keep the referrer in the loop, so they never chase you for status. When it closes, referral fees and revenue share are calculated and paid through commission plans tied to partner attribution.

The mechanics build on Introw's forms, notifications, and commissions, framed for the referral motion: low-friction sourcing, automatic follow-through, and trustworthy payout.

## Run it from your AI assistant

<Headless>
  * Share a lead for Acme: contact [john@acme.com](mailto:john@acme.com), interested in the enterprise plan.
  * Show all shared leads still pending review.
  * What reward is owed on the referral that just closed?
</Headless>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.