An admissions team stops losing enrolments to slow callbacks
An illustrative deployment: a seasonal admissions cycle where every enquiry is contested, and the whole game is who calls back first and who remembers the parent.
Illustrative scenario. This is a composite of deployment patterns we build for, not a named customer account, and the figures are modelled rather than measured. We will publish attributed results with named customers once they have agreed to be named — until then, treat this as a worked example of how the product is used, and ask us for specifics on a call.
This is an illustrative scenario. It is a composite of the deployment patterns this product is built for, with modelled figures — not an account of a named customer. See the note above.
The shape of the problem
Admissions is seasonal, and the season is short. Six weeks produce most of the year's enrolments, enquiry volume is four or five times the off-season, and every parent enquiring with you is enquiring with three competitors on the same afternoon.
Three things go wrong every year:
- The enquiry spike outruns the counsellors, and the overflow is worked by whoever is free, so nobody owns the relationship.
- A parent who called in March and re-enquires in May is treated as a new enquiry, and has to explain everything again.
- Counsellors carry their own follow-up lists, so when one is on leave during the busiest fortnight of the year, their conversations pause.
What is built
Branch and stream decide the owner. An enquiry for the science stream at the south branch goes to that branch's counsellors, always — never to the general pool, and never to whoever happens to be next in a global rotation.
Contact history is the first thing on the screen. Re-enquiries attach to the existing parent record, so the counsellor opens with what was discussed in March instead of asking for it again. In a purchase decided by trust, this is worth more than any other single change.
Follow-ups belong to the branch, not the person. Each counsellor works their own queue, but the branch head can see all of them — so leave, illness and a sudden Saturday spike are covered rather than silently dropped.
Capacity is a routing input. During peak weeks, a counsellor already holding forty live conversations stops receiving new ones automatically, instead of receiving them and working none of them well.
What it changes
The counsellor's morning is one screen: overdue first, today next, nothing else. The branch head's morning is four numbers: unowned, median first response, overdue, and enquiries untouched for three days.
The interesting outcome in a seasonal business is not that conversion jumps. It is that the season is survivable at the same headcount — the volume that previously required temporary hires, and produced the dropped-enquiry problem in the first place, is absorbed by the queue.
The part worth copying
Do not build the reporting first. In a six-week season, a dashboard that explains in July why June went badly is a post-mortem. What matters is a screen in June that shows which parents have not been called back yet, while calling them back is still possible.
More case studies
A developer makes the site-visit pipeline visible
An illustrative deployment: a long sales cycle where the only number that predicts revenue is site visits booked and attended — and where nobody could see it weekly.
A diagnostics chain moves 40 telecallers off spreadsheets
An illustrative deployment: eleven centres, four spreadsheets and no owner on half the enquiries — and what changes in the first month when routing is automatic.
Get your team off spreadsheets this week
Import your leads, add your users, set your routing rules. Most teams are live the same day.