How to add a contact form to your website

Open the contact form template. It asks for a name, an email address, an optional phone number, a topic, the message and an optional attachment. It opens with a short privacy line where you add a link to your own policy.

You do not need an account to look at it. PulseFormCreator lets you build and preview the whole form first, and asks for an email address when you press publish, because that is where the messages are sent.

If most of your first contacts are job enquiries or pricing requests, the enquiry form template and the quote request form template ask the follow-up questions that save you a reply.

Edit the topic dropdown first. Replace the default options with the reasons people write to you, such as “question about an order”, “book a job” or “media”, and the messages arrive already sorted.

Avoid adding fields after that, because each extra field reduces the number of messages you receive. If a question only matters for one topic, put a condition on it so it appears for that topic alone. The template already does this with the order-number question. Logic, calculations and scoring explains how.

Press publish and confirm your email. Then copy an inline embed snippet from the Share tab and paste it into your contact page. Inline is the right style here because the form is the purpose of the page. Embedding a form covers all 8 styles and what to do if your site builder strips scripts.

An embedded form renders at your own address, so visitors stay on your site. Keep a plain link to the form as well, for an email signature or a business card.

Bots find a public contact form within days. There are two defences, and visitors see neither. The first is a hidden honeypot field that only an automated submitter fills in. Those submissions look successful to the bot and are not stored. The second is an optional minimum completion time that refuses anything sent faster than a person could read the form.

You can also switch on duplicate prevention so the same browser cannot send the same message repeatedly. Most small sites need nothing more.

Every message is stored in your dashboard and emailed to your account address. Turn on Slack or Discord if your team watches a channel, or send a webhook to open a ticket in your help desk. All of that is free. Sending the person who wrote to you a copy of their message is a Pro feature.

One limit to know before you build around it: notifications go to the account's email address, and there is no per-topic routing to separate inboxes. A shared address or a Slack channel is the usual answer. Integrations has the setup for each, and the pricing page shows which plan each feature needs.