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

# Web forms

> Speed-to-lead — respond to a form submission by call, text, and email within seconds.

A lead who fills in your contact form is comparing you against two or three competitors right now. Response speed decides who wins, and the drop-off is brutal after the first few minutes.

Recepta.ai web forms respond automatically — across call, SMS, and email — the moment a submission lands.

## How it works

<Steps>
  <Step title="Create a form">
    Under **Web forms**, define the fields you want. Keep it short: name, phone, and what they need is usually enough. Every additional field costs you completions.
  </Step>

  <Step title="Put it on your site">
    Embed the Recepta.ai form, or point your existing form at Recepta.ai so submissions arrive here.
  </Step>

  <Step title="Configure the response">
    Choose what fires on submission and in what order — an outbound call from your agent, an SMS, an email, or a combination.
  </Step>

  <Step title="A contact is created">
    Every submission creates or updates a [contact](/outbound/contacts) tagged with its source, ready to be worked by a [sequence](/outbound/sequences) if nobody connects first.
  </Step>
</Steps>

## Tri-channel speed-to-lead

The strongest pattern is to hit all three channels quickly, in a sensible order:

| Timing                     | Channel | Why                                                       |
| -------------------------- | ------- | --------------------------------------------------------- |
| Immediately                | Call    | Highest chance of a live conversation while intent is hot |
| If the call isn't answered | SMS     | Lands even when they won't pick up an unknown number      |
| Alongside                  | Email   | Leaves a record with your details and next steps          |

<Tip>
  Text and email should reference the form: "Thanks for reaching out about your water heater — it's Dan from Coral Plumbing." A generic auto-reply reads as a robot; a specific one reads as attention.
</Tip>

## Consent

If you're going to call or text form submitters, say so on the form and capture the agreement. A short line beside the submit button, with a checkbox where you need explicit consent, is what a carrier or regulator will want to see.

<Warning>
  Consent captured on your form is what backs your [A2P 10DLC campaign](/phone/a2p-10dlc) and your TCPA position. Don't skip it, and keep the wording where reviewers can find it.
</Warning>

## Where submissions go

Submissions appear as contacts in the dashboard, flow into any connected [CRM](/integrations/overview), and are available over the [Contacts API](/api-reference/contacts). Subscribe to `contact.created` to push them into your own systems — see [Webhooks](/api-reference/webhooks).

## Other lead sources

The same immediate-response pattern applies to leads arriving from elsewhere:

<Card title="Facebook lead ads" icon="facebook" href="/integrations/facebook-lead-ads">
  Sync lead form submissions and work them with outbound campaigns.
</Card>