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

# Submit a proposal

> Every way a partner can propose an MDF activity - link, embed, email, Slack, Teams, AI assistant, or the API - all feeding the same proposal form, attributed.

export const noun_6 = "MDF proposal"

export const verb_5 = "propose"

export const noun_5 = "MDF proposal"

export const noun_4 = "MDF proposal"

export const verb_4 = "propose"

export const noun_3 = "MDF proposal"

export const verb_3 = "propose"

export const noun_2 = "MDF proposal"

export const verb_2 = "propose"

export const noun_1 = "MDF proposal"

export const verb_1 = "propose"

export const noun_0 = "MDF proposal"

export const verb_0 = "propose"

> Every step between a partner's idea for an activity and the proposal landing against the fund costs you participation. Configure the proposal form once, then let partners propose 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 request always lands attributed to the partner against the right fund.

You configure one proposal form - with its CRM automation, partner attribution, and approval - 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="Configure the proposal step">
    A fund with its proposal form must exist, and every channel below feeds it. Set it up in [Configure the proposal step](./configure-the-proposal-form), which also covers attribution and approval.
  </Step>
</Steps>

## Choose a channel

<AccordionGroup>
  <Accordion title="Share a link" icon="link">
    The lowest-friction way for a partner to propose is a link they open and fill in anywhere. A **partner-specific link** attributes every submission to that partner automatically, so the request is tied to the right allocation from the start. Prefer the partner link over the general link whenever you send the form to a known partner.

    <Tabs>
      <Tab title="Video">
        <video controls playsInline preload="none" poster="https://assets.introw.io/docs/features/mdf/requests-claims-roi/guides/request-by-link/steps/01.png?v=1783350543" className="w-full rounded-xl" src="https://assets.introw.io/docs/features/mdf/requests-claims-roi/guides/request-by-link/video.webm?v=1783350543#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/mdf/requests-claims-roi/guides/request-by-link/walkthrough.html?v=1783350543" />
      </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">
    Many partners arrive on pages you already own - a partner marketing page or portal. Embedding the proposal form there lets a partner propose in context, with your branding, without leaving the page. Where the page is partner-specific, use an attributed embed so each submission credits the right partner. 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/mdf/requests-claims-roi/guides/request-by-embed/steps/01.png?v=1783350543" className="w-full rounded-xl" src="https://assets.introw.io/docs/features/mdf/requests-claims-roi/guides/request-by-embed/video.webm?v=1783350543#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/mdf/requests-claims-roi/guides/request-by-embed/walkthrough.html?v=1783350543" />
      </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="Propose by email" icon="envelope">
    A partner often thinks of an activity to fund mid email thread. Letting them email the details captures the moment: the AI agent reads the forwarded message and fills in the proposal form for them, so it still lands attributed and against the right fund. 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="Propose from Slack" icon="slack">
    If your partners live in Slack, bringing the Introw agent into the channel lets them propose 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="Propose 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="Propose 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 proposal 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="Propose over the API" icon="code">
    When a partner plans campaigns in their own marketing tooling, the proposal can start there instead of in a form. The API submits the same proposal form from anywhere, with no browser and no login, so their system, your tooling, or an agent files the request. It lands attributed to the partner you name, against the right fund, and follows the same approval flow. 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 proposal, then confirm it appears in [Submissions](https://app.introw.io/submissions) under **Form submissions**, attributed to the right partner, against the correct fund.

## Related

<CardGroup cols={2}>
  <Card title="Configure the proposal step" icon="book-open" href="./configure-the-proposal-form">
    Build the form, attribution, and approval behind every channel.
  </Card>

  <Card title="Run the MDF lifecycle" icon="book-open" href="./run-the-mdf-lifecycle">
    Review and process the proposals that come in.
  </Card>

  <Card title="Connect an MCP client" icon="plug" href="/features/developer/mcp/guides/connect-an-mcp-client">
    Let assistants propose 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 propose headlessly.
  </Card>

  <Card title="Implementation reference" icon="screwdriver-wrench" href="../technical">
    Full proposal and submission configuration options.
  </Card>
</CardGroup>