Skip to content
Sign inJoin waitlist

The inquiry form — Cerette AI Prompts

Cerette has one inquiry form, in two versions: on Contact and on the Services page, where Project type is a list of categories, and on every service page, where Project type is a text field that starts with the service’s name. The prompts build it with 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
Inquiry Contact, Services contact contactForm in src/content/pages/forms.json
Service inquiry every service page service serviceForm in src/content/pages/forms.json
Field Name it sends Required
Name name no
Email email no
Phone phone no
Location location no
Project type type (a choice of six categories; on a service page, the service’s name or what the visitor typed) yes on Contact and Services, no on a service page
Project budget budget (a choice of five ranges) yes
Project details details no

Labels, placeholders, the choices and the button texts are in each form’s fields, submit, success and error. The browser checks the required choices before anything is sent. Empty fields are sent empty. As in the design, only the choices are required: to require an e-mail address too, add "required": true to the email field and ask your tool to follow it.

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.

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
  1. Create a form at a service that accepts JSON posts — for example Formspree or Basin — or a webhook in Zapier, Make or n8n.
  2. Copy the address it gives you (e.g. https://formspree.io/f/abcdwxyz).
  3. Set it as the variable above: in the tool’s settings for secrets or environment variables, or in a .env file. The address is built into the site, so build or publish again after you change it.
  4. Send the form once from Contact and once from a service page, and check that both requests arrive the way you want to read them.

Every submission also carries form (contact or service) and subject (the form’s notification: “New inquiry from the Cerette website” or “New service inquiry from the Cerette website”), which form services use as the email subject — change them to your studio’s name. To send the inquiries to several places — your inbox, a CRM, a project board — 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.

  • Your tool’s database: Lovable and some others can save submissions in a database and email you. Ask: “Save the inquiries to the database and email me each one.”
  • Your own server: the endpoint can be any URL that accepts a JSON POST — your CRM, a serverless function.
  • A booking tool: “Book a call” (Home’s hero, About) and “Schedule Consultation” (the call to action) link to Cal.com’s home page in the demo (href in pages/home.json, about.json, projects.json, services.json and cta.json): point them at your own Cal.com or Calendly page.

The fields, their labels, placeholders and choices are content (fields of each form): ask your tool to add or remove a field there and show it in the form (“Add an optional Company field after Email in both inquiry forms”). A field arrives at your form service under its name, so keep the names you already use somewhere.

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.