Email signup forms: what to ask, what to say, what happens next

One field, and what a second one costs

Ask for the email address. Nothing else, unless a later message is genuinely different because of the answer. A first name field is commonly reported to cost around a tenth of sign-ups, and on a sequence that reads identically for everybody it buys a greeting that most readers do not notice and some find slightly wrong.

The usual defence of a name field is personalisation, and it is worth testing against what personalisation actually produces: an address typed as a nickname, a job title, a blank, or the word test. A greeting built from that field is then wrong for a meaningful share of readers, which is a worse outcome than no greeting. If the name matters to you, ask in the first message and let people answer who want to.

Where a second field is genuinely load-bearing — a country that changes what you may lawfully send, a role that changes the content — put it on the form and accept the cost knowingly. The rule is not never ask; it is never ask for something nothing will use.

Label the field and the button with what they do

The button should name what arrives: send me the five emails, start the course, get the checklist. Subscribe describes what the reader is agreeing to become rather than what they are about to receive, and submit describes what the software is about to do. Both are weaker than a sentence about the thing.

The field needs a real label, not only a placeholder. A placeholder disappears the moment somebody types, which leaves a person who was interrupted mid-form looking at a box with no idea what belongs in it, and screen readers treat a placeholder inconsistently. A visible label above the field costs one line and removes a whole class of abandonment.

Keep the whole thing operable without a mouse and wide enough to press on a phone. Set the input type to email so a phone shows the right keyboard, do not disable paste, and do not make the field so narrow that a long address scrolls out of view while it is being checked.

The parts of a form, and what each one is actually for:

• A heading that repeats the promise in the same words as the page it sits on, so a reader who scrolled straight to the form still knows what they are getting.
• One labelled field, type email, with no placeholder standing in for the label.
• A button naming the thing that arrives, in the first person where it reads naturally.
• One line under the button saying what happens next, including that a confirmation is coming and the name it will arrive from.
• A link to how the address will be used and how to leave, close enough to the button that it is part of the decision.
• An error message next to the field, in words, saying what to change. Not a red border and nothing else.

The consent line, and what it has to say

Somewhere by the button, say what the address will be used for and how to stop. This is both the decent thing and the legally load-bearing thing: the GDPR requires consent to be freely given, specific, informed and unambiguous, and informed means the person knew what they were agreeing to at the moment they agreed.

Specific matters as much as informed. A form that collects an address for a five-day course does not thereby acquire permission to send a weekly newsletter and a product launch. If you intend to send both, say so on the form in words a reader can decline; a single tick covering unrelated purposes is the shape regulators single out.

A pre-ticked box is not consent anywhere in the European Union, and a box that is compulsory in order to receive the thing is not freely given either. The clean pattern is no box at all: the form does one thing, the line under the button says what that thing is, and pressing the button is the unambiguous action. Then keep the wording as it appeared on the day, with a timestamp, because you have to be able to demonstrate consent later rather than describe it.

What has to happen after the button is pressed

The screen after the button is where most forms lose the people they just persuaded. It says thanks for subscribing, which is wrong under confirmed opt-in — nobody is subscribed yet — and it says nothing about the message now sitting unopened in a spam folder.

Say instead exactly what to do next: a message has been sent to that address, it comes from this name, click the link in it, and check the spam folder if it is not there in a few minutes. That screen is the cheapest recovery available at the stage lists lose most people, because a fifth to a third of sign-ups never confirm and a good share of that is a message nobody was told to expect.

Then make the confirmation message itself easy. Send it immediately, put the link high as readable link text rather than only as a button image, and send exactly one reminder a day later. After that, stop: an address that has received one message and one reminder has answered.

The failures nobody reports

A person who abandons a form does not write to tell you why, so form defects live for years. Most of them are in the handling rather than the design: what happens on a typo, on a repeat submission, on a slow network, on a bot.

Handle a repeat submission as a success from the visitor’s point of view and as nothing at all from the sending side. Somebody who fills the form in twice should see the same calm screen, not an error implying they have done something wrong, and should not receive a second confirmation. Handle an obvious typo in the domain by saying so next to the field before submitting, because a mistyped address is a sign-up that can never be recovered.

Keep bots off the form without punishing people. An invisible field a human never sees and a bot fills in, plus a simple rate limit per address, removes most automated submissions. A puzzle that everybody has to solve costs real sign-ups to stop a problem that confirmed opt-in already contains: an unconfirmed address receives exactly one message and never joins anything.