DIRECT ANSWER
A website tells a business who is reaching out through three sources: self-selection, where visitors choose the situation that applies; path context, where the inquiry records the page it came from; and a few intake fields. Each field should change who responds, what they prepare or whether the business can help. The first conversation then starts at the customer's situation.
Key terms
- Self-selection
- A visitor identifying the situation or service that applies to them, by following a situation entrance or choosing an option in a form.
- Path context
- What a website already knows about an inquiry from the route the visitor took, such as the service page or entrance the inquiry came from, recorded without asking the visitor.
- Intake
- The set of questions a business asks when a visitor reaches out, designed so the first conversation starts with the facts that change the response.
- Field purpose test
- A test for each intake field: beyond the contact details needed to reply, a field stays only if its answer changes who responds, what they prepare or whether the business can help.
- Situation entrance
- A link or page that opens a customer type's pathway by naming the visitor's situation in their own words. Full entry: One Service, Several Customers: How to Build a Website That Speaks to Each One
Three ways a website learns who is reaching out
An inquiry that arrives as a name, an email address and "please call me" tells the business almost nothing. The first conversation then spends its opening minutes on questions the website could have answered or recorded. A website can tell the business who is reaching out through three sources, used together.
| Source | What it captures | How it works |
|---|---|---|
| Self-selection | The situation or service the visitor says applies to them | A situation entrance they followed, or a choice they make in the form |
| Path context | What the website already knows from the route they took | The page or service the inquiry came from, recorded automatically with the submission |
| Intake answers | The few facts that change the response | A short set of fields that each pass the field purpose test |
Self-selection and path context cost the visitor little or nothing. Intake answers cost effort, so they are kept to the fields that earn it. The choice between a plain intake form, an assessment and a calculator is covered in which tool fits. A self-assessment that gives the visitor a useful result before they share details is covered in when visitors are not ready to call.
The field purpose test
Every intake field should change something on the business's side. A field passes the test when the answer changes at least one of three things:
- Who responds. The answer routes the inquiry to the right person or team.
- What they prepare. The answer lets the business arrive at the first conversation with the right information, examples or estimate.
- Whether the business can help. The answer reveals fit, such as service area, project size or timing.
Contact details the business needs to reply, such as a name and an email address or phone number, pass by definition. Any other field that changes none of the three is moved to the first conversation or removed. A field that asks for something the website already knows, such as which service page the visitor came from, is replaced by path context. Nielsen Norman Group's guidance on reducing effort in forms supports the same discipline from the visitor's side: every optional question adds length and perceived effort, the most important questions belong first, and visitors should know before they start what the form will ask of them [1].
Building the intake
- Label every field and say what is expected. WCAG 2.2 requires labels or instructions wherever content requires input [2]. The W3C forms tutorial adds grouping related fields, giving instructions for the form as a whole and confirming success or errors clearly [5].
- Mark personal fields for autofill. Fields that collect the visitor's own details, such as name, email and phone, should identify their purpose to the browser, which WCAG 2.2 sets out as a Level AA criterion and which lets browsers fill known details automatically [3].
- Offer an "I'm not sure" option. Self-selection assumes visitors can place themselves. Visitors may fit several situations or none, and choosing a group adds effort before they reach their goal [4]. A "not sure" choice and a free-text box keep them moving.
- Record the path automatically. A hidden value or a form variant on each service page records where the inquiry started, so the visitor is not asked.
- Keep sensitive information off the form. Identification numbers, financial records, health details and legal case facts belong in a secure system built for them, reached through the handoff the website links to.
- Put the summary where it is read. The business sees the situation, the service and the key answers at the top of the notification, so the first call can open with them.
What the first conversation gains
When intake works, the first conversation starts at the customer's situation. The business already knows the service, the timing and the scope, and has prepared accordingly. The visitor is not asked to repeat what they already told the website. Inquiries that fall outside the business's service area or scope are recognized early, and both sides save time. Self-selected answers remain the visitor's own account, so the conversation still confirms them. The whole chain, from the first search to that conversation, is covered in from a search question to a better first conversation.
Applications
An IT support company for small offices
Illustrative example. An IT support company receives three kinds of inquiries: something is broken now, an office is moving, and a business wants ongoing support. The website gives each its own entrance. The "broken now" entrance leads to a phone number and response hours, since that visitor is ready to act immediately and no form helps them. The office move entrance asks for the move date, the number of workstations and the new address's city. The ongoing support entrance asks for the number of staff, the systems in use and whether a contract is ending. Each form records which entrance it came from, so the technician who calls back already knows the situation.
A commercial cleaning company
Illustrative example. A commercial cleaning company's original quote form asked for name, email, phone, company, address, how the visitor heard about the company and a message. The field purpose test kept name, email, phone and company, added facility type, approximate square footage, cleaning frequency and desired start date, and moved "how did you hear about us" to the first conversation. The service area question was replaced by the city field, which already reveals fit. The estimator now prepares a rough scope before the walkthrough is scheduled.
| Field | Who responds | What they prepare | Whether they can help | Decision |
|---|---|---|---|---|
| Facility type | Yes | Yes | Yes | Keep |
| Approximate square footage | Yes | Keep | ||
| Cleaning frequency | Yes | Keep | ||
| Desired start date | Yes | Yes | Keep | |
| City | Yes | Yes | Keep | |
| How did you hear about us? | Move to the first conversation |
Limits and edge cases
- Urgent situations. A visitor with an emergency needs a phone number. Forms serve visitors who can wait for a reply.
- Over-qualification. A long, demanding intake can turn away good customers along with poor fits. Fields that only screen out visitors are weighed against the customers they may lose.
- Self-selection errors. Visitors sometimes pick the wrong situation. The first conversation confirms it, and the intake's free-text box often reveals it sooner.
- Regulated intake. Professions with confidentiality duties, such as accountants, attorneys and medical practices, often route client intake through their own secure portals. The public website collects only high-level questions and links to the portal.
- Analytics. Recording the page an inquiry came from is part of the inquiry itself. Measuring what happens after it is covered in measuring website leads beyond clicks.
Audit your intake fields
List the fields on your inquiry form. For each, mark what it changes, whether it is required, whether the website already knows it and whether it is sensitive. The tool sorts each field by the field purpose test.
Audit your intake fields
For each field on your inquiry form, ask whether the answer changes who responds, what they prepare or whether you can help. Keep the fields that do. Move the rest to the first conversation, record what the website already knows from the page the inquiry came from, and send sensitive details to a secure portal.
The sorting follows the field purpose test in this entry. Test the finished form from start to finish, as described in testing a website contact form.
How So It Sticks applies this
We design every inquiry form with the field purpose test, plan how it records the page and situation each inquiry came from, and route sensitive details to the client's own secure systems. Start a Project Brief and send us the questions you ask on every first call.
Sources and method
The three sources, the field purpose test, the examples and the tool are So It Sticks editorial frameworks. The examples are illustrative and describe no real business. Each linked source supports only the statements numbered beside it. Sources verified October 15, 2026.
- Nielsen Norman Group: Few Guesses, More Success: 4 Principles to Reduce Cognitive Load in Forms
- W3C: Understanding Success Criterion 3.3.2, Labels or Instructions
- W3C: Understanding Success Criterion 1.3.5, Identify Input Purpose
- Nielsen Norman Group: Audience-Based Navigation: 5 Reasons to Avoid It
- W3C Web Accessibility Initiative: Forms Tutorial