Letter to the PM Who Just Replaced the Bot Greeting With a Real Name

You’re the product manager who just inherited an AI mandate inside a denomination where half the staff still prints bulletins on Thursday afternoons. The mandate arrived with a deck that promised “scalable pastoral care” and a timeline that assumed the hard part was the model. No one mentioned the volunteers who answer the phones, or the fact that trust here moves through names and clear trust signals, not notifications.

You made the first change quickly. You swapped the bot greeting for a real person’s name because the early logs showed people typing “who is this” before they typed anything else. That move felt small. It also exposed the larger pattern no one had named yet.

John Wesley’s three rules give the frame. Do no harm. Do good. Stay in love with God. In product terms the first rule means never letting an interface pretend to be a relationship it cannot sustain. The second means designing every surface so it actually routes people toward living people. The third means keeping the goal of the work pointed at real formation instead of simulated engagement.

The greeting change we made after the first week of complaints

The first version opened with a clean line: “Hi, I’m here to help with your ministry questions.” Within days the support inbox filled with messages that ranged from polite confusion to outright anger. People wanted to know who was on the other side and whether their question would reach anyone who actually knew their church.

We replaced the line with a name and a short role: “Sarah, children’s ministry coordinator, responds here.” The complaints dropped. Reply volume stayed flat for a couple of days, then climbed. The difference was not the model. It was the removal of the pretense.

Wesley’s first rule showed up immediately. Pretending the system was a person did harm because it trained users to expect a relationship that would never appear. Naming Sarah removed the deception before it could compound.

Why the photo and direct number mattered more than the model behind it

The next iteration added a small headshot next to Sarah’s name and a direct extension that routed to her desk line during posted hours. Session length did not change. First-reply rate did. People who saw the photo and the number were noticeably more likely to send a second message instead of closing the tab.

The photo worked because it signaled that a real human had agreed to be visible. The number worked because it gave an escape hatch. Both moves followed Wesley’s second rule. They turned the interface into a handoff instead of a trap.

We tested the same pattern on a different surface, a volunteer scheduling agent. When we hid the coordinator’s name and photo behind a generic “Support” label, completion rates fell. When the name and photo returned, completion rose again. The model stayed identical. The trust signal changed the outcome.

The metric we now track instead of session length

Session length rewarded long conversations with the agent. We stopped measuring it. The number we watch is the share of conversations that end with an explicit handoff to a named person within two messages. That metric now sits on the same dashboard as weekly active volunteers.

Wesley’s third rule keeps the target honest. The work is not to keep users inside the product. It is to keep them connected to the actual body they joined. When the handoff rate rises, we know the interface is doing its job instead of substituting for one.

The same shift appeared when we applied the pattern to a prayer request form. Adding the name and photo of the intercessor who would receive the request meaningfully increased the number of follow-up emails from church members. People treated the request as a relationship because the surface told them it was one.

Your Turn: Apply This Today

• Pick the single ministry surface that currently opens with a generic bot line and replace it with one named person’s name plus role this week.
• Add that person’s actual headshot from the staff directory, sized no larger than the name itself.
• Include their direct extension or Slack handle with posted availability hours.
• Run the change for seven days and record the reply rate on day one and day seven.
• Compare it against the prior seven-day average for the same surface.
• If reply rate rises, leave the change live and apply the same pattern to the next surface on your roadmap.

Two recent posts that trace the same thread are Letter to the PM Who Just Inherited the Ministry Agent Schedule and The Context Layer Ministry Teams Skipped When Agents Arrived.

I consult with ministry product leaders on human-first AI interfaces, trust signals in faith-facing products, and metrics that track handoffs rather than dwell time. Let’s talk.