splitforms.com
CONTACT FORM (WITH PHONE) · TAILWIND CSS

Contact Form (with phone) for Tailwind CSS

Name, email, phone, company, reason — for B2B inquiries that need qualification. Free for 500 submissions per month — no backend, no SDK, no plugin.

500/mo free·no card·drop-in for Tailwind CSS
form.htmlhtml30 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 detailed contact submission">
04
05 <label for="name">Full name *</label>
06 <input id="name" type="text" name="name" placeholder="Jane Builder" required>
07 <label for="email">Work email *</label>
08 <input id="email" type="email" name="email" placeholder="jane@company.com" required>
09 <label for="phone">Phone *</label>
10 <input id="phone" type="tel" name="phone" placeholder="+1 415 555 0142" required>
11 <label for="company">Company</label>
12 <input id="company" type="text" name="company" placeholder="Acme Inc">
13 <label for="reason">What's this about? *</label>
14 <select id="reason" name="reason" required>
15 <option value="">Choose…</option>
16 <option>Sales / pricing</option>
17 <option>Partnerships</option>
18 <option>Press / media</option>
19 <option>Support</option>
20 <option>Careers</option>
21 <option>Other</option>
22 </select>
23 <label for="message">Message *</label>
24 <textarea id="message" name="message" placeholder="Give us context — links, dates, deal size, anything we should know." required></textarea>
25
26 <!-- honeypot — bots fill every field -->
27 <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">
28
29 <button type="submit">Send</button>
30</form>
500
submissions / mo, free
6
fields, ready to ship
5
code outputs
60s
from copy to inbox
§ 00Tailwind CSS + Contact Form (with phone)platform-specific integration guide

Why Tailwind CSS developers choose splitforms for contact form (with phone)

Tailwind CSS handles the styling side — utility classes for layout, spacing, colors, and responsive breakpoints. But styling a form is only half the job; you still need email delivery, spam filtering, webhook routing, and storage. The contact form (with phone) on this page combines Tailwind's utility-first CSS with splitforms' backend API: Tailwind makes it look right, splitforms makes it work. No form library needed — just standard HTML inputs with Tailwind classes, posting <code>FormData</code> to one endpoint. Works in Next.js, React, Vue, Astro, or any framework that supports Tailwind.

§ 00Quick answerHTML · lead capture

Yes — this is the shortest safe path for Tailwind CSS.

Use the HTML snippet on this page, keep the contact form (with phone) fields visible in your Tailwind CSS 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 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 tailwind css reality

Tailwind is a styling layer — it has no opinion on form submission, networking, or backend.

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) × Tailwind CSSwhy this combination, in 80 words

Built for Tailwind CSS developers who hate operating a backend.

Splitforms is the form backend for Tailwind CSS 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 Tailwind CSS 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 · 30 lines

Drop into any Tailwind CSS project.

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

form.htmlhtml30 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 detailed contact submission">
04
05 <label for="name">Full name *</label>
06 <input id="name" type="text" name="name" placeholder="Jane Builder" required>
07 <label for="email">Work email *</label>
08 <input id="email" type="email" name="email" placeholder="jane@company.com" required>
09 <label for="phone">Phone *</label>
10 <input id="phone" type="tel" name="phone" placeholder="+1 415 555 0142" required>
11 <label for="company">Company</label>
12 <input id="company" type="text" name="company" placeholder="Acme Inc">
13 <label for="reason">What's this about? *</label>
14 <select id="reason" name="reason" required>
15 <option value="">Choose…</option>
16 <option>Sales / pricing</option>
17 <option>Partnerships</option>
18 <option>Press / media</option>
19 <option>Support</option>
20 <option>Careers</option>
21 <option>Other</option>
22 </select>
23 <label for="message">Message *</label>
24 <textarea id="message" name="message" placeholder="Give us context — links, dates, deal size, anything we should know." required></textarea>
25
26 <!-- honeypot — bots fill every field -->
27 <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">
28
29 <button type="submit">Send</button>
30</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

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 contact form (with phone) into your Tailwind CSS project

Drop the form snippet into a Tailwind CSS 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 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
01

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.

02

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}"`.

03

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

§ 03cTailwind CSS production notesnative path · deploy · gotchas

What changes when this contact form (with phone) lives in Tailwind CSS.

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

without splitforms

Tailwind is a styling layer — it has no opinion on form submission, networking, or backend. The 'native' approach means writing utility classes for visual treatment and bringing your own delivery mechanism: a Next.js route handler, a Vite + React + fetch combo, an HTMX endpoint, etc. Tailwind UI ($299 one-time) sells styled form templates but doesn't include a backend either. Tailwind v4's @theme directive changes how tokens are defined, not what forms do. The shape of the problem stays: utility classes for look-and-feel, splitforms for delivery. Drop the snippet on this page into any framework with Tailwind configured and you have a styled, working form in 60 seconds.

deploy notes

Tailwind is purely a build-time concern — utilities are compiled into your CSS bundle, then deployed as static assets. JIT mode (default in v3+) and the v4 engine both purge unused classes; if you build form HTML inside a JS template literal at runtime, Tailwind can't see those classes and purges them — add to safelist or move markup into source files. Works on every host. For dark mode toggled via class, set darkMode: 'class' in v3 config or use @variant dark (.dark &) in v4 CSS. The @tailwindcss/forms plugin resets input styles aggressively — pick one (plugin OR explicit utilities), not both.

Tailwind CSS gotcha

JIT mode purges classes inside template strings

If you build the form HTML inside a JS template literal, Tailwind's JIT can't see your classes and purges them. Either move the markup into a .html / .tsx / .vue file, or add the classes to your safelist in tailwind.config.js.

Tailwind CSS gotcha

Tailwind 4's @theme replaces tailwind.config.js — focus colors break

Tailwind 4 (released 2026) moved theme tokens into CSS via @theme { … }. If you copy a Tailwind 3 snippet using focus:ring-orange-500, the orange-500 token has to be defined in your @theme block or it falls back to no ring color. Use a CSS variable: focus:ring-[var(--accent)] for portability.

Tailwind CSS gotcha

Form gets no styling at all — Preflight not loaded

If you're embedding the form inside a Shadow DOM, iframe, or a CMS that strips global CSS, Tailwind's Preflight (the global reset) doesn't apply. Inputs render with browser-default white backgrounds, ignoring bg-white if you set it in @apply but not as a utility on the element. Always use utilities directly on the input.

Tailwind CSS gotcha

Dark mode classes need `class` strategy explicitly set

Tailwind defaults to media-query dark mode (prefers-color-scheme). If your form has dark:bg-gray-900 and you toggle dark mode via a class on <html>, you need darkMode: 'class' in tailwind.config.js (Tailwind 3) or @variant dark (.dark &) in your CSS (Tailwind 4).

PATTERN A

Pattern A — utility-first inline styles

Every input gets utilities directly on the element — explicit, JIT-safe, no @apply indirection. Works in HTML, JSX, TSX, Vue, Svelte, Astro identically. Use the same wiring for the contact form (with phone) fields on this page.

pattern-a.htmlhtml12 lines
01<form action="https://splitforms.com/api/submit" method="POST"
02 class="max-w-md mx-auto space-y-4 p-6 bg-white rounded-2xl border border-gray-200">
03 <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY" />
04 <input name="email" type="email" required
05 class="w-full rounded-lg border px-3 py-2 focus:ring-2 focus:ring-orange-500" />
06 <textarea name="message" rows="4" required
07 class="w-full rounded-lg border px-3 py-2 focus:ring-2 focus:ring-orange-500" />
08 <button type="submit"
09 class="w-full bg-orange-600 hover:bg-orange-700 text-white font-semibold py-2 rounded-lg">
10 Send
11 </button>
12</form>
PATTERN B

Pattern B — dark-mode + accessible focus states (Tailwind v4)

Pairs dark: variants with focus-visible: for keyboard-only focus rings. Uses CSS variables for accent color so the same component works in light/dark without rewriting utilities. Use the same wiring for the contact form (with phone) fields on this page.

pattern-b.htmlhtml9 lines
01<form action="https://splitforms.com/api/submit" method="POST"
02 class="max-w-md mx-auto p-6 rounded-2xl border bg-white dark:bg-zinc-900 dark:border-zinc-800">
03 <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY" />
04 <input name="email" type="email" required
05 class="w-full rounded-lg border bg-white dark:bg-zinc-950 px-3 py-2
06 text-gray-900 dark:text-zinc-100
07 focus-visible:ring-2 focus-visible:ring-[var(--accent)]" />
08 <button class="w-full bg-[var(--accent)] text-white py-2 rounded-lg">Send</button>
09</form>
§ 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
EMAIL

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 Tailwind CSSFAQ.

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

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

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 contact form (with phone) on Tailwind CSS in 60 seconds.

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

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