What should happen after someone submits the form?

Something visible and immediate. A clear confirmation on screen, and ideally a short email to the person saying you received it and when you will reply. Silence after submitting is the point where people assume it broke and go to a competitor.

Why should a contact form store submissions instead of just emailing me?

Because email fails quietly. A message lands in spam, a filter eats it, someone deletes the wrong thread — and you never know an enquiry existed. Storing every submission in the app gives you a record you can check, so a lost email is an inconvenience rather than a lost customer.

How do I stop spam from filling the form?

Ask for basic protection when you build it and expect to tighten it after launch. Sensible first steps are a hidden field automated tools tend to fill, a limit on how often one visitor can submit, and required fields that a bot handles badly. Do not add a puzzle real customers have to solve until spam actually becomes a problem.

Data & Backend

Add a contact / lead form that emails you and saves submissions

Capture enquiries — email them to you and store them so none are lost.

Time: ~15 minutes Difficulty: Beginner Works with: Base44 / Lovable / v0

When to use this

Almost every site; the simplest way to turn visitors into leads.

Before you start

Decide exactly which fields you need — every extra field costs you responses. Name, contact and one open question is usually enough.
The email address where you want to be notified.
Nothing else: no keys, no external service, no payment.

The prompt

Add a contact / enquiry form to my site.
Outcome: a visitor sends me an enquiry; I get emailed instantly and the submission is saved so I never lose a lead.
Requirements:
- Fields: [name, email, phone, message — plus anything specific: budget, date, service].
- On submit: email the details to [my email], show the visitor a friendly thank-you, and save the submission to a list I can view.
- A simple admin/table view where I can see and search all enquiries.
Must-haves: validate every field, protect against spam/bots (a honeypot or similar), never expose my email or keys in the frontend, and show a clear error if sending fails so the visitor can retry.
Build it end to end and tell me how to test that the email arrives and the submission is saved.

Already building? Paste this into your project. Starting fresh? Open a free account with a compatible builder below.

Build it on

Start free with Base44 Read Review: Base44

Start free with Lovable Read Review: Lovable

Start free with v0 Read Review: v0 by Vercel

How we make money

What this creates

A contact form with the fields you specified
Email notification to you on every submission
A stored list of submissions you can view and export
A friendly confirmation message for the person who submitted
Basic spam protection

Check it worked

Paste the prompt, wait for the build to finish, then confirm these — in plain language, no technical checks needed:

Submitting the form shows the confirmation message you asked for
The notification email reaches your inbox (check spam the first time)
The submission appears in your stored list with everything the person typed
Submitting with a required field empty shows a clear, polite error instead of failing silently
The form works on your phone

Something missing? That's normal — ask for it in one short follow-up message rather than re-running the whole prompt.

Next steps

Auto-reply so nobody wonders

As soon as the form works

Send an automatic reply to anyone who submits the form: thank them, tell them when they'll hear from me ([TIMEFRAME]), and include my phone number for anything urgent. Keep it short and warm, in my voice.

You'll know it worked when: A test submission produces an email to you and a friendly auto-reply to the sender.

Route different enquiries differently

Once you get several kinds of enquiry

Add a "what is this about?" dropdown to the form with these options: [OPTION 1, OPTION 2, OPTION 3]. Send each type to the right email address: [OPTION 1 → EMAIL, ...]. Show the chosen type in the stored submission and in the notification subject line.

You'll know it worked when: Choosing each option sends the notification to the matching address.

See where your leads come from

When you start promoting the site

Record with each submission which page the person was on when they filled the form, and add a "How did you hear about us?" dropdown with these options: [SEARCH, INSTAGRAM, REFERRAL, OTHER]. Show both in the stored list so I can see what actually brings enquiries.

You'll know it worked when: New submissions show the source page and the chosen answer in your list.

Watch out for

Always test the email, from a different address. "The form works" and "the email arrives" are separate facts, and the second one is the one that costs you customers.
First notification often lands in spam — mark it as not spam once and add the sender to your contacts.
Don't collect sensitive information here. ID numbers, medical details, card numbers: not in a website form. Ask for those in the conversation that follows, in an appropriate place.
Storing submissions matters more than you think. If the email ever fails, the stored list is the only thing standing between you and a lost customer.

Platform notes

Base44 has email and storage built in — this usually works from the first prompt. Lovable sends via an email integration (e.g., Resend) and stores in Supabase; v0 wires an email/API route. This replaces paid form tools for most sites.

Spend fewer credits

Every builder charges you for the work its AI does — so the cheapest habit is thinking before you build. These six rules cut most of the waste, whichever platform you choose.

Plan in a free chat first. Sketch the whole thing in ChatGPT, Claude or Gemini — pages, features, what each form collects, what it should look like. Thinking there is free; thinking inside a builder is billed.
Start from a written prompt, not a sentence. "Make me a website" is the most expensive sentence in AI building. A complete first prompt — like the ones on this site — saves dozens of correction rounds.
Don't be lazy with the details. Every detail you leave out comes back as a correction you pay for. Business name, colors, every page, every form field, what happens after someone submits — put it all in the first prompt.
One change per message afterwards. "Fix the header, and the form, and the colors" produces a tangle that costs more to unpick than it saved.
Stuck? Stop patching. If the same fix fails about three times, don't send a fourth correction — describe the whole section's desired end state in one fresh message instead.
Start free. Upgrade when you need more. Use the free allowance to build and explore your first version. Upgrade when you need more usage or paid features, and check any connected service costs before launch.

The prompts on this page are written to do most of this work for you — that's the point of them.

Read the full guide

Related playbooks

Related prompts

Part of these kits

forms leads contact email data

Last reviewed: 2026-07-27