What is a call to action?
A call to action (CTA) is a prompt inviting someone to take a next step, such as reading a guide, sending a request or buying an item. The prompt may appear in a link, button or sentence. Its wording should describe the action the visitor can actually take.
Help the visitor understand the next step
Before choosing button copy, decide what the visitor needs to know or do. Opening a service description, asking about availability and confirming a booking are different steps. Make the request understandable alongside the information needed to decide whether to proceed.
Review the prompt and its destination together
Write down the immediate action, what information or commitment it requires, and what happens afterward. Then follow the route yourself: does the link open the expected information, or does the form perform the action the label describes? Check the confirmation message as well as the initial prompt.
Use the surrounding copy for details that would make the label unwieldy, such as what a request includes or whether staff must confirm availability. Keep those details consistent with the actual process. A more persuasive phrase is not useful if it describes a step the service does not provide.
Choose a label for the action available
The following constructed labels describe different possible flows for a fictional business, Maple Repair. They are editorial examples, not tested variants or a live service. Choose a label only when its action and next screen match the process being offered.
| Intended step | Illustrative label | Check before using it |
|---|---|---|
| Explore the service | Read repair options | The link opens information about the available repair work. |
| Check available times | View appointment times | Use this only if the next screen actually shows time choices. |
| Submit a request | Send repair request | The form sends the request, and the response explains any staff review. |
| Commit to a booking | Confirm appointment | Use this only when the step actually confirms the selected appointment. |
A repair request is not a confirmed appointment
Assume Maple’s form sends a preferred time to staff for review; it does not reserve that time. A button labeled “Confirm appointment” would misdescribe this fictional step. “Send repair request” describes the immediate action, with nearby copy explaining that staff must confirm availability.
After submission, the message should acknowledge receipt rather than announce a booking. Give the visitor the next instructions that this service can support. If the business later introduces direct booking, review the label, form and confirmation together so they reflect the changed process.
CTA describes the purpose; link and button describe behavior
The WAI link pattern describes a link as an interactive reference to a resource and encourages native link elements. A link to a service or booking page can carry a primary CTA, even if it is visually styled as a button.
The WAI button pattern describes buttons as triggering actions, such as submitting a form or opening a dialog. It says appearance and role should match the function. Choose the control for what it does, then make the prompt describe that behavior.
Make the purpose understandable in context
W3C’s Link Purpose (In Context) explanation says a link’s purpose can be determined from its text alone or together with programmatically determined context, except where the purpose would be ambiguous to users generally. It recommends meaningful link text and explains how associated context can help.
Read the prompt where the visitor encounters it. A short label may make sense beside a specific service description, while the same label could be unclear in a list of unrelated links. Prefer wording that identifies the actual next step; do not assume that a particular pronoun or verb guarantees an improvement.
Check operation as well as appearance
The WAI button pattern specifies activation with Space and Enter when a button has focus. The link pattern specifies Enter for a link. These documented interactions help distinguish the controls; their visual styling alone does not establish how they work.
Check the actual page with keyboard and pointer input, including whether focus is visible and the next screen is usable. Review small-screen wrapping and whether nearby information remains readable. These checks address usability; choosing the strongest color contrast does not by itself demonstrate a conversion gain.
Measure the action the prompt is meant to support
Decide whether you are evaluating a click, a submitted request or a confirmed booking. Keep the action, eligible population and reporting period with the result. The Conversion Rate guide explains why changing the denominator or action can change the meaning of a rate.
If you compare alternatives, use the A/B Testing guide to plan the comparison and interpret uncertainty. A clearer-sounding label is a proposal to evaluate, not a measured winner. Check completed actions and their quality rather than treating every additional click as a better business result.
Match service contact choices to the actual process
A service page may need to explain both how to request planned work and how to contact staff about an urgent question. Offer the routes the business can support, with accurate availability and next-step information. Do not promise an immediate answer, free quote or callback time unless the actual service provides it.
In the Maple example, keep the staff-reviewed request route distinct from a confirmed appointment. Repeating a useful prompt farther down a long page can be considered where the reader needs it, but the number and placement should follow the page’s tasks rather than a fixed quota.
Related terms
Use Landing Page for the wider offer and page structure, and Conversion Rate Optimization for the broader improvement process. The CTA review keeps the prompt, actual action and next screen connected within that work.
Sources
The W3C/WAI documents supply the link-purpose and control-pattern guidance. The Maple flow and labels are constructed illustrations, not observed customer behavior or a conversion experiment. Review the implemented page separately; this glossary explanation does not certify its accessibility.