- Published on
How to Build a Better Prayer Request Workflow in Planning Center
Prayer requests rarely arrive through one neat channel.
Someone fills out the form on your website. Someone else tells a pastor after a service. Another person calls the church office. A volunteer receives a text. Someone submits a request through Church Center.
The problem usually isn't receiving prayer requests.
It's making sure each request reaches the right people, contains enough information for follow-up, and doesn't disappear somewhere between intake and care.
Planning Center People already provides most of the building blocks for solving that problem: profiles, notes, Forms, notifications, automations, and Workflows. Planning Center's own documentation recommends using forms and profile notes to capture prayer requests and Workflows to coordinate follow-up. (Planning Center Help)
The challenge is designing the intake process around those tools.
Here's a practical way to think about it.
Start With the Outcome, Not the Form
Before building anything, decide what should happen after someone asks for prayer.
For example:
- The prayer request should be attached to the correct person.
- The request should be visible only to the appropriate ministry team.
- Someone should know that follow-up is needed.
- The person should enter your church's existing care process.
- Staff should be able to see what has already happened.
That sounds obvious, but it's easy to start with:
"We need a prayer request form."
A form is only the front door.
The actual system is everything that happens after someone walks through it.
Planning Center's prayer-request guidance already reflects this approach. Requests can be stored as notes on a person's profile, access to sensitive prayer-note categories can be restricted, notifications can be configured, and a Workflow field can put someone into a follow-up process. (Planning Center Help)
A Simple Planning Center Prayer Request Workflow
A useful baseline looks like this:
Prayer request
↓
Identify or create the person
↓
Store the request
↓
Route it to the appropriate team
↓
Create follow-up responsibility
↓
Human care
The important part is that each stage has a clear purpose.
1. Identify the person
Whenever appropriate, connect the prayer request to a Planning Center People profile.
That gives your team context and prevents the request from becoming an isolated message sitting in an inbox.
Planning Center Forms already work with People profiles, and Planning Center recommends using Forms to collect information such as prayer requests directly from people in your community. (Planning Center)
For anonymous prayer requests, your church can obviously design a different path. Not every request needs to become a named contact.
2. Store the prayer request somewhere intentional
Planning Center provides a Prayer Requests note category by default, and churches can create private note categories where more sensitive requests should only be visible to specific collaborators. (Planning Center Help)
This is preferable to scattering prayer requests across:
- general email accounts
- spreadsheets
- staff text messages
- handwritten notes
- random CRM fields
The goal isn't sophisticated technology.
It's simply having one reliable place where the people responsible for care know to look.
3. Decide who needs to know
Not every prayer request requires the same response.
Some may simply need to reach the prayer team.
Others may require:
- a pastoral call
- an email
- follow-up after a hospital visit
- contact from a specific ministry
- confidential handling by a small group of staff
Planning Center lets churches configure notifications for prayer-request notes and form submissions, while its Workflow system can assign people to structured follow-up processes. (Planning Center Help)
4. Let a Workflow carry the follow-up
This is where prayer-request management becomes much more reliable.
Planning Center describes Workflows as multi-step processes where cards move through assigned steps and staff are notified when action is required. Its current documentation even gives prayer or praise requests as a common Workflow example, with steps such as scheduling a phone call and sending a follow-up email. (Planning Center Help)
That means the prayer request itself doesn't need to become your task-management system.
It can simply start the system you already use.
Use Forms as Part of the Workflow, Not the Whole Workflow
Planning Center Forms are already a good way to collect prayer requests.
A form can:
- collect contact information
- write a prayer request into a profile note
- notify members of the prayer team
- add someone to a Workflow
- trigger other automations
Planning Center specifically documents Forms as a way to collect prayer requests and save them to someone's profile, while Workflow fields and automations can route submissions into follow-up processes. (Planning Center)
So there's no reason to replace a working prayer-request form simply because a new technology exists.
But a form does not have to be the only way someone can enter the workflow.
Some People Would Rather Talk
Prayer requests are unusual data.
They're often not:
Name
Category
Description
They're more like:
"My mother was diagnosed last week and we're trying to work out what happens next. She has surgery Thursday, and I'd really appreciate prayer for her and the family."
Someone can absolutely type that into a form.
But some people may find it easier to explain their situation conversationally.
That creates an interesting alternative front door:
voice conversation
↓
structured information
↓
the same Planning Center process
The crucial idea is that conversational intake shouldn't create another place for church staff to work.
It should feed the systems they're already using.
Planning Center's MCP Opens a New Intake Option
Planning Center recently introduced its official Model Context Protocol, or MCP, which lets authorized AI tools interact with Planning Center data.
Most Planning Center products currently expose read access through the MCP. People also supports limited write actions, including creating notes and filling out Forms. Planning Center itself lists adding a prayer-request note to someone's profile as one example of how the MCP can be used. (Planning Center)
That makes a new kind of prayer-request workflow possible.
Instead of asking someone to manually complete the Planning Center Form, a conversational agent can gather the information and submit the appropriate structured data on their behalf.
The ministry workflow doesn't change.
Only the intake experience does.
What a Conversational Prayer Request Workflow Can Look Like
At Babelbeez, we've implemented this as a preconfigured Prayer Requests voice-agent role.
The flow is:
1. Someone opens the prayer-request agent
The agent lives directly on the church website, so the visitor doesn't need to call another number or install anything.
2. They explain the request naturally
The agent gathers the details the church has configured for that workflow.
That might include:
- name
- contact information
- the prayer request
- whether follow-up is wanted
- fields required by the church's Planning Center Form
3. Babelbeez checks the Planning Center Form
Through the church's authorized Planning Center connection, Babelbeez can inspect the relevant PCO Form and determine which fields are required before submitting anything.
4. The request is submitted into Planning Center
The current Babelbeez implementation can create or update the relevant People record and submit the completed Planning Center Form. That Form can then trigger the church's existing Planning Center Workflow. (Babelbeez)
5. Humans take over
The care pastor, prayer team, administrator, or other assigned staff member continues the process exactly where the church already manages it.
The goal isn't to automate pastoral care.
It's to automate the administrative gap before pastoral care.
Keep AI Permissions Narrow
Connecting any public-facing AI system to a church database deserves caution.
The useful question isn't simply:
"Can the AI access Planning Center?"
It is:
"Exactly what is this particular agent allowed to do?"
Babelbeez uses scoped tool allow-lists for public agents.
For the prayer-intake implementation, the agent can be limited to the specific Planning Center MCP tools needed to:
- locate the appropriate Form
- inspect its required fields
- submit the completed Form
Broader administrative capabilities are excluded from the default public-agent scope. (Babelbeez)
This follows a simple principle:
Give a public intake agent only the permissions required to perform the intake workflow.
Nothing more.
The church still authorizes the underlying Planning Center connection through OAuth.
Prayer Requests Still Need Humans
It's worth being explicit about this because AI marketing occasionally becomes drunk on its own adjectives.
Receiving a prayer request is not the same as providing pastoral care.
A conversational agent can help:
- receive information
- ask configured follow-up questions
- organize the answers
- submit them to Planning Center
- route the request into the appropriate process
- hand off to a person
It should not replace:
- pastoral judgment
- counseling
- prayer
- safeguarding decisions
- crisis care
- human compassion
A good prayer-request workflow uses automation to make the human part more reliable, not to remove the human part.
A Practical Planning Center Setup
If your church is designing this workflow from scratch, a sensible structure is:
In Planning Center People
Create or confirm the appropriate prayer-request note categories, including private categories where necessary.
In Forms
Build a prayer-request Form containing the information your team actually needs.
Avoid collecting fields simply because you can. Every extra question adds friction.
In Workflows
Create the steps your ministry team follows after a request arrives.
For example:
New prayer request
→ Review request
→ Assign appropriate staff member
→ Call or email if follow-up requested
→ Record outcome
→ Follow up later if needed
Planning Center Workflows can assign responsibility and track people through multi-step processes, while Forms and automations can add people to those Workflows automatically. (Planning Center Help)
At the intake layer
Offer the channels that make sense for your community:
- Planning Center Form
- Church Center
- website form
- voice prayer-request agent
- staff-entered request for phone or in-person conversations
They do not have to compete with each other.
They can all lead to the same underlying care workflow.
And if your church uses broader automation tooling, Babelbeez's workflow automation can carry the same structured conversation data into n8n, Zapier, Make, webhooks, and other connected systems.
The Best Prayer Request System Is the One Your Team Actually Uses
Church technology has an unfortunate habit of producing new dashboards.
Prayer-management dashboard.
Volunteer dashboard.
Communications dashboard.
Care dashboard.
Then somebody creates a spreadsheet to remember which dashboard they're supposed to check.
A better approach is often to make new intake channels feed the system your staff already uses.
For churches built around Planning Center People, that means the important destination isn't the AI agent.
It's Planning Center.
The agent is simply another way of getting information there.
Try the Workflow Yourself
Babelbeez includes a preconfigured Prayer Requests role designed for exactly this use case.
You can create an account, enter your church website, and preview a trained voice agent on your actual site in about three minutes. No prompt engineering or conversation-flow building is required.
Our Faith Operations page also runs a real public Prayer Request agent, so you can try the conversation before setting anything up.
→ Try the live Prayer Request workflow
For the public demo, use fictional names and information rather than submitting a real prayer request.
For developers and church IT teams who want to inspect the Planning Center MCP itself, we've also released our open-source PCO MCP Explorer, which displays the live MCP tools and schemas exposed by Planning Center.