Someone who recommends your business is doing you a favor.
That is why a referral form should not feel like paperwork. If a person has already decided to introduce someone they know, asking them to complete a long list of questions can turn a simple introduction into a task they may not finish.
The better approach is to make the form feel like what it really is: a bridge between two people.
You need enough information to understand who is being introduced and why the introduction might be useful. You do not need to turn the person making the referral into your sales assistant.
First, Understand What the Form Is Supposed to Do
A referral form has a fairly simple job.
Someone who knows your business wants to say, “I know someone who might need this.”
Your form should help them make that introduction.
That means the form is different from the contact form on your website. A contact form is normally completed by the person who is interested in your service. A referral form is completed by someone else, often with incomplete information.
That changes what you should ask.
If a client refers a business owner to you, for example, they may know the person's name and company but have no idea what their budget is, which service they need, or when they want to start.
Do not make the referral fail because the referrer does not know information they were never expected to know.
Start With the Smallest Useful Set of Questions
A good first version of a referral form can be surprisingly short.
You might ask:
- Who are you?
- How can we contact you?
- Who are you referring?
- How can we contact them?
- How do you know them?
- What do you think they need help with?
That may be enough.
The temptation is to add more because your business would like more information. But there is an important difference between useful information and information that would simply be nice to have.
If a field does not help you understand, process, or follow up on the referral, question whether it belongs on the first form.
W3C's Forms Tutorial notes that users generally prefer simple, short forms and recommends asking only for information required to complete the relevant process.
That is a useful principle even when accessibility is not the main reason you are designing the form.
Think About What the Referrer Knows
This is probably the most important question when deciding what to include.
What can the person making the referral realistically know?
They may know:
- The person's name
- Their email or phone number
- Their company
- Their relationship to them
- The general problem they are facing
- They may not know:
Their exact budget
- Their preferred service package
- Their timeline
- Their technical requirements
- Their complete business information
So instead of asking the referrer to qualify the lead, give them a simple way to provide context.
For example:
“What made you think they might be interested in our services?”
That question can produce much more useful information than a complicated qualification section.
Give the Form a Clear Introduction
The text above the form matters.
Someone should know what will happen before they start typing.
A simple introduction could explain:
Know someone who could benefit from our services? Share their details and tell us a little about why you think we could help.
Then add a short explanation of what happens after submission.
This is particularly useful because the person filling out the form is not necessarily the person who will become your customer.
Clear instructions also make the form feel more trustworthy.
W3C recommends providing instructions that explain required information, expected formats, and how individual form controls should be completed.
Use Plain Questions Instead of Business Language
Imagine two versions of the same field.
Lead Relationship
or
How do you know this person?
The second one is easier.
The same applies to:
Referral Context
versus:
What do you think they need help with?
Good forms do not make people translate business terminology before they can answer a question.
Use the language your customers naturally use.
If you would say “Who are you referring?” in a conversation, that can probably be the field label too.
Separate the Form Into Small Sections
A little structure can make a form much easier to scan.
You could divide it into three simple areas:
About You
Your name and email.
About the Person You're Referring
Their name, contact information, and perhaps their company.
A Little More Context
How you know them and why you think they may need help.
This is enough structure to create a comfortable reading flow without turning the form into a multi-step application.
If the form becomes significantly longer, then you can consider whether it should be split into stages. W3C's Forms Tutorial discusses grouping related controls and using multiple smaller stages when a form is long.
Make Required Fields Obvious
A person should not discover which fields are required only after clicking the submit button.
If a field is necessary, make that clear before they start.
For example:
Name *
Email *
Then provide a short explanation near the beginning of the form if needed.
Do not make every field required simply because you want complete records.
Suppose the person making the referral does not know the referred person's phone number. If your form requires it, they may stop.
A better approach might be to accept either email or phone.
The form should accommodate the reality of how referrals happen.
Do Not Rely on Placeholder Text
You might be tempted to make a field look cleaner by using placeholder text instead of a visible label.
For example:
Enter their email address
inside an empty field.
The problem is that the instruction disappears as soon as someone starts typing.
W3C specifically notes that placeholder text is not a replacement for labels and can make it harder for users to review what information a field requires.
A visible label is usually the safer choice.
You can still use placeholder text for a helpful example when appropriate, but the user should not have to remember what the field means after they start typing.
Ask for Context, Not an Essay
The open-ended field can be useful, but keep it focused.
Instead of:
Tell us everything we should know about this referral.
try:
What do you think they need help with?
The second question gives people a direction.
Someone might write:
“They are redesigning their website and asked me who I would recommend.”
That is enough context for a first conversation.
You do not need a 500-word explanation.
Make the Submit Button Specific
A button saying Submit works, but it does not tell the user much.
Depending on your brand voice, you might use:
- Send Referral
- Refer Someone
- Make an Introduction
- Send Introduction
The best choice depends on what happens next.
If the person is introducing someone to your business, Make an Introduction can feel more human than Submit.
The important thing is clarity. The button should make sense when someone looks at it without having to think about what “submit” means.
Think About the Moment After Submission
Imagine completing the form and clicking the button.
What do you see?
If the page simply says:
Thank you.
the experience feels unfinished.
A better confirmation explains what happens next.
For example:
- “Thanks for making the introduction. We’ll review the information and follow up with the person you referred.”
If your team normally contacts the referrer first, say that instead.
Do not promise something that your actual process does not guarantee.
W3C recommends clear feedback after form submission, including understandable error messages and confirmation that the task was completed.
Make the Form Comfortable on a Phone
A referral can happen anywhere.
Someone might be talking to a colleague at an event, remember your business, and open your referral page from their phone.
That means mobile usability matters.
Avoid tiny fields. Keep labels close to the fields they describe. Give the submit button enough space to tap comfortably. Make sure the form does not require unnecessary horizontal scrolling.
You do not need a complicated mobile design.
You need a form that feels natural to complete with one hand and a few minutes of attention.
Decide What Happens Inside Your Business
This part is easy to overlook because the visitor never sees it.
But what happens after submission can determine whether the referral process actually works.
Suppose three people submit referrals on Monday. Where do those referrals go?
Are they sent to one inbox? A CRM? A spreadsheet? A notification system?
Who reviews them?
Who contacts the referred person?
How do you know which customer or partner made the introduction?
These questions are not really about form design. They are about designing the referral process.
Your website form is simply the front door.
Track What Is Worth Tracking
You do not need to measure everything.
Start with a few useful questions:
- How many referrals are submitted?
- Which referral sources produce introductions?
- How many referrals become conversations?
- Which referrals eventually become customers?
- Are people abandoning the form?
If the referral form is promoted through different campaigns or channels, campaign tracking can help separate those sources. Google provides documentation for using campaign parameters to collect campaign-related data in Analytics.
But do not add complicated tracking simply because it sounds useful.
Track information that can actually influence a decision.
A Simple Referral Form Example
Here is a practical structure you could adapt:
Make an Introduction
Know someone who may benefit from our services? Share a few details and we'll take it from there.
Your Details
- Your name *
- Your email *
Their Details
- Their name *
- Their email or phone *
Company
About the Introduction
How do you know them?
What do you think they need help with?
Before You Send
- Short explanation of how the referral information will be handled
Make an Introduction
After submission:
Thanks for making the introduction. We'll review the information and follow up with the person you referred.
This is not a universal template. A referral program for a financial adviser, a wedding photographer, a software consultancy, and a local home service company may need different information.
The principle is what stays consistent: ask for enough information to move the introduction forward, and no more than that.
A Quick Test Before You Publish
Before putting the form on your website, ask someone unfamiliar with the process to complete it.
Do not explain anything while they are doing it.
Watch where they hesitate.
Do they ask what a field means?
Do they wonder whether a field is required?
Do they look confused by the wording?
Do they know what will happen after they click the button?
Those moments are useful.
A form that looks obvious to the person who created it may not be obvious to the person using it.
You can also test it yourself on a phone, submit incomplete information intentionally, enter an incorrect email address, and see whether the form gives useful feedback.
The goal is not simply to make the form work.
It is to make the experience understandable.
The Real Goal Is a Better Introduction
A referral form does not need to be clever.
It needs to make a good introduction easy.
The person referring someone should understand what you need, provide the information they actually know, and finish the process without unnecessary effort. Your team should then have enough context to understand the introduction and take the next appropriate step.
That is why the best referral form is rarely the one with the most fields. It is the one that respects both sides of the introduction.
If you are redesigning one for your own business, start with the referral journey, decide what information genuinely matters, and only then design the form around it. The interface becomes much easier once the underlying process is clear.
%20(2).webp)
.webp)
.webp)
.webp)
0 Comments