Use this when... you want prospective families to submit enquiries, trial lesson requests, or booking information in a consistent format that your admin team can follow up in TuitionFlow.

Before you start... decide what information you genuinely need at first contact. Keep the form short enough for parents to complete, but detailed enough for your team to assess subject, level, availability, location, and urgency.

Use Leads to review incoming enquiries and understand what your form needs to capture.

A good enquiry form should help your team answer three questions quickly: who is asking, what support does the student need, and what should happen next. Avoid turning the first form into a full onboarding pack. You can collect detailed consent, billing, and learning information later once the family is likely to proceed.

Open Growth or Leads and look at the stages your team uses: new enquiry, contacted, trial offered, trial booked, converted, lost, or similar. Your form fields should support those stages.

Expected outcome: the form asks for information that helps your team move the lead forward, not just information that is interesting to have.

Typical required fields include parent name, contact details, student name, subject, year group or level, preferred format, postcode or branch, and a short goal or message. Make sensitive fields optional unless they are essential at enquiry stage.

Use controlled lists for subjects, levels, branches, lesson formats, and referral sources where possible. Consistent options make reporting and filtering much easier later.

Use Settings for shared lists and configuration that affects forms across the organisation.

Submit a test enquiry using realistic demo information. Check that the form is clear, works on mobile, and does not ask for unnecessary data. Then open Leads and confirm the submitted enquiry appears with the right source, status, and fields.

Decide who receives new lead notifications, how quickly they should respond, and when a lead becomes a family record. If trial lessons are part of your process, make sure the scheduling workflow is ready.

Enquiries are not appearing: check the form status, embed or link, required fields, and whether leads are filtered by branch, date, or owner.

Leads are hard to sort: replace repeated free-text answers with controlled lists where appropriate.

Parents abandon the form: remove non-essential fields, improve labels, and move detailed questions to a later onboarding step.

Before sharing the form publicly, ask someone who was not involved in setup to complete it from a phone. They should be able to understand each question without extra explanation. Check that required fields are obvious, error messages are clear, and the confirmation message tells the parent what happens next.

Open the lead that was created by the test submission. Check that the parent name, student name, contact details, subject, level, branch, source, and message are all easy to find. If your team has to read several free-text fields to understand the enquiry, simplify the form or add clearer options.

Agree who owns new enquiries each day. A form is only useful if someone reviews it quickly, records the first response, and moves the lead to the next stage. If your business has multiple branches, confirm whether leads are assigned by branch, subject, tutor availability, or a central admin queue.

Document the response target your team expects, such as same day, next working day, or within a fixed number of hours. This helps everyone treat new enquiries consistently and makes it easier to spot when follow-up is slipping.

After testing the form, publish it on your website, enquiry pages, campaigns, or booking links. Review lead quality after a week and adjust fields based on real follow-up work.