In short
A call to action should say what happens when it is clicked, in the reader's terms, and reduce the perceived commitment where that is honest. Name the outcome rather than the mechanism — 'Book a 20-minute call' rather than 'Submit' — and offer one action per page, repeated, rather than several competing ones.
Say what happens next
The single most common failure is a button that describes the mechanism rather than the outcome.
"Submit" describes what the form does. "Send" describes what the browser does. Neither tells the reader what they get.
Name the outcome: Book a call. Get the checklist. Start the trial. See the pricing.
This matters because clicking is a small act of trust. Someone hesitating at a button is asking what happens — and if the button does not answer, hesitation is a reasonable response.
Reduce the perceived commitment
People overestimate what a click will cost them. They imagine a long form, a salesperson, an obligation.
So where it is honest, say what it does not involve:
Book a 20-minute call is more specific and less alarming than Get in touch. Start free — no card required removes the assumption that it will ask for payment. See pricing promises information rather than a conversation.
This has to be true. A button promising twenty minutes that produces a sales sequence is worse than a vague one, because it converts a click into resentment.
One action, repeated
A page should ask for one thing.
Offering book a call, or download the guide, or subscribe converts worse than any one of them alone, because choosing between options is harder than deciding to act. Every additional option adds a decision at the moment you want momentum.
But repeat the one action as the page progresses — after the offer, after the proof, at the end. People reach readiness at different points, and making someone scroll back to act loses a proportion of them.
A secondary action is fine when it is genuinely secondary and visually subordinate: a quiet text link beside a prominent button, not two buttons of equal weight.
Write in the reader's terms
First-person phrasing sometimes tests well — Start my trial rather than Start your trial — but the effect is small and inconsistent, and it is not the lever people hope.
What reliably matters is whether the words match how the reader thinks about the task. Someone comparing prices wants See pricing, not Explore our solutions. Someone ready to talk wants Book a call, not Begin your journey.
Use the vocabulary from your own enquiries and search queries. It is already the right register.
Phrases that quietly lose clicks
"Learn more." Ubiquitous and empty. Learn what? It is the default when nobody decided what the link is for.
"Click here." Meaningless out of context, and unusable for anyone navigating by a list of links — which is a genuine accessibility problem as well as a copy one.
"Submit." Describes the form's job, not the reader's outcome.
"Get started." Slightly better, still vague. Started with what?
"Contact us." Feels like work. Naming the specific action — book, ask, request a quote — is more concrete and less effortful.
Placement and appearance
Put the action where the decision happens, which is usually after the argument for it — not exclusively at the top before anyone knows what you do.
Make it look interactive. A button should read as a button: sufficient size, sufficient contrast, an obvious hover and focus state, and a target large enough to tap comfortably.
And give it room. A button crowded by text is harder to see and harder to hit.
Supporting text does the reassuring
A short line under the button removes the remaining objection without lengthening the label.
No card required. Takes 2 minutes. We reply within one working day. Cancel anytime.
That placement works because the doubt occurs at the button — putting the reassurance anywhere else means it is read too early or not at all.
After the click
The call to action includes what happens next, and this is where the promise is kept or broken.
If the button said twenty minutes, the next screen should confirm twenty minutes. If it said no card required, no card should be requested. A mismatch between the button and the page it leads to is the fastest way to lose someone who had already decided.
The test
Read each button label on its own, out of context. Can you tell what happens? If not, neither can the reader — and they are not going to read the surrounding paragraph to work it out.
If you have a page with traffic that is not converting, the button copy is worth checking before anything structural — book a call.
Common questions
What should a call to action button say?
What happens when it is clicked, in the reader's terms — 'Book a 20-minute call' rather than 'Submit' or 'Get in touch'. Submit describes what the form does; the reader wants to know what they get. Naming the outcome removes the hesitation that vagueness creates.
How many calls to action should a page have?
One action, repeated at several points as the page progresses. Offering several different actions converts worse than any one alone, because choosing between options is harder than deciding to act. A secondary option is acceptable only if it is visually subordinate.
Why is 'Learn more' a weak call to action?
Because it says nothing about what the reader gets, and it is usually the default when nobody decided what the link is for. 'Click here' is worse still, since it is meaningless out of context and unusable for anyone navigating by a list of links.
Does first-person button copy work better?
Sometimes, but the effect is small and inconsistent, and it is not the lever people hope for. What reliably matters is whether the words match how the reader thinks about the task — use the vocabulary from your own enquiries and search queries.
Should you add text under a call to action button?
A short reassurance often helps — no card required, takes two minutes, we reply within one working day. Placing it at the button works because that is where the doubt occurs; the same words elsewhere are read too early or not at all. It must also be true on the next screen.
