Your Website Gets Visitors. Why Does Nobody Contact You?

She found your website. She still doesn’t know if you can help.

Imagine Mara wants to keep a favorite armchair, but its fabric is worn. She finds a local upholstery business on her phone. The photographs look lovely. The heading says “Beautiful interiors, thoughtfully renewed.” There is a button marked “Begin your transformation.” She pauses. Does this shop recover a single chair, or only furnish whole houses?

Mara is a fictional customer, but her uncertainty gives us a useful design exercise. Before she asks for a quote, she wants to know whether the business takes her kind of job, whether getting the chair there is practical, and what she would be agreeing to by making contact. A polished page can leave all three questions unanswered.

A clearer opening might say: “Reupholstery for chairs and sofas in the Verde Valley.” A short explanation can name the work the shop accepts and link to its actual service area. Nielsen Norman Group recommends explaining what a company does in concise language and using descriptive labels for the actions available. That is a useful starting point for this fictional rewrite, not evidence of a guaranteed increase in inquiries. [1] (opens in a new tab)

There is another possibility: Mara reached a fabric-care article while looking for a do-it-yourself fix. She might be a useful future reader without being a prospective customer today. Look at the page people enter and the question that brought them there before treating every quiet visit as a lost sale. A small number of visits also gives you very little evidence to diagnose.

Show her the decision behind the pretty photograph

Suppose the gallery shows finished furniture but says nothing about the jobs. Mara cannot tell whether a similar chair needed new fabric, new padding or a repaired frame. Add a short, accurate account beside a real project: what the customer wanted, what work was done, and which parts of the job affected the quote. Use photographs you own or have permission to publish. A generated image can illustrate an idea, but it cannot stand in for completed customer work.

An exact price may be impossible before inspection. The page can still explain the main price drivers, what a preliminary estimate includes, and when a firm quote is provided. If you publish a starting price or range, use actual current business information and explain its conditions. An attractive invented number creates the wrong expectation.

Practical details matter just as much. Does Mara bring the chair in? Is collection offered in her area? Can she keep using it until a workshop slot is available? Say what the real process is, including any limits, rather than making a promise the team cannot keep.

This principle applies beyond repairs. The Les Clés Sedona portfolio project brings property photography, amenities and practical details together with a direct inquiry route. It illustrates how information can support a decision before contact. The project description does not establish a measured increase in bookings, and none is claimed here.

Let the first message be a first message

Mara reaches the inquiry form. It asks for a full address, exact dimensions, fabric choice, budget and preferred collection date. She has not chosen fabric and does not know whether collection is available. Instead of guessing, she leaves. The business has asked her to complete the project brief before helping her understand the project.

For this fictional shop, a first inquiry could ask how to reply, what item needs attention and the customer’s town if that determines service eligibility. Dimensions or photographs might be useful later, or optional now. If an image upload is offered, explain what picture helps, accepted file limits and an alternative for someone who cannot upload. A delivery address can wait until the business actually needs it.

GOV.UK’s form-design guidance suggests documenting why each question is needed and how the answer will be used. Apply that test to your own intake: if nobody uses a required answer to decide or respond at this stage, reconsider requiring it. This is a design method, not a rule that every business form must have the same number of fields. [2] (opens in a new tab)

The words around the button are part of the offer. “Ask about my chair” tells Mara what she is starting. “We’ll email you within two working days to discuss suitability and the next step” tells her what follows—if that is a promise the shop can honor. Explain whether the inquiry is free and whether it commits her to anything, based on the actual process.

Offer a second contact route if it fits how the team works. An email link can suit someone who already has photos ready; a phone number can suit someone who wants a conversation. Keep the main action easy to distinguish. An unattended chat window is another promise to maintain, so adding one should be a staffing decision as well as a design decision.

Make sure the conversation can actually begin

Now imagine Mara tries again with larger text or without using a mouse. She should still be able to identify each field and reach the action. W3C’s forms guidance explains how meaningful labels, associated with their controls, help people understand and operate a form. A disappearing placeholder should not be the only explanation your customer gets. [3] (opens in a new tab)

If she mistypes an email address, the page should explain what needs correction. If the request succeeds, it should clearly say so. W3C recommends concise feedback for both errors and successful submissions. The business must make that confirmation truthful: a button animation by itself is not proof that the request reached a system someone checks. [4] (opens in a new tab)

Arrange a clearly labeled internal test on your own site. Follow the same page and contact route a customer would use, check the confirmation, and verify receipt with the person responsible for responding. Also try an incomplete field and make sure the recovery is understandable. Test on a phone, with a keyboard and with enlarged text. These practical checks can find barriers; they are not accessibility certification.

Watch the ordinary experience too. Does a large photograph delay the useful text? Does a pop-up cover the action? Does an embedded calendar require a login the page never mentioned? Record the specific obstacle you observe. “The address field blocks the first inquiry” is a repairable finding; “the website needs to be more modern” is too vague to guide the work.

Judge the change by the conversations it creates

A useful measurement plan separates attempts from outcomes. Google Analytics documents form_start and form_submit events for form interactions. Those can help describe a path, but a recorded submission does not tell you whether the request is suitable, a person answered it or a job was booked. Check that the tracking behaves correctly on your particular form and compare it with the business’s received requests. [5] (opens in a new tab)

Keep a simple private record of suitable inquiries, replies and eventual bookings. Record the date of a page change and what you expected it to improve. Compare similar time periods and traffic sources, and allow for seasonality, campaigns and small samples. A rise after an edit is a reason to investigate, not proof that the edit caused it. Analytics consent choices and blocking can also leave gaps, so do not force your inbox total to match an analytics total.

Keep customer names, email addresses, messages and photographs out of analytics events and page URLs sent to Google. Google’s Analytics guidance prohibits sending information it can recognize as personally identifiable. The details needed to answer a request belong in the business’s appropriately protected inquiry system, with access and retention planned for that purpose. [6] (opens in a new tab)

Start with one observed hesitation. Ask a few people who resemble your customers to try a realistic task, without coaching them through it. For the fictional shop: “You want this chair recovered. Find out whether the business can help and how you would ask.” Write down the unanswered questions. This is a proposed exercise for you to run; no user study was conducted for this article.

Then choose the smallest useful change. Better wording and a relevant project explanation may fit your current website. Repairing a form, handling uploads or connecting a booking service takes implementation and testing. A larger rebuild makes sense when the existing setup prevents the experience you need. The scope should include who updates the information and checks the contact route after launch.

The aim is to let a suitable customer make an informed choice and start a manageable conversation. For Mara, that begins with knowing someone will look at her chair—not with committing to a transformation. If that sounds like your website, bring the page and the customer’s unanswered question to a design conversation.