The booking form — Metuo AI Prompts
Metuo has one form, the booking request “Tell us about you.”, on three pages: at the end of Home, at the end of the Service page, and as the Contact page’s main section. The prompts build it with its check of the email address, its states — sending, “Thank you”, “Something went wrong”, each shown on the Submit button — and a hidden field that catches spam bots.
| Form | Where | form it sends |
Content |
|---|---|---|---|
| Book a session | Home, Service, Contact | book |
form in src/content/pages/book.json |
The fields
Section titled “The fields”| Field | Name it sends | Required |
|---|---|---|
| First Name | first-name |
no |
| Last Name | last-name |
no |
email |
yes (a valid address) | |
| Phone | phone |
no |
| Preferred session type (a checkbox per service) | service, the list of the ticked services’ names |
no |
| Preferred Date | date (2026-11-03) |
no |
| Preferred Time | time (14:30) |
no |
| What would you like support with? | message |
no |
Labels, placeholders, the email’s error message and the button texts are in the form’s fields, submit, success
and error. The session types are the names of the services in src/content/collections/services.json: a new service
adds a checkbox. Empty fields are sent empty.
Demo mode
Section titled “Demo mode”Until you connect a service, the form runs in demo mode: it waits a moment and says “Thank you”, but nothing is sent anywhere. Connect it before you publish.
Connecting a form service
Section titled “Connecting a form service”The form sends its fields as JSON to the address in an environment variable:
| Tool / framework | Variable |
|---|---|
| Lovable, Bolt, Replit (Vite) | VITE_FORM_ENDPOINT |
| v0 and other Next.js projects | NEXT_PUBLIC_FORM_ENDPOINT |
| Astro | PUBLIC_FORM_ENDPOINT |
- Create a form at a service that accepts JSON posts — for example Formspree or Basin — or a webhook in Zapier, Make or n8n.
- Copy the address it gives you (e.g.
https://formspree.io/f/abcdwxyz). - Set it as the variable above: in the tool’s settings for secrets or environment variables, or in a
.envfile. The address is built into the site, so build or publish again after you change it. - Send the form once, with two session types ticked, and check that the request arrives the way you want to read it.
Every submission also carries form (book) and subject (the form’s notification: “New session request”), which
form services use as the email subject. To send the requests to several places — your inbox, a calendar tool, a CRM —
route them through a Zapier, Make or n8n webhook.
When the service answers with an error, or the network fails, the button says “Something went wrong” and the visitor’s answers stay in the fields.
Other ways
Section titled “Other ways”- Your tool’s database: Lovable and some others can save submissions in a database and email you. Ask: “Save the booking requests to the database and email me each one.”
- Your own server: the endpoint can be any URL that accepts a JSON POST — your practice software, a serverless function.
- A booking tool: to let visitors pick a time themselves, point the “Book a session” buttons (
bookLinkinsite.json) at your Cal.com or Calendly page instead of/contact.
Changing the form
Section titled “Changing the form”The fields, their labels and placeholders are content (fields of form): ask your tool to add or remove a field there
and show it in the form (“Add an optional Pronouns field after Last Name in the booking form”). A field arrives at your
form service under its name, so keep the names you already use somewhere.
Privacy
Section titled “Privacy”Booking requests can hold sensitive details about a person’s wellbeing. They go only where you point them: choose a
service you trust with that, and say in the Privacy Policy (src/content/collections/legal.json) what the form collects
and where it goes.
The hidden fax field stays empty for people and gets filled by bots; when it is filled, the form says “Thank you” and
sends nothing. Most form services also filter spam themselves.