> ## 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 form by email

> Give a form its own email address: partners send or BCC it with the details, Introw fills in and submits the form, and replies with the result.

> Partners already email your team about every deal.
> Give the form its own address, and the email they were sending anyway becomes the registration.
> They BCC the address, Introw fills in the form, and they get an answer in the same thread.

## What you'll achieve

Every form gets an address like `acme.dealreg@bcc.introw.io`.
A partner sends it, or BCCs it on the email to their account executive, with the details written however they like.
Introw reads the email, submits the form, and replies to the sender with what it registered.
The partner manager and the partner team are copied on every reply.
When a required detail is missing or invalid, nothing is submitted: the reply lists what to fix, and the partner's answer in the same thread completes the submission.

## Before you start

<Steps>
  <Step title="Set a portal subdomain">
    The address starts with your portal subdomain, so it is unique to your organization.
    Set one in [Portal settings](https://app.introw.io/settings/portal) if you don't have one yet.
  </Step>

  <Step title="Build and publish the form">
    Any form works: deal registration, lead sharing, MDF requests, support.
    See [Build and publish a form](/features/forms/form-builder/guides/build-and-publish-a-form).
  </Step>
</Steps>

## Steps

### Get the form's email address

<Steps>
  <Step title="Open the form's Share dialog">
    Go to [Forms](https://app.introw.io/forms), open the row menu on the form, and select **Share**.
  </Step>

  <Step title="Switch to the Email tab">
    The tab shows the form's address: your subdomain, the editable part, and `@bcc.introw.io`.
    The editable part starts from the form name, for example `deal-registration`.
  </Step>

  <Step title="Rename it to something partners remember">
    Type a new name such as `dealreg` and press **Save**.
    Use lowercase letters, numbers and single hyphens.
    Every form in your organization needs its own name.
  </Step>

  <Step title="Share it with your partners">
    Select **Copy email address** and add it to your partner onboarding, your portal, or your email signature.
    Renaming the address later stops the old one from working.
  </Step>
</Steps>

### What a partner does

<Steps>
  <Step title="Send or BCC the address">
    The partner writes a normal email with the details and sends it to the address, or BCCs it on the email they already send to your team.
    The subject and the body are both read, so "New deal: Globex, 120 seats, about 98k, closing end of Q1" is enough.
  </Step>

  <Step title="Get the result in the same thread">
    A confirmation lists what was registered and whether it is accepted or waiting for your review.
    Replies to the confirmation go to the partner manager and the partner team.
  </Step>

  <Step title="Answer a correction request">
    When a required field is missing or a value is invalid, the reply lists each field and what is wrong.
    The partner answers in the same thread, and Introw submits the form with their earlier email and the answer combined.
  </Step>
</Steps>

## Who the submission belongs to

The email is attributed exactly like the general form link.
Introw matches the sender to a partner through their portal access, then through their email domain.
A sender it cannot match still submits, unattributed, and waits in your inbox like any other unattributed submission.

When someone on your team forwards a partner's email to the address, the partner who wrote the forwarded email becomes the submitter.
If the forwarded sender can't be read, the submission lands unattributed and the reply goes to the person who forwarded it.

## Verify it worked

Open [Submissions](https://app.introw.io/submissions).
The emailed submission appears with the partner it was attributed to, and runs the same approval steps and CRM automation as a portal submission.

## Limits & gotchas

<Warning>
  Partner selection, CRM record pickers, file uploads, quote selection and batch upload can't be filled in by email.
  When one of them is required, the reply sends the partner to the form link instead.
</Warning>

* **Only verified senders are processed.** An email whose sender fails SPF and DKIM checks is ignored and gets no reply.
* **Automatic replies are ignored.** Out-of-office messages, bounces and mailing-list copies never create a submission or a reply.
* **One email is one submission.** Each new email to the address submits the form again, so partners should reply in the thread only to answer a correction request.
* **The address follows your subdomain.** Changing your portal subdomain changes every form's address.


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