AI website contact form that actually reaches your inbox

A contact form on an AI-built website only works if the submission has somewhere to go. On a published Zugo site it does: the form posts the enquiry to Zugo, the submission is stored with your project, and you get it by email — no connector required. The thank-you message appears only after the server confirms it arrived, so what the visitor sees matches what actually happened.

Why most AI-generated contact forms quietly lose the lead

This is the failure worth understanding before you trust any builder's form, ours included. A generated form is easy to render and easy to fake: a submit handler hides the fields and reveals "Thanks — we'll be in touch shortly."

If nothing is wired behind that handler, the message is a lie that nobody catches. The owner tests the form, sees the green thank-you, and believes lead capture works. Their customers see the same green thank-you. Every enquiry evaporates. It surfaces weeks later, usually as "why did nobody reply to me?"

We shipped exactly this bug and fixed it in July 2026. The endpoint that receives submissions had been injected into every published page for months and had zero callers — the form was showing a thank-you nobody had received. That is why the rule below matters more than any feature list.

Test the form on the published address, not in the preview. A form that cannot fail its own test is not a working form.

Where a submission goes on a published Zugo site

The last row is the part to insist on in any tool. If the confirmation appears before the server answers, it is decoration, not confirmation.

What the form does when something goes wrong

Three outcomes, and each says something different, on purpose:

• Delivered. The thank-you appears and the fields collapse.
• Send failed. The visitor is told it did not send and the button becomes clickable again — and, importantly, the message they typed stays on screen. A failed send that hides someone's typed enquiry behind a thank-you loses the lead twice.
• Not published yet. In the builder preview there is no live address to attach a submission to, so the form says submissions start once you publish, rather than claiming an enquiry was received.

That third state is why testing in the preview proves nothing. It is not a bug — it is the form refusing to lie to you.

How to add a contact form to your site

Describe it in plain words when you build or edit: "add a contact section with name, email and message, and a note that we reply within a day." The fields you name are the fields you get, and the copy in the thank-you is yours to set — ask for it in the same sentence.

For a booking or quote form, name the fields that actually matter to you: "a form with name, phone, service and preferred date." Every named field arrives in the email, so the enquiry lands ready to act on instead of needing a reply just to ask the basics.

An edit like this costs 3 credits and does not touch the rest of the page.

Sending from your own domain instead

The default is that Zugo emails you the submission. If you would rather send from your own address — useful once you are forwarding enquiries to a team or matching your brand — connect Resend in Settings and submissions go out through your account.

That is also the honest boundary of the built-in path: it notifies you, the owner. It is not a CRM, and it does not push to third-party services on its own. What it guarantees is that the enquiry is captured and reaches you.

How to verify yours in two minutes

1. Publish the site (one click, to an address like <slug>.zugo.run).
2. Open the published address — not the builder preview.
3. Submit the form with a real address you can check.
4. Confirm two things: the thank-you appeared, and the email arrived.

If the thank-you appears but no email does, say so in the chat and ask to check the form — do not assume it will start working on its own. If the preview showed the "submissions start once you publish" note, that is expected: repeat the test on the live address.

What it costs

Adding or changing a form is an edit: 3 credits. A fresh site build is 6 credits; a multi-page site is 12. Starter credits are free and no card is needed, which is enough to build a site, publish it and test the form end to end. Beyond that, Pro is $25/month for 200 credits — 33 quick builds or 16 multi-page platforms — and Business is $99/month.

Build one on zugo.dev, or start from a ready-made layout: the catalogue has 25 templates in 5 categories, and every one of them can be edited by describing the change. If you want the enquiries to land in a database you control rather than an inbox, see connecting Supabase; to take payments on the same site, see adding Stripe.