Most school CRMs are contact tables with a follow-up date column nobody fills in. EduDrive treats every admission lead as a workflow with memory — duplicate-checked at the gate, blocked from being saved without a next call, and refreshed in place so context never breaks.
No new training. No SOP document on the fridge. Three small constraints inside the enquiry form do the remembering for your front office.
The instant a number is typed, the duplicate_phone check fires. If that parent has called before, the existing enquiry surfaces — with its full timeline — instead of a fresh blank record.
An enquiry can sit in Active or Passive — but neither state can be saved without a next_follow_up_date. The form simply will not close. The "I'll remember to call them" failure mode is engineered out.
Add a follow-up, change status, log a call — the timeline refreshes via AJAX inside the same modal. Your front-office staff never leave the conversation thread. Context is the product.
The difference between a traditional ERP and EduDrive isn't a feature list. It's whether yesterday's enquiry is still alive on Friday.
Send us one parent number and one current enquiry. In 20 minutes you'll see duplicate-checks, timeline refresh, and WhatsApp follow-up triggers running on your school's data.