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

# Forms

> Build interactive multi-step question flows in your chat to qualify visitors, capture leads, and track completion rates.

Forms turn data collection into a natural conversation. Instead of sending visitors to an external page or showing a long static form, your chat asks questions one at a time. Visitors tap options or reply directly in the chat bar.

Every response is saved, your CRM updates instantly, and you can track drop-offs step by step in a built-in funnel.

***

## Accessing Forms

> [!TIP]
>
> To open your forms, select your chat in the dashboard and click the **<kbd>Forms</kbd>** tab in the left sidebar.

From this page, you can create new forms, edit existing ones, check how many questions each form has, and inspect their conversion numbers.

***

## Creating and editing a form

![form-builder](https://mintcdn.com/attlas/EvPsRd8XHb9jIEoz/images/form.webp?fit=max\&auto=format\&n=EvPsRd8XHb9jIEoz\&q=85\&s=8fa373d21a98bff084bb4c934974fb59)

Click **<kbd>Create</kbd>** in the top header to start a new form.

Attlas uses a document-style editor. You write your form like a text document, with no complex flowchart nodes:

* **Type plain text** to make your chat speak. Each paragraph becomes an individual chat bubble.
* **Type `/`** to insert questions, choices, media, or contact fields.
* **Drag blocks** using the handle on the left to reorder your sequence.
* **Preview in real time**: the preview panel on the right runs your form in an interactive chat as you edit.
* **Save your work**: click **<kbd>Save</kbd>** in the top-right corner when you are ready to publish changes.

> [!TIP]
>
> Keep your questions conversational and place contact fields at the end. Visitors convert better when they answer simple qualifying questions first.

***

## Available blocks

Type `/` anywhere in the editor to open the block menu:

### Chat messages

| Block | Command | Description |
| :- | :- | :- |
| **Message** | Plain text | Regular text displayed in a chat bubble. Supports bold, italics, links, and emojis. |
| **Image** | `/image` | An image displayed inside a chat bubble. |
| **Video** | `/video` | A short, muted looping video displayed inside a chat bubble. |

### Visitor answers

When the form reaches an answer block, the chat input bar adapts to what is expected.

| Block | Command | Input mode | Validation |
| :- | :- | :- | :- |
| **Choice** | `/choice` | Button options under the question. | Select one option. You can also toggle **Several answers** in settings for multi-select. |
| **Checkboxes** | `/checkboxes` | Checkbox options under the question. | Select one or more options, then tap **Continue**. |
| **Text** | `/text` | Standard text input. | Non-empty text with optional maximum length. Supports voice dictation on mobile. |
| **Number** | `/number` | Numeric keyboard. | Numbers only, with optional minimum and maximum limits. |
| **Link** | `/url` | URL keyboard. | Valid website address (`https://` added automatically if missing). |
| **Period** | `/period` | Date range selector. | Start date and end date picker. |
| **Upload a file** | `/file` | File attachment button. | Photos or PDF documents up to 20 MB. Enable **Several files (5 max)** for multiple uploads. Requires the Pro plan. |

### Contact fields

Contact fields capture visitor details and qualify leads in your CRM. Each contact field can appear once per form:

| Block | Command | Description |
| :- | :- | :- |
| **First name** | `/firstname` | Captures the visitor's first name with browser autofill. |
| **Last name** | `/lastname` | Captures the visitor's last name. |
| **Email** | `/email` | Captures and validates an email address. |
| **Phone** | `/phone` | International phone input with country code selector. |
| **WhatsApp** | `/whatsapp` | Phone input pre-filled with the visitor's detected country. |
| **Preferred date** | `/schedule` | Date picker for meeting preferences or target dates. |

> [!WARNING]
>
> A form needs at least one contact field to create a lead in your CRM. If you only ask choice, checkbox, or text questions, responses are stored in the conversation history but no contact card is created.

***

## Thank-you message and redirection

The last block in your editor is the thank-you message. This message displays automatically when a visitor finishes the form.

You can personalize this final message by typing `@` to cite any earlier response:

```text theme={null}
Thank you, @firstname! We received your request for @choice and will reach out via WhatsApp at @whatsapp.
```

If left empty, Attlas displays a default confirmation message in the visitor's language.

### Automatic redirection

You can redirect visitors to an external address (such as a payment page, a calendar booking, or your main website) after they complete the form:

1. Click the end block at the bottom of the form editor.
2. Enter a full address (`https://...`) in the **Redirect URL** field.

Once submitted, the chat displays your thank-you message and a **Continue** link. The page redirects automatically after 3 seconds. In embedded widgets and iframes, visitors tap **Continue** to open the link in the top window.

***

## How visitors experience your form

The form runs directly inside the chat interface:

1. **Step by step**: The chat asks one question at a time.
2. **Context-aware input**: For phone, date, or text inputs, the chat input bar displays a dedicated badge (such as "Your WhatsApp" or "Preferred date") and sets the correct mobile keyboard.
3. **Side questions**: Visitors can click the **<kbd>×</kbd>** icon on the input badge to pause the form and ask a question. The chat answers using your knowledge base, then resumes the form at the current step.
4. **Exit option**: Under choice or checkbox questions, visitors can tap **"Not now"** to leave the form flow without breaking the conversation.

***

## Connecting your form

You can trigger a form through four different paths:

### 1. Triggers

Add a **Form** trigger in your chat's **Triggers** tab. Select your form from the dropdown. It appears as an interactive button in your chat menu.

### 2. Campaigns (Launch on arrival)

In [Campaigns](https://attlas.so/docs/pro/campaigns.md), select your campaign channel and set **Launch on arrival** to your form trigger. When visitors click your ad or campaign link, the chat opens with the form already active, without requiring an initial click.

> [card] [Campaigns](https://attlas.so/docs/pro/campaigns.md)
>
> Learn how to build dedicated welcome screens for paid ads with custom headlines and automatic form launch.

### 3. Chat goal (Capture leads)

In **Actions** > **Goal**, select **Capture leads**. Attlas connects your lead objective directly to a form. When the conversation reaches lead capture, the assistant starts the form and automatically pre-fills any details the visitor already mentioned.

### 4. Direct link

Share a link with the `?form=<slug>` parameter to open your chat directly on a specific form.

***

## Tracking performance (Funnel)

On the **Forms** list page, click the **chart icon** next to any form to expand its conversion funnel.

The funnel tracks data over the last 30 days:

* **Starting points**: Shows where visitors came from, including visits from ad [campaigns](https://attlas.so/docs/pro/campaigns.md) and clicks on menu triggers.
* **Step completion**: Displays the number of visitors who answered each step, along with the retention rate compared to the previous step.
* **Leads generated**: The total number of completed contacts collected by this form.

> [!NOTE]
>
> Internal test conversations from workspace members and editor previews are excluded from funnel metrics.

***

## Data collection and integrations

* **CRM**: Submitted details appear immediately in your **<kbd>CRM</kbd>** tab, with all custom answers saved to the contact record.
* **Webhooks**: Completing a form dispatches a `form_completed` webhook payload containing all answers and contact information.
* **Meta CAPI**: When Meta Conversions API is configured, completing a form sends a `Lead` event server-side for ad tracking.
* **Automatic translations**: Form text is translated automatically into all 13 supported languages so visitors see questions in their preferred language.


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