CRM
Educational Consultant Client Follow-Up CRM: From First Enquiry to Consultation
Build a simple educational consultant follow-up workflow from first enquiry to booked consultation using ordinary CRM records without turning the system into admissions case management.
Overview
A missed follow-up can cost a consulting practice more than a weak homepage.
Families often contact several advisors. If an enquiry sits in an inbox without a clear owner or next step, the practice can lose a qualified client before the first conversation.
A lightweight CRM workflow helps organize the sales side of the relationship.
It should not become a shadow admissions database.
OneStudio's current public CRM scope includes client records, contact details, interaction history, related bookings, notes/labels and booking history. See Features.
Define the stages before adding labels
A simple lead flow might be:
The exact labels can differ.
What matters is that everyone understands what each stage means.
- New enquiry
- Needs response
- Consultation offered
- Consultation booked
- Consultation completed
- Follow-up required
- Converted to client
- Not a fit / closed
Capture only first-contact information
For a new lead, the practice may need:
Do not fill a generic CRM record with every admissions detail at the first touch. Keep detailed student casework in the practice's appropriate system.
- parent or student name;
- email;
- phone if used;
- student grade;
- service interest;
- broad timeline;
- source;
- short note.
Respond with one clear next step
A good first reply does not create another maze.
Depending on the business, the next step may be:
Make the next action obvious.
- book a free fit call;
- book a paid strategy session;
- answer one qualification question;
- review services and reply;
- wait for the consultant to confirm fit.
Use booking history as sales context
If a prospect books a consultation, the consultant should be able to see that event alongside the client record.
Useful context includes:
This reduces duplicate outreach.
- consultation type;
- date/time;
- completed/cancelled status;
- payment status where enabled;
- ordinary notes.
Separate sales notes from student case notes
A CRM note might say:
Interested in comprehensive Grade 11 support. Parent requested evening consultation. Follow up Friday if not booked.
It should not become a full student case file with academic records and application materials.
Different data deserves different systems and access controls.
Create a post-consultation rule
Every completed consultation should end with a defined state.
Possible outcomes:
Converted
The family chooses a service.
Considering
Send the agreed follow-up and set a review date.
Not a fit
Close the lead respectfully and retain only appropriate business records.
Future timing
The family may be relevant later. Add a clear follow-up date rather than an indefinite “maybe.”
Use reminders for appointments, not for every marketing touch
OneStudio supports booking reminders and notifications when configured.
That is useful for:
Do not assume this equals a full marketing automation platform with complex nurture sequences.
If the practice needs long email campaigns, verify the actual system used for those campaigns.
- consultation confirmation;
- appointment reminder;
- change/cancellation communication.
Track source carefully
OneStudio's public analytics include information by booking source where available.
That can help compare booked appointments from different sources.
For ordinary CRM follow-up, source labels can still be useful:
Do not invent attribution precision the system does not provide.
- referral;
- organic search;
- school/community referral;
- social;
- event;
- returning family.
Create a lightweight service handoff
When a lead becomes a client:
The handoff should be deliberate.
- confirm the purchased service;
- confirm payment state if relevant;
- record the agreed next step;
- move student casework into the appropriate operational system;
- avoid copying detailed student materials into generic notes.
Follow-up timing examples
These are business-process examples, not platform automation promises.
After initial enquiry
Respond within the practice's real service standard.
After consultation
Send the agreed proposal, package link or next step.
If no response
Use one or two reasonable follow-ups, then close or pause.
Before the booked appointment
Use the real configured reminder.
Avoid relentless follow-up that feels automated or intrusive.
A useful weekly CRM review
Once a week, review:
This is simple, but it prevents the quiet leakage that happens when leads live only in email.
- new enquiries with no response;
- consultation offers not booked;
- upcoming consultations;
- completed consultations needing follow-up;
- leads waiting on a future date;
- duplicate or stale records.
What this CRM should not do
Do not use an ordinary client CRM as a substitute for:
Those belong to specialist workflows if the practice needs them.
- essay management;
- application task tracking;
- school lists;
- admissions deadlines;
- student portals;
- counselor caseload management.
CTA
Keep the sales relationship organized without turning the CRM into an admissions system.
Explore OneStudio client and booking features, or review current plans for CRM, booking, payments and reminders.