Machina

Machina — Marketing that moves numbers.

Reach out today

Industries

One growth engine.

Design, advertising, development, and marketing built for the sectors driving what comes next — AI, fintech, health tech, and beyond.

All industries

Machina — Marketing that moves numbers.

Reach out today
Technology

Why visitors leave before they call or ask for a quote

A service page can get visits all week while the phone stays quiet. More traffic sends people through the same missing answer, broken call button or lost quote request. We follow the path on a phone, repair the first break we can reproduce, and judge the change by qualified inquiries.

Francisco Contreras

Francisco Contreras · Founder, Machina

5 min read

A dotted cream path passes through a gap opened in a split vermilion block, while a few short strands peel away before reaching it, on a black background.

Where does the visitor first lose the path?

We let the first broken step decide the repair. A failed quote link needs a working destination. A page that never says which towns you serve needs that answer near the request. We check those basics before changing the design or buying more visits.

Choose a page that prospective buyers reach from search, a listing, an ad or a shared link. Open it on your phone as if you had never seen the homepage. Can you tell what the company does, whether it serves you, and what happens when you ask for a quote? Tap the action. Note the first place you have to guess, wait or give up.

The customer’s task decides what we check. A restaurant visitor may need today’s hours and a way to call before driving over. A contractor’s prospect may need the service area and a place to describe the job. We put those details where the visitor needs them, then check the call or request that follows.

Walk the mobile path before proposing a redesign

Follow the page through to contact. Tap the phone number and check the number it opens. Send a test quote request with a recognizable name or email. Look for the success message, then ask the team whether the request arrived with enough detail to answer it. Record the page address, phone and failed step so someone else can repeat the check after a repair.

When we rebuilt Portobello’s On Main, the Eat, Drink and Visit links on the former site led to missing pages, and the menu page opened a banquet PDF. The home page showed a phone number and address beneath the headline, but there was no contact page or page with opening hours. We kept the familiar headline, made breakfast and lunch searchable on the page, added written and mapped directions, and put a call button in every page header. The home page also gained Call and Get directions buttons beneath the headline.

A guest could now find the menu, the hours and the door from a phone. That is the kind of path we check before proposing work across the rest of a site.

We also check whether someone can hit the call button with a thumb without opening the menu by mistake. W3C’s accessibility guidance sets minimum size or spacing for tap targets. Give the call control enough room and try it on the phone in your hand.

What does each failed step tell you?

Use the first failed step to decide what to inspect next. This field sheet pairs a visible problem with a check you can run on your phone or with your team.

Mobile inquiry-path field sheet
What you observeWhat to check nextFirst repair to consider
Visitors reach the page, but cannot tell what you offer or where you work.Ask a new reader what the page offers and whether you serve their area.Put the service area and next step near the call or quote button.
The page explains the offer, but the call or quote button is missing or fails.Tap the phone link and submit a test request on the same phone and page.Make the button work and check where it sends people.
The form starts but does not finish.Try every required field, error message and return step with realistic answers.Remove an unnecessary question or fix the step that blocks completion.
The site records a submission, but the team cannot find it.Match a named test request to the receiving inbox or sales record.Make sure the request reaches the right person, then repeat the test.

Machina diagnostic worksheet. Each row describes a possible finding and a check to run.

Form trouble deserves its own check. In Baymard’s insurance quote-flow testing, some participants encountered field and navigation problems severe enough to abandon the process. We run a realistic request through the form on a phone. We choose an option, enter an unusual but valid answer, correct a mistake, go back and submit. If a step traps us, we record it before trusting the form’s completion count.

If the page or form takes too long to become usable, use our website-speed guide to choose the exact page and delay worth repairing. If a test request appears to send but never arrives, we make sure it reaches the team before changing the page.

Which action should the test count?

We choose the measure before editing the page. A call-button tap shows that someone tried to dial. We ask the team which connected calls became conversations. A form start shows interest, while a confirmed submission tells us the request was sent. The team then checks whether that person is reachable and needs a service it offers.

For forms, we count a successful send once and check that the request reached the team. Google Analytics’ key-event tutorial uses a confirmation page as its example and warns against marking every page view as a key event. If the form has no confirmation page, we verify its successful-send signal. A button click alone leaves delivery unanswered.

For a baseline, we record the page, whether visitors used a phone or computer, where they came from, completed requests and inquiries the team accepts. We note repeat requests and addresses outside the service area. When calls matter, we look for connected calls that became relevant conversations.

How do you know the repair worked?

We fix a broken link or lost request as soon as we confirm it. Then we tap the repaired link and send a named test request to make sure it reaches the right person. A choice such as a shorter form calls for a split test when enough visitors use the page.

For a quieter page, we ask someone new to try the task on a phone and compare similar periods before and after the change. We treat that comparison as a clue. Traffic, season or the offer may also have changed.

For a split test, we agree on the audience, duration and meaning of a qualified inquiry before starting. We also need to connect each inquiry to the version that person saw. We randomly show visitors either the current page or the new one and keep each person on that version. For each version, we divide visitors who make a qualified inquiry by all visitors who saw it, including those who never started the form. We count each person once and leave staff checks out. If the difference is unclear, we keep investigating.

Our conversion work starts with the page and the request a buyer should be able to send. We find the break and choose a repair the team can check. If you want help with that decision, reach out to Machina with the page address, the request you want buyers to make, and the step that worries you.

Next steps

Let's talk about your project

Tell us what you're working on. We'll tell you if we can help — and exactly what we'd do.

We use cookies and analytics to understand how visitors use our site and improve your experience. Privacy Policy · Do Not Sell or Share My Personal Information