Prayer cards pile up in a basket, and nobody knows who wrote which one or who may read it. I would rather ask for the request and the sharing choice together. Then the person decides, and your team knows how to treat every line.
The request. The prayer itself, who it is for, and a few topic choices so your team can sort.
The privacy choice. Pastoral staff only, the prayer team, or the whole congregation. It matters most, so it is required.
Follow up. An optional name, email and phone, plus a box for "please contact me". You see who wants a call and who wants quiet prayer.
Who fills it and who reads it
Anyone in your congregation or community can fill it in. You or a pastor read the answers as JSON or CSV. The form records the choice a person made, but it does not hide rows from anyone. Share the CSV only with the people that choice allows.
A tip
Leave health details to the person. Do not add questions about illness. A visitor's AI would ask "What would you like us to pray for?" Then "Who may read this?" Then "Would you like someone to contact you?" It shows the answers and sends only after a yes. See agent-fillable forms.
More ideas are in forms for churches. A volunteer application helps you grow the prayer team, and a potluck sign-up suits the meal after the gathering.
Questions
Can people send a request without a name?
Yes. This template leaves the name and the contact fields optional. Make a name required only if your team always follows up in person.
How do I sort urgent requests?
Filter the CSV on the urgent column and read those first. The topic column groups the rest, so a pastor can take grief while the prayer team takes the others.
Can my AI agent send a request for me?
Yes. The visitor copies the prompt from the public form into their own AI chat. The AI asks what is missing, shows the answers and submits only after a yes.