Small staffs carry wide responsibilities, and phones often ring after the office closes. A family loss, a pastoral emergency, a member in crisis, or a routine question may all arrive through the same number. ThryvHQ builds a quiet first response that identifies urgency, reaches the right person, and leaves a clear summary.
What does a nonprofit or congregation lose to missed calls?
Nonprofits and congregations need reliable coverage because the cost of a missed call is often measured in trust and care rather than a sales figure. The assistant helps a small staff distinguish urgent pastoral or member needs from routine questions, so the right call reaches a person quickly and ordinary requests do not disappear.
Missed-call figures for Nonprofits and congregations
Most difficult coverage
Evenings, weekends, and holidays
Urgent calls
Pastoral emergencies, bereavement, and member crisis
Routine calls
Service times, office hours, events, and facility rental
Useful outcome
A clear human handoff with a texted summary
What does the assistant actually handle on a call for a nonprofit or congregation?
A congregational assistant can ask a gentle urgency question, route pastoral emergencies to the designated person, answer approved routine questions, capture facility or event requests, and send a concise summary. It does not replace pastoral care or make a judgment about a person's situation.
After-hours urgency triage using the organization's approved questions
Routing pastoral emergencies to the right person immediately
Service times, office hours, event details, and facility-rental questions
Message capture with caller details and a texted summary
Calendar and member-system lookup where the organization approves it
What does it need to connect to?
The connection should fit the calendar and member systems already in use. The organization decides what information can be read, what may be written, which people receive alerts, and how long a routine message can wait.
The organization's calendarThe member system already in useApproved email or text notification channelsA shared office or pastoral callback workflow
What does this cost for a nonprofit or congregation?
The phone offer is $297 per month with setup from $1,497. This page does not frame the service as recovered revenue. The useful comparison is coverage: the organization can decide whether a reliable first response, clear escalation, and fewer dropped messages justify the monthly cost within its staffing and care model.
Hear it before you talk to anyone
Call (703) 423-0203. It's a live assistant, not a recording, and there's no form first.
It will ask what kind of business it should answer the phone for. Tell it "a synagogue" or "a church" — then call in with something urgent after hours and listen to how it handles the call. The demo is a role-play, so any times it offers during the role-play are invented. If you want a real conversation at the end of it, it will book that properly.
What happens if it can't handle the call?
The assistant is not pastoral care and should not attempt to counsel someone in crisis. It follows the organization's approved urgency instruction, routes the call to the designated person, and states plainly when a person will respond. Routine requests receive a useful answer or a documented callback.
The organization defines which people receive urgent alerts
Crisis or pastoral concerns route to a trained human rather than an automated answer
Routine questions use approved information and a normal callback path
The assistant never promises confidentiality, availability, or a response time the organization has not approved
Questions nonprofits and congregations ask
Can it handle an urgent call after hours?+
It can ask the approved urgency question, route the call to the designated person, and send the context needed for a human response.
Can it answer service-time questions?+
Yes, when the organization provides current approved information about services, office hours, events, and facility use.
Does it replace pastoral care?+
No. It provides a first response and routes the call. Care, judgment, and conversation stay with people.
Can it use our calendar or member system?+
It can connect to the systems the organization approves, with access and notification rules defined during the assessment.
The tone matters because not every call is an administrative task. A caller may be worried, grieving, or unsure who to contact. The assistant should sound direct and calm, ask only what is needed to choose the next step, and make the handoff visible. It should not perform warmth as a substitute for a person.
Routine questions deserve the same reliability in a different way. Service times, office hours, event details, and facility-rental requests can wait less anxiously when the answer is clear. The organization supplies those answers and decides how changes are maintained so an outdated calendar does not create confusion.
The escalation map is the heart of the build. Who receives an urgent alert? What happens if that person does not answer? Which calls become a morning callback? Which details belong in a text summary? These are organizational decisions, not defaults an assistant should invent.
The measures are simple: urgent calls routed, messages delivered, routine questions answered, callbacks completed, and cases that needed correction. Those signals help a small staff improve coverage while keeping care, discernment, and accountability with the people who carry them.
The organization can change the escalation map without rebuilding its identity. A new office schedule, event calendar, volunteer rotation, or on-call person should become a reviewed workflow update. The assistant remains a dependable doorway while the people behind it keep deciding what care and responsibility require.
