Someone messages at half past eleven at night asking whether there is anybody they can talk to. Nothing else. No context, no name.
Everything about how that message is handled matters, and almost none of the handling should be automated.
Myth 1: a warm automated reply is supportive
Reality: someone reaching out at that hour needs a person, and a sympathetic automated message can feel worse than none. The useful response says what is available, when, and where to go if it is urgent.
Myth 2: urgent routes can be implied
Reality: they must be explicit and immediate. Crisis lines, emergency services and whatever local urgent support exists, shown before anything else, in plain language.
Myth 3: an assistant should ask what is wrong
Reality: it should not. Gathering detail from someone in distress, into an automated system, serves nobody. A name and a contact method is enough to get a person calling.
Myth 4: the name of the service is obvious
Reality: pastoral care means nothing to most people. A page saying somebody is available to talk, privately, with no expectation attached, reaches far more people than one using a term only insiders use.
Myth 5: availability does not need publishing
Reality: it is the main question. Who, when, how quickly somebody responds and whether it can be arranged discreetly. Uncertainty is what stops people asking.
Myth 6: only members of the congregation ask
Reality: many enquiries come from people with no connection at all, who have simply found a church website at a difficult moment. Saying explicitly that anybody can ask is important.
Myth 7: confidentiality needs no explanation
Reality: it is what people most want to know before saying anything. Publishing the position, including any limits, is what makes the first message possible.
Myth 8: automation adds nothing
Reality: it adds one thing well. At half past eleven, it can show the urgent routes, say who is available and when, explain that contact can be discreet, and pass a name and number to that person. That is the whole safe contribution.
What to publish
Who is available, how to reach them, how quickly, whether it can be confidential, that anybody can ask, and the urgent routes shown first.
Give the contact a name
People are far more likely to reach out to a named person than to an office. It costs nothing and it changes the response rate.
Explain what happens next
A conversation, at a time and place that suits, with no obligation to anything. People fear being drawn into something and need telling they will not be.
Route safeguarding concerns properly
Anything involving a child, a vulnerable adult or a risk of harm needs the safeguarding contact and the proper authorities, immediately and without discussion.
Other contact arrives through the same channel
It is covered in community groups and volunteering at churches and weddings, baptisms and funerals questions for churches.
Routing is a discipline worth measuring
It is covered in complaints and feedback routed to the right person and how to measure support deflection rate the right way.
Getting started
Publish who is available, how to reach them and the urgent routes first, then capture a name and number at any hour and get it to a person. SpideyChat for churches answers from your published pages and never attempts support. Try SpideyChat on your own site, or read about answers on the features page.