Client support

Static Website Forms And Lead Delivery

How contact forms work on static websites, what setup details Banyan Tree Design needs, and how to share form keys or endpoints safely.

Why a form service is needed

A static website can load quickly and stay simple, but it does not include a traditional backend by default. If the site has a contact, quote, booking request, or intake form, that form needs somewhere to send the submission.

For many brochure sites, a hosted form service is the simplest option. The site stays static, and leads still arrive at the right email address.

Common form service options

What Banyan Tree Design needs

Send form setup details through the client portal when possible. The exact details depend on the form service, but these are the usual pieces.

  1. The email address where form submissions should arrive
  2. The fields the form should collect, such as name, email, phone, service, location, or message
  3. Any required subject line or routing note
  4. The success message customers should see after submitting
  5. Any spam protection or confirmation behavior the form service supports

Web3Forms access key

Web3Forms uses an access key to route submissions to your email. Their documentation says this access key is public and can be used in client-side form code. It is not the same as a private API key or password.

  1. Create or open your Web3Forms account
  2. Verify the email address that should receive form submissions
  3. Create an access key for the form
  4. Send the access key through the portal request or project message
  5. Test the form after launch and confirm the message reaches the right inbox

Formspree endpoint

Formspree forms usually use a form endpoint URL in the form action. If the project uses Formspree, send the endpoint URL or form ID through the portal so Banyan Tree Design can add it to the website.

  1. Create or open your Formspree account
  2. Create the form for the website
  3. Confirm the receiving email address and notification settings
  4. Send the form endpoint URL or form ID through the portal
  5. Test the form after launch and confirm the message reaches the right inbox

Do not send account passwords

A public form access key or endpoint can be shared for website setup. Do not send provider passwords, recovery codes, private API keys, billing details, or account login credentials. If dashboard access is needed, use a provider invitation or temporary collaborator access when available.

Official references

Provider setup details can change. Use the official docs for current form creation steps and account settings.

  1. Web3Forms: Installation and access key setup
  2. Web3Forms: Access key FAQ
  3. Formspree: Building an HTML form
View all support guides Back to Banyan Tree Design