The form collects the info. It won't decide which tutor the student should get.
A parent writes "my kid's falling behind in math" and a form dutifully files it away. The real work — which tutor, which level, and a reply before they enrol elsewhere — is judgment, and it's exactly what a small service can hand off.
01 The pain
Enquiries arrive with the raw facts — grade, subject, "struggling with math" — but a Google Form only collects them. Someone still has to read each one, work out the right tutor and level, and get back before the parent's patience runs out.
The rush hits at back-to-school and before exams, and it's unforgiving: miss the window and an anxious parent has already booked the tutor who replied first.
02 Where your software stops
A form is a bucket. It gathers the grade and subject but doesn't match — it can't look at "Grade 9 math, falling behind" and suggest which tutor and what level fits, or draft the reply that keeps the parent engaged.
So every submission still waits on a person to interpret and respond, and at peak season that queue is where families are lost.
Software stops at "collects the answers." The real gap is "which tutor, what level, reply now" before the parent enrols elsewhere.
03 Why you can't just offshore it
A remote team can't match to a curriculum they don't know — Manitoba's grade structure and course outlines decide who's the right fit. And in Winnipeg's Chinese-speaking families, my bilingual background is an advantage an offshore desk can't offer.
04 The gap I fill
I build the matching layer that reads each enquiry, suggests the right tutor and level from your roster, and drafts a fast, warm reply — so families hear back inside the window instead of after it, and your intake keeps up through the back-to-school rush.
And it never assigns a student on its own. You review every match and approve the reply before it sends. Each suggestion is drawn from your actual tutors and their subjects — if there's no clear fit, it says "not found" instead of guessing.