Loading
Because the enquiry arrives in one system, the application in another, and the fee in a third. Each is correct; none of them agrees, and the number reported to the board is assembled by hand the week before.
By the time an applicant is enrolled they exist three times, with three different versions of what they were offered.
Each intake is a pipeline with its own stages and dates, so September and January do not compete in one funnel. An applicant is one record that moves through it, keeping every conversation and document.
Conversion is measured per intake and per source, which is the comparison that tells you which open day was worth running.
It is not a student information system. It takes an applicant to enrolled; what happens academically afterwards belongs somewhere built for it.
It also will not decide admissions. It records the criteria you applied and when, which makes an appeal answerable rather than arguable.
Books raises the fee schedule from the offer that was accepted, including any bursary applied, rather than from a form somebody re-keys. Nest can open the onboarding if the applicant becomes a member of staff.
The offer, the acceptance and the invoice therefore cannot quietly disagree about the amount.
Products, not integrations. Each one reads the same record, so a join is a permission rather than a sync job with a mapping screen behind it.
Yes. Multiple pipelines is the mechanism, and intakes are the most common use of it.
Yes, against their own record, with expiry dates where a document has one.
Yes — source tracking carries the agent through to enrolled and to the fee, so commission is calculable.
Half an hour on your own numbers is usually enough to say whether Flow is the right place to start.