You have traffic but no inquiries: ten places where contacts disappear

Traffic is growing, but the number of inquiries is standing still. A single failure is rarely to blame. Usually, it is a series of small leaks spread across the entire journey—from the moment someone looks for a way to get in touch to the moment someone at the company should respond.

Below are the ten places where contacts disappear most often. We cover each in three steps: the symptom, a quick test, and a direction for fixing it. You will not find a research methodology or rules for prioritizing hypotheses here—we describe that structured process separately in our article on website conversion audits. This article focuses solely on specific drop-off points.

1. Before you begin: check whether you measure contacts at all

Before deciding that your website generates no inquiries, make sure every inquiry leaves a trace. Untracked form submissions, chat conversations counted from an operator's memory, and callback requests recorded in an email inbox create a picture that is worse than reality. The company then optimizes a problem it does not have while overlooking the one it does.

• A form submission records a business goal, not merely a reload of the thank-you page.
• Started chat conversations are counted separately from completed conversations.
• Callback requests have their own counter instead of falling into a general ‘contact’ bucket.
• Messages sent outside business hours become numbered tickets instead of landing in a private inbox.
• You know how many inquiries arrived last week without asking anyone on the team.

If any of these conditions is not met, start there. It is worth measuring not only the contact itself but also the steps leading up to it—a click on the phone number, opening the chat window, or reaching the form. We explain how to select such signals in our article on website micro-conversions.

2. Drop-off points before contact

The first group of leaks affects people who never touched the form or chat window. They did not abandon anything—they simply could not find a way to get in touch or did not receive the information they needed for contacting you to make sense.

↔ Scroll the table sideways to see all columns.

This is where teams most often misdiagnose the cause. They assume the visitor does not want to talk when, in reality, the visitor cannot see the channel or does not know whether anyone is on the other side. We cover channel selection and placement in our guide to accessible contact paths, and the lack of cost information in our article on pricing pages.

Treat phones separately. The same layout can work on a desktop and fall apart completely at 360 pixels wide—form fields slip under the keyboard, the button ends up beyond thumb reach, and the consent banner covers the contact option. We collected the common pitfalls in our article on mobile conversion.

When designing a return path from an error page, use the guide: 404 page: help customers return to the interrupted task.

3. Drop-off points during contact

The second group concerns people who had already started. Someone opened a form, clicked the chat, or selected a callback time—and stopped. This is the costliest group because their intent had already been confirmed, yet the company still came away from the interaction empty-handed.

• A form longer than the decisionSymptom: many opens, few submissions. Test: count the fields and ask which ones genuinely affect the first response. Fix: keep only what you need to call back and ask for the rest during the conversation.
• Required fields without a reasonSymptom: abandonment always occurs at the same field, usually the tax ID, company name, or budget. Test: complete the form without this information. Fix: make fields optional wherever the data can be added later.
• A validation error with no guidanceSymptom: repeated clicks on the submit button in session recordings. Test: enter a phone number with spaces and see what happens. Fix: show a specific message beside the field and do not clear the entire form.
• A prompt at the wrong momentSymptom: the chat window opens in the first second and is closed immediately. Test: arrive from an ad and measure how long reading takes before the message appears. Fix: trigger the prompt based on behavior, not time alone.

A prompt sent too early costs you twice: it fails to start a conversation and teaches the visitor to close the window before reading it. We expand on field selection, microcopy, and post-submission states in our article on website contact forms.

4. Drop-off points after contact

The third group is the most painful and the least frequently checked. The customer did everything asked of them: they wrote, left their number, and described the issue. The inquiry physically exists—nobody has picked it up. In website statistics, it is a conversion. For the company, it is a more expensive loss than any before it because the full cost of acquiring that traffic has already been paid.

↔ Scroll the table sideways to see all columns.

A number, status, and assignee are not administrative extras—they are the only way to stop an inquiry from depending on someone's memory. We explain how to organize such a workflow in our article on customer service ticketing systems, and how to measure response itself in our guide to first response time.

The most common cause of this leak is a missed notification. We explain how to configure notifications so they interrupt work only when necessary in our article on customer service notifications. It is just as easy to miss an inquiry stuck in a filter or buried among sales offers in the inbox, as our guide to contact form spam explains.

5. The fifteen-minute ‘walk your own journey’ test

You can detect most of these leaks in one afternoon without analytics tools. There is one condition: walk the journey like a stranger, not the person who created the website. Do it in a private window, on a phone, and outside business hours, because that is when you will see the most.

1. Arrive from a search engine on an inner page, not the homepage.Check whether you can start a conversation from that page without returning to the menu.
2. Look for pricing and availability hours.Give yourself two minutes. If you cannot find them, neither will the customer.
3. Send a real inquiry from your phone.Complete the form one-handed with the on-screen keyboard open. Notice what covers the button.
4. Try submitting the form with an error.Enter a phone number with spaces and skip one field. Check whether the message points to the right place and whether your data remains.
5. Write in the chat outside business hours.See whether you are told when to expect a response and whether the message becomes a ticket.
6. Wait a day and count what came back.Check every inquiry you sent: did it reach the system, does it have an owner, and when did the first response arrive?

Record the results of this test as observations, not judgments. ‘The mobile form requires seven fields, and the submit button disappears under the keyboard’ is an observation you can fix. ‘The form is bad’ does not lead to any change.

If this walkthrough leaves you with a list longer than five items, that is good news: the leaks are specific, and most are a matter of configuration rather than rebuilding the website.

6. What to fix first

Order matters because not all leaks cost the same. First, close the ones where the customer has already done their part—an ownerless inquiry or a response after two days. Only then return to channel visibility and form length.

1. Lost after contact.A numbered ticket with a status and assignee, plus confirmation for the customer. The highest return at the lowest cost of change.
2. Lost during contact.A shorter form, fewer required fields, and a clear validation error. Changes you can make without rebuilding the website.
3. Lost before contact.Channel visibility on key pages, availability hours, and an indication of the rough price range.
4. Everything else.Prompt timing, mobile layout, and copy. Return to these once the earlier layers no longer leak.

Fix one thing at a time and give it two weeks. If you improve four elements in one release, you will not know which one worked—and the next time results fall, you will be guessing again.

Inquiries rarely disappear because the offer is weak. They usually disappear because, at several points, the path to a conversation was one step longer than the customer was prepared to take. That is good news—you can identify those places precisely and close them one by one.