CUSTOMER SUPPORT FORM · ASTRO

Customer Support Form for Astro

Help-desk intake with topic, priority, and order/account reference fields. 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 Astro

form.htmlhtml28 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 support ticket">
04 
05  <label for="name">Your name *</label>
06  <input id="name" type="text" name="name" placeholder="Jane Builder" required>
07  <label for="email">Email *</label>
08  <input id="email" type="email" name="email" placeholder="jane@example.com" required>
09  <label for="phone">Phone (for urgent issues)</label>
10  <input id="phone" type="tel" name="phone" placeholder="+1 415 555 0142">
11  <label for="order_id">Order / account ID (optional)</label>
12  <input id="order_id" type="text" name="order_id" placeholder="ORD-49281">
13  <label for="severity">How urgent is this? *</label>
14  <select id="severity" name="severity" required>
15    <option value="">Choose…</option>
16    <option>Critical — blocking us</option>
17    <option>High — losing time</option>
18    <option>Medium — annoying</option>
19    <option>Low — heads-up</option>
20  </select>
21  <label for="description">What's wrong? *</label>
22  <textarea id="description" name="description" placeholder="Steps to reproduce, error messages, screenshots if you have them." required></textarea>
23 
24  <!-- honeypot — bots fill every field -->
25  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">
26 
27  <button type="submit">Send</button>
28</form>

500

submissions / mo, free

fields, ready to ship

code outputs

60s

from copy to inbox

§ 00Astro + Customer Support Formplatform-specific integration guide

Why Astro developers choose splitforms for customer support form

Astro's static-first architecture means your form HTML ships pre-rendered with zero client JavaScript — perfect for fast page loads, but it also means you can't call a server-side endpoint on static hosts. splitforms is designed for exactly this: the browser POSTs directly to our edge endpoint, so the form works on Netlify, Cloudflare Pages, Vercel, or any static host without an Astro API route. The customer support form is pure HTML — no <code><script></code> tag, no client component, no island. Astro's view transitions and partial hydration don't interfere with the form submission because it uses a standard browser POST.

§ 00Quick answerHTML · support

Yes — this is the shortest safe path for Astro.

Use the HTML snippet on this page, keep the customer support form fields visible in your Astro 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 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 astro reality

Astro's whole pitch is shipping zero JavaScript by default.

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 × Astrowhy this combination, in 80 words

Built for Astro developers who hate operating a backend.

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

Splitforms is the form backend for Astro 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 · 28 lines

Drop into any Astro project.

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

form.htmlhtml28 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 support ticket">
04 
05  <label for="name">Your name *</label>
06  <input id="name" type="text" name="name" placeholder="Jane Builder" required>
07  <label for="email">Email *</label>
08  <input id="email" type="email" name="email" placeholder="jane@example.com" required>
09  <label for="phone">Phone (for urgent issues)</label>
10  <input id="phone" type="tel" name="phone" placeholder="+1 415 555 0142">
11  <label for="order_id">Order / account ID (optional)</label>
12  <input id="order_id" type="text" name="order_id" placeholder="ORD-49281">
13  <label for="severity">How urgent is this? *</label>
14  <select id="severity" name="severity" required>
15    <option value="">Choose…</option>
16    <option>Critical — blocking us</option>
17    <option>High — losing time</option>
18    <option>Medium — annoying</option>
19    <option>Low — heads-up</option>
20  </select>
21  <label for="description">What's wrong? *</label>
22  <textarea id="description" name="description" placeholder="Steps to reproduce, error messages, screenshots if you have them." required></textarea>
23 
24  <!-- honeypot — bots fill every field -->
25  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">
26 
27  <button type="submit">Send</button>
28</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

Create your form

key=sk_live_••••••••

STEP 02EMBED

Paste the customer support form into your Astro project

Drop the form snippet into a Astro 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 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

Capture ticket category

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

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.

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.

§ 03cAstro production notesnative path · deploy · gotchas

What changes when this customer support form lives in Astro.

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

without splitforms

Astro's whole pitch is shipping zero JavaScript by default. A native contact form on Astro means either (a) building a form with no submission target — useless — or (b) standing up an API endpoint via output: 'server' or 'hybrid', which means writing a Node/Bun/Deno handler, picking an email provider, writing your own honeypot logic. Astro 5 added typed Actions, but they're a wrapper around the same underlying fetch — you still deliver the email yourself. The result: every Astro contact-form tutorial ends with 'now configure SendGrid'. Splitforms is the SendGrid-replacement that doesn't require an account, an API key for the email provider, or DNS records for SPF/DKIM.

deploy notes

Astro deploys cleanly to Vercel, Netlify, Cloudflare Pages, GitHub Pages, and any static host with output: 'static'. For Astro Actions (Pattern B), you need output: 'server' or 'hybrid' and a matching adapter (@astrojs/vercel, @astrojs/netlify, @astrojs/cloudflare). On Cloudflare Pages with the Cloudflare adapter, the Action runs in a Worker — keep the splitforms fetch tight (no extra proxying) to stay under the 10ms CPU budget on the free plan. The PUBLIC_ prefix is mandatory for env vars exposed to client-rendered .astro files; vars without it are silently undefined. Lock the key to your *.pages.dev and custom domain.

Astro gotcha

PUBLIC_ prefix is required for client-exposed env vars

Astro mirrors Vite's env-var convention: only variables prefixed with PUBLIC_ are exposed to client-side code (and to .astro files when output: 'static'). If you write import.meta.env.SPLITFORMS_KEY, you'll get undefined at build time. Rename to PUBLIC_SPLITFORMS_KEY.

Astro gotcha

client:load on the form island defeats the point of Astro

If you wrap the form in <MyForm client:load />, you ship a full React/Preact runtime just for one form. Use client:visible (load when scrolled into view) or client:idle (load after main thread is free) instead. For zero-JS forms, skip the island entirely and use a plain HTML form action.

Astro gotcha

Astro Actions need a try/catch or they crash the page

If your action throws, Astro 5's behavior is to render an error page rather than return the error to your form. Wrap the splitforms fetch in try/catch and return { success: false, message } from the action — your form component can then render the message.

Astro gotcha

View Transitions can break form re-submit state

If you've enabled <ViewTransitions /> in your layout, navigating to /contact and back may re-mount the form mid-submission. Add data-astro-reload to the form's submit anchor or guard with if (status === 'loading') return at the top of your handler.

PATTERN A

Pattern A — pure HTML form (zero JS shipped)

The Astro-native approach: a .astro file with frontmatter pulling the key from import.meta.env, then a static <form action> that posts directly. Zero hydration, zero island, zero KB JavaScript. Use the same wiring for the customer support form fields on this page.

pattern-a.txtastro10 lines

01---
02const ACCESS_KEY = import.meta.env.PUBLIC_SPLITFORMS_KEY;
03---
04<form action="https://splitforms.com/api/submit" method="POST">
05  <input type="hidden" name="access_key" value={ACCESS_KEY} />
06  <input type="hidden" name="redirect"   value="/thanks" />
07  <input name="email" type="email" required />
08  <textarea name="message" required />
09  <button type="submit">Send</button>
10</form>

PATTERN B

Pattern B — Astro Action for typed server-side proxying

Astro 5 Actions give you Zod-validated, type-safe form handlers. Use one to keep the access key off the client entirely — the form posts to the action, the action proxies to splitforms. Use the same wiring for the customer support form fields on this page.

pattern-b.txtastro17 lines

01// src/actions/index.ts
02import { defineAction } from "astro:actions";
03import { z } from "astro:schema";
04export const server = {
05  contact: defineAction({
06    accept: "form",
07    input: z.object({ email: z.string().email(), message: z.string() }),
08    async handler(input) {
09      const fd = new FormData();
10      Object.entries(input).forEach(([k, v]) => fd.append(k, v));
11      fd.append("access_key", import.meta.env.SPLITFORMS_KEY);
12      const r = await fetch("https://splitforms.com/api/submit", { method: "POST", body: fd });
13      if (!(await r.json()).success) throw new Error("Submission failed");
14      return { ok: true };
15    },
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

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 Astro — FAQ.

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

01Does this customer support form work on Astro?

Yes. The form is plain HTML with a single POST endpoint, so it runs on any Astro site without server-side code, plugins, or SDKs. Drop the snippet into a Astro page or component and submissions land in your splitforms dashboard.

02How much does the customer support form cost on Astro?

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

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 Astro5 adjacent patterns

Ship a customer support form on Astro in 60 seconds.

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

Get free access key →Read the docs

founders pricing locked in · early access open

Customer Support Form for Astro

Why Astro developers choose splitforms for customer support form

Yes — this is the shortest safe path for Astro.

Paste the HTML version, then replace YOUR_ACCESS_KEY.

Built for Astro developers who hate operating a backend.

Drop into any Astro project.

Generate, embed, receive.

Generate a free splitforms key

Paste the customer support form into your Astro project

Receive submissions

The reason this customer support form exists.

Capture ticket category

Route by category

Auto-confirm with SLA

What changes when this customer support form lives in Astro.

PUBLIC_ prefix is required for client-exposed env vars

client:load on the form island defeats the point of Astro

Astro Actions need a try/catch or they crash the page

View Transitions can break form re-submit state

Pattern A — pure HTML form (zero JS shipped)

Pattern B — Astro Action for typed server-side proxying

What every field actually does.

Your name

Email

Phone (for urgent issues)

Order / account ID (optional)

How urgent is this?

What's wrong?

One backend. Every framework.

Customer Support Form on Astro — FAQ.

splitforms vs everything else.

Other ready-to-ship Astro forms.

Ship a customer support form on Astro in 60 seconds.