A student writes to a general enquiry address at two in the morning. They are struggling, they are not sure who they should be telling, and the message lands in a queue that opens at nine.
Every institution has some version of this, and how it is handled matters more than any other message the website receives.
Myth 1: an assistant should try to help
Reality: it should not attempt support, reassurance or advice of any kind. Its entire job is to make sure the person reaches a human service quickly and knows where emergency help is. Anything else risks someone in difficulty receiving an automated reply instead of a person.
Myth 2: crisis information can sit on a support page
Reality: it must be immediate and unavoidable, at the top of any wellbeing route, before service descriptions, opening hours or booking forms. Someone in crisis will not read three paragraphs.
Myth 3: routing is a minor detail
Reality: institutions have counselling, disability support, financial hardship, academic support, accommodation and chaplaincy, and students cannot tell them apart. Explaining plainly what each does is genuinely useful and entirely safe.
Myth 4: confidentiality does not need explaining
Reality: it is the question that decides whether a student engages at all. What is confidential, what is shared, what triggers an exception and whether academic staff are told must be published clearly.
Myth 5: wait times can be left vague
Reality: a student told nothing assumes the worst and gives up. Publishing honest waits, and what is available immediately while waiting, keeps people in the system.
Myth 6: international students have the same needs
Reality: they may be unfamiliar with how support works, worried about visa implications and far from family. Saying explicitly that using support does not affect immigration status removes a real barrier.
Myth 7: this is separate from everything else
Reality: hardship, accommodation problems and academic difficulty are frequently the same situation. Publishing how services work together stops a student being passed between four inboxes.
Myth 8: automation has no place here
Reality: it has a narrow and valuable one. Answering what each service does, when it opens, how to book and where urgent help is, at two in the morning, is useful. Attempting anything beyond that is not.
Myth 9: only students in crisis use these services
Reality: most contact is practical, about a deadline that cannot be met, a bill that cannot be paid, a diagnosis needing adjustments or a difficult housemate. Treating every wellbeing enquiry as an emergency is as unhelpful as treating none of them that way, and publishing what routine support exists gets people help long before anything becomes urgent.
What to publish
Each service with what it covers, who it is for, how to access it, opening hours, wait times, confidentiality terms and the urgent contacts. That single page answers most enquiries safely.
Route rather than resolve
Every wellbeing contact should end in a named service or an urgent number, not in a conversation, which is a stricter version of the routing described in how SaaS teams route chat to sales or support.
Applicants and students use the same site
Prospective enquiries are covered in prospective student questions that arrive after open days and postgraduate enquiries that need different answers.
Urgent routing is a general discipline
The same pattern applies wherever contact can be an emergency, as in an AI receptionist for IT support.
How SpideyChat handles it
SpideyChat for education providers answers service and access questions from your published pages, shows urgent contacts first and hands every wellbeing enquiry to a person. You can see it on the demo, and plans are on the pricing page.