Case study · Illustrative example

Recovered 14% of stalled admissions enquiries in one intake season

Illustrative example. This shows how an engagement of this kind typically runs. It is not a report of a specific client's project, and the figures are typical outcomes, not measured client results. Your numbers depend on your data; the readiness assessment tells you what to expect.

The typical situation

Tens of thousands of enquiries arrived each season. Counsellors worked them in the order they came in, and a large share stalled silently after the second contact.

The admissions CRM held every interaction; nobody had asked it which enquiries were worth a third call.

What the data looked like

Three seasons of CRM interaction logs, application outcomes, call records and campaign source. Call-outcome fields were inconsistently filled; part of the work was a call-verification app so that outcomes could be trusted.

What we built

  • A daily priority list for counsellors: which stalled enquiries are most likely to convert with one more contact.
  • Verified call logging so the model trained on real outcomes.
  • A weekly funnel report for admissions leadership by source and programme.
Your systemsClean data layerModel or rulesAlerts and reports

Typical outcome

MeasureBeforeAfterPeriod
Stalled enquiries converted to applicationbaseline+14%one intake season vs the previous
Counsellor calls per application11.28.6same period

What usually trips these projects up

The verification app should have been a separate, earlier project. Model work waited six weeks for trustworthy outcome data.

Have a similar problem?

Tell us what is going wrong and what data you keep. The first conversation is free and usually ends with a straight answer about whether this is worth doing.

Start the readiness checkTalk to us