send.webforms.toRead the docs →

For agencies

Every client's forms, without a server per client

Give each client site its own form and endpoint, send its submissions straight to the client's inbox or Slack, and lock each form to the client's domain so a copied key does nothing. Your team shares one workspace with a seat each, each client can get a free read-only login that shows only their own forms, and white-label notifications are an add-on when the client should never see our name.

What it handles

A form per site, not a plan per site

Forms are unlimited on every plan, so thirty client sites are thirty forms in one workspace rather than thirty subscriptions. Each has its own endpoint, its own destinations and its own spam settings, and the monthly quota is shared across all of them.

Submissions that go to the client, not to you

Point each form's email destination at the client, add yourself on CC if you want visibility (paid plans), and the client gets their leads without logging in anywhere. On paid plans the same form can also post to the client's Slack or a webhook into their CRM.

A key that only works on the site it belongs to

Endpoint keys sit in public HTML, so anyone can copy one. Each form takes a list of allowed domains, and submissions from anywhere else are refused. When a site is rebuilt on a new domain, you update one list instead of chasing junk submissions.

A login for each client, on one shared pool

On Agency, add each client on the Clients page and put their forms under them. Invite the client to a free, read-only login that shows only their own forms, submissions and unfinished forms, nothing of your other clients. Every client draws on your one monthly allowance, and the page shows how much each one used this period.

Your name, or nobody's

Notification emails can go out under your agency's sender name on paid plans. White labelling removes the WebForms mention from notifications and the confirmation screen entirely, as an add-on to any paid plan at $9 a month.

Handing a site over cleanly

If a client wants to own their data and the bill, have them create the workspace and invite you as a member. You can belong to several workspaces and switch between them, so the client keeps everything if the relationship ends and you never hold data you should not.

The limits, plainly

There is no per-client billing inside one workspace: clients share your allowance and you invoice them yourself, using the per-client usage on the Clients page. If a client should own the data and the bill, give them their own workspace instead.

Which plan

Agency is built for this: clients with their own read-only logins, 25,000 submissions a month shared across every client form, 10 seats for your team, 365 days of history and priority support, for $12 a month. A small studio with a handful of sites usually fits Pro, with 3 seats and 12,000 submissions for $5.

Also written for