> ## 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.

# Ways to refer a deal

> Every way partners can refer a deal - link, embed, email, Slack, Teams, AI assistant, or the API - all feeding one attributed referral form.

export const noun_6 = "referral"

export const verb_5 = "refer"

export const noun_5 = "referral"

export const noun_4 = "referral"

export const verb_4 = "refer"

export const noun_3 = "referral"

export const verb_3 = "refer"

export const noun_2 = "referral"

export const verb_2 = "refer"

export const noun_1 = "referral"

export const verb_1 = "refer"

export const noun_0 = "referral"

export const verb_0 = "refer"

> Every step between a partner's intent to refer and the lead landing in your CRM costs you referrals. Build the referral form once, then let partners refer through whichever entry point fits how they work - a link, an embed, email, Slack, Teams, their AI assistant, or a call from their own systems. Every channel feeds the same form, so the lead always lands attributed to the referrer.

You build one referral form - with its CRM automation, partner attribution, and conflict and duplicate checks - and then expose it through as many channels as you like. This guide covers each one. Pick the channels where your partners already are; you don't need all of them.

## Before you start

<Steps>
  <Step title="Build the referral form">
    A referral form that captures an attributed lead - and, when partner-qualified, creates the opportunity, account, and contact - should already exist, and every channel below feeds it. Build it in [Build and share a referral form](./build-and-share-a-referral-form), which also sets up attribution and channel-conflict checks.
  </Step>
</Steps>

## Choose a channel

<AccordionGroup>
  <Accordion title="Share a link" icon="link">
    The lowest-friction way for a partner to refer is a link they open and fill in anywhere. A **partner-specific link** attributes every submission to that referrer automatically, so credit is never in question. Prefer the partner link over the general link whenever you send the form to a known referrer.

    <Tabs>
      <Tab title="Video">
        <video controls playsInline preload="none" poster="https://assets.introw.io/docs/features/referrals/lead-sharing/guides/share-a-referral-link/steps/01.png?v=1783349670" className="w-full rounded-xl" src="https://assets.introw.io/docs/features/referrals/lead-sharing/guides/share-a-referral-link/video.webm?v=1783349670#t=2.5" />
      </Tab>

      <Tab title="Click through">
        <iframe className="w-full rounded-xl" style={{ width: "100%", aspectRatio: "16 / 11", border: 0, backgroundColor: "#FAFAFA" }} src="https://assets.introw.io/docs/features/referrals/lead-sharing/guides/share-a-referral-link/walkthrough.html?v=1783349670" />
      </Tab>
    </Tabs>

    <Steps>
      <Step title="Open the form's share dialog">
        In [Forms](https://app.introw.io/forms), open your {noun_0} form and open its **Share form** dialog.
      </Step>

      <Step title="Copy the link">
        On the **Link** tab, copy the general link to share with anyone, or the partner link to attribute every submission to a specific partner.
      </Step>

      <Step title="Send it to partners">
        Drop the link into an email, a portal message, a Slack channel, or anywhere your partners already are. A partner link credits that partner every time they {verb_0} a deal.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Embed on your site" icon="window-maximize">
    Some partners and prospects arrive on your own pages. Embedding the referral form there captures referrals in context, with your branding. Where the page is partner-specific, use an attributed embed so each submission credits the right partner instead of arriving anonymous. Embedding requires a custom domain; without one, share the link instead.

    <Tabs>
      <Tab title="Video">
        <video controls playsInline preload="none" poster="https://assets.introw.io/docs/features/referrals/lead-sharing/guides/embed-a-referral-form/steps/01.png?v=1783349670" className="w-full rounded-xl" src="https://assets.introw.io/docs/features/referrals/lead-sharing/guides/embed-a-referral-form/video.webm?v=1783349670#t=2.5" />
      </Tab>

      <Tab title="Click through">
        <iframe className="w-full rounded-xl" style={{ width: "100%", aspectRatio: "16 / 11", border: 0, backgroundColor: "#FAFAFA" }} src="https://assets.introw.io/docs/features/referrals/lead-sharing/guides/embed-a-referral-form/walkthrough.html?v=1783349670" />
      </Tab>
    </Tabs>

    <Steps>
      <Step title="Open the share dialog">
        In [Forms](https://app.introw.io/forms), open your {noun_1} form and open its **Share form** dialog.
      </Step>

      <Step title="Switch to the Embed tab">
        On the **Embed** tab, copy the generated HTML snippet.
      </Step>

      <Step title="Paste it on your page">
        Add the snippet to the page where you want partners to {verb_1}, such as a partner landing page or a website footer.
      </Step>

      <Step title="Attribute where possible">
        Where you know the partner, use an attributed embed so each submission credits the right partner instead of arriving anonymous.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Refer by email" icon="envelope">
    A partner often spots an opportunity mid email thread. Letting them forward that email captures the lead, with the AI agent filling in the referral form so it still lands attributed and CRM-ready. The [AI agent](/features/ai/partner-support) must be enabled for your program.

    <Steps>
      <Step title="Set up the partner support email">
        Confirm your partner support email address is active. Partners forward a lead to it, and the AI agent reads the email and submits the {noun_2} for them.
      </Step>

      <Step title="Tell partners they can email">
        Share the address and a short note that they can forward a prospect with a sentence of context to {verb_2} a deal, no portal needed.
      </Step>

      <Step title="Let the agent fill the form">
        The agent maps the email into your {noun_2} form, so the deal still lands attributed and CRM-ready.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Refer from Slack" icon="slack">
    If your partners live in Slack, bringing the Introw agent into the channel lets them refer in the same place they already talk to your team. Connect your workspace first - see [Connect Slack](/features/integrations/chat/guides/connect-slack).

    <Steps>
      <Step title="Connect Slack">
        Connect your Slack workspace so the Introw agent can take {noun_3}s from chat. See [Connect Slack](/features/integrations/chat/guides/connect-slack).
      </Step>

      <Step title="Bring the agent into a channel">
        Add the Introw agent to the partner channel where deals come up.
      </Step>

      <Step title="Let partners submit from a message">
        Partners give the agent the deal details in a message, and it submits the {noun_3} through the same form flow so they can {verb_3} without leaving Slack.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Refer from Microsoft Teams" icon="microsoft">
    Same as Slack, for Teams-first channels. Connect your tenant first - see [Connect Microsoft Teams](/features/integrations/chat/guides/connect-microsoft-teams).

    <Steps>
      <Step title="Connect Microsoft Teams">
        Connect your Teams tenant so the Introw agent can take {noun_4}s from chat. See [Connect Microsoft Teams](/features/integrations/chat/guides/connect-microsoft-teams).
      </Step>

      <Step title="Bring the agent into a channel">
        Add the Introw agent to the partner channel where deals come up.
      </Step>

      <Step title="Let partners submit from a message">
        Partners give the agent the deal details in a message, and it submits the {noun_4} through the same form flow so they can {verb_4} without leaving Teams.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Refer with an AI assistant (MCP)" icon="robot">
    When a partner already works in an AI assistant, the lowest-friction path is to just ask it. An assistant connected to Introw over MCP fills in the referral form and submits it, attributed to the partner, without switching tools. See [Connect an MCP client](/features/developer/mcp/guides/connect-an-mcp-client) and, for partners running their own assistant, [Partner Connect](/features/partner-connect).

    <Steps>
      <Step title="Enable the AI agent">
        The AI agent powers assistant submissions. Confirm it is enabled for your program.
      </Step>

      <Step title="Connect an AI assistant">
        Where partners use an AI assistant connected to Introw through the [MCP server](/features/developer/mcp), they can ask it to {verb_5} a deal in plain language.
      </Step>

      <Step title="Share an example prompt">
        Give partners a short example prompt so they know they can {verb_5} a deal straight from their assistant, which calls the same {noun_5} form flow.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Refer over the API" icon="code">
    Your largest partners often want referrals to flow system to system rather than person to form. Their portal, your internal tooling, a backfill script, or an agent posts the same referral form over the API, from anywhere, with no browser and no login. The referral is attributed to the partner you name and runs the same automation, conflict checks, and approval as a form a partner filled in by hand. See [Submit a form via the API](/features/forms/sharing-submitting/guides/submit-a-form-via-the-api).

    <Steps>
      <Step title="Create an API key with Forms - Write">
        In [API keys](https://app.introw.io/settings/developers/api-keys), create a key with the **Forms - Write** permission and copy the secret once. Add **Forms - Read** if your code should also fetch the form's field schema. See [Create and manage API keys](/features/developer/api/guides/create-and-manage-api-keys).
      </Step>

      <Step title="Copy the request from the API tab">
        In [Forms](https://app.introw.io/forms), open your {noun_6} form, open **Share form**, and switch to the **API** tab. The cURL snippet there already carries this form's id and every field id, and the **Fields** table below it marks which ones are required.
      </Step>

      <Step title="Post it from your own system">
        Call the endpoint from your product, your internal tooling, a script, or an agent. Send `partnerId` so the {noun_6} is attributed to the right partner, and Introw runs the same automation, checks, and approval flow as a partner filling in the form. See [Submit a form via the API](/features/forms/sharing-submitting/guides/submit-a-form-via-the-api).
      </Step>
    </Steps>
  </Accordion>
</AccordionGroup>

## Verify it worked

Use whichever channel you set up to submit a test referral, then confirm it appears in [Submissions](https://app.introw.io/submissions) under **Form submissions**, attributed to the right partner, with a matching lead created in your CRM.

## Related

<CardGroup cols={2}>
  <Card title="Build and share a referral form" icon="book-open" href="./build-and-share-a-referral-form">
    Build the form, attribution, and conflict checks behind every channel.
  </Card>

  <Card title="Channel Conflict" icon="shield-halved" href="/features/referrals/channel-conflict">
    How each referral is screened for overlap before it credits.
  </Card>

  <Card title="Keep referrers updated" icon="bell" href="/features/referrals/deal-updates/guides/keep-referrers-updated">
    Notify referrers as their deals progress.
  </Card>

  <Card title="Connect an MCP client" icon="plug" href="/features/developer/mcp/guides/connect-an-mcp-client">
    Let assistants submit through Introw's MCP server.
  </Card>

  <Card title="Submit a form via the API" icon="code" href="/features/forms/sharing-submitting/guides/submit-a-form-via-the-api">
    Let a partner's own system, your tooling, or an agent refer headlessly.
  </Card>
</CardGroup>
