A school can know someone long before they have an account. People is the school's CRM directory. A public qualification form gathers a candidate's answers, and an owner or admin reviews the resulting application. These are different parts of one journey: answering questions neither admits someone nor charges them.
Consider Maya Chen. An owner first records her Instagram handle as a Person in the school. Maya later shares an email address and answers a public form about her goals. The owner reviews her response, chooses To follow up, and decides whether to invite her to a conversation. Maya has not been given a school account, offer, or enrollment by any of those steps.
- People, leads and applications explains which records and states exist, including why “lead” is not a separate CRM object.
- Contacts and import covers one-contact capture, CSV import, scoped reading, and reversible links between duplicate Person records.
- Qualification forms takes an owner/admin from a draft questionnaire to a frozen public version, then through later changes and closing.
- Application triage follows Maya's submitted answers into the response detail and an explicit decision.
The form and response screens belong to the school's owner and admins. A respondent follows a public school-specific address without a school account. People access has a separate scope: an owner/admin sees the school's directory; a closer sees assigned people; a setter does not open the CRM list. See contacts and import before handing a task to another role.
A complete acquisition or opportunity pipeline, automatic setter handoff, and automatic admission are outside these screens. After qualification, a human can arrange a conversation through Setting & Booking or prepare a named offer through Closing, Offers & Payments.
