How many fields should a contact form have?

As few as let you reply usefully — typically name, email and message. Every additional field measurably lowers completion, so cut anything you don't truly need before someone can respond.

Can a contact form work without a backend?

Yes. Vireya's contact form can fall back to a pre-filled mailto link that opens the visitor's mail client, so you can ship a working contact section before wiring up any server-side handling.

All categories

contact/*

Contact forms

Get-in-touch sections — centered card or split with info column.

2 variants

@vireya/blocks/contact/simple

Centered contact card with name, email, and message. Uses state — opts into 'use client'.

client

Get in touch

Tell us what you're working on. We usually reply within one business day.

By submitting, you agree to our privacy policy.

@vireya/blocks/contact/split

Two-column contact section: details on the left, form on the right. Uses state — opts into 'use client'.

client

Talk to us

Whether you want a demo, have a partnership idea, or just want to say hi — we read every message.

hello@example.com

Phone

+1 (415) 555-0142

Office

548 Market St, Suite 27531
San Francisco, CA 94104

Hours

Mon–Fri, 9:00–18:00 PT

Understanding Contact forms

A contact section is the bridge between interest and conversation. Its job is to lower the friction of getting in touch — a short form, the right alternative channels, and a reason to expect a useful reply. Every extra field is a reason to abandon.

Vireya offers a centered card and a split layout with an information column, and the form can hand off to a backend or fall back to the visitor's mail client.

When to use

Sales, support or general get-in-touch sections.
Pairing a form with context — hours, location, alternative channels (split layout).
Capturing structured enquiries while you have no backend yet (mailto fallback).

When to avoid

Long forms for low-commitment contact, which suppress submissions.
Forms with no alternative channel for users who won't fill one in.

Best practices

Ask only for the fields you genuinely need to respond.
Set expectations — response time, what happens next.
Offer an alternative (email, social) alongside the form.
Label every field clearly and validate inline, not only on submit.

Accessibility

Associate every input with a visible <label>.
Announce validation errors programmatically and in text.
Ensure the form is fully keyboard-navigable in a logical order.

Frequently asked questions

How many fields should a contact form have?: As few as let you reply usefully — typically name, email and message. Every additional field measurably lowers completion, so cut anything you don't truly need before someone can respond.
Can a contact form work without a backend?: Yes. Vireya's contact form can fall back to a pre-filled mailto link that opens the visitor's mail client, so you can ship a working contact section before wiring up any server-side handling.