Picture the person reading your website on a phone. They are on a train, one hand holding a rail. Or they are on the sofa with the television on. Or they are standing in their own kitchen looking at the thing that broke. They have maybe ninety seconds of attention and one thumb.
Now look at your enquiry form on that phone. Eight fields, a dropdown that opens a tiny scroll wheel, a message box that hides behind the keyboard, and a submit button below the fold. Almost nobody fills that in on a train.
Mobile website enquiries are rarely lost because the visitor was not interested. They are lost because the effort of enquiring on a small screen is higher than the effort of thinking "I'll do this later". And later tends not to happen.
Test it the way your visitors use it
Before changing anything, borrow a phone that is not yours (so nothing is saved or autofilled) and try to enquire on your own site, one-handed, standing up.
Note every moment you had to zoom, scroll back, retype or hunt for a button. Then try asking a question in your chat widget the same way. Do it on your busiest service page, not just the home page. Most owners who do this find at least one problem they had never seen in the desktop preview.
What makes mobile chat easier than a form
A conversation has one big structural advantage on a phone: it asks for one thing at a time. That makes it a natural fit for mobile lead capture, if you set it up with the small screen in mind.
- Short answers first. The direct answer goes in the opening sentence. Detail comes after, or only if the visitor asks for more.
- Suggested prompts. Tappable questions like "Prices" or "Do you cover my area?" save typing and get people started.
- One field per message. Ask for a name, then later an email or phone number, instead of presenting a mini form inside the chat.
- Answers before details. Help the visitor first. People give contact details far more readily once they have got something useful.
- Accept rough input. Postcodes without spaces, phone numbers with or without a country code, lowercase names. Do not make people correct their typing.
- Room to leave. A clear close button and a window that does not trap the page. Nothing annoys mobile users faster than a box they cannot get rid of.
Long answers versus phone-sized answers
The same content can feel very different on a small screen. This is an invented example for a physiotherapy clinic.
| Desktop-style answer | Phone-sized answer | |
|---|---|---|
| Question | "How much is a first appointment?" | "How much is a first appointment?" |
| Answer | A paragraph explaining the clinic's philosophy, the assessment process, the qualifications of the team, parking, then the price at the end | "A first assessment is 45 minutes and costs a fixed fee shown on our prices page. Want me to take a booking request?" |
| What the visitor has to do | Scroll through four screens to find the number | Read two lines and tap yes |
The longer answer is not wrong. It is just in the wrong place. Put the background on the page for people who want it, and let the assistant give the short version. You can shape this through your Q&A pairs and the persona instructions, telling the assistant to keep replies brief and lead with the answer.
As always for health services, the assistant should share practical information like fees and opening times, not clinical advice.
Asking for contact details on a small screen
This is where most mobile enquiries die. The fix is mostly restraint.
Only ask for what you will use. If you always follow up by phone, you probably do not need an email address and a phone number and a postal address at the first contact. One reliable way to reach them, plus a name, is often enough.
Explain why you want it, in plain words. "What's the best number to call you on about the quote?" works better than "Please provide your phone number."
Here is a mobile-friendly exchange for a garden landscaping firm:
Visitor: do u do small gardens, mine is tiny
Assistant: Yes, small gardens are a big part of our work. Roughly how big is the space, and is it mainly paving, lawn or a mix?
Visitor: about 5 x 6 m, just grass and a broken patio
Assistant: That is a common job for us. A designer would need to see it to quote properly. What's your first name, and a mobile number we can text to arrange a visit?
Four short messages, a qualifying question, and a clear reason for asking. More on phrasing lives in asking for contact details politely.
Greetings and pop-ups on phones
Screen space on a phone is precious, and anything that covers the content feels aggressive. A large pop-up the moment the page loads is a quick way to lose someone.
If you use a proactive greeting, keep it small, delay it until the visitor has scrolled or spent some time, and never let it cover the main heading or the call button. Exit-intent tricks were designed around desktop mouse movement and are less reliable on phones, so do not build your mobile plan around them.
Some businesses find a visible, compact launcher button is enough on mobile, with no automatic greeting at all. Try both and read what happens in the transcripts.
Forms still have a place
Chat is not the only answer. If your visitors already know exactly what they want, for example a callback about a specific product, a very short form can be quicker than a conversation. The trick is keeping it short: three fields, large tap targets, the right keyboard for each field, and a button that is visible without scrolling. The forms page shows how forms and chat can sit side by side.
What matters is offering one easy route, not five competing ones stacked down the page.
Do this on your phone today
Run the one-handed test on your top two pages and write down every snag. Cut your contact form to the fields you really use. Rewrite your five most common answers so the key fact sits in the first sentence. Add three or four suggested prompts that match what mobile visitors ask.
Then try the live demo on your own phone to feel how a short, conversational flow compares with what you have now. Check your mobile enquiries again after a month.