Quick answer: AI should never write grief messages, crisis statements, counseling correspondence, conflict or discipline communication, or anything describing an individual's private circumstances. These are trust moments, not content tasks. Enforce the boundary by naming the categories in your AI policy settings so the assistant declines and routes them to a pastor, and by training your team that sensitive topics go to a person first.
The line most churches draw instinctively
Ask any pastor whether AI should write a condolence message and the answer is immediate. No.
They are right, and the reason is worth naming precisely. It is not that AI would write something bad. It might write something beautiful. The problem is that the family would be receiving carefully composed words from a system that does not know them, has not sat with them, and will not be at the funeral.
Presence is the message. Words are just how presence gets delivered.
The prohibited list
These categories belong in every church AI policy as hard limits.
Grief, death, and condolence
Any message to a grieving family. Any announcement of a death that goes beyond service logistics. Any memorial content describing the person.
The narrow exception is pure logistics — "The service will be Saturday at 2pm in the sanctuary" — and even that should be reviewed by someone who knew the family.
Crisis communication
Staff misconduct, a safety incident, a financial problem, a public accusation, a building emergency. These are the moments your congregation's trust is either reinforced or damaged permanently.
Crisis statements require someone who understands the full situation, the legal exposure, the pastoral weight, and what has already been said privately. AI has none of that context and cannot be given it safely.
Counseling and personal correspondence
Never. And underneath the obvious problem is a second one: using AI here means pasting someone's private situation into a tool. That is a confidentiality breach regardless of what gets written back.
Conflict and church discipline
Disputes between members, communication about a discipline process, responses to complaints about leadership. Every word carries weight in these situations and every word may be repeated later.
Anything about a specific person's hardship
Illness, job loss, divorce, addiction, a struggling child. Even with permission, even with good intent, these should be written by someone in relationship with the person.
The gray areas, and how to think about them
Some cases are genuinely harder. A useful test: would the recipient feel differently if they knew this was drafted by AI?
A Sunday event reminder — no. A message about their child's illness — yes, deeply. That gap is the boundary.
Prayer requests
Never paste them into any tool. The general prayer prompt for a bulletin is fine. The specific request is not.
Pastoral encouragement to the whole church
A general note from the pastor after a hard week can be AI-assisted in structure, but the pastor should write the substance. Congregations can tell the difference between a pastor's voice and a well-organized one.
Hospital and care team logistics
Scheduling and coordination are fine. What gets said at the bedside is not a content task.
Making the boundary real
A prohibited list in a document only works if people remember it at the moment they need it — which is usually late at night under pressure, exactly when memory fails.
The better approach is to build it into the tool. In ChurchCopy, prohibited topics live in your AI Policy and Guardrails settings. When someone asks the AI Chat Assistant for something in a restricted category, it does not produce a draft — it says this is a pastoral matter and points the person to leadership.
That behavior does more training than any handbook. It teaches the boundary at the exact moment it matters, to every person, including a volunteer who never read the policy.
Train the instinct, not just the rule
Rules cover the cases you anticipated. Instinct covers the rest. Teach your team one sentence:
If a real person's pain is in the message, a real person writes the message.
That single line handles nearly every situation your list did not predict.
What AI should do instead
There is a positive version of this boundary that is easy to miss. Every hour AI takes off the routine pile is an hour available for the work that cannot be delegated.
The event graphics, the six-channel rewrite, the newsletter assembly, the ads, the FAQ page — all of that is legitimately mechanical. A single Copy Package handles a week's worth in minutes.
That is the trade churches should be making. Automate the production so the pastoral work gets the attention it deserves, rather than getting squeezed into whatever is left on Thursday night.
A short audit for your team
Look at last month's communication and sort it into three piles:
- Pile one: routine and logistical. This is safe AI territory.
- Pile two: pastoral and personal. This is never AI territory.
- Pile three: genuinely unclear.
Pile three is the valuable one. Take it to your leadership, decide each case, and add the decisions to your policy. Do that once and your gray area shrinks permanently.
Why this boundary is worth guarding
Churches are one of the few places left where people expect to be known. The whole premise is that someone notices when you are absent, remembers your mother's name, and shows up when something breaks.
Speed is not the value there. Presence is. Any tool that quietly substitutes for presence costs more than the time it saves, no matter how good the writing is.
Use AI generously for the mechanical work. Guard the pastoral work carefully. That is the entire discipline, and churches that hold it will get the benefits without paying the price.
What to do when a sensitive request arrives anyway
Policies describe the ideal. Real weeks are messier. A ministry leader asks for help writing something about a family in crisis. It is Friday, the person asking is stressed, and saying "our policy prohibits that" feels cold.
Give your team a path rather than just a prohibition.
Step one: name the category out loud. "This one's pastoral, so it needs to come from a person rather than a draft." Said plainly and without apology, this almost never causes friction. People understand immediately.
Step two: route it, do not just decline. The volunteer or staff member should know exactly who to hand it to. A prohibition with no next step turns into either a delay or a workaround, and workarounds are how the boundary erodes.
Step three: help with the parts that are not pastoral. Often a sensitive situation has a logistical wrapper — a service time, a meal sign-up, a room change. Those pieces can be handled normally. Separating them lets the pastor spend their limited time on the words that carry weight.
Step four: write down the decision. If the request was genuinely a gray area, add it to your policy after the fact. Your prohibited list should get slightly more precise every quarter, shaped by the actual situations your church encounters rather than the ones you imagined.
Churches that handle these moments well are not the ones with the strictest rules. They are the ones where everybody knows what to do in the ninety seconds after a hard request lands, because the path was decided long before anyone was under pressure.
Try for free — set your guardrails once and let them hold the line.