What a church website form needs in 2026
Church websites serve a unique mix of audiences: first-time visitors checking service times, members submitting prayer requests, couples inquiring about weddings, parents signing up kids for VBS, and community members asking about facility rentals. A single generic contact form can't serve all of these well. Here's what you need:
- Visitor welcome form: name, email, phone (optional), service time preference, how they heard about the church, any questions. Warm tone, minimal fields.
- Prayer request form: name (or anonymous option), prayer request textarea, whether it's for the prayer team only or can be shared with the congregation.
- Event registration: event name, attendee name, email, number attending, child/adult count, dietary or accessibility needs.
- Counseling/pastoral care inquiry: name, contact, nature of need (grief, marriage, premarital, crisis), preferred contact method and time.
- Instant notifications. Route prayer requests to the prayer team, visitor forms to the welcome team, and event registrations to the coordinator — all via webhooks.
Why splitforms works for churches
Most church websites are maintained by volunteers or part-time staff. They don't have budget for $50/month form tools, and they need something that works reliably without constant attention. splitforms is ideal because:
- Free tier that's actually enough. 500 submissions/month, unlimited forms, no credit card. Most churches never exceed this.
- GDPR-compliant data storage. Row-level-secured Postgres, edge-deployed, EU-compatible. Important for international congregations. Learn more.
- AI spam filtering. Church forms are frequent spam targets. The built-in classifier keeps bot noise out without CAPTCHA — which matters because older members struggle with CAPTCHA puzzles.
- Signed webhooks. Route each form to the right team — prayer requests to pastoral staff, event registrations to the coordinator. Available on Starter ($1/month) and above.
- Plain HTML. No widget, no JavaScript bloat. The form loads instantly, which matters for accessibility and SEO.
Copy-paste: prayer request form
Drop this on a /prayer page. Replace YOUR_ACCESS_KEY with the key from your free splitforms account. Note the anonymous option and the privacy selector — both are important for pastoral care.
<form action="https://splitforms.com/api/submit" method="POST">
<input type="hidden" name="access_key" value="YOUR_ACCESS_KEY" />
<input type="hidden" name="subject" value="New prayer request" />
<label>Your name (or leave blank for anonymous)
<input type="text" name="name" placeholder="Optional" />
</label>
<label>Email (if you'd like a reply)
<input type="email" name="email" placeholder="Optional" />
</label>
<label>Phone (optional)
<input type="tel" name="phone" placeholder="Optional" />
</label>
<label>Prayer request
<textarea name="prayer_request" rows="5" required
placeholder="Share your prayer request here…"></textarea>
</label>
<label>Who may see this?
<select name="visibility" required>
<option value="pastoral-only">Pastoral / prayer team only</option>
<option value="congregation">May share with congregation</option>
<option value="anonymous">Keep anonymous either way</option>
</select>
</label>
<label>
<input type="checkbox" name="follow_up" />
I'd like someone to contact me
</label>
<!-- honeypot -->
<input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off" />
<button type="submit">Submit prayer request</button>
</form>Copy-paste: visitor welcome form
Put this on your /visit or /new-here page. This is the form a first-time visitor fills out before or after a service. Keep it warm, short, and welcoming.
<form action="https://splitforms.com/api/submit" method="POST">
<input type="hidden" name="access_key" value="YOUR_VISITOR_KEY" />
<input type="hidden" name="subject" value="New visitor welcome" />
<label>Name
<input type="text" name="name" required autocomplete="name" />
</label>
<label>Email
<input type="email" name="email" required autocomplete="email" />
</label>
<label>Phone (optional)
<input type="tel" name="phone" autocomplete="tel" />
</label>
<label>Which service are you planning to attend?
<select name="service_time">
<option>Sunday 9:00 AM</option>
<option>Sunday 11:00 AM</option>
<option>Saturday 6:00 PM</option>
<option>Not sure yet</option>
</select>
</label>
<label>How did you hear about us?
<select name="referral">
<option>Friend or family</option>
<option>Online search</option>
<option>Social media</option>
<option>Drove by</option>
<option>Community event</option>
<option>Other</option>
</select>
</label>
<label>Anything we should know? (kids, accessibility, questions)
<textarea name="message" rows="3"></textarea>
</label>
<input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off" />
<button type="submit">Can't wait to meet you!</button>
</form>Route visitor forms to your welcome team with a Slack webhook so someone reaches out within 24 hours.
Common mistakes churches make with contact forms
- One form for everything. A prayer request shouldn't go to the same inbox as a facility rental inquiry. Split them — separate forms, separate routing, separate tone.
- No follow-up process. A visitor fills out the form and nobody calls. Within 48 hours, the moment is gone. Assign a volunteer to check submissions daily.
- CAPTCHA on every form. Older congregation members often struggle with CAPTCHA puzzles. Use honeypot plus AI filtering — it's invisible to users.
- Asking for too much. A visitor form asking for address, birthday, family members, and spiritual history will not be filled out. Five fields maximum for first touch.
- Not mobile-friendly. Many visitors find your church on their phone after a Google search. Native HTML input types ensure mobile keyboards work correctly.
What to do next
- Get a free splitforms access key — 500 submissions/month, no credit card.
- Related: nonprofit forms · school forms
- Add to your site: WordPress · Squarespace
- Questions? Email hello@splitforms.com
FAQ
What should a church contact form include?
Name, email, phone (optional), and a reason selector: I'm new, prayer request, counseling inquiry, volunteer interest, event question, facility rental, or general message. Keep it short — 5–7 fields maximum. For prayer requests, add a dedicated textarea and make it clear who will see the message. For visitor follow-up, ask for service time preference and how they heard about the church.
Is a free contact form enough for a church website?
Yes. splitforms offers 500 submissions/month for free with no credit card — churches rarely exceed this volume. You get a dashboard, email delivery, AI spam filtering, and GDPR-compliant data storage. If you need webhooks for automated routing (e.g., prayer team notifications), Starter is $1/month. Most churches never need to pay.
How do we keep prayer requests private?
Route prayer-request submissions to a dedicated splitforms access key that only the prayer team or pastoral staff can see. Use a separate form and key for general inquiries so the front-office team only sees what they need to. splitforms stores data in row-level-secured Postgres with GDPR-compliant controls — but the key principle is access on a need-to-know basis.
Can we use one form for everything — prayer, events, visitor info?
You can, but splitting forms is better. A prayer request form should feel safe and spiritual; an event registration form should be quick and logistical; a visitor form should be warm and welcoming. Different tones, different fields, different routing. With splitforms you can create separate forms at no extra cost — the free plan includes unlimited forms.
Will this work on our church's website platform?
Yes. Whether your site is on WordPress, Wix, Squarespace, Sharefaith, or a custom build, you paste the HTML form and point it at the splitforms endpoint. No plugin required. Many church websites are maintained by volunteers — the form is simple HTML that anyone can update.