splitforms.com
← Back to the journal

Best Contact Form for Churches (2026): Options by Use Case

Church contact form options compared by use case for 2026: prayer requests, visitor follow-up, event sign-up, donations, and when a form backend falls…

Start free — 500 submissionsSee pricing →No card, no time limit. Pro is $5 per month.
Short answer
Which contact form fits a church website depends on the job. Tally is a free no-code builder for prayer requests and sign-ups, Jotform adds payment gateways for paid events, giving platforms and church management software handle donations and member records, Web3Forms has the largest monthly free tier for a plain HTML form, and splitforms is one option with 500 free submissions in total.
Try it on your own form

Point any HTML form at one endpoint. 500 free submissions — no card, no time limit — and unlimited forms.

Create free account

Disclosure: splitforms publishes this guide and is one of the options in it. There is no overall ranking: options are listed alphabetically and each pick names the use case it wins. Competitor figures come from each vendor's own pricing page, last checked November 1, 2026; plans change, so confirm before you sign up.

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.
  • Notifications. Send prayer requests to the prayer team, visitor forms to the welcome team, and event registrations to the coordinator. Email works everywhere; webhooks to Slack or Teams are a paid feature on splitforms and are included on Tally's free plan.

Which option is best for each use case?

Competitors win most of these rows. Each pick names the use case it wins on published plan limits and what the tool does.

Your situationPickWhy
A volunteer who wants a drag-and-drop builder, for freeTallyFree plan has unlimited forms and submissions under its fair use policy, 10 MB file uploads and webhooks. splitforms is not a visual builder: you paste an HTML form.
Recurring gifts, tithes, tax receipts, donor recordsA dedicated giving or donation platformA contact form collects a message. It does not manage recurring gifts, receipts or donor history, and neither does a form backend.
Member directory, small groups, attendance, check-inChurch management softwareThese tools keep records over time. A form backend or form builder captures one submission at a time.
Paid event, camp or VBS registration with card paymentJotform or TallyJotform connects to 40+ payment gateways, though its free Starter plan allows 10 payment submissions a month; Tally supports Stripe payment forms. Compare current plans on each pricing page.
Your website platform already has a form blockThe platform's built-in formNothing extra to install or maintain, and submissions stay in the site you already log in to. Check how long it keeps entries and whether it blocks spam.
Biggest monthly free allowance on a plain HTML formWeb3FormsFree plan is 250 submissions a month and resets monthly. splitforms' free allowance is 500 in total, one time.
Form data stored in EuropeTallyTally says form data is stored in Europe. splitforms hosts in the US (see the DPA).
A plain HTML form on a site you control, light volume, no cardsplitforms500 submissions in total, one time, with no card and no expiry. Notification emails are free on all plans.
Signed webhooks from a plain HTML form to Slack or Teams on a low-cost paid plansplitformsPro is $5 per month for 5,000 submissions a month with HMAC-signed webhooks. Web3Forms webhooks are on paid plans (Pro $149 per year); Tally includes webhooks on Free but is a builder, not a form endpoint.

What are the options, in alphabetical order?

  • Church management software: keeps member records, groups and attendance; many also include online forms and giving. Compare features on each product's own site.
  • Giving and donation platforms: built for one-time and recurring gifts, receipts and donor records. A separate job from a contact form.
  • Jotform: hosted drag-and-drop builder with payment gateways and e-signatures. Free Starter plan: 5 forms, 100 submissions a month, Jotform branding. See the Jotform review.
  • splitforms: a form endpoint for plain HTML forms. Free is 500 submissions in total; Pro is $5/month for 5,000 a month; Annual is $49/year for 15,000 a month.
  • Tally: hosted no-code builder; the free plan covers unlimited forms and submissions under fair use, with uploads and webhooks. See the Tally review.
  • Web3Forms: form endpoint with 250 free submissions a month. See the Web3Forms review.
  • Your website platform's own form: the zero-install option on Wix, Squarespace, WordPress form plugins and similar.

How a form backend fits a church website

Most church websites are maintained by volunteers or part-time staff, so a form should keep working without constant attention. A form backend suits that when your site is plain HTML or a page builder that lets you paste a form, and you only need submissions delivered to the right people:

  • Per-purpose forms. Separate forms and keys let prayer requests, visitor info and event questions reach different people.
  • Access. Submissions are stored in Postgres with row-level security. Review the security details and the DPA against your congregation's privacy requirements; data is hosted in the US.
  • Spam handling without CAPTCHA. A honeypot field, a time trap and rule-based smart spam filtering keep most bot noise out, which spares older members from solving CAPTCHA puzzles.
  • Plain HTML. No widget or iframe, so the form loads with the page. The person updating the site only needs to edit the HTML.

Copy-paste: prayer request form

Drop this on a /prayer page. Replace YOUR_ACCESS_KEY with the key from your free splitforms account (or point the form at another form backend). Note the anonymous option and the privacy selector, both useful 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>

To route visitor forms to your welcome team, a paid-plan webhook can post to Slack (see submissions to Slack) so someone reaches out within 24 hours. Email notifications work on every plan.

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. Assign a volunteer to check submissions daily.
  • CAPTCHA on every form. Some congregation members find CAPTCHA puzzles hard. A honeypot plus automatic spam scoring is invisible to users.
  • Asking for too much. A visitor form asking for address, birthday, family members, and spiritual history is less likely to be completed. Keep first contact to about five fields.
  • Not mobile-friendly. Many visitors find your church on their phone after a search. Native HTML input types make mobile keyboards behave correctly.
  • Using a contact form for donations. Gifts need a payment-capable tool with receipts and records, not a message field.

When is splitforms not the right choice?

  • You want a drag-and-drop builder. splitforms takes a plain HTML form. If nobody on your team will touch HTML, Tally or Jotform fit better.
  • You need to take donations or paid registrations. A form backend does not process payments or keep donor records. Use a giving platform or a payment-capable builder such as Jotform or Tally.
  • You need member records, groups or check-in. That is church management software, not a form tool. splitforms is not a CRM.
  • File uploads or webhooks on a free plan. On splitforms both are paid-plan features (Pro from $5 per month). Tally includes uploads and webhooks on its free plan.
  • You expect steady monthly volume on a free plan. splitforms' free allowance is 500 submissions in total, one time, not per month. Web3Forms gives 250 a month, resetting monthly.
  • Your congregation needs EU data residency. splitforms hosts in the US under standard contractual clauses (see the DPA). Tally says it stores form data in Europe.

Contact form guides for other industries

What to do next

FAQ

Is this guide biased toward splitforms?

splitforms publishes this guide and is one of the options in it, so read it as a vendor-written comparison. To keep it checkable, there is no overall ranking, the options are listed alphabetically, each pick names the use case it wins, competitor figures come from each vendor's own pricing page, and a section lists when splitforms is not the right choice. For several church needs (donations, member records, paid registration) a different kind of tool is the better fit.

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 to 7 fields at most. 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?

Often, for a small congregation. Tally's free plan has unlimited forms and submissions under its fair use policy, Web3Forms' free plan is 250 submissions a month, and splitforms' free plan is 500 submissions in total, one time, with no card and no expiry. Notification emails are free on all splitforms plans; webhooks are a paid feature. Because the splitforms allowance does not reset, check your expected volume before relying on it.

How do we keep prayer requests private?

Route prayer-request submissions to a dedicated form and access key that only the prayer team or pastoral staff can see, and use a separate form for general inquiries so the front-office team only sees what they need. Limit dashboard and inbox access on a need-to-know basis, and tell people on the form who will read the request. No form tool replaces that process.

Can we use one form for everything: prayer, events, visitor info?

You can, but splitting forms is usually better. A prayer request form should feel safe, an event registration form should be quick and logistical, and a visitor form should be warm and welcoming. Different tones, different fields, different routing. Check each tool's form limits on its current plan, because some free plans cap the number of forms.

Will this work on our church's website platform?

A form backend such as splitforms, Web3Forms or Basin works on WordPress, Wix, Squarespace, Sharefaith or a custom build wherever you can paste an HTML form, with no plugin required. A hosted builder such as Tally or Jotform is shared as a link or embedded instead. Many church sites are maintained by volunteers, so pick the approach the person updating it can maintain.

What about online giving and tithes?

A contact form is not a giving system. Recurring gifts, receipts and donor records belong in a dedicated donation or giving platform, or in a payment-capable form builder if your needs are simple. A form backend can carry a 'how can we help?' message, but it does not process or record donations.

Related articles

More practical guidance from guides.

Browse the journal →
Guides

WPForms Not Sending Email? 6 Fixes That Work (2026)

WPForms notifications not arriving? Find the wp_mail cause in 2 minutes, then fix it with si…

7 min readRead →
Guides

Ninja Forms Not Sending Email? 8 Fixes for WordPress

Ninja Forms notifications not arriving? Learn why wp_mail fails, how to check email actions…

7 min readRead →
Guides

Netlify Form Not Working? 7 Fixes for Missing Submissions

Netlify form not showing submissions or returning 404? Check the 7 causes, from missing data…

7 min readRead →

Explore this topic

Start with the overview, then move into focused guides.

OverviewContact Forms for Every FrameworkStart here →GuideContact Form for Next.jsRead →GuideContact Form for ReactRead →GuideContact Form for VueRead →ReferenceContact form guideOpen →

Building forms with ChatGPT, Claude, Cursor, or v0? Connect the native MCP server and give your agent a production form backend.

Explore the MCP server →

Give your form a production backend.

One endpoint adds delivery, spam filtering, storage, and integrations. Start with 500 free submissions — no card, no time limit.

Create free accountRead the docs →
Secure checkoutSSL encryptionPrivacyProtected
VISAAMERICANEXPRESSstripe