splitforms.com
CUSTOMER SUPPORT FORM · NEXT.JS

Customer Support Form for Next.js

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

500/mo free·no card·drop-in for Next.js
Form.tsxtsx57 lines
01'use client';
02
03import { useState, type FormEvent } from 'react';
04
05export default function SupportForm() {
06 const [status, setStatus] = useState<'idle' | 'sending' | 'sent' | 'error'>('idle');
07
08 async function onSubmit(e: FormEvent<HTMLFormElement>) {
09 e.preventDefault();
10 setStatus('sending');
11
12 const data = new FormData(e.currentTarget);
13 data.set('access_key', 'YOUR_ACCESS_KEY');
14 data.set('subject', 'New support ticket');
15
16 const res = await fetch('https://splitforms.com/api/submit', {
17 method: 'POST',
18 body: data,
19 headers: { Accept: 'application/json' },
20 });
21
22 const json = await res.json();
23 setStatus(json.success ? 'sent' : 'error');
24 if (json.success) e.currentTarget.reset();
25 }
26
27 if (status === 'sent') return <p>Thanks — we&rsquo;ll be in touch.</p>;
28
29 return (
30 <form onSubmit={onSubmit}>
31 <label htmlFor="name">Your name *</label>
32 <input id="name" type="text" name="name" placeholder="Jane Builder" required />
33 <label htmlFor="email">Email *</label>
34 <input id="email" type="email" name="email" placeholder="jane@example.com" required />
35 <label htmlFor="phone">Phone (for urgent issues)</label>
36 <input id="phone" type="tel" name="phone" placeholder="+1 415 555 0142" />
37 <label htmlFor="order_id">Order / account ID (optional)</label>
38 <input id="order_id" type="text" name="order_id" placeholder="ORD-49281" />
39 <label htmlFor="severity">How urgent is this? *</label>
40 <select id="severity" name="severity" required>
41 <option value="">Choose…</option>
42 <option>Critical — blocking us</option>
43 <option>High — losing time</option>
44 <option>Medium — annoying</option>
45 <option>Low — heads-up</option>
46 </select>
47 <label htmlFor="description">What's wrong? *</label>
48 <textarea id="description" name="description" placeholder="Steps to reproduce, error messages, screenshots if you have them." required />
49
50 <button type="submit" disabled={status === 'sending'}>
51 {status === 'sending' ? 'Sending…' : 'Send'}
52 </button>
53
54 {status === 'error' && <p>Something went wrong. Try again.</p>}
55 </form>
56 );
57}
500
submissions / mo, free
6
fields, ready to ship
5
code outputs
60s
from copy to inbox
§ 00Next.js + Customer Support Formplatform-specific integration guide

Why Next.js developers choose splitforms for customer support form

Next.js Server Actions handle the submit side but still leave you wiring SMTP, spam filtering, file uploads, and a dashboard. splitforms replaces all of that with one <code>fetch('/api/submit')</code> call. The customer support form works identically in App Router and Pages Router — it's just a <code>FormData</code> POST, no router-specific magic. Because Next.js pre-renders pages, the form HTML is in the DOM before any JavaScript executes, meaning instant Time-to-Interactive. The honeypot field is invisible to users but catches bots that scrape rendered HTML — especially important for Next.js sites where the form HTML is statically generated and predictable.

§ 00Quick answerReact / Next.js · support

Yes — this is the shortest safe path for Next.js.

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

best implementation

Paste the React / Next.js 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 next.js reality

Without splitforms, you'd write a route handler at app/api/contact/route.ts, parse the FormData, configure SMTP via nodemailer or Resend (~10 minutes of secrets wrangling), add a Postgres or SQLite store for submissions, and then bolt on rate limiting, a honeypot check, an email-classifier or reCAPTCHA, and webhook fan-out.

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 × Next.jswhy this combination, in 80 words

Built for Next.js developers who hate operating a backend.

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

Splitforms is the form backend for Next.js 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 codeReact / Next.js · 57 lines

Drop into any Next.js project.

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

Form.tsxtsx57 lines
01'use client';
02
03import { useState, type FormEvent } from 'react';
04
05export default function SupportForm() {
06 const [status, setStatus] = useState<'idle' | 'sending' | 'sent' | 'error'>('idle');
07
08 async function onSubmit(e: FormEvent<HTMLFormElement>) {
09 e.preventDefault();
10 setStatus('sending');
11
12 const data = new FormData(e.currentTarget);
13 data.set('access_key', 'YOUR_ACCESS_KEY');
14 data.set('subject', 'New support ticket');
15
16 const res = await fetch('https://splitforms.com/api/submit', {
17 method: 'POST',
18 body: data,
19 headers: { Accept: 'application/json' },
20 });
21
22 const json = await res.json();
23 setStatus(json.success ? 'sent' : 'error');
24 if (json.success) e.currentTarget.reset();
25 }
26
27 if (status === 'sent') return <p>Thanks — we&rsquo;ll be in touch.</p>;
28
29 return (
30 <form onSubmit={onSubmit}>
31 <label htmlFor="name">Your name *</label>
32 <input id="name" type="text" name="name" placeholder="Jane Builder" required />
33 <label htmlFor="email">Email *</label>
34 <input id="email" type="email" name="email" placeholder="jane@example.com" required />
35 <label htmlFor="phone">Phone (for urgent issues)</label>
36 <input id="phone" type="tel" name="phone" placeholder="+1 415 555 0142" />
37 <label htmlFor="order_id">Order / account ID (optional)</label>
38 <input id="order_id" type="text" name="order_id" placeholder="ORD-49281" />
39 <label htmlFor="severity">How urgent is this? *</label>
40 <select id="severity" name="severity" required>
41 <option value="">Choose…</option>
42 <option>Critical — blocking us</option>
43 <option>High — losing time</option>
44 <option>Medium — annoying</option>
45 <option>Low — heads-up</option>
46 </select>
47 <label htmlFor="description">What's wrong? *</label>
48 <textarea id="description" name="description" placeholder="Steps to reproduce, error messages, screenshots if you have them." required />
49
50 <button type="submit" disabled={status === 'sending'}>
51 {status === 'sending' ? 'Sending…' : 'Send'}
52 </button>
53
54 {status === 'error' && <p>Something went wrong. Try again.</p>}
55 </form>
56 );
57}
ALTPrefer plain HTML? View the universal customer support form HTML snippet28 lines
form.htmlHTML
<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 support ticket">

  <label for="name">Your name *</label>
  <input id="name" type="text" name="name" placeholder="Jane Builder" required>
  <label for="email">Email *</label>
  <input id="email" type="email" name="email" placeholder="jane@example.com" required>
  <label for="phone">Phone (for urgent issues)</label>
  <input id="phone" type="tel" name="phone" placeholder="+1 415 555 0142">
  <label for="order_id">Order / account ID (optional)</label>
  <input id="order_id" type="text" name="order_id" placeholder="ORD-49281">
  <label for="severity">How urgent is this? *</label>
  <select id="severity" name="severity" required>
    <option value="">Choose…</option>
    <option>Critical — blocking us</option>
    <option>High — losing time</option>
    <option>Medium — annoying</option>
    <option>Low — heads-up</option>
  </select>
  <label for="description">What's wrong? *</label>
  <textarea id="description" name="description" placeholder="Steps to reproduce, error messages, screenshots if you have them." 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>
§ 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

Sign in at splitforms.com — your access key is created instantly. No credit card, no setup wizard, no SDK to install.

Create your form
key=sk_live_••••••••
STEP 02EMBED

Paste the customer support form into your Next.js project

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

snippettsx
'use client';
  …
</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
01

Capture ticket category

Required: category (billing / bug / feature / account / general), urgency, account email, description. Optional: screenshot upload (Pro), order/invoice number for billing.

02

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.

03

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.

§ 03cNext.js production notesnative path · deploy · gotchas

What changes when this customer support form lives in Next.js.

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

without splitforms

Without splitforms, you'd write a route handler at app/api/contact/route.ts, parse the FormData, configure SMTP via nodemailer or Resend (~10 minutes of secrets wrangling), add a Postgres or SQLite store for submissions, and then bolt on rate limiting, a honeypot check, an email-classifier or reCAPTCHA, and webhook fan-out. Server actions made the wiring slightly tidier in Next 14+, but the operational cost stays the same: a function with a runtime, a database, an outbound email provider, an inbox to monitor, and your name on the spam-filter incident report. Splitforms collapses all of that into a POST to a single URL.

deploy notes

On Vercel, the form works on every plan tier — server actions and client components both run inside the same edge/serverless function. Don't put the splitforms fetch inside a Vercel cron or background function (it's user-facing, latency matters). On Netlify with the Next runtime, server actions need the latest @netlify/plugin-nextjs (≥5.6). For self-hosted / Docker: configure output: 'standalone' in next.config.ts and pass SPLITFORMS_KEY as a runtime env var — never bake it into the image. For static export (output: 'export'), use the client-component path only — server actions aren't supported in static mode.

Next.js gotcha

Don't expose your access key client-side without domain locking

Inlining access_key in a "use client" component makes the key visible to anyone who views source. That's fine if you've enabled allowed-domains in your Splitforms dashboard (Settings → Security) — anyone copying the key from your bundle can't use it from a different origin. If you haven't, use a server action so the key stays on the server.

Next.js gotcha

Server actions need `'use server'` and a real form, not fetch

If you submit to a server action via <form action={myAction}>, Next handles the FormData serialization for you. If you call the action manually with fetch, you have to set the right Content-Type and stringify yourself. Pick one path and stick with it — mixing causes 'Server Action invalid' errors.

Next.js gotcha

App Router + Suspense + useSearchParams = static-prerender bailout

If your form reads ?next=/something to support post-submit redirects, useSearchParams forces the page out of static generation. Either wrap the inner component in a <Suspense fallback={<Skeleton/>}> so the wrapper still prerenders, or accept dynamic rendering for the form route only.

Next.js gotcha

Vercel Edge runtime can't read FormData from `multipart/form-data`

If your route handler uses export const runtime = 'edge' and the form posts as multipart (file inputs), it'll silently miss fields. Use application/x-www-form-urlencoded or remove the edge runtime declaration.

PATTERN A

Pattern A — server action (no client JS, key stays server-side)

Form posts to a server action; the action appends the access key from process.env.SPLITFORMS_KEY and proxies to splitforms. Works without JavaScript, key never reaches the bundle. Use the same wiring for the customer support form fields on this page.

pattern-a.tsxtsx10 lines
01// app/actions/contact.ts
02"use server";
03import { redirect } from "next/navigation";
04
05export async function submitContact(formData: FormData) {
06 formData.append("access_key", process.env.SPLITFORMS_KEY!);
07 const res = await fetch("https://splitforms.com/api/submit", { method: "POST", body: formData });
08 if (!(await res.json()).success) throw new Error("Submission failed");
09 redirect("/thanks");
10}
PATTERN B

Pattern B — client component with fetch and inline status

'use client' component using useState for a 4-state status machine. Lets you show a spinner, inline errors, optimistic resets — at the cost of a hydration boundary. Use NEXT_PUBLIC_SPLITFORMS_KEY and rely on splitforms' domain-locking for safety. Use the same wiring for the customer support form fields on this page.

pattern-b.tsxtsx17 lines
01"use client";
02import { useState } from "react";
03export default function ContactForm() {
04 const [s, setS] = useState<"idle" | "loading" | "ok" | "err">("idle");
05 return (
06 <form onSubmit={async (e) => {
07 e.preventDefault(); setS("loading");
08 const fd = new FormData(e.currentTarget);
09 fd.append("access_key", process.env.NEXT_PUBLIC_SPLITFORMS_KEY!);
10 const r = await fetch("https://splitforms.com/api/submit", { method: "POST", body: fd });
11 setS((await r.json()).success ? "ok" : "err");
12 }}>
13 <input name="email" type="email" required />
14 <button disabled={s === "loading"}>{s === "loading" ? "…" : "Send"}</button>
15 </form>
16 );
17}
§ 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

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 Next.jsFAQ.

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

01Does this customer support form work on Next.js?
Yes. The form is plain HTML with a single POST endpoint, so it runs on any Next.js site without server-side code, plugins, or SDKs. Drop the snippet into a Next.js page or component and submissions land in your splitforms dashboard.
02How much does the customer support form cost on Next.js?
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 Next.js 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 Next.js 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.

FeatureWeb3FormsFormspreesplitforms
Free monthly submissions25050500
Custom fields beyond contactYesPro tierFree
Webhooks (Slack / Discord)Pro tierPro tierFree, signed
AI / MCP submission inboxNoNoYes
Long-term plan (3-year flat)$59 every 3 years
✻ ✻ ✻

Ship a customer support form on Next.js in 60 seconds.

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

Get free access key →Read the docs
founders pricing locked in · early access open