Skip to content
Sign inJoin waitlist

The contact form — Tustel AI Prompts

Tustel has one form, the project enquiry on the Contact page. 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.

Field Name it sends Required
Name name yes
Email email yes
Organization organization
Project Type (Photography, Brand Identity, Web Design, Creative Direction, Art Direction, Other) project yes
Estimated Budget (Under $2,000, $2,000 – $5,000, $5,000 – $10,000, $10,000+) budget yes
Timeline timeline
Message message

Labels, placeholders, the choices of the two selects, the note (“All fields marked with * are required.”) and the button texts are in src/content/pages/contact.json → contactForm.

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 and check that the enquiry arrives.

Every submission also carries form (contact) and subject (“New project enquiry”, contactForm.notification), which form services use as the email subject. To pass the enquiries on to a CRM or a spreadsheet, 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 text stays in the fields.

  • Your tool’s database: Lovable and some others can save submissions in a database and email you. Ask: “Save the project enquiries 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.

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

Enquiries go only where you point them. Tustel has no privacy policy page and no consent checkbox: if you need a policy, ask your tool for a page in the style of a post, and mention it in the Contact page’s text (contactPage.text).

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.