Likely leakage
Where the enquiry cools
- No standard first-reply questions, so staff ask details one by one.
- Parent intent cools overnight because there is no immediate expectation-setting.
- Follow-up owner is unclear after the first reply.
See the practical output before you buy.
This sample shows how Pellex turns one messy enquiry path into a concrete next step: where intent cools, what information is missing, what staff should ask, and whether a small automation is worth testing.
Scenario
After-hours tutoring enquiry via WhatsApp
A parent messages at 9:40pm asking about Primary 5 maths support. The team replies the next morning, but often misses student level, preferred schedule, exam timeline and follow-up owner.
Fix
Smallest useful fix
- Auto-collect four safe admin fields: student level, topic, target date, preferred times.
- Create a staff-ready summary in email or Sheets.
- Use an approved first-reply template that promises a human follow-up window.
Suggested handoff
Staff-ready summary format
Enquiry: P5 maths help for fractions before school test.
Missing details: preferred weekday/weekend time, current materials, trial preference.
Next action: reply with approved questions and assign owner for same-day follow-up.
Boundary: no educational assessment or guarantee; admin scheduling and information collection only.
Paid next step
What Pellex would build in a starter pilot
A single intake form or message-to-summary workflow connected to email, Google Sheets or the existing team inbox, with approved copy and documentation. Scope stays narrow so the team can test it without changing all operations.