Customer Support Form for Eleventy
Help-desk intake with topic, priority, and order/account reference fields. Free for 500 submissions per month — no backend, no SDK, no plugin.
Why Eleventy developers choose splitforms for customer support form
Eleventy (11ty) is a flexible static site generator that lets you use any templating language, but it doesn't process form submissions — the output is static HTML. Adding a Node server or a Netlify function just for a contact form defeats the simplicity that makes Eleventy appealing. The customer support form on this page posts from the browser to splitforms, so your Eleventy site stays static. It works with Nunjucks, Handlebars, Liquid, Markdown, and every Eleventy template language because the form is plain HTML.
Yes — this is the shortest safe path for Eleventy.
Use the HTML snippet on this page, keep the customer support form fields visible in your Eleventy UI, and let splitforms handle delivery, spam filtering, storage, and webhooks.
Paste the HTML version, then replace YOUR_ACCESS_KEY.
The posted payload contains your name, email, phone (for urgent issues), order / account id (optional), how urgent is this?, what's wrong?. Required fields are your name, email, how urgent is this? and what's wrong?.
Eleventy is a Node-based static site generator — it produces HTML at build time and ships nothing else.
Live chat plugins start at $50-100/month per seat. For low-volume support, a structured contact form plus a Starter webhook into Linear or Help Scout does the same job for far less.
Built for Eleventy developers who hate operating a backend.
Splitforms is the form backend for Eleventy sites. One POST endpoint, no SDK, no plugin — drop the customer support form into a page and ship.
Splitforms is the form backend for Eleventy sites. One POST endpoint, spam filtering, and a real dashboard — drop-in, no server, no PHP. Free for 500 dashboard submissions per month; Starter adds email, signed webhooks, exports, and retained uploads; Pro is $5/mo for 5,000.
- ✓500 form submissions per month
- ✓2 forms on Free; unlimited forms on Pro
- ✓Spam protection (honeypot + classifier)
- ✓Webhooks: Slack, Discord, WhatsApp, custom
- ✓CSV export of all submissions
- ✓Email notifications (CC and BCC on Pro)
Drop into any Eleventy project.
Replace YOUR_ACCESS_KEY with your splitforms key, paste into a Eleventy page, and ship. No build-time integration required.
Generate, embed, receive.
Three actions stand between you and your first customer support form submission. None of them require a backend, a database, or a CAPTCHA library.
Generate a free splitforms key
Sign in at splitforms.com — your access key is created instantly. No credit card, no setup wizard, no SDK to install.
Paste the customer support form into your Eleventy project
Drop the form snippet into a Eleventy page, component, or layout. Replace YOUR_ACCESS_KEY with the key from your dashboard. The form action is a hard-coded URL — no env vars or build-time wiring needed.
Receive submissions
Dashboard updates live on Free. Starter adds email delivery, signed webhooks, CSV export, Slack/Discord forwarding, and BCC to your team.
The reason this customer support form exists.
Webhooks into Linear / Notion / Help Scout / Zendesk · category-based routing.
Support tools (Zendesk, Intercom, Help Scout) start at $20-100/seat/month. For early-stage SaaS handling 10-50 tickets a week, a structured support form that webhooks into Linear / Notion / Slack handles the volume without the subscription. The form captures ticket category (billing / bug / feature request / account access / general), urgency (blocking / high / medium / low), account email, and description. Routing the categories to different Slack channels or Linear teams turns the form into a triage layer. As you scale, switch the webhook target to Zendesk or Intercom and the form stays — same UX, different backend. SLA tracking still works because submission timestamps are stored.
Capture ticket category
Required: category (billing / bug / feature / account / general), urgency, account email, description. Optional: screenshot upload (Pro), order/invoice number for billing.
Route by category
Webhook branches on category — billing goes to finance Slack; bugs to engineering Linear; feature requests to product Productboard. Each team owns their queue.
Auto-confirm with SLA
Auto-respond with ticket number and SLA promise ('we'll reply within 24 hours on weekdays'). Sets expectations and reduces the 'have you seen this?' follow-up email two days later.
What changes when this customer support form lives in Eleventy.
These notes come from the Eleventy platform registry and are rendered on this template page so crawlers see the framework-specific answer without opening a separate guide.
Eleventy is a Node-based static site generator — it produces HTML at build time and ships nothing else. There is no runtime, no /api/contact endpoint, no hooks for handling a form POST. The historical workarounds: (a) deploy to Netlify and use Netlify Forms, (b) write a Cloudflare Worker that handles POST /contact and forwards to your email provider (~4 hours plus ongoing operation), or (c) use a third-party form API (Formspree, Web3Forms, Basin, splitforms). Eleventy's data cascade lets you neatly pull an access key from _data/site.js and use it in a Nunjucks/Liquid include — but the actual delivery layer is always external. Splitforms is the lowest-friction external option.
Eleventy deploys to any static host. The form posts cross-origin to splitforms.com so the host is irrelevant for delivery. Eleventy v3's ESM-only config is the major upgrade gotcha — .eleventy.js (CommonJS) silently stops exposing globals; rename to eleventy.config.mjs. Local dev runs on localhost:8080 — add to splitforms allowed-domains for testing or use a separate dev key. _data/site.js (not .json) lets you read from process.env; keep .env in gitignore. For 11ty + Netlify (the classic combo), you can use Netlify Forms instead, but you cap out at 100/mo — splitforms gives 500/mo and works on every host.
Eleventy v3 is ESM-only — your config must be .mjs
If you upgraded to Eleventy 3 and your .eleventy.js (CommonJS) silently stopped exposing globals, that's why. Rename to eleventy.config.mjs and use ESM export default. Otherwise addGlobalData('splitformsKey', …) won't reach your templates.
Liquid filters and Nunjucks filters have different names
{{ '/thanks/' | url }} works in Nunjucks (with the eleventy-plugin-url plugin). In Liquid, the filter is | url_for or you skip the filter entirely and write the path literally. Mismatched filter names render nothing — the form's redirect URL becomes empty.
Global data with sensitive values gets committed by accident
If you put your access key in _data/site.json (the obvious place), it ships to your repo. Use _data/site.js and read from process.env.SPLITFORMS_KEY instead — then add .env to gitignore. Eleventy auto-loads .env if you have dotenv installed.
Permalinks: false on the contact page makes the redirect fail
If your contact page has permalink: false (rare but possible), it's not built — and splitforms's redirect target points at a 404. Always ensure both the form page and the /thanks page have valid permalinks.
Pattern A — Nunjucks include from `_includes/partials/`
Save as src/_includes/partials/contact-form.njk. Use from any template with {% include "partials/contact-form.njk" %}. Pulls the key from a global data file that reads process.env.SPLITFORMS_KEY. Use the same wiring for the customer support form fields on this page.
Pattern B — Eleventy v3 ESM config
Eleventy 3 is ESM-only. Use eleventy.config.mjs and addGlobalData to wire the key from environment. Liquid templates work the same way — just save as .liquid. Use the same wiring for the customer support form fields on this page.
What every field actually does.
Each field below ships in the customer support form template — rename, remove, or add your own. Splitforms accepts any name you POST.
Your name
Greeting + dashboard label so submissions don't all read 'anonymous'.
Reply-to address — splitforms wires this so hitting reply goes back to the sender.
Phone (for urgent issues)
Faster qualification — phone leads convert ~3× higher than email-only on B2B forms.
Order / account ID (optional)
Standard input — splitforms accepts whatever you POST under this name.
How urgent is this?
Triage signal — drives whether this pages on-call or waits till Monday.
What's wrong?
Free-text input — no character limit, expands as the visitor types.
One backend. Every framework.
The same customer support form template works on every framework splitforms supports. Pick yours.
Customer Support Form on Eleventy — FAQ.
Direct answers, no marketing fluff. Missing one? Email hello@splitforms.com.
splitforms vs everything else.
Same drop-in API. More free submissions, Starter signed webhooks, MCP support no other backend has.
Other ready-to-ship Eleventy forms.
Same backend, different qualifying fields. Click through to copy the snippet.
Ship a customer support form on Eleventy in 60 seconds.
500 submissions per month, free forever. No credit card. Copy the snippet above and paste it into your Eleventy project.