Add a reason dropdown
Options: 'I'm new / planning a visit', 'Prayer request', 'Weddings, baptisms & dedications', 'Volunteering', 'General question'. That one field routes everything.
Form template · Detailed contact form
A church website's contact form serves three very different visitors: the family checking you out before Sunday, the member with a prayer request, and the person asking about weddings or baptisms. One form, one routing dropdown, all three handled.
Every template is free and fully editable in the drag-drop builder — swap fields, colors, and the button label before you publish.
No server, API route, or SDK — your Church Contact Form posts straight to one endpoint.
Every submission is emailed to you and saved to a searchable dashboard — spam filtered before it reaches you.
It's plain HTML you own — paste the Church Contact Form snippet, swap in your access key, and ship.
Copy and ship
HTML by default — the same field set also renders as React, Next.js, PHP, and cURL in your dashboard. Every variant posts to the same /api/submit endpoint. Replace YOUR_ACCESS_KEY with the key from your dashboard; that's the only edit.
<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 detailed contact submission">
<label for="name">Full name *</label>
<input id="name" type="text" name="name" placeholder="Jane Builder" required>
<label for="email">Work email *</label>
<input id="email" type="email" name="email" placeholder="jane@company.com" required>
<label for="phone">Phone *</label>
<input id="phone" type="tel" name="phone" placeholder="+1 415 555 0142" required>
<label for="company">Company</label>
<input id="company" type="text" name="company" placeholder="Acme Inc">
<label for="reason">What's this about? *</label>
<select id="reason" name="reason" required>
<option value="">Choose…</option>
<option>Sales / pricing</option>
<option>Partnerships</option>
<option>Press / media</option>
<option>Support</option>
<option>Careers</option>
<option>Other</option>
</select>
<label for="message">Message *</label>
<textarea id="message" name="message" placeholder="Give us context — links, dates, deal size, anything we should know." required></textarea>
<!-- honeypot — bots fill every field -->
<input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">
<button type="submit">Send</button>
</form><p class="splitforms-attribution" style="margin-top:12px;font-size:11px;color:#888;text-align:right">
Powered by <a href="https://splitforms.com" style="color:#888;text-decoration:none" target="_blank" rel="sponsored noopener">splitforms</a>
</p>How to add it
To add a Church Contact Form to your site you need three things: a free splitforms access key, the HTML snippet above, and your key pasted into it. No backend, database, or CAPTCHA library — the form posts to one URL and every submission lands in your inbox and dashboard.
Options: 'I'm new / planning a visit', 'Prayer request', 'Weddings, baptisms & dedications', 'Volunteering', 'General question'. That one field routes everything.
Webhook or BCC each reason to the right inbox — prayer requests to the pastoral team, visitor inquiries to the welcome team, event questions to the office. Nobody's message sits unread for a week.
Set up an auto-responder that thanks the sender and tells visitors what to expect (service times, parking, kids check-in). A same-week personal follow-up is what turns a website visit into a pew visit.
What's included
Most church websites run on a volunteer-maintained WordPress or Squarespace site, and the contact form is either broken or dumps everything into one unwatched inbox. The fix is a routing dropdown — 'I'm new', 'prayer request', 'weddings / baptisms', 'general question' — with each option BCC'd or webhooked to the right person. Prayer requests deserve confidentiality and a fast, personal reply; a first-time visitor inquiry deserves a warm welcome email before Sunday. One form can honour both. Works on volunteer-maintained sites — no plugin, nothing to break, free forever.

Where submissions go
Reply-to is wired to the visitor's email, so one tap on Reply answers them directly — while the built-in honeypot and spam classifier filter out bots before they reach you. Every submission is emailed to your inbox and can forward to a webhook or Slack the moment a visitor hits send.

How SplitForms works
Connect your form, collect every submission, and send data where it needs to go — without building backend infrastructure.

Point your form to your unique SplitForms endpoint. That's it.

We instantly capture and organize every submission in your inbox.

Send data to email, spreadsheets, CRMs, webhooks, and 7,000+ apps.

No credit card required. Set up in under 60 seconds.
Connect & automate
SplitForms works with the destinations you route to and the platforms you build on — from Slack and Sheets to WordPress, Shopify, and Next.js.

Trusted by indie teams and agencies shipping forms worldwide
Testimonials
40 quotes on record — from indie hacks to agency migrations.
“I replaced a Lambda + DynamoDB + SES contact form with six lines of HTML. It took eleven minutes, and the dashboard is better than what I was going to build.”
“We migrated 14 client sites off Formspree in a single weekend. The price is a third of what we paid, the API is more honest, and the spam filter actually works.”
“The webhook payload is signed, idempotent, and well-shaped. It reads like code from a competent team, not a CRUD app held together with duct tape.”
“I stopped reaching for Typeform on small marketing sites. splitforms covers 90% of the use case at none of the bloat.”
“I onboarded our whole agency in an afternoon. The MCP integration meant Cursor literally dropped the form straight into our client repos for us.”
“The free plan gave me 500 submissions before I paid a cent, and Pro is five dollars a month. I've spent more on coffee deciding which backend to use.”
“Spam went from forty junk entries a day to zero, with no reCAPTCHA puzzle ruining the form. The honeypot and time-trap just quietly do their job.”
“Point the form action at one endpoint and you're done. No SDK, no client library, no build step. This is how a form backend should feel.”
“Leads land in Slack the second someone submits, and a copy goes to Google Sheets for the sales team. I wired both up in under ten minutes.”
“I run a static Hugo site on a five-dollar VPS. splitforms gave it a real contact form without me standing up a single server.”
Questions
Submissions go only to the email addresses you configure — they're not published anywhere. splitforms stores them encrypted at rest, and you can delete any submission permanently from the dashboard. Add a 'share with prayer team / pastor only' checkbox if your congregation expects that distinction.
Yes — the form is plain HTML and posts to splitforms, so it works in a Squarespace code block, a Wix HTML embed, or a WordPress page with no plugin. Church sites maintained by volunteers especially benefit: nothing to update, no plugin to break.
Yes — that's the 'I'm new' path. Add optional fields for how they found you and whether they'd like someone to reach out. Many churches put a QR code on the physical bulletin pointing at the same form so Sunday visitors and website visitors land in one place.
Yes — add BCC addresses in the dashboard, or webhook into a shared Slack / Planning Center workflow. Most churches send everything to the office admin plus the reason-specific lead (pastor for prayer, welcome-team lead for visitors).
Simple pricing
Choose a plan that fits your workflow — from a free form endpoint to full automations, exports, and higher submission limits.
Free forever
For side projects and indie devs.
For agencies and growing products.
Pay $59. 3 years sorted.
No credit card required on Free • Cancel anytime