Contact Forms

How Contact Forms Work

When a visitor submits a contact form on your Landingsite website, the submission is sent to the form’s email recipients. You receive the form data by email, and you can also read submissions in the editor under Settings → Forms → Submissions.

Built-in contact forms do not send submissions directly to WhatsApp or other messaging apps by themselves.

Built-in contact forms accept file uploads. Ask the AI to add a file field, and uploaded files arrive attached to the notification email.

Built-in contact forms can also send submissions to Make, Zapier, a CRM, or your own endpoint. Open a form’s Settings and add a webhook — see Webhooks. This works alongside email; submissions are still emailed and still stored in your dashboard.

Legacy (HTML) sites

Neither applies to legacy HTML sites. Their older form handler does not deliver uploaded files and has no webhook option — a file field on such a form silently drops what visitors attach. For either of those, use a third-party form tool that supports them and embed it on the page.

Where Submissions Are Sent

Form delivery is managed in Settings → Forms. Open the website editor, then go to Settings → Forms. From there you can:

• open Submissions to read form entries inside Landingsite
• open a form and click Settings to manage where submissions are sent

Inside a form’s Settings, you can manage:

• Email Recipients — the addresses that receive each submission. New forms default to the website owner’s email, and you can add more addresses so every submission is forwarded to the whole list. Recipients are stored per form and are not tied to your Landingsite account email — you can change them at any time, to any address, without touching your account settings.
• Redirect URL — where visitors land after a successful submission (for example, /thank-you). Leave it empty to use the default success page.
• Form Endpoint — the URL the form posts to. The AI wires this up for you when it builds the form.
• Captcha Protection — Turnstile CAPTCHA is enabled automatically to reduce spam.

You can also read submissions directly in the editor under Settings → Forms → Submissions, not just by email.

Landingsite does not provide a shareable public admin page for viewing built-in form submissions. If you or the AI created a custom /admin or dashboard page on your website, that page is not automatically connected to your real Landingsite form data.

Changing or Adding Recipients

The fastest way on React sites (the current platform for new websites): ask the AI in the website chat — for example, “Send form submissions to dana@example.com” or “Change the email the contact form sends to.” The AI updates the form’s recipients directly, and the change takes effect immediately without republishing.

On some older HTML sites, you may not see a separate Settings → Forms area at all. In that older layout, the destination address is often managed under Website Settings → General → Contact Form Email Override instead.

You can also do it manually on sites that have the Forms UI: open Settings → Forms, click Settings on the form, edit Email Recipients, then save. Add as many addresses as you need.

This works for any email address — it does not have to be the account owner’s email. If you’re building the website for a client or someone else, just ask the AI to send submissions to their address (or enter it in Email Recipients). You do not need to change your account email, add them as a collaborator, or transfer the website for form notifications to reach them.

If you transfer ownership of a website to a client, submissions go to whatever recipients are configured on the form. If you clone or copy a website, the copy can keep the original form’s recipients, so update them on the new copy if they should be different.

About the Sender Address

Changing the destination email only changes where submissions are delivered. The notification email itself still comes from Landingsite’s built-in form sender.

That means you currently cannot white-label the From/sender address for built-in contact form emails with your own domain.

Built-in form emails also do not support a custom or dynamic Reply-To based on the visitor’s submitted email address. In some email clients, pressing Reply on the notification may reply to your own inbox or the fixed sender behavior rather than directly to the person who filled out the form.

You also cannot set a custom subject line for different built-in form workflows, and the native form system does not send a custom autoresponder email with a PDF or other attachment after submission.

You also cannot fully redesign the built-in notification email or remove individual built-in lines from it. If you need fully custom notification formatting, custom subject lines, branded follow-up emails, PDF delivery, or specific reply behavior, use a third-party form service and embed it on your site instead.

If you need submissions to appear as if they were sent fully from your own branded email address, use a third-party form service and embed it on your site instead.

If Form Submissions Are Not Arriving

If your form uses data-landingsite-contact-form but you are not receiving submissions:

1. Confirm the website has a valid destination email set in Settings → Forms.
2. If your site is on the older HTML settings layout and there is no Forms menu, check Website Settings → General → Contact Form Email Override instead.
3. If the website was cloned from another site, re-enter the destination email on the cloned copy, save it, and publish again.
4. If you see an “Invalid captcha” error, refresh the page and submit again. This can happen if the form tab was left open too long or if you retry after a failed submit without reloading first.
5. If you changed the destination email recently, save the setting and publish the website again.
6. If no override is set, submissions go to the current website owner’s email address.
7. Submit a test entry from the live site and check the inbox (and spam folder) for that destination email.

If the site is still not delivering submissions after those checks, contact support with the exact website name or URL and a screenshot of the form email setting.

If a Recipient Address Was Blocked After a Bounce

Sometimes Landingsite shows a warning that one of your recipient addresses was blocked after a previous bounce.

One common reason is that the recipient uses an address on the same custom domain as the website, and that domain’s email stopped working for a while. For example, if hello@yourdomain.com was one of the form recipients but your domain’s mail records were removed or broken during a DNS change, repeated bounces can cause that address to be blocked for deliverability protection.

If that happens:

1. Confirm whether that recipient address is still valid.
2. If the blocked inbox uses your website’s custom domain, make sure that domain’s email service is working again first.
3. Remove or replace the invalid address in Settings → Forms if needed.
4. Save the form settings and publish the website again.
5. If you still need that same address to receive submissions after the mailbox is working again, contact support and mention that the recipient was blocked after a bounce so we can help unblock it.

In many cases, the problem is limited to the bounced address rather than every recipient on the form.

If You Want Submissions to Go to WhatsApp or a Webhook

For Make, Zapier, a CRM, or your own endpoint, use a built-in webhook — open a form’s Settings and add one. See Webhooks. Submissions are still emailed and still stored in your dashboard.

For WhatsApp, connect the webhook to an automation platform (Make, Zapier, Twilio) and let that platform deliver the message. There is no direct form-to-WhatsApp integration.

A third-party embedded form is still the right choice when you want something Landingsite’s form does not do — its own email subject line, an autoresponder, or file delivery to the visitor. Jotform, Typeform, and Tally are common options.

Legacy (HTML) sites

Webhooks are not available on legacy HTML sites — their forms have no Settings → Webhooks. Use a third-party form tool that supports webhooks and embed it on the page instead.

See also: Custom Scripts

If iPhone or Safari Zooms In When Someone Taps a Form Field

On iPhone, Safari can automatically zoom in when a form field’s text size is too small. That often feels like the page is “zooming in and out” while someone is trying to fill out the form.

If that happens:

1. Ask the AI to increase the input and textarea font size to at least 16px on mobile.
2. Publish the website again.
3. Test the live form on an iPhone or in mobile Safari.

This is usually a field styling issue, not a problem with form delivery itself.

Redirecting After a Successful Form Submission

The simplest way to send visitors to a specific page after they submit is the Redirect URL field in Settings → Forms (for example, /thank-you). Leave it empty to use the default success page.

If you’d rather set it in markup, add the data-landingsite-success-redirect attribute directly to the <form> element.

Example:

<form
  data-landingsite-contact-form
  data-landingsite-success-redirect="/thank-you"
>

Important details:

• Put the redirect attribute on the same <form> element that has data-landingsite-contact-form.
• Use the exact attribute name data-landingsite-success-redirect.
• data-landingsite-redirect is not the supported built-in success-redirect attribute.
• Use a path on your site such as /thank-you or /quiz.
• Publish the website again after making the change.
• If emails are sending but the redirect is not happening, check whether the live site is missing the data-landingsite-success-redirect attribute.

If You See unnamed_field Entries

If your submission emails include fields like unnamed_field_1 or unnamed_field_2, it usually means the form is still sending extra inputs that do not have clean field names.

This often happens when a form includes helper inputs, mirrored checkbox values, separators, headings, quantity toggles, or other auxiliary fields that are still part of the submitted form data.

To fix it:

1. Open the page in the editor.
2. Ask the AI to review the whole form and remove any helper inputs or extra fields that should not be submitted.
3. Ask the AI to give every real customer-facing field a clear name.
4. Publish the site again.

A prompt like this usually works better than only asking the AI to rename fields:

Review this form and remove any helper inputs, mirrored checkbox fields, separators, or unnamed fields from the submitted email. Keep only the real customer fields and give each one a clear label.

If unnamed_field_* entries keep appearing after that, the built-in Landingsite form may still be sending extra structural fields and you may not be able to fully control the email format with the native form alone.

In that case, the cleanest option is to use a third-party embedded form if you need full control over exactly which fields are submitted and how the notification is formatted.

For Agencies

If you manage websites for clients, the email override setting is especially useful. You can route form submissions directly to your client’s email address so they receive leads without needing access to the Landingsite editor.

On React sites this is a one-message change: tell the AI in the website chat “Send this form’s submissions to client@business.com” and it updates the form immediately. The client does not need a Landingsite account, collaborator access, or ownership of the website to receive form submissions.