Submit Button Text Form Design: Wording, State, Failure

The last thing a visitor reads before committing, and on most forms it describes what the software does rather than what happens to them.

Submit button text on a form: say what happens next

The button at the bottom of a form is the last thing a visitor reads before committing, and on most forms it says “Submit”. That word describes what the software does. It says nothing about what happens to the person who presses it — which is the only thing they actually want to know at that moment.

Replacing it costs nothing and is one of the few changes on a form that is purely upside: a button describing the outcome removes a small uncertainty at the exact point where uncertainty is most expensive.

Write the outcome, in the visitor’s words

Three principles run through those. Use a verb that names the result rather than the mechanism. Write it from the visitor’s side — “get my quote” rather than “request a quote” — because the button is their action, not yours. And keep it short enough to read at a glance, which on a phone means a few words, not a sentence.

Avoid overclaiming. A button reading “start saving money” promises an outcome the form cannot deliver, and it sets up a disappointment on the page that follows. The button should describe what pressing it does, and nothing more.

The button is also a promise about what comes next

Whatever the button says has to match what actually happens. A button reading “Book my call” that leads to a page saying someone will be in touch is a small broken promise, and it is the kind visitors remember. Write the button, the confirmation and the follow-up together — the structure for the second of those is in the thank-you step, and where the form genuinely books a time it should reach a calendar clients can book into rather than a queue.

Where something happens beyond the obvious — a card is charged, a subscription starts, a confirmation email must be clicked — the button or the line directly under it should say so. That is not only courtesy: a purchase button that does not make clear a recurring charge is starting is the origin of a large share of disputes, and it interacts with the record described in what a consent record has to contain.

State, and the double submission problem

• Disable it on click and change the label. “Sending…” tells the visitor the press registered. Without it, a slow response produces a second press and often a duplicate record.
• Never leave it looking pressable while working. This is the single most common cause of duplicate enquiries, and it is entirely preventable.
• Restore it on failure. A button permanently stuck in “Sending…” after an error strands the visitor with no way forward.
• Keep it enabled before validation. A button greyed out until every field is correct hides the reason nothing is happening; let the press occur and show the specific error, which is the standard in required-field validation.
• Handle slow uploads visibly. Where a form carries a file, the wait can be long, and the button state is what stops the visitor assuming it has frozen — see file size limits on uploads.

On a multi-step form, the buttons mean different things

An intermediate step’s button is not a submit button; it is “next”, and it should say so or say what the next step covers. Reserve the outcome wording for the final press, so a visitor knows which one commits them. Combined with an honest the progress bar element, that removes most of the uncertainty about how much is left — and the wider trade-offs of stepping a form are in splitting a form across steps.

Offer a way back. A step with only a forward button traps someone who mistyped an earlier answer, and they will start again or leave.

Placement and appearance

Make it obviously a button, and the most prominent thing in the form. Where there are two actions, the secondary one should look secondary — two buttons of equal weight force a decision the visitor did not want to make.

On a phone, check it is reachable without awkward scrolling and large enough to press accurately; layouts reorder in the way how a phone stacks your columns describes, and a button that ends up beside a fixed element is easy to miss. Inside an embedded frame, confirm the frame is tall enough that the button is visible at all — a form that appears to have no button is usually a case of why an embedded frame clips, and placement constraints are covered in inline and popup placement.

Worth testing, unlike most micro-copy

Button wording is a rare case where a small change can produce a measurable difference, because the button is read by everyone who reaches it and it sits at the decision point. Test the outcome-describing version against the generic one the way testing a funnel step describes.

Judge it on what the form is for rather than on submissions alone. A button promising more than the form delivers will raise presses and lower the quality of what arrives, which is the same trap as any other overstatement in a funnel — and the honest version, which simply says what happens next, tends to hold up across every measurement you can take of it.

Frequently Asked Questions

What should a submit button say?

What happens when it is pressed, in the visitor’s words — ‘Send my enquiry’, ‘Get my quote’, ‘Confirm this time’. ‘Submit’ describes what the software does and tells the person nothing about the outcome, which is the only thing they want to know at that point.

Can the button promise too much?

Yes. A button reading ‘start saving money’ promises an outcome the form cannot deliver and sets up a disappointment on the page that follows. Describe what pressing it does, and nothing beyond that.

How do you prevent duplicate submissions?

Disable the button on click and change its label to something like ‘Sending…’, so the visitor knows the press registered. A button that still looks pressable while the form is working is the most common cause of duplicate records, and it is entirely preventable.

Should the button be greyed out until the form is valid?

Usually not. A disabled button hides the reason nothing is happening. Let the press occur and show a specific error next to the field that caused it, which is more useful than an inert button the visitor cannot diagnose.

What should the buttons say on a multi-step form?

Intermediate steps are not submitting anything — they should say ‘next’ or name what the next step covers. Reserve the outcome wording for the final press, so the visitor knows which button commits them, and always offer a way back.

Is button wording worth testing?

It is one of the few pieces of micro-copy that is, because everyone who reaches the form reads it and it sits at the decision point. Judge the result on what the form is for rather than on submissions alone, since an overclaiming button raises presses and lowers quality.

We build your GoHighLevel account for you

CRM, pipelines, funnels, SMS and automation — configured for your business, not left for you to figure out.

• Setup (one-time)$850
• Ongoing (per month)$38.80

Get my free setup quote

No obligation quote · reply within 1 business day

This site is independently operated and is not officially affiliated with, endorsed by, or sponsored by HighLevel LLC. We do not receive referral commissions — this is our own flat-fee implementation service.