CUSTOMER SUPPORT FORM · CARRD

Customer Support Form for Carrd

Help-desk intake with topic, priority, and order/account reference fields. Free for 500 submissions per month — no backend, no SDK, no plugin.

Get free access key Copy the code

500/mo free·no card·drop-in for Carrd

form.htmlhtml28 lines

01<form action="https://splitforms.com/api/submit" method="POST">
02  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY">
03  <input type="hidden" name="subject" value="New support ticket">
04 
05  <label for="name">Your name *</label>
06  <input id="name" type="text" name="name" placeholder="Jane Builder" required>
07  <label for="email">Email *</label>
08  <input id="email" type="email" name="email" placeholder="jane@example.com" required>
09  <label for="phone">Phone (for urgent issues)</label>
10  <input id="phone" type="tel" name="phone" placeholder="+1 415 555 0142">
11  <label for="order_id">Order / account ID (optional)</label>
12  <input id="order_id" type="text" name="order_id" placeholder="ORD-49281">
13  <label for="severity">How urgent is this? *</label>
14  <select id="severity" name="severity" required>
15    <option value="">Choose…</option>
16    <option>Critical — blocking us</option>
17    <option>High — losing time</option>
18    <option>Medium — annoying</option>
19    <option>Low — heads-up</option>
20  </select>
21  <label for="description">What's wrong? *</label>
22  <textarea id="description" name="description" placeholder="Steps to reproduce, error messages, screenshots if you have them." required></textarea>
23 
24  <!-- honeypot — bots fill every field -->
25  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">
26 
27  <button type="submit">Send</button>
28</form>

500

submissions / mo, free

fields, ready to ship

code outputs

60s

from copy to inbox

§ 00Carrd + Customer Support Formplatform-specific integration guide

Why Carrd developers choose splitforms for customer support form

Carrd's embed element lets you inject custom HTML into your one-page site — perfect for a lightweight contact form. Carrd Pro includes a native form feature, but it caps submissions at 100/month on paid plans and lacks webhook delivery. The customer support form on this page drops into a Carrd embed, posts to splitforms, and gives you 500 dashboard submissions/month free; Starter adds Slack/Discord notifications. No Carrd Pro upgrade needed for the form to work. The HTML is self-contained — Carrd's minimal runtime handles the display, splitforms handles the backend.

§ 00Quick answerHTML · support

Yes — this is the shortest safe path for Carrd.

Use the HTML snippet on this page, keep the customer support form fields visible in your Carrd UI, and let splitforms handle delivery, spam filtering, storage, and webhooks.

best implementation

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?.

native carrd reality

use case fit

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.

§ 01Customer Support Form × Carrdwhy this combination, in 80 words

Built for Carrd developers who hate operating a backend.

Splitforms is the form backend for Carrd sites. One POST endpoint, no SDK, no plugin — drop the customer support form into a page and ship.

Splitforms is the form backend for Carrd 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.

✦ what you get on the free plan

✓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)

§ 02Copy-paste codeHTML · 28 lines

Drop into any Carrd project.

Replace YOUR_ACCESS_KEY with your splitforms key, paste into a Carrd page, and ship. No build-time integration required.

form.htmlhtml28 lines

01<form action="https://splitforms.com/api/submit" method="POST">
02  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY">
03  <input type="hidden" name="subject" value="New support ticket">
04 
05  <label for="name">Your name *</label>
06  <input id="name" type="text" name="name" placeholder="Jane Builder" required>
07  <label for="email">Email *</label>
08  <input id="email" type="email" name="email" placeholder="jane@example.com" required>
09  <label for="phone">Phone (for urgent issues)</label>
10  <input id="phone" type="tel" name="phone" placeholder="+1 415 555 0142">
11  <label for="order_id">Order / account ID (optional)</label>
12  <input id="order_id" type="text" name="order_id" placeholder="ORD-49281">
13  <label for="severity">How urgent is this? *</label>
14  <select id="severity" name="severity" required>
15    <option value="">Choose…</option>
16    <option>Critical — blocking us</option>
17    <option>High — losing time</option>
18    <option>Medium — annoying</option>
19    <option>Low — heads-up</option>
20  </select>
21  <label for="description">What's wrong? *</label>
22  <textarea id="description" name="description" placeholder="Steps to reproduce, error messages, screenshots if you have them." required></textarea>
23 
24  <!-- honeypot — bots fill every field -->
25  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">
26 
27  <button type="submit">Send</button>
28</form>

§ 03Setup3 steps · 60 seconds · zero config

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.

STEP 01GENERATE

Generate a free splitforms key

Create your form

key=sk_live_••••••••

STEP 02EMBED

Paste the customer support form into your Carrd project

Drop the form snippet into a Carrd 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.

snippethtml

<form action="https://splitforms.com/api/submit" method="POST">
  …
</form>

STEP 03RECEIVE

Receive submissions

Dashboard updates live on Free. Starter adds email delivery, signed webhooks, CSV export, Slack/Discord forwarding, and BCC to your team.

inbox · 1 newjust now

FROM contact@yoursite.com

New support ticket

Maya Iyer maya@studio71.co

Loved the demo — quick question about pricing on the 3-year plan. Are usage limits per project or account-wide?

§ 03bCustomer Support Contact Form (Help Desk)template-specific playbook

The reason this customer support form exists.

Webhooks into Linear / Notion / Help Scout / Zendesk · category-based routing.

why it matters

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.

route the submission

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.

§ 03cCarrd production notesnative path · deploy · gotchas

What changes when this customer support form lives in Carrd.

These notes come from the Carrd platform registry and are rendered on this template page so crawlers see the framework-specific answer without opening a separate guide.

without splitforms

Carrd's Form widget requires Pro Standard ($19/year) just to exist on the page, and even then it doesn't deliver email itself — the form 'works' by posting to an external integration: Mailchimp, SendGrid, Basin, Formspree, etc. So the question isn't 'native vs splitforms' but 'which third-party backend do you wire up?'. Mailchimp is overkill (and surprisingly expensive once your list grows); Basin and Formspree limit free submissions; SendGrid requires DNS verification. Splitforms is the same shape of integration (Type: Custom, Method: POST, Action: a URL) at a better free tier and with built-in spam filtering. Carrd's Form widget settings don't change.

deploy notes

Carrd publishes to a *.carrd.co subdomain on every plan; Pro Standard adds a custom domain. The form posts to splitforms from the browser, so neither subdomain nor custom domain matters for delivery. Lock the splitforms access key to BOTH the *.carrd.co URL and your custom domain — Carrd serves the same content under both, with different Origin headers. Carrd's Designer preview never actually POSTs; you have to publish (free) and submit from the live URL to test. Embed elements bypass Carrd's CSS, so the form will look browser-default unless you inline styles.

Carrd gotcha

Pro Standard plan still required for Custom form Type

Carrd's free plan and Pro Lite don't expose the Form widget at all. Pro Standard ($19/yr) unlocks the Form widget with Type → Custom. Splitforms doesn't change Carrd's plan requirements — it just fills in the backend that Carrd doesn't ship.

Carrd gotcha

Embed element forms don't inherit Carrd's site styles

If you paste raw HTML via an Embed element, your form will look like browser-default — no Carrd typography, no site colors. Use the native Form widget for styling, then add a hidden access_key field via Custom fields.

Carrd gotcha

Carrd's success message + splitforms redirect can fight each other

Carrd's Form widget has a built-in success message that shows on 2xx response. If you also set a redirect field in the form, the user sees the success blip then redirects mid-message. Pick one: redirect via splitforms OR Carrd's success text.

Carrd gotcha

The form widget's Field labels don't match input names by default

Carrd uses friendly labels like 'Your name', but the actual input name attribute is name-1 or similar unless you set Custom in the field settings. Set the Custom name to name, email, message — splitforms uses the input names as keys in your inbox.

PATTERN A

Pattern A — native Form widget set to Custom type

In the Form widget's settings, set Type to Custom, Method to POST, Action to the splitforms URL. Add a hidden field access_key via the Custom Fields tab. Carrd handles the styling and mobile layout; splitforms handles delivery. Use the same wiring for the customer support form fields on this page.

pattern-a.htmlhtml8 lines

01<!-- Carrd auto-generates this on publish: -->
02<form action="https://splitforms.com/api/submit" method="POST">
03  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY" />
04  <input type="text"  name="name" placeholder="Name" required />
05  <input type="email" name="email" placeholder="Email" required />
06  <textarea name="message" placeholder="Message" required></textarea>
07  <button type="submit">Submit</button>
08</form>

PATTERN B

Pattern B — Embed element with full HTML control

Drop an Embed element into a Carrd section and paste raw HTML. Loses Carrd's auto-styling but lets you add a honeypot, multi-field validation, or custom redirect. Useful for waitlist or job-application forms that exceed the Form widget's capability. Use the same wiring for the customer support form fields on this page.

pattern-b.htmlhtml9 lines

01<form action="https://splitforms.com/api/submit" method="POST" style="display:grid;gap:8px;max-width:380px;">
02  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY" />
03  <input type="hidden" name="redirect" value="/thanks" />
04  <input name="name" placeholder="Name" required />
05  <input name="email" type="email" placeholder="Email" required />
06  <textarea name="message" placeholder="What's up?" required></textarea>
07  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" />
08  <button type="submit">Send</button>
09</form>

§ 04Field-by-field rundown6 fields · names you POST

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.

nameREQUIRED

TEXT

Your name

Greeting + dashboard label so submissions don't all read 'anonymous'.

placeholder · Jane Builder

emailREQUIRED

Email

Reply-to address — splitforms wires this so hitting reply goes back to the sender.

placeholder · jane@example.com

phone

PHONE

Phone (for urgent issues)

Faster qualification — phone leads convert ~3× higher than email-only on B2B forms.

placeholder · +1 415 555 0142

order_id

TEXT

Order / account ID (optional)

Standard input — splitforms accepts whatever you POST under this name.

placeholder · ORD-49281

severityREQUIRED

SELECT

How urgent is this?

Triage signal — drives whether this pages on-call or waits till Monday.

Critical — blocking usHigh — losing timeMedium — annoyingLow — heads-up

descriptionREQUIRED

TEXTAREA

What's wrong?

Free-text input — no character limit, expands as the visitor types.

placeholder · Steps to reproduce, error messages, screenshots if you have them.

§ 05Customer Support Form on other frameworks21 frameworks · same backend

One backend. Every framework.

The same customer support form template works on every framework splitforms supports. Pick yours.

§ 06Questions9 answered

Customer Support Form on Carrd — FAQ.

Direct answers, no marketing fluff. Missing one? Email hello@splitforms.com.

01Does this customer support form work on Carrd?

Yes. The form is plain HTML with a single POST endpoint, so it runs on any Carrd site without server-side code, plugins, or SDKs. Drop the snippet into a Carrd page or component and submissions land in your splitforms dashboard.

02How much does the customer support form cost on Carrd?

Free for 500 submissions per month — no credit card, no trial. Pro is $5/mo for 5,000 submissions, and there's a one-time $59 3-year plan (15,000 submissions/mo for 36 months). The same pricing applies regardless of which framework hosts the form.

03Can I customize the fields?

Yes. The template ships with sensible defaults (your name, email, phone (for urgent issues), order / account id (optional)…) — add, remove, or rename any of them. Splitforms accepts whatever fields you POST.

04How does spam protection work on the customer support form?

A hidden honeypot field catches dumb bots, and a tuned classifier scores the rest. You only see real submissions in your dashboard. No CAPTCHA, no friction for human users — and it works the same on Carrd as on any other framework.

05Can I send the customer support form submissions to Slack or Discord?

Yes. Webhooks are available on Starter and above, with auto-formatted payloads for Slack, Discord, and WhatsApp (via CallMeBot). Or send raw signed JSON to any URL — Zapier, n8n, your own server. Configure in the splitforms dashboard.

06Will it work on a static Carrd site?

Yes — the form posts directly to splitforms from the browser, so no server is involved. Works on Vercel, Netlify, GitHub Pages, Cloudflare Pages, S3, or any plain Apache host.

07Should I integrate with Zendesk / Intercom / Help Scout?

When ticket volume crosses ~50/week, the dedicated tool's UX (queue management, canned responses, customer history) starts paying back the subscription. Below that, webhooks into Linear or Slack handle volume cheaper. Switch when you outgrow the simpler tools, not before.

08How do I handle SLA tracking without a help desk?

splitforms timestamps every submission. A daily Zapier / Make automation flags any unresponded submission older than your SLA threshold and pings the owning team in Slack. Crude but effective for small teams. At scale, switch to a tool that tracks time-to-first-response natively.

09Can I integrate with Linear / Notion / Productboard?

Yes — webhook the JSON. Linear and Notion both accept issue / database creation via API. Productboard accepts feature requests via Zapier. Routing categories to the right tool (bugs to Linear, features to Productboard) means each gets triaged in the place that team works.

§ 07Comparisonvs Web3Forms · vs Formspree

splitforms vs everything else.

Same drop-in API. More free submissions, Starter signed webhooks, MCP support no other backend has.

Feature	Web3Forms	Formspree	splitforms
Free monthly submissions	250	50	500
Custom fields beyond contact	Yes	Pro tier	Free
Webhooks (Slack / Discord)	Pro tier	Pro tier	Free, signed
AI / MCP submission inbox	No	No	Yes
Long-term plan (3-year flat)	—	—	$59 every 3 years

§ 08More templates for Carrd5 adjacent patterns

Ship a customer support form on Carrd in 60 seconds.

500 submissions per month, free forever. No credit card. Copy the snippet above and paste it into your Carrd project.

Get free access key →Read the docs

founders pricing locked in · early access open

Customer Support Form for Carrd

Why Carrd developers choose splitforms for customer support form

Yes — this is the shortest safe path for Carrd.

Paste the HTML version, then replace YOUR_ACCESS_KEY.

Built for Carrd developers who hate operating a backend.

Drop into any Carrd project.

Generate, embed, receive.

Generate a free splitforms key

Paste the customer support form into your Carrd project

Receive submissions

The reason this customer support form exists.

Capture ticket category

Route by category

Auto-confirm with SLA

What changes when this customer support form lives in Carrd.

Pro Standard plan still required for Custom form Type

Embed element forms don't inherit Carrd's site styles

Carrd's success message + splitforms redirect can fight each other

The form widget's Field labels don't match input names by default

Pattern A — native Form widget set to Custom type

Pattern B — Embed element with full HTML control

What every field actually does.

Your name

Email

Phone (for urgent issues)

Order / account ID (optional)

How urgent is this?

What's wrong?

One backend. Every framework.

Customer Support Form on Carrd — FAQ.

splitforms vs everything else.

Other ready-to-ship Carrd forms.

Ship a customer support form on Carrd in 60 seconds.