Skip to content
Sign inJoin waitlist

The forms — KorDent AI Prompts

KorDent has four forms. The prompts build each with its states — sending, “Thank you”, “Something went wrong”, each shown on the submit button — and a hidden field that catches spam bots. All four send to the same address, each with its own name, so you can tell them apart.

Form Where form it sends Content
Booking request The Book page, the Services page and every service page (at #booking) booking booking in src/content/site.json
Contact message The Contact page contact form in src/content/pages/contact.json
Patient review Home and the Services page, under the reviews review testimonials.form in src/content/pages/home.json (and its copy in pages/services.json)
Newsletter The footer of every page newsletter footer.newsletter in src/content/site.json
Field Name it sends Booking Contact Review Newsletter
Select Dental Treatment (a service page: its own service, already chosen) service required — — —
Select Preferred Expert Dentist (only the dentists of the chosen treatment) dentist — — —
Select Date / Select Preferred Time Slot date, time required — — —
Full Name name required —
Phone Number phone required — —
Email email required required needed (sent empty, it shows the error)
Confirmation Contact Preference (Call, Whatsapp, Email) preference — — —
Special Notes or Dental Symptoms notes — — —
Message / Inquiry message — required — —
Treatment Type (every service’s name) treatment — — required —
Satisfaction Rating (1 to 5 stars, five at the start) rating — — —
Your Review review — — —

The treatment and the dentist are sent by name (“Dental Implants”, “Dr. Emily Carter, DDS”). Labels, placeholders, the choices of the selects and the button texts are in each form’s content (fields, submit, success and error; the booking form’s step1 … step3). Empty fields are sent empty.

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 submissions arrive.

Every submission also carries form (booking, contact, review or newsletter) and subject (the form’s notification: “New appointment request”, “New contact message”, “New patient review”, and “New newsletter subscriber” for the newsletter), which form services use as the email subject. To send each kind somewhere else — booking requests to your practice software or front desk, sign-ups to your mailing list — route the submissions through a Zapier, Make or n8n webhook and branch on form.

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 submissions of the four forms to the database and email me each one.”
  • Your own server: the endpoint can be any URL that accepts a JSON POST — your booking system, a serverless function.
  • The newsletter: a mailing-list service (Mailchimp, Brevo, Kit) can take the sign-ups through its own form address or a webhook; ask your tool to point only the newsletter there if you like.

The fields, their labels and the choices are content: ask your tool to add or remove a field there and show it in the form (“Add an optional Date of Birth field after Phone Number in the booking form”). A field arrives at your form service under its name, so keep the names you already use somewhere. The booking form’s treatments and dentists, and the review form’s treatments, come from the services and dentists collections: they follow your changes there.

A booking request is a request, not a confirmed appointment: the form doesn’t check your calendar. Confirm each one the way the visitor chose (preference), or ask your tool to connect a scheduling service if you need live availability.

Submissions go only where you point them. Booking requests and messages can carry health details (“Special Notes or Dental Symptoms”): choose a form service and an inbox that suit the rules for patient data where you work. The demo’s Privacy Policy (collections/legal.json) is sample text: write your own, saying what the forms collect 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.