Every vendor demo is a good day: the software works, the presenter knows every screen, and every question has a confident answer. The other 364 days are what you are actually buying — and those days are determined by school software vendor support evaluation, the step most schools skip entirely. Six months after signing, when fee bills are wrong and nobody answers the support number, the feature list in the brochure is worthless.
This guide gives you ten practical tests to run before you sign — tests that reveal how a vendor actually behaves when something goes wrong. Run them during the evaluation period, while you still have leverage, and get the answers in writing.
Why Support Matters More Than Features
School software is not a product you buy once; it is a service you depend on every working day. Attendance is marked every morning, fees are collected every month, results are published every term — and every one of those moments can be blocked by a bug, a forgotten password, or a misconfigured report. The quality of support determines how long each blockage lasts: minutes, hours, or days. For a school, a fee-day outage is not an inconvenience; it is hundreds of parents standing at the counter.
Support also determines whether your staff actually adopt the system. Teachers who get a helpful answer in Urdu within an hour learn to trust the software; teachers whose tickets vanish into silence learn to keep paper registers. When comparing vendors, weight support at least as heavily as features — a simpler system with excellent support beats a feature-rich system with no one to call. Our 15-point software checklist puts support alongside features for exactly this reason.
Tests 1-5: Response, Channels, and Language
Test 1 — The real response-time test. During your trial, submit a genuine support request at a realistic time (a Tuesday morning, not a Sunday night) and time the first human response — not the auto-reply. Ask for their written SLA: first response within how many hours, resolution within how many days, for critical versus routine issues? If they will not put numbers in writing, assume there are none.
Test 2 — The channel test. Check which channels actually work: phone, WhatsApp, email, in-app chat. A vendor whose only channel is an email form that nobody answers is a vendor you cannot reach during a fee-day crisis. Call the support number during the trial and see who picks up.
Test 3 — The Urdu test. Ask your question in Urdu (or Roman Urdu, as your staff would) and see whether you get a clear answer in the same language. Support that only works in English fails the staff who need it most — the office clerk and the junior teacher, not the principal. Good vendors in Pakistan support Urdu, Roman Urdu, and English.
Test 4 — The new-user test. Ask the vendor to explain one feature to a non-technical staff member — your accountant or a junior teacher — and watch. Patient, plain-language explanations predict good training; jargon and impatience predict a painful rollout. Test 5 — The reference test. Ask for two or three school references you can call, preferably schools of similar size in Pakistan. Then actually call them, and ask one question: "When something breaks, what happens?" References who hesitate are telling you something.
Tests 6-10: Escalation, Training, and Contract Terms
Test 6 — The escalation test. Ask: "If my issue is not resolved in 48 hours, who do I contact, and what happens next?" A real escalation path has named levels — support agent, team lead, manager — with time limits. "Email us again" is not an escalation path.
Test 7 — The critical-issue test. Ask how they handle a showstopper: fee bills cannot be generated on fee day, or attendance is down during morning assembly. Is there a priority channel, a phone number, a guaranteed response time? Get the critical-issue process in writing before you need it.
Test 8 — The training test. What training is included — how many sessions, in which languages, on-site or online, and is refresher training available for new staff? Vendors who charge for every training session after launch leave schools with untrained new hires within a year. Test 9 — The update test. How often is the software updated, and how are schools notified? Updates that arrive unannounced on a working morning, changing screens staff rely on, are a support failure in themselves.
Test 10 — The exit test. Ask how you get your data out if you leave. A vendor who answers clearly — "full export in standard formats within 7 days" — respects your school's ownership of its own data. A vendor who dodges this question is telling you that leaving will be painful. Read our guides on switching costs and hidden costs before you sign anything.
Negotiation Tip
Red Flags That Should Stop the Deal
Walk away — or at least pause — if you see these: no working phone support, only a contact form; no references willing to speak; support hours that end before your school day does; extra charges for every support interaction; a contract that locks you in for years with no service-level commitments; or a vendor who cannot explain how you export your data. Also be wary of the vendor whose demo is perfect but who has no local presence, no Urdu-speaking support staff, and no understanding of Pakistani school workflows like BISE registrations, fee vouchers, or multi-shift timetables. International software can be excellent, but only if the support understands the local reality — see our comparison of local vs international school software.
Scoring Vendors and Making the Call
Score each vendor on the ten tests — 2 points for a strong, evidenced answer, 1 for an acceptable answer, 0 for vague or missing. A vendor scoring below 12 out of 20 is a risk, whatever the feature list says. Weight the tests that match your reality: a school with non-technical staff should weight Urdu support and training heavily; a large school should weight escalation and critical-issue response.
Finally, remember that support is a relationship you will live with for years. Choose the vendor whose team you would trust to answer the phone on fee day — because one day, they will have to. And once you have chosen, protect the relationship with clear expectations: log every issue in writing, track response times against the agreed SLA, and raise patterns (not just incidents) in a quarterly review with the vendor.
AI Help: Muse AI
Muse AI is Meta's personal AI assistant, available in the Muse app. It can help you build a vendor scorecard from these ten tests — with space to record each vendor's answers — and draft the reference-call questions to ask other schools before you sign.
Join Muse with invite code LTGSWD — in the Muse app, go to Settings > Redeem token and enter the code.
Disclosure: LTGSWD is the author's Muse invite code.