Lanlan.docs

Forms beyond contact

What forms can do today, what they can't, and how to manage the ones you've already built.

Add a contact form covers the basics. This page is for everything else — the field types you can use, what's not supported yet, and the small operational tasks (renaming a form, changing where notifications go, deleting old submissions).

Field types you can use

Lanlan accepts whatever standard HTML form fields you ask for. Tell Claude the shape of what you want and it builds the right input:

  • Single-line text — names, subjects, short answers.
  • Email — the browser checks the address looks right before submitting.
  • Phone, URL, number, date — each gets its own keyboard on phones (numeric, calendar picker, etc.).
  • Long text — a textarea for messages, descriptions, notes.
  • Dropdown (select) — a list of options the visitor picks from.
  • Radio buttons — pick one from a small set.
  • Checkboxes — pick any number of options, or a single yes/no like "subscribe me to the newsletter."

Claude figures out the right input type from how you describe the field. Some examples that work:

  • "Add a booking form with name, email, the date they want to book, and a dropdown to pick the service — haircut, color, or both."
  • "Add a feedback form with a rating from 1 to 5 (radio buttons) and a textarea for comments."
  • "Newsletter signup at the bottom of every page — just email and a checkbox to confirm they're 16 or older."

What forms can't do today

Be honest about the edges so you don't promise things to your visitors that don't work:

  • No file uploads in forms. A visitor can't attach a photo, PDF, or any other file through a Lanlan form. It's on the roadmap. For now, ask the visitor to email the file separately or paste a public link in the message.
  • No multi-step / wizard forms. Every form is a single page that submits in one click. If you'd planned a long form, consider breaking it into a few short forms on different pages instead.
  • No conditional fields. You can't make field B appear only if field A has a particular answer. Every field on the form is always visible.
  • No custom server-side validation rules. The browser handles standard checks (required fields, email format, number ranges via min/max). Anything beyond that — "this code must start with two letters and four digits," "this date can't be in the past" — isn't enforced after the form is submitted.

If any of those are dealbreakers, tell Claude what you're trying to do — there's often a workaround using collections, redirects, or a third-party form embed.

Manage your forms

Open your dashboard's forms page. For each form you can:

  • Read submissions — newest first, with read/unread state.
  • Mark as spam — trains the platform-wide filter so similar submissions get caught faster.
  • Export — download submissions as CSV (good for moving to a spreadsheet or CRM).
  • Delete a single submission — cleanup for test entries or anything you don't want kept.

In Claude, you can ask for the operational changes:

  • "Rename the form on my contact page to 'Booking enquiry'."
  • "Send my contact form submissions to bookings@my-business.com from now on."
  • "Delete the form on the old services page — I removed that page last week."

Deleting a form removes the form definition; existing submissions for it stay in your dashboard for the record.

Spam: what's automatic

Every form on every plan ships with basic spam filtering that catches obvious bots. Paid plans include advanced filtering that catches more sophisticated patterns — repeat offenders, content tricks, and ambiguous cases. Anything that does slip through, mark it as spam in your dashboard; that trains the filter to catch similar submissions next time.

What to try next

If you get stuck

Ask Claude. "I can't figure out how to…" almost always gets you unstuck. For anything Claude can't help with, email support.