Consultation Request for Svelte
Discovery-call request with service, budget, and timeline qualification. Free for 500 submissions per month — no backend, no SDK, no plugin.
Why Svelte developers choose splitforms for consultation request
Svelte's lightweight runtime is one of its biggest selling points — adding a heavy form library defeats the purpose. The consultation request on this page keeps that promise: it uses Svelte's native <code>on:submit</code> directive and a <code>fetch</code> POST, with no external dependencies. The form state lives in a simple <code>let</code> variable, not a store or a state machine. In SvelteKit, you could alternatively use a <code>+page.server.ts</code> action, but that couples your form to SvelteKit's server-side runtime — splitforms decouples it so the same form works on static hosts and other frameworks.
Yes — this is the shortest safe path for Svelte.
Use the HTML snippet on this page, keep the consultation request fields visible in your Svelte UI, and let splitforms handle delivery, spam filtering, storage, and webhooks.
Paste the HTML version, then replace YOUR_ACCESS_KEY.
The posted payload contains full name, email, phone, topic, what do you need help with?. Required fields are full name, email, phone, topic and what do you need help with?.
Plain Svelte (without SvelteKit) is a compiler — there's no runtime route handler, no server, no built-in form delivery.
Discovery-call request with service, budget, and timeline qualification.
Built for Svelte developers who hate operating a backend.
Splitforms is the form backend for Svelte sites. One POST endpoint, no SDK, no plugin — drop the consultation request into a page and ship.
Splitforms is the form backend for Svelte 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.
- ✓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)
Drop into any Svelte project.
Replace YOUR_ACCESS_KEY with your splitforms key, paste into a Svelte page, and ship. No build-time integration required.
Generate, embed, receive.
Three actions stand between you and your first consultation request submission. None of them require a backend, a database, or a CAPTCHA library.
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.
Paste the consultation request into your Svelte project
Drop the form snippet into a Svelte 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.
Receive submissions
Dashboard updates live on Free. Starter adds email delivery, signed webhooks, CSV export, Slack/Discord forwarding, and BCC to your team.
What changes when this consultation request lives in Svelte.
These notes come from the Svelte platform registry and are rendered on this template page so crawlers see the framework-specific answer without opening a separate guide.
Plain Svelte (without SvelteKit) is a compiler — there's no runtime route handler, no server, no built-in form delivery. To ship a working form natively you'd add a separate Node/Bun/Express layer, write the SMTP wiring, and operate it. SvelteKit ships form actions and use:enhance for progressive enhancement, but those just give you ergonomic ways to call your own backend; the actual email-delivery, spam-filtering, and submission-storage are still on you. Svelte 5 runes change reactivity syntax, not the operational model. Splitforms removes the entire 'add a backend' step: the runtime is one URL, hosted by us.
Vite + Svelte (non-Kit) builds a static bundle for any host. SvelteKit deploys via adapters: @sveltejs/adapter-vercel, -netlify, -cloudflare, -node, -static. The form posts client-side regardless of adapter, so the form itself works identically on each. Use VITE_SPLITFORMS_KEY for plain Vite-Svelte projects; SvelteKit uses $env/static/public from PUBLIC_SPLITFORMS_KEY. Svelte islands embedded in Astro hydrate via client:visible — the form's fetch only runs after the user scrolls to it, saving JS execution on initial load. Lock the access key to your domain.
Svelte 5 runes vs Svelte 4 reactive let — pick one
Svelte 5 introduces $state(...) runes; Svelte 4 uses plain let status = 'idle'. They're not interchangeable in the same component. Check package.json for "svelte": "^5" and use runes accordingly. Mixing them throws a confusing 'rune used outside .svelte.js' error.
on:submit|preventDefault becomes onsubmit={(e) => …} in Svelte 5
If you copy a Svelte 4 snippet into a Svelte 5 project, the on:submit|preventDefault modifier syntax is gone. Use onsubmit={(e) => { e.preventDefault(); … }} or migrate to a SvelteKit form action that handles preventDefault for you.
bind:value desyncs FormData if you forget the `name` attribute
FormData reads from name="…" attributes, not Svelte's bind:value. If you bind a value but skip the name attribute, the field is silently dropped from the POST body. Always set both.
Vite-only Svelte projects can't use $env/static/private
$env/static/private is a SvelteKit feature, not a Vite-Svelte one. In a vanilla Vite + Svelte project, use import.meta.env.VITE_SPLITFORMS_KEY (must have the VITE_ prefix or it's undefined client-side).
Pattern A — Svelte 4 reactive let
Classic Svelte syntax: let status = 'idle', reactive by assignment. Works in every Svelte version with a deprecation warning in Svelte 5. Single-file component, no SvelteKit required. Use the same wiring for the consultation request fields on this page.
Pattern B — Svelte 5 runes
$state(...) for reactive variables, onsubmit={...} (no on: prefix) for events. Cleaner reactivity model, full TypeScript inference on state. Use the same wiring for the consultation request fields on this page.
What every field actually does.
Each field below ships in the consultation request template — rename, remove, or add your own. Splitforms accepts any name you POST.
Full name
Greeting + dashboard label so submissions don't all read 'anonymous'.
Reply-to address — splitforms wires this so hitting reply goes back to the sender.
Phone
Faster qualification — phone leads convert ~3× higher than email-only on B2B forms.
Topic
Dropdown — keeps responses normalised so you can filter the dashboard.
What do you need help with?
Free-text context — what the visitor actually wants you to know.
One backend. Every framework.
The same consultation request template works on every framework splitforms supports. Pick yours.
Consultation Request on Svelte — FAQ.
Direct answers, no marketing fluff. Missing one? Email hello@splitforms.com.
splitforms vs everything else.
Same drop-in API. More free submissions, Starter signed webhooks, MCP support no other backend has.
Other ready-to-ship Svelte forms.
Same backend, different qualifying fields. Click through to copy the snippet.
Ship a consultation request on Svelte in 60 seconds.
500 submissions per month, free forever. No credit card. Copy the snippet above and paste it into your Svelte project.