Customer Support Form for Framer
Help-desk intake with topic, priority, and order/account reference fields. Free for 500 submissions per month — no backend, no SDK, no plugin.
Why Framer developers choose splitforms for customer support form
Framer's code component feature lets you drop custom HTML directly into your design, which is where this customer support form fits. Framer's built-in form actions are limited — they forward to a Framer webhook that lacks email delivery, spam filtering, and a dashboard. The customer support form on this page bypasses Framer's form system entirely: paste it into a code component, and submissions go straight to splitforms for email, webhooks, spam filtering, and dashboard storage. Framer handles the design; splitforms handles the delivery.
Yes — this is the shortest safe path for Framer.
Use the HTML snippet on this page, keep the customer support form fields visible in your Framer 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?.
Framer's built-in form widget delivers submissions to a single email address (configured per form) with no dashboard for managing submissions, no webhooks below the Pro plan, and no spam filtering beyond Framer's basic bot detection.
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 Framer developers who hate operating a backend.
Splitforms is the form backend for Framer sites. One POST endpoint, no SDK, no plugin — drop the customer support form into a page and ship.
Splitforms is the form backend for Framer 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 Framer project.
Replace YOUR_ACCESS_KEY with your splitforms key, paste into a Framer 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 Framer project
Drop the form snippet into a Framer 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 Framer.
These notes come from the Framer platform registry and are rendered on this template page so crawlers see the framework-specific answer without opening a separate guide.
Framer's built-in form widget delivers submissions to a single email address (configured per form) with no dashboard for managing submissions, no webhooks below the Pro plan, and no spam filtering beyond Framer's basic bot detection. CMS-driven Framer forms inherit the same constraints. The native flow works for a portfolio's contact form; it falls apart for any setup that needs Slack/Discord notifications, multiple recipients, CSV export, or tagged form-name routing. Replacing it means writing a Code Component — Framer's mechanism for embedding custom React. That's the pattern splitforms uses: a Code Component with the access key as a property control, dropped onto the canvas like a native widget.
Framer publishes sites to its own CDN — there's no Vercel/Netlify config to manage. The form posts cross-origin to splitforms regardless. Framer's published sites have a default Content Security Policy that may block connect-src to splitforms.com on some plans; if submissions silently fail, add <meta http-equiv="Content-Security-Policy" content="connect-src https://splitforms.com"> via Site Settings → Custom Code → Head HTML. Lock the access key to BOTH your *.framer.app preview URL AND your custom domain — Framer serves both with different Origin headers. Framer's preview environment runs Code Components live, so you can test the form before publishing.
addPropertyControls must be the LAST statement in the file
Framer reads property controls only if addPropertyControls(Component, {...}) is called after the component is exported. If you put it before the export or wrap it in a conditional, the access-key control disappears from the right panel and you can't set the key visually.
Framer's canvas re-renders the component on every prop change
Editing the access key in the right panel re-mounts the form mid-edit. If a user is testing the form when you change the key, their status === 'loading' state resets to 'idle' visually but the in-flight fetch still completes. Not a bug in production — only an editor quirk.
Framer's published page CSP blocks splitforms.com unless you set it
Framer's published sites have a default Content Security Policy that allows known integrations. Splitforms isn't on the default allowlist — you may need to add connect-src https://splitforms.com via Framer's Site Settings → Custom Code → Head HTML, inside a <meta http-equiv="Content-Security-Policy" content="…"> tag.
Code Components don't get Framer's font system by default
If you use style={{ fontFamily: '...' }} in a Code Component, you have to import the font manually — Framer's site fonts only auto-apply to canvas-built elements. Use font-family: inherit to inherit from the parent frame.
Pattern A — Code Component with property control
Paste into Framer's Code Components panel. The access key becomes a property in the right-side inspector — designers swap keys per page or per environment without touching code. Use the same wiring for the customer support form fields on this page.
Pattern B — Framer override (apply to existing canvas form)
If you already designed a form on the canvas with Framer's native form widget, an override can intercept its submit and re-route to splitforms. Useful when you want to keep the canvas-built design but swap the backend. 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 Framer — 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 Framer forms.
Same backend, different qualifying fields. Click through to copy the snippet.
Ship a customer support form on Framer in 60 seconds.
500 submissions per month, free forever. No credit card. Copy the snippet above and paste it into your Framer project.