Skip to main content
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. Open Surveys, click New Survey and choose Start from scratch. Then open Settings → Survey Type and make sure Link survey is selected.
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:
Use validation rules 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 Share dialog and choose Website embed. The Website embed panel of the Share dialog 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.
A contact form is a link survey, not an app survey. It does not need the Formbricks widget, and none of the app survey 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 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, so sales and support enquiries stay separable.