Care at Scale Needs Clear Ownership

When someone asks for support, the organization needs a clear answer to three questions: who responds, what happens next, and how will we know the need was addressed?

I was hired to lead a newly created role at Churchome and designed and built Pastor Chat’s digital care infrastructure from scratch using Crisp chat technology. The work equipped more than 90 staff members and 30 volunteers and supported more than 85,000 practical and spiritual care conversations.

Build the service around the request

The chat window was the entry point. Behind it, I built conversation guides, training resources, quality practices, multilingual access, and escalation pathways. A useful service required the team and workflow to support the promise people saw on screen.

Make three responsibilities explicit

• Receive: Give people an accessible way to raise a need and realistic expectations about the response.
• Route: Name the person or team responsible, provide guidance, and identify when additional help is needed.
• Follow through: Define what completion means and how unresolved needs are reviewed.

The service promise is only as dependable as the handoff behind it.

Use a scale your team can sustain

A small organization may begin with a simple process and a named owner. A larger service may require staffing plans, permissions, training, and regular quality review. Both need clear responsibility and appropriate handling of personal information.

Trace one request from arrival to follow-up. Look for repeated explanations, unclear ownership, and requests that wait without a next step. Those points reveal where additional capacity would improve the experience.