Skip to main content
Back to Blog
online prayer request form
church forms
prayer request template
church website
prayer ministry

Online Prayer Request Form for Churches: Template + Best Tools

February 3, 20268 min read
A prayer request form is the single most important page on most church websites — and one of the most overlooked. It's where vulnerability meets your ministry. Get it right and you build trust, capture needs, and route them to people who can actually pray. Get it wrong and requests die in an inbox no one checks.

This guide gives you a complete field template you can copy, plus a clear-eyed comparison of the tools churches use to host these forms.

What Makes a Good Online Prayer Request Form

Before fields and tools, the principles:

  • Short enough to finish on a phone in under 90 seconds. Most submissions happen on mobile, often in a hard moment.
  • Honest about what happens next. Tell people who will see this and when to expect a response.
  • Privacy choices, not assumptions. Let the requester decide what's shared.
  • Routes to a human, not a black hole. Every submission should hit at least one real person within hours.
  • Accessible. Proper labels, sensible tab order, screen-reader friendly. Many submissions come from people who genuinely need accessibility.
  • The Field Template (Copy-Paste Ready)

    Here's a complete field set. Adapt to your church, but resist the urge to add more — every field cuts completion rate.

    Required fields

  • Your name *(text, optional toggle: "Submit anonymously")*
  • Email *(text — used only for follow-up if requested)*
  • Your campus / location *(dropdown — only if multi-site)*
  • Your prayer request *(long text, no character limit visible to user, soft cap ~1000 chars)*
  • Privacy and routing

  • Who should see this request? *(radio)*
  • - Just the prayer team - The prayer team and our online prayer wall (your name shown) - The prayer team and our online prayer wall (anonymous) - Pastor only — confidential

  • How urgent is this? *(radio)*
  • - Immediate / crisis (please pray today) - This week - Ongoing — please pray over time

    Optional but valuable

  • Category *(dropdown — Health, Family, Work, Salvation, Praise, Other)*
  • Is this a praise / answered prayer? *(checkbox — flips the request into a celebration post)*
  • Would you like a pastor to follow up with you? *(checkbox)*
  • Best way to reach you *(radio: Email / Phone / Text — only shown if follow-up checked)*
  • Phone number *(text — only shown if Phone or Text selected)*
  • Things to leave OFF the form

  • Address
  • Date of birth
  • Marital status
  • "How did you hear about us"
  • Newsletter signup checkbox (don't bundle prayer with marketing — ever)
  • CAPTCHA *if you can avoid it.* Use invisible spam protection instead; visible CAPTCHA in a moment of crisis is cruel.
  • What to Do With the Submission

    The form is the easy part. The pipeline behind it matters more.

    A healthy submission flow:

  • Confirmation screen with a real next step ("A member of our prayer team will see this within a few hours. If you're in immediate crisis, please call [number].")
  • Confirmation email to the requester restating their privacy choice and what to expect.
  • Notification to the prayer team — Slack, email, or push to a moderation queue.
  • Triage by a coordinator — assign tier, route to chain, post to wall, or pastor follow-up.
  • Closeout — when answered, mark it and (with permission) celebrate it publicly.
  • Without steps 4 and 5, the form is just a feelings dropbox.

    Best Tools to Host the Form

    Honest comparison. The right pick depends on your size, your tech stack, and how much manual triage you can absorb.

    ToolBest forStrengthsLimits
    Google FormsChurches under 100 attendeesNo cost, fast to set up, exports to SheetsNo privacy controls, no routing, no prayer wall, no follow-up tracking
    Typeform / TallyBrand-conscious small churchesBeautiful UX, conditional logicSame fundamental gaps as Google Forms — it's still just a form
    Planning Center FormsChurches already on PCOConnects to People records, decent permissionsGeneric forms; no native prayer wall, no chain routing, no anonymity flow tuned for prayer
    WordPress plugins (Gravity Forms, WPForms)Churches with a WP site and a developerLives on your site, full controlYou're now responsible for spam, deliverability, GDPR, and triage UI
    Tithe.ly / Subsplash formsChurches already on those platformsBundled with what you haveForm-level only; no prayer-specific workflows
    Dedicated prayer platforms (e.g., PrayerConnect)Multi-campus churches, growing prayer ministriesForm + wall + chain + moderation + analytics in one model; per-campus routing; native anonymityAdds a tool to your stack

    How to choose

  • Under 100 people, single campus, low volume: Google Forms with a daily email digest to one coordinator is honestly fine. Upgrade when you can't keep up.
  • Already on Planning Center: Start with PCO Forms. Add a dedicated prayer tool when you need a public wall, anonymity, or per-campus routing PCO doesn't give you natively. (Our Planning Center prayer requests guide walks through where PCO ends and a dedicated tool starts.)
  • Multi-site or 500+ people: A dedicated prayer platform pays for itself in the time it saves coordinators. Submission, routing, moderation, wall, chain, and analytics in one place beats stitching five tools.
  • Embedding the Form on Your Church Website

    Wherever you host it, embed it on your site rather than linking out. Two reasons:

  • Trust. Bouncing people to a third-party domain in a vulnerable moment kills completion.
  • SEO. A prayer request page on your domain ranks for "[your church] prayer request" — the most valuable search term you'll ever own.
  • Most form tools provide an iframe embed snippet. Drop it on a page titled "Prayer Requests" with a short intro that says: who will see this, how soon you'll respond, and what to do in a true emergency.

    Privacy and Compliance Notes

    Even small churches handle data that meets legal definitions of "sensitive personal data" — health, religion, sometimes mental health. Two practical floors:

  • Don't store more than you need. No address, no DOB. If you don't ask, you can't leak it.
  • Have a stated retention period. "Prayer requests are kept for 90 days unless you ask us to keep them longer." Then actually delete them.
  • GDPR / UK GDPR applies if you serve any EU/UK residents. The basics: lawful basis (consent for prayer requests), right to deletion, no transfer to non-vetted third parties.
  • FAQ

    Should prayer requests be anonymous by default?

    No — but anonymity should always be one click away. Defaulting to anonymous reduces pastoral follow-up; defaulting to named without an opt-out reduces submissions. Offer the choice on every form.

    Can I use a Google Form for prayer requests?

    Yes, for small churches with low volume. You'll outgrow it the moment you need privacy levels, per-campus routing, or a public prayer wall. Google Forms is a starting line, not a finish.

    How do I prevent spam submissions?

    Invisible reCAPTCHA or honeypot fields, not visible CAPTCHA. Most dedicated tools handle this for you.

    Where should the form live on my website?

    A dedicated /prayer or /prayer-requests page linked from your main nav and footer. Don't bury it in a contact form.

    How quickly should we respond?

    Set the expectation on the form ("within 24 hours") and meet it. Speed matters less than honesty about your speed.

    The Bottom Line

    A great church prayer request form is short, honest about what happens next, and connected to a real human pipeline. The form itself is 20% of the work — the routing, moderation, and response habits behind it are the other 80%. Pick the simplest tool that supports the workflow you actually run, and upgrade when manual triage starts costing more than software.

    Ready to transform your church's prayer ministry?

    Set up your digital prayer wall in under 30 minutes. Plans start at $15/month.

    Get Started