Is Your Website Turning Away the Right People?

Are You Accidentally Disqualifying Your Own Customers?

Imagine discovering a leak in your ceiling. You find a home repair company that looks promising, but before you can request help, its website asks whether you need plumbing repair, roof repair, or water damage restoration. How should you know? You're contacting a professional precisely because you don't know what's wrong.

The company might handle your exact problem, yet its website expects you to understand the business before the business can understand you. Maybe you guess, research the problem yourself, or try another company. Either way, a perfectly suitable customer could slip away without the business knowing why.

This happens in less obvious ways across all kinds of organizations. A prospective student might assume they don't qualify for a program. Someone seeking assistance may not recognize which service applies to their situation. A potential customer might postpone contacting a business because they don't have the information its form requires.

Your website could be unintentionally screening out people you actually want to reach. When understanding your internal terminology and processes becomes a prerequisite for getting help, you risk mistaking someone's lack of familiarity for a lack of fit.

What Your Team Knows Without Reading the Page

You open your website and everything makes sense. You know your services, how your organization makes decisions and what happens when a situation does not fit the usual process.

You may know that a consultation is an informal conversation, that a quoted timeline assumes materials are ready, or that someone can ask for help choosing between services. Those facts shape how you interpret the website, even when none of them is written down.

A visitor could reach a different conclusion. They may think a consultation requires preparation or that selecting the wrong service will send their request to the wrong place. You cannot assume they will recognize an invitation you have left implicit.

You can also distinguish between two similar offerings because you understand the problems each addresses. A newcomer may see two descriptions of essentially the same thing, with little indication of which one applies to their situation.

Your team fills in the missing context without realizing it. Visitors are left to make their own assumptions, and those assumptions can influence whether they decide to approach you at all

Don't Make Visitors Diagnose Their Own Problems

Think back to that ceiling leak. To the home repair company, roofing, plumbing, and restoration are distinct services. To the homeowner, they're three possible explanations for the same wet ceiling. The company's service categories make perfect sense internally while offering little help to someone figuring out where to start.

People often arrive knowing what they want to accomplish, but not the terminology your team uses to describe the solution. Asking them to choose immediately makes them responsible for diagnosing a problem they came to you to discuss.

Help visitors connect their circumstances to your offerings. Describe what someone might be experiencing, what each service addresses, and what it can help them accomplish. A home repair company could offer a starting point for people dealing with an unexplained leak, then help direct them toward the appropriate service.

The same principle applies elsewhere. Someone looking to advance their career might not know whether a short course, professional certificate, or degree program best fits their goals. Explaining what each option involves and who it serves makes that distinction easier.

Once someone understands the distinction, the service name becomes useful. They can compare options and have a more productive conversation with your team. If they're still unsure, give them a way to ask for guidance without choosing a service first.

Ready to Get Started? Define “Ready.”

Even after finding a relevant offering, someone may doubt whether they're qualified or prepared enough to pursue it. Unclear requirements can make the first step feel like an assessment.

Consider a professional development program requiring "relevant work experience." Someone with years of volunteer leadership or community project experience might assume they don't qualify because they lack a traditional professional background. If the program accepts those experiences, a suitable applicant could rule themselves out before ever asking.

Good qualification works in both directions. It helps people recognize when an opportunity suits them and when it doesn't. If volunteer experience counts, explain how it's evaluated. If specific credentials are required, make those expectations equally clear.

Preparation presents a similar challenge. To your team, requesting a project brief might simply mean asking someone to describe their goals. To a prospective client, it could sound like they need a fully defined scope before the first conversation. If you can begin with a description of the problem, say so. When formal preparation is required, explain what's needed and why.

You can explain a process accurately and still leave someone unable to picture their part in it. Terms such as discovery, assessment, and onboarding don't necessarily explain what they'll be doing. A short preview of the first meeting, what to bring, any fees, and what happens afterward can help people understand what they're agreeing to.

These details also shape how welcome someone feels. As I explored in Why Most Digital Experiences Feel Technically Correct and Emotionally Empty, an experience can function correctly while still leaving people feeling out of place. Clear expectations and an opportunity to ask questions can do more than another generic promise about being welcoming.

Your Contact Form Isn't an Entrance Exam

Your contact form is often where hidden assumptions become unavoidable. Someone could skim past an unfamiliar term on a page, but a required field now demands an answer.

Our homeowner finally reaches the booking form, only to find a question asking them to identify the source of the leak. Plumbing? Roofing? Something else? We're right back where we started, except now the website won't let them continue without guessing.

A more useful question might be "Where have you noticed water, and when did it start?" The homeowner can answer based on what they've observed, and the company gets information that may help determine the next step. You're collecting useful information without asking the customer to diagnose the problem.

Here's a useful test for your own forms: Can visitors answer each question based on what they know about their situation, or do they need to understand how your organization works?

Ask why each field is needed at this stage. Some information may be necessary to route an inquiry, confirm eligibility, or determine whether a request is within your scope. Other details can wait until someone explains their situation.

The goal isn't necessarily to get more inquiries. It's to get better ones. Asking about someone's circumstances can help determine whether they're a good fit, while requiring them to understand your service categories may simply discourage someone you could help.

You can still collect meaningful information without demanding answers visitors don't have. Someone who hasn't chosen a service can describe what's happening. Someone with an approximate deadline can explain what's driving it. Where your process allows, an "I'm not sure yet" option can be more useful than forcing a guess. That gives your team useful context without requiring false precision.

Finally, make sure the person answering the inquiry receives that context. If visitors explain what they know and where they need help, your team's response should acknowledge it. The care you put into the form should continue into the conversation.

Make Room for Beginners and Experts

You may worry that additional explanations will slow down experienced visitors. That's a reasonable concern, especially when your website serves people with different levels of familiarity.

More explanation doesn't have to mean more reading for everyone. Keep the main answer easy to scan, place brief explanations where someone first needs them, and offer more detail through descriptive links or supporting sections.

For example, a program might offer a "prior learning assessment" as part of its admissions process. Someone familiar with the term recognizes it immediately. A brief explanation that previous coursework or experience may count toward program requirements helps someone else understand why it's worth exploring.

Keep professional terminology when precision matters. Introduce it with enough context that people outside your field can understand its relevance without slowing down those who already know the subject.

Where you place that explanation matters, too. In Your Website Isn't a Funnel. It's a City., I explored how visitors arrive through different routes rather than following a single planned journey. Someone might land directly on a service page from search without reading the introduction elsewhere. Keep essential explanations close to the decisions they support.

Be selective. A page overloaded with definitions can make important information harder to find. Focus on terms and assumptions that affect a choice, a requirement, or the next step.