> For the complete documentation index, see [llms.txt](https://help.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.distro.so/routing-forms/lead-forms.md). # Lead forms Build a branded lead form, qualify visitors with a Form Router, and collect meeting requests. Create a form in Distro, share its hosted page or embed it on your website, and let qualified visitors choose a meeting time. Lead forms use your Form Router's qualification, assignment, and CRM settings. Qualified visitors continue to scheduling with their name and email already collected. Unqualified visitors see the router's configured redirect or a request-received message. Open **Form routing → Lead forms**. Workspace admins can create, edit, publish, and review submissions. ### Before you start Configure and publish a [Form Router](https://help.distro.so/routing/form-router) with a connected [form mapping](https://help.distro.so/routing-forms/overview), an event type, and the rules and hosts needed for your routing. A lead form supplies the visitor-facing questions. The router's form mapping supplies the fields those questions can map to. You do not need an existing website form or its installation snippet to share a Distro lead form. {% hint style="info" %} **Already have a website form?** Keep using [Form mapping and provider installation guides](https://help.distro.so/routing-forms/overview) to connect it. Lead forms are for building the form itself in Distro. {% endhint %} ### Create and configure a form {% stepper %} {% step %} #### Create the draft Choose **New Form**. In the **Create lead form** dialog, enter a **Form name** and choose **Create form**. The editor opens with required Name and Email questions. The new form is an unpublished draft. {% endstep %} {% step %} #### Set the page and router Under **Page and routing**, configure: | Setting | What it controls | | -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | | **Form name** | The name used to find the form in Distro. | | **Page URL** | The final part of the hosted address, such as `/forms/request-a-demo`. Use lowercase letters, numbers, and hyphens, with 3–80 characters. | | **Form Router** | The published routing configuration used to qualify and assign visitors. | | **Heading** and **Introduction** | The title and introductory text visitors see. | | **Submit button label** | The text on the form's submit button. | Choose your **Form Router**, then **Save draft** to load its published field mappings. {% endstep %} {% step %} #### Add questions and map answers Under **Questions**, choose a **Question type**, then **Add question**. Set the **Question label**, **Router field mapping**, and whether an answer is **Required**. | Question type | Available settings | | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | | **Name**, **Email** | Included by default and required for booking. You can change their labels and mappings, but cannot remove them or make them optional. | | **Phone**, **Short text**, **Long text** | Collect additional visitor information. | | **Number** | Optionally set a minimum and maximum. | | **Dropdown** | Add unique choices, one per line. | | **Checkbox** | Collect a yes/no answer. A required checkbox must be checked to continue. | A form supports up to 30 questions, including Name and Email. Use **Move up**, **Move down**, and **Remove** to organize additional questions. Map answers to the fields your router or CRM needs. Each router field can be mapped only once. Leave other questions as **Submission only** to retain their answers without mapping them to CRM properties. If HubSpot or Salesforce is connected, map the Email question to the router field connected to the CRM's Email property before publishing. {% endstep %} {% step %} #### Choose the design Under **Design**, set the **Question layout**: | Layout | Visitor experience | | -------------------------- | --------------------------------------------------------------------------------------- | | **Full-page form** | Shows the questions together below the introduction. This is the default for new forms. | | **Split introduction** | Separates the introduction and questions on wider screens. | | **One question at a time** | Guides visitors through questions individually. | Choose **Typography**, **Appearance**, and **Color mode**. Use **Brand theme** to select a published booking theme or **Workspace default**. The logo and cover image come from that theme. See [Booking themes](https://help.distro.so/settings/workspace-settings/branding). Enable **Customize colors for this form** to set the light and dark colors for its accent, background, cards and fields, text, and borders. Use **Desktop** and **Mobile** in **Live preview** to check the design. Click a question's edit button in the preview to open its settings. {% endstep %} {% endstepper %} ### Preview and publish {% stepper %} {% step %} #### Save and preview the draft Choose **Save draft**, then **Preview saved draft**. Fill out the form to review validation and the simulated routing and scheduling journey. The editor's live preview checks design. The saved-draft preview simulates the journey without creating a submission, CRM update, invitation, or real booking. CRM ownership and enrichment use no live lookups, so this preview does not verify live integrations or calendar availability. {% endstep %} {% step %} #### Publish the saved version Choose **Publish saved draft** when ready. Publication checks that the router is published and has a form mapping and meeting type, that selected question mappings exist in that published router, and that the page URL is available. With a connected CRM, the Email question must map to the CRM Email field. Saving alone does not update the public form. Preview and publication use the last saved draft. {% endstep %} {% step %} #### Share and check the live journey Under **Share the published form**, copy the **Hosted page** link or choose **Open published page**. To place the form on your website, copy **Website embed**. See [Embed a lead form](https://help.distro.so/routing-forms/lead-forms/embed). Use controlled test details to check qualified and unqualified submissions on the published form, including the scheduler, configured redirects, and CRM delivery. A live submission runs the configured routing and CRM actions; completing a booking can send invitations. {% endstep %} {% endstepper %} ### Update a published form Edit the form and **Save draft** while the existing published version remains available. Choose **Publish saved draft** to make the saved questions, design settings, and routing selection live. Each publication uses the router version that is published at that time. **After publishing changes to the Form Router, republish the lead form to adopt that router version.** When the Page URL is unchanged, visitors with an already-open form continue with the version they loaded. Changes published to the selected brand theme can also update the form's inherited appearance without republishing the form. If you publish a different **Page URL**, update your shared links and website embeds. The old address is not retained as a redirect. ### Review submissions Open the form's **Submissions** action. This list includes submissions across all published versions of the form. Answers are saved when the visitor successfully submits the form, before routing and booking finish. You can therefore follow up with someone who submitted their answers but left before choosing a time. Answers are not captured while someone is still filling out an unsubmitted form. Use **Search answers...** in the subheader to search by name, email, or another submitted answer. Add an **Outcome** filter: | Outcome | Meaning | | ------------------------- | -------------------------------------------------------------------------------------------------- | | **Booked** | A booking was created. Cancelled bookings remain in this filter and display **Booking cancelled**. | | **Qualified, not booked** | The visitor qualified but has no booking. | | **Unqualified** | The visitor did not qualify for scheduling. | | **Awaiting routing** | The answers are saved and routing has not completed. | Choose **View answers** for the submitted values and their original question labels. The row shows the form version, routing or booking outcome, assigned owner, and **CRM delivery** status. Choose **View routing details** to investigate the routing decision. CRM delivery follows the connected router's configured actions and mapped fields. **Submission only** answers are kept in the submission; adding a question does not automatically create a CRM property or action. Use **Review CRM connection** when a failed delivery needs attention. ### Manage and troubleshoot The Lead forms list supports search by form name or page URL and a **Status** filter for **Published** or **Unpublished** forms. **Duplicate** creates an unpublished draft with a new page URL. | What you see | What to check | | ------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | | A router field is missing | Publish the intended Form Router configuration, select it in the lead form, and save the draft to reload mappings. | | Publication asks for an email mapping | Map Email to the router field connected to the CRM's Email property. | | The live form still shows old changes | Save the draft, then publish it. For router changes, publish the router first and then republish the lead form. | | A visitor is unqualified | Review their answers, field mappings, email validation, and routing rules through **View routing details**. | | No meeting times appear | Check the effective event type, eligible hosts, calendars, and availability. Use [Availability preview](https://help.distro.so/settings/calendar-troubleshooter). | | The embedded form is clipped | Keep both parts of the generated snippet and allow the resizing script to run. See [Embed a lead form](https://help.distro.so/routing-forms/lead-forms/embed). | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.distro.so/routing-forms/lead-forms.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.