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

# Contact Form

> Build a contact form as a Formbricks survey and embed it on your website.

A contact form is a survey that happens to sit on a website. Building it in Formbricks means the submissions land where the rest of your feedback already is, rather than in an inbox.

## What you will build

A four-question form — name, email, reason for contact, message — embedded on a page of your site.

## 1. Create a link survey

Open **Surveys**, click **New Survey** and choose **Start from scratch**. Then open **Settings → Survey Type** and make sure **Link survey** is selected.

> [!NOTE]
>
> Check it rather than assuming it. A new survey inherits its type from the workspace channel you picked
> during onboarding, so a workspace set up for a website or app creates **app** surveys by default — only
> a workspace with no channel set defaults to link.

## 2. Add the questions

Four questions, each a standard type documented in its own page:

| Field | Question type | Notes |
| - | - | - |
| Name | [Free text](https://formbricks.com/docs/surveys/question-type/free-text.md) | Text input |
| Email | [Free text](https://formbricks.com/docs/surveys/question-type/free-text.md) | Set the input type to **Email** so the address is validated |
| Reason for contact | [Select single](https://formbricks.com/docs/surveys/question-type/select-single.md) | Sales, support, something else — keep the list short |
| Message | [Free text](https://formbricks.com/docs/surveys/question-type/free-text.md) | Switch on **Long answer** |

> [!TIP]
>
> Use [validation rules](https://formbricks.com/docs/surveys/general-features/validation-rules.md) on the message — a minimum length of
> 20 characters or so filters out the "hi" submissions without annoying anyone with something real to say.

Turn off the welcome card unless you want an extra click before the form, and edit the ending card to say what happens next: how soon someone will reply is the one thing every person filling in a contact form wants to know.

## 3. Embed it on your site

Open the survey's **Distribute** dialog and choose **Website embed**.

![The Website embed panel of the Distribute dialog](https://mintcdn.com/formbricks/iXG9xO1vWD0VUZc9/images/surveys/best-practices/contact-form/embed.webp?fit=max\&auto=format\&n=iXG9xO1vWD0VUZc9\&q=85\&s=dc3d8edc7a27ea1540fffcbdf494d78a)

Copy the snippet into the page where the form should appear. The embed is an iframe, so it needs no widget and no SDK — this works on a static site.

> [!NOTE]
>
> A contact form is a link survey, not an app survey. It does not need the Formbricks widget, and none
> of the [app survey](https://formbricks.com/docs/surveys/website-app-surveys/quickstart.md) targeting applies to it.

## 4. Handle what comes in

Submissions arrive in the survey's **Responses** tab. Two things worth setting up before you announce the form:

* A [Workflow](https://formbricks.com/docs/workflows/overview.md) that emails an internal teammate — support, sales, whoever answers — on
  **Response completed**, so nothing waits on someone remembering to check the tab. The literal address you
  put in the **Send email** action has to belong to a member of this workspace; the workflow will not enable
  otherwise. To acknowledge the sender instead, point the recipient at the Email question rather than at a
  literal address.
* [Tags](https://formbricks.com/docs/surveys/general-features/tags.md), so sales and support enquiries stay separable.


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