Chosen
How to Make Contact Pages, Forms and CTAs Easier to Act On
Reduce uncertainty around clicking, completing a form and hearing back so interested visitors can take the next step.

Milan Gohil
·
7 min read
OVERVIEW
Here is a short version of what I write.
Improve contact forms and calls to action by making the next step, information requirements and response expectations clear. Test the full journey on a phone, including submission and confirmation.
Use a CTA that describes what will happen next.
Ask for information needed at the first-contact stage.
Make errors and completion feedback easy to understand.
Explain who responds and what happens after submission.
Someone can understand your business, trust what you offer and still stop at the final step. Not because the button is the wrong colour. Usually because something is still unclear:
What happens after I click?
Is this just an enquiry or am I committing to something?
Why do they need this information?
How long will they take to reply?
Am I contacting the right team?
What should I prepare before I start?
Before redesigning a CTA or shortening a form, find the uncertainty first.
Test your own contact journey in 5 minutes
Open your website on your phone. Choose the most important action and complete it yourself. Maybe:
Request a quote
Book an appointment
Contact sales
Ask for technical support
Check availability
Apply
Request a callback
At each step, ask:
Check | Question |
|---|---|
Before click | Do I know what will happen? |
After click | Did I reach what the CTA promised? |
Form | Do I understand why this information is needed? |
Submit | Do I know whether it worked? |
After submit | Do I know what happens next? |
If one of those is unclear, start there.

Your CTA, form and confirmation message solve three different problems. Treat them separately.
Want AI to review it first?
Give an AI tool access to the relevant page and paste this prompt:
Review the main contact/enquiry journey on this website:
[PASTE WEBSITE URL]
Act as a potential customer who knows nothing about the company's internal process.
Identify the most important CTA and follow the journey as far as publicly possible.
Review three stages:
1. BEFORE THE CLICK
- What does the CTA promise?
- Is the action clear?
- Does the visitor understand the level of commitment?
- What might they reasonably want to know before clicking?2. DURING THE FORM
- What information is requested?
- Which questions appear necessary at this stage?
- Which questions may need an explanation?
- Which questions could potentially be asked later?
- Are required and optional fields clear?
- Is there anything that may make someone hesitate?3. AFTER SUBMISSION
- Is it clear that the form was submitted?
- Does the user know who will respond?
- Is an expected next step explained?
- Is a response time shown if relevant?For every issue separate:
OBSERVED
What you can directly see.POSSIBLE UNCERTAINTY
What may make a visitor hesitate.NEEDS TESTING
What cannot be known without analytics or user behaviour.Do not invent conversion rates or user behaviour.
Finish with:
- 5 most important problems
- 5 practical changes
- fields worth reviewing
- CTA wording worth reviewing
- information missing before the form
- information missing after submission
Use it as a first pass. Then complete the journey yourself.
1. Make the CTA match what actually happens
Compare:
Get Started
with:
Request a Site Survey
For a commercial solar company, the second tells you much more. Or:
Submit
versus:
Request Equipment Pricing
for an industrial supplier. The more commitment involved, the more useful specificity becomes.

CTA | Visitor expects |
|---|---|
Request a quote | I am giving enough information to discuss pricing |
Book an appointment | I will choose a time |
Contact sales | I will speak with the commercial team |
Request technical support | Someone will help with an existing product/problem |
Check availability | I will learn whether the service/product/date is available |
Start application | I am beginning a longer process |
Now check the page after the click. If:
Check Availability
opens a generic “Tell us about yourself” contact form, the CTA promised something the next step did not deliver. Fix the mismatch before changing the design.
2. Explain the process before a complicated form
Imagine a construction company asks for:
Name
Company
Email
Phone
Project type
Location
Estimated value
Expected start date
Planning status
Project description
Some of those questions may genuinely be necessary. The problem is asking all of them without context. A short introduction can change the experience:
Tell us about the project. Our estimating team will review the details and confirm within two business days whether we can help and what information we need next.
Now the visitor understands why the form exists. GOV.UK's form guidance recommends knowing why every question is being asked and only collecting information genuinely needed for the service. GOV.UK: structuring forms.
3. Separate what you need now from what you need later
Do not ask:
How can we make this form as short as possible?
Ask:
What do we need to move this person to the next step?

An emergency equipment-repair company may need:
machine type
location
fault
contact number
immediately. An accounting firm might only need:
contact information
business type
service needed
before arranging a call. Different business. Different form.
4. Explain fields that are not obviously necessary
If someone requests a product brochure and the form asks:
Annual revenue
they may reasonably wonder why. If the answer is:
Sales uses it for lead qualification
that may be useful internally, but it does not automatically mean it belongs in the first interaction. Either:
explain why it is needed
make it optional
ask it later
remove it
GOV.UK's guidance similarly recommends telling users why information is being requested when that context helps them answer. GOV.UK: structuring forms.
5. Make optional information clear
Do not make people experiment with the form to discover what is required. If something is optional, say so. For example:
Phone number (optional)
Baymard's checkout research has repeatedly found confusion and validation errors when required and optional fields are unclear, although its research is specifically focused on ecommerce checkout and should not be treated as a universal rule for every short contact form. The principle is simple: Do not make the user guess what they have to provide. Baymard: required and optional checkout fields.
6. Use the contact page to route people, not just collect everyone
Imagine an industrial equipment company receives:
New Project: "I need pricing for a new installation."
Existing Customer: "Our machine has stopped."
Supplier: "I need to contact purchasing."
One generic form creates three very different conversations in the same inbox. The contact page could instead show:
New projects
Request a quote →
Existing equipment
Get technical support →
General enquiries
Contact the team → No complicated redesign. Just clearer routes.
7. Tell people what happens after they submit
Compare:
Thank you. Your message has been submitted.
with:
We've received your enquiry. Our service team normally reviews new requests within one business day. If we need more technical information, we'll contact you before preparing the next step.
The second tells the visitor:
it worked
who receives it
what will happen
roughly when
Only state response times your business can actually meet.
8. Check whether reassurance appears where people need it
Do not create one giant “Why Trust Us?” section and assume it solves everything. Different actions create different concerns.
Moment | Typical uncertainty | Useful information |
|---|---|---|
Quote request | What do I need to provide? | Required project information |
Consultation | Is this free? Who attends? | Duration, cost, purpose |
Support request | How urgent can this be? | Hours, emergency contact |
Application | What documents do I need? | Requirements before starting |
Ecommerce | What if I need to return this? | Delivery/returns/payment information |
GOV.UK's service-start guidance similarly recommends giving users important information before they begin, such as costs, approximate duration and documents they may need. GOV.UK: starting a service.
9. Measure where people actually stop
Do not assume the CTA is the problem. Suppose:
1,000 service-page visits → 220 CTA clicks → 200 form views → 150 form starts → 40 form submissions
The biggest problem appears after the form begins. Now investigate the form. Compare:
1,000 service-page visits → 30 CTA clicks → 26 form views → 22 form starts → 19 submissions
Here, people who reach the form mostly continue. The bigger question sits before the CTA. GA4 enhanced measurement can collect form_start and form_submit events for supported forms, which lets you compare users who began interacting with a form against those who submitted it. Google: enhanced measurement events.

Measure enough to find the weak point. Do not track twenty events just because you can.
Use this final check on your main enquiry journey
Question | Yes / No |
|---|---|
Does the CTA describe the real next step? | — |
Does the next page match that promise? | — |
Does the visitor know what commitment they are making? | — |
Is every requested field useful at this stage? | — |
Are unusual questions explained? | — |
Are optional fields clear? | — |
Does the visitor know what happens after submission? | — |
Is the correct contact route obvious? | — |
Does the journey work properly on mobile? | — |
Can you measure form starts and submissions? | — |
You do not need all Yes answers before launching anything. But every No gives you something more useful to investigate than:
“Maybe we need a stronger CTA.”
The goal is not to make people click harder. It is to make the next step clear enough that the right person can take it without unnecessary guessing.
Sources and further reading
All Blogs
All Blogs & Articles
© 2026 Webshunya Studio®. All rights reserved.







