CONTACT FORM (WITH PHONE) · NEXT.JS

Contact Form (with phone) for Next.js

Name, email, phone, company, reason — for B2B inquiries that need qualification. 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 Next.js

Form.tsxtsx59 lines

01'use client';
02 
03import { useState, type FormEvent } from 'react';
04 
05export default function ContactDetailedForm() {
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 detailed contact submission');
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">Full name *</label>
32      <input id="name" type="text" name="name" placeholder="Jane Builder" required />
33      <label htmlFor="email">Work email *</label>
34      <input id="email" type="email" name="email" placeholder="jane@company.com" required />
35      <label htmlFor="phone">Phone *</label>
36      <input id="phone" type="tel" name="phone" placeholder="+1 415 555 0142" required />
37      <label htmlFor="company">Company</label>
38      <input id="company" type="text" name="company" placeholder="Acme Inc" />
39      <label htmlFor="reason">What's this about? *</label>
40      <select id="reason" name="reason" required>
41        <option value="">Choose…</option>
42        <option>Sales / pricing</option>
43        <option>Partnerships</option>
44        <option>Press / media</option>
45        <option>Support</option>
46        <option>Careers</option>
47        <option>Other</option>
48      </select>
49      <label htmlFor="message">Message *</label>
50      <textarea id="message" name="message" placeholder="Give us context — links, dates, deal size, anything we should know." required />
51 
52      <button type="submit" disabled={status === 'sending'}>
53        {status === 'sending' ? 'Sending…' : 'Send'}
54      </button>
55 
56      {status === 'error' && <p>Something went wrong. Try again.</p>}
57    </form>
58  );
59}

500

submissions / mo, free

fields, ready to ship

code outputs

60s

from copy to inbox

§ 00Next.js + Contact Form (with phone)platform-specific integration guide

Why Next.js developers choose splitforms for contact form (with phone)

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 contact form (with phone) 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 · lead capture

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

Use the React / Next.js snippet on this page, keep the contact form (with phone) 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 full name, work email, phone, company, what's this about?, message. Required fields are full name, work email, phone, what's this about? and message.

native next.js reality

use case fit

A contact form with a phone number field that auto-formats as the user types — (555) 123-4567 emerges from raw digits. Pure pattern validation, optional JS mask for the live formatting.

§ 01Contact Form (with phone) × 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 contact form (with phone) 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 · 59 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.tsxtsx59 lines

01'use client';
02 
03import { useState, type FormEvent } from 'react';
04 
05export default function ContactDetailedForm() {
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 detailed contact submission');
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">Full name *</label>
32      <input id="name" type="text" name="name" placeholder="Jane Builder" required />
33      <label htmlFor="email">Work email *</label>
34      <input id="email" type="email" name="email" placeholder="jane@company.com" required />
35      <label htmlFor="phone">Phone *</label>
36      <input id="phone" type="tel" name="phone" placeholder="+1 415 555 0142" required />
37      <label htmlFor="company">Company</label>
38      <input id="company" type="text" name="company" placeholder="Acme Inc" />
39      <label htmlFor="reason">What's this about? *</label>
40      <select id="reason" name="reason" required>
41        <option value="">Choose…</option>
42        <option>Sales / pricing</option>
43        <option>Partnerships</option>
44        <option>Press / media</option>
45        <option>Support</option>
46        <option>Careers</option>
47        <option>Other</option>
48      </select>
49      <label htmlFor="message">Message *</label>
50      <textarea id="message" name="message" placeholder="Give us context — links, dates, deal size, anything we should know." required />
51 
52      <button type="submit" disabled={status === 'sending'}>
53        {status === 'sending' ? 'Sending…' : 'Send'}
54      </button>
55 
56      {status === 'error' && <p>Something went wrong. Try again.</p>}
57    </form>
58  );
59}

ALTPrefer plain HTML? View the universal contact form (with phone) HTML snippet30 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 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>

§ 03Setup3 steps · 60 seconds · zero config

Generate, embed, receive.

Three actions stand between you and your first contact form (with phone) 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 contact form (with phone) 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 detailed contact submission

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?

§ 03bPhone Number Input Form (with masked input)template-specific playbook

The reason this contact form (with phone) exists.

Mobile-friendly numeric keypad, live mask, format-tolerant.

why it matters

Phone fields suffer from format chaos — users type +1 555 123 4567, (555) 123 4567, 555.123.4567, 5551234567. Three options: accept anything and normalize server-side (best for international), use a pattern attribute for client-side validation (good for US-only), or apply a JavaScript mask that formats as the user types (highest conversion, more code). splitforms accepts any format and your form's UX is whichever approach fits your audience.

route the submission

Use type="tel" not type="text"

Mobile keyboards open the numeric keypad for tel inputs. Desktop accepts the same characters as text but signals intent.

Add a pattern attribute for validation

`pattern="[0-9() +-]+"` allows the common phone characters. Or use a strict US format: `pattern="$?\d{3}$?[ -]?\d{3}[ -]?\d{4}"`.

(Optional) Add the JS mask

On input, strip non-digits and reformat to `(XXX) XXX-XXXX`. The mask runs on every keystroke, giving live formatting feedback.

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

What changes when this contact form (with phone) 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 contact form (with phone) 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 contact form (with phone) 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 contact form (with phone) template — rename, remove, or add your own. Splitforms accepts any name you POST.

nameREQUIRED

TEXT

Full name

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

placeholder · Jane Builder

emailREQUIRED

Work email

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

placeholder · jane@company.com

phoneREQUIRED

PHONE

Phone

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

placeholder · +1 415 555 0142

company

TEXT

Company

Lets you sort enterprise vs SMB inquiries before you reply.

placeholder · Acme Inc

reasonREQUIRED

SELECT

What's this about?

Routes the lead to the right inbox folder or teammate.

Sales / pricingPartnershipsPress / mediaSupportCareersOther

messageREQUIRED

TEXTAREA

Message

Free-text context — what the visitor actually wants you to know.

placeholder · Give us context — links, dates, deal size, anything we should know.

§ 05Contact Form (with phone) on other frameworks21 frameworks · same backend

One backend. Every framework.

The same contact form (with phone) template works on every framework splitforms supports. Pick yours.

§ 06Questions9 answered

Contact Form (with phone) on Next.js — FAQ.

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

01Does this contact form (with phone) 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 contact form (with phone) 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 (full name, work email, phone, company…) — add, remove, or rename any of them. Splitforms accepts whatever fields you POST.

04How does spam protection work on the contact form (with phone)?

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 contact form (with phone) 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.

07Why use type="tel" if it doesn't do anything special on desktop?

Two reasons. (1) Mobile keyboards: tel triggers the numeric keypad, dramatically reducing typos. (2) Accessibility: screen readers announce the field type, helping users with assistive tech understand what's expected. The 'no desktop benefit' is a feature, not a bug — the behavior matches user intent.

08Should I validate international or US-only?

Depends on your audience. International contact forms should accept any format (use a permissive pattern + server-side normalization). US-only forms can use a strict pattern that matches `(555) 123-4567`. Either way, splitforms accepts whatever format the user submits — the validation is for UX, not data integrity.

09Does the JS mask work with paste?

Yes — listen for both `input` and `paste` events, and reformat on every change. The pattern only validates on submit, so the mask gives live feedback as the user types or pastes.

§ 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 Next.js5 adjacent patterns

Ship a contact form (with phone) 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

Contact Form (with phone) for Next.js

Why Next.js developers choose splitforms for contact form (with phone)

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

Paste the React / Next.js version, then replace YOUR_ACCESS_KEY.

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

Drop into any Next.js project.

Generate, embed, receive.

Generate a free splitforms key

Paste the contact form (with phone) into your Next.js project

Receive submissions

The reason this contact form (with phone) exists.

Use type="tel" not type="text"

Add a pattern attribute for validation

(Optional) Add the JS mask

What changes when this contact form (with phone) lives in Next.js.

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

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

App Router + Suspense + useSearchParams = static-prerender bailout

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

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

Pattern B — client component with fetch and inline status

What every field actually does.

Full name

Work email

Phone

Company

What's this about?

Message

One backend. Every framework.

Contact Form (with phone) on Next.js — FAQ.

splitforms vs everything else.

Other ready-to-ship Next.js forms.

Ship a contact form (with phone) on Next.js in 60 seconds.