Contact form

Every Bulido website has a simple form in the Contact section. The client fills in their name, phone, email, and a description of what they need, then clicks Send. You get an email with the contents.

Where the email lands

The notification goes to the email address from your Contact info. By default it's the email from your Bulido account. If you want enquiries from the website to go elsewhere (e.g. a separate "office@..." address), open Settings → Website, scroll the Content tab down to the Contact info section, and click Override next to the Email field. Type the address where you want enquiries to land — the change goes into the global save bar at the bottom of the panel; click Save changes to publish it.

The same applies to the phone number and address shown under the form — you can show clients different contact details than your main account.

What's in the email

Example of what you receive:

Subject: New website enquiry — Anna Smith

Name: Anna Smith Email: anna@example.com Phone: +44 7700 900123 Message: Hi, I need a quote for a 12m² kitchen renovation in Mayfair... Submitted: 2026-05-05 14

IP address: 91.123.45.67

The Reply-To field is set to the client's address — you can reply straight from the email and your response goes to them.

What the client gets

After submitting, the client sees a short message "Thanks for your message — we'll reply as soon as we can" and receives a confirmation email letting them know their enquiry reached you. This matters — it builds trust (the client can be confident the message has been received) and puts your business name in their inbox so they can find you later.

Spam protection

We have three layers, applied in this order on every submission:

1. Honeypot — invisible field in the form. Bots fill everything, real humans don't see it. If the field is filled, we treat the submission as spam and discard it without sending an email (the bot sees success, so it doesn't retry).
2. Google reCAPTCHA v3 — runs silently in the background. Each click of Send generates a score; submissions that look like bot traffic are rejected before the email is sent. The visitor sees a small notice under the form: "This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply." — required wording by Google, no badge.
3. Per-IP rate limit — 3 submissions per hour. If someone gets past reCAPTCHA and tries to spam manually, the fourth attempt within an hour returns an error.

These measures are sufficient for a small landing page. If you ever receive a heavy wave of spam (unlikely), let us know — we'll help.

What the visitor experiences if reCAPTCHA flags them

If reCAPTCHA scores the submission too low (e.g. the visitor is on a brand-new browser profile, behind a VPN, or moving too fast), they see a short message: "We couldn't verify that you're human. Refresh the page and try again." A genuine refresh usually fixes it — the score recalibrates as the page loads.

What's not there

• Storing submissions in Bulido. You get the email but can't see a history of enquiries in the panel. That's intentional — the website is meant to be simple. If you want client history, use the Clients module in the main Bulido app.
• Attachments. The client can't attach photos. If you need them, ask the client to send them as a reply to your first email — you have their address in Reply-To.

Next

• Contact info — how to override the address for the website
• Website status — what happens to the form when the site is hidden