Formstep

Contact form template

A contact form asks for a name, an email address and a message, and nothing else. Embed it on your site or share its link, turn on bot protection, and read each message where you already work.

Updated

Use this template

Opens in the editor. No account needed to try it.

The Contact Us form under a photo of a wall of numbered mailboxes, with name, email and message questions
What the recipient sees. Swap the photo and logo for your own.

What it asks

Question
Name
Email
Message

This one is a public form

The request templates here go to one known person. A contact form is the opposite: anyone finds it on your site and writes to you, through a share link or an embed instead of a request. Logic, translations and integrations work the same way.

How to use it

  1. Select Use this template. Swap the cover photo and the logo for your own; the form becomes part of your site, so it should look like it.
  2. Publish it, and embed the form on your contact page, open it as a popup, or share its link.
  3. Turn on the notification email so each message reaches your inbox, or send them to Slack so the team sees them as they arrive.

What to change

  • Three questions is the point. Each one you add costs you messages. Add a phone number only if you will call, and a dropdown for the topic only if different people answer different topics.
  • The reply. Edit the thank-you page to say when the person will hear back, and the confirmation email if you want them to have a copy of what they wrote.
  • Languages. A site in two languages gets one form in two languages: translate the labels in the editor, and the form follows the visitor’s language or the one you set on the share link.
  • Bot protection. Leave it on. A form that is embedded on a public page gets found by bots within days.

Where the messages go

Each message comes back under keys derived from the titles, name, email and message, which become the columns in Google Sheets or the fields of a Slack message. For a shared inbox, Linear or GitHub Issues open a ticket per message. A webhook hands the message to your own code.

When another template fits

  • Support request when the message is a problem to solve and you want a category, a priority and a file with it.
  • Lead generation when the visitor is a prospect and you need the company and its size, not just a note.

More templates

Questions about this template

Something else on your mind? The docs cover every setting, and we answer email.

Read the docs

Publish the form and copy the embed code from the Share sheet, or open it as a popup from a button. The form keeps your logo, colors and fonts, and works on phones.

Bot protection is on every plan, and you can close a share link or cap its responses. Nothing stops a determined human, so keep the questions few and read the messages where you will see them.

To the dashboard, to your inbox with a notification email, and to Slack, Discord, Notion, Google Sheets or your own endpoint with an integration, as soon as someone submits.

A way to reach the person back, and the message. Every extra question costs you messages. Ask for a phone number only if you will call, and ask what it is about only if it changes who answers.

Collect information from anyone.

Publish a sample form, answer it as your recipient would, and watch the answers come back. No account needed.

Read the docs