Tutoring centers
Match students to the right tutor
Tutor matching usually slows down when parent inquiries, student goals, subject needs, tutor skills, calendars, and assessment notes do not tell the same story, or when a family asks for tutoring or a student needs a new tutor match. Imagine keeps those sources in view, prepares a student summary, tutor-match recommendation, and parent response draft, and separates the ready work from the judgment calls. After review, the approved update goes back to the CRM and scheduling system, so students get matched faster without directors rebuilding context.
The manual reality today
-
01
Too many tabs before tutor matching can move
parent inquiries, student goals, subject needs, tutor skills, calendars, and assessment notes each hold part of the answer, so the team burns time piecing together what happened before they can respond.
-
02
Tutor matching can stall until someone notices
When a family asks for tutoring or a student needs a new tutor match, the next step can sit until someone checks the right queue, thread, portal, or spreadsheet.
-
03
The tutor matching history is hard to defend
Approvals, notes, and updates end up in side channels, making it hard to tell what was sent, what changed, and who signed off.
How Imagine handles it
-
01
Read the tutor matching signals
Imagine watches parent inquiries, student goals, subject needs, tutor skills, calendars, and assessment notes for new activity, stale items, and changes that affect the work.
-
02
Separate routine tutor matching work from judgment
Messages, records, dates, and prior decisions are grouped so the next step starts with the facts already attached.
-
03
Draft the next tutor matching touch
Imagine drafts a student summary, tutor-match recommendation, and parent response draft using your rules, tone, and thresholds, then flags anything that needs judgment.
-
04
Write the tutor matching result back
After review, approved actions are recorded in the CRM and scheduling system with the context, approver, and timestamp preserved.
Works with the tools you already run
- TutorCruncher
- Teachworks
- Acuity Scheduling
- Calendly
- HubSpot
- Google Workspace
What changes
Decisions around tutor matching surface sooner
Prep work and status checks run continuously, so the team sees the few items that actually need a decision.
Tutor matching communication feels less random
Each next step follows the same rules and cadence, so customers, clients, candidates, and vendors get a reliable experience.
The tutor matching record is easier to explain
Source context, approver, and destination update stay together, so the workflow is easier to audit or explain.
Frequently asked questions
How does Imagine handle tutor matching?
Imagine watches parent inquiries, student goals, subject needs, tutor skills, calendars, and assessment notes, spots when a family asks for tutoring or a student needs a new tutor match, and prepares a student summary, tutor-match recommendation, and parent response draft for review. Approved actions sync back to the CRM and scheduling system with the supporting context attached.
What parts of tutor matching can stay manual?
You decide what can move automatically and what needs review. Anything outside your rules is routed to the responsible person before the CRM and scheduling system is updated.
Which tools feed tutor matching?
This workflow can connect to systems such as TutorCruncher, Teachworks, Acuity Scheduling, Calendly, HubSpot, Google Workspace. Imagine works on top of those tools instead of replacing the system of record.
How does tutor matching feel different?
The team stops rebuilding status by hand. They open a queue that shows what changed, what is ready, and what still needs approval so students get matched faster without directors rebuilding context.