A chatbot on a phone is a different product

Most people who talk to a website chatbot are holding a phone, standing up, with one hand. Everything that is comfortable on a desktop - a long answer, a six-field form, a table - is uncomfortable there. This guide is the list of things that change, and what to do about each.

Answers get shorter, or they do not get read

Two or three sentences fills a phone screen. A paragraph that reads well on a monitor arrives as a wall that has to be scrolled past, and the visitor skips to the end. Write the knowledge in short, complete statements rather than prose, and put the thing the visitor asked for in the first sentence rather than after the context. If an answer genuinely needs five points, write it as five short lines, which render as a list.

The form is the moment you lose people

Typing an e-mail address on a phone keyboard is the single highest-friction act in the whole conversation. Three consequences:

• Ask for the minimum. One contact method is enough to call somebody back. Allinaa's inquiry form needs one, not both, plus the consent.
• Pre-fill from the conversation. If the visitor has already said their name and what they need, those fields should arrive filled in and editable, so the form is a confirmation rather than an interview.
• Do not ask twice. Nothing already answered in the chat should reappear as an empty field.

See capturing contacts and inquiries.

One question at a time, really one

On a desktop a three-part question is answerable. On a phone it produces an answer to the last part only. An assistant that asks one short question per turn, and only the ones still missing, gets three answers where a form gets none.

The phone is the reason uploads matter

A phone has a camera, which makes it better than a desktop for the things businesses actually need: a photo of the model plate, the leaking joint, the room, the damage, the rash on a pet, the broken part. On Premium a visitor can send photos and documents, which are checked for viruses and stored privately against the enquiry. In several trades a single photograph replaces a paragraph of description and a second visit. See files customers send.

The keyboard eats half the screen

When the keyboard opens, the visible chat area halves. That is why a long answer immediately above the input box is worse than it looks, and why a widget that does not handle the keyboard well leaves the input hidden behind it. Test it yourself: open the chat on a real phone, tap the input, type, and see whether you can still read what you are replying to.

The bottom-right corner is contested

A cookie banner, a sticky basket bar, a floating call button, a back-to-top arrow and the chat bubble all want the same corner of a phone screen. Two overlapping makes both unusable and nobody reports it. Check your longest page on a real phone with the cookie banner showing, which is what a first-time visitor sees. See where to put the chat widget.

Phone visitors are less patient and more decisive

They are often comparing you with two other businesses in the same minute, frequently outside working hours. That cuts both ways: an answer about your area or your price keeps them, and a slow or evasive answer loses them in seconds. It is also why the fallback matters - if the assistant cannot answer, the inquiry form has to be right there rather than at the end of a journey. See after-hours answers.

Links, phone numbers and the thing a phone can do best

A phone can dial. If the right outcome is a call - a lockout, a no-heat emergency, a burst pipe - the answer should contain the number, and your knowledge should say when that is the right outcome rather than walking somebody through a form. Equally, a link to the one page that answers the question is better on a phone than a long explanation of it.

It must not slow the page down

Phones are where a heavy page hurts most, and a chat widget that blocks rendering is a reason to lose the visitor before they see the bubble. Allinaa's tag is deferred, so the page becomes usable first, and the widget's styles are isolated so your theme cannot break it and it cannot break your theme.

Test on a phone you hold

A desktop browser's phone emulator will not show you a keyboard covering the input, a thumb that cannot reach the top-left close button, or a bubble under the cookie banner. Open your own site on your own phone, in a private window so you see what a first-time visitor sees, and have the whole conversation through to the form. Ten minutes finds more than an hour of reading. See the launch checklist.