Skip to content
Sign inJoin waitlist

The forms — Balancee AI Prompts

Balancee has two forms: the contact form “Tell us about your project.” on the Contact page and at the end of the Services page, and the newsletter box “Never Miss an Update — Subscribe!” in the footer of every page. The prompts build both with their checks, their states — sending, “Thank you”, “Something went wrong” (the newsletter button says “Try again”), each shown on the button — and a hidden field that catches spam bots.

Form Where form it sends Content
Contact Contact, Services contact contactForm in src/content/pages/shared.json
Newsletter every page (footer) newsletter footer.newsletter in src/content/site.json
Field Name it sends Required
Name Name yes
Company Company yes
Email Email yes (a valid address)
Phone Phone no
I’m interested in … (one service, as radio buttons) Service, the chosen service’s name or empty no
Tell us about your project. Message no

Labels, placeholders, the error messages and the button texts are in contactForm (fields, submit, success, error). The eight choices of “I’m interested in …” are the names of the services, written out in contactForm.fields.service.options: they do not follow the services collection, so when you add, rename or remove a service, change them too. Empty fields are sent empty. The newsletter box sends only Email.

Until you connect a service, the forms run in demo mode: they wait a moment and say “Thank you”, but nothing is sent anywhere. Connect them before you publish.

The forms send their 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 each form once and check that the request arrives the way you want to read it.

Every submission also carries form (contact or newsletter) and subject (the contact form’s notification: “New message from the Balancee contact form”; “New newsletter subscriber”), which form services use as the email subject. To send the messages to several places — your inbox, 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” (or “Try again”) 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 contact messages 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: the “Book a Free Consultation” button opens bookingLink in src/content/site.json (the demo points to https://cal.com/): set it to your Cal.com or Calendly page.

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

Contact messages and newsletter sign-ups hold personal data. They go only where you point them: choose a service you trust, and say in the Privacy Policy (src/content/collections/legal.json) what the forms collect and where it goes. If you send the newsletter box to an email-marketing tool, ask for consent in the way your country requires.

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.