Review a documentation chatbot on a small screen

Inspect the actual reading task

Open a representative article on a narrow viewport, then open the chat. Check whether the reader can still identify the article, close the panel and return to the same place. Look for overlap with navigation, consent controls and important buttons. A launcher that occupies little space when closed can still create an unusable experience once the software keyboard and a long response appear.

Check long and awkward content

Use a harmless long answer, a citation with a descriptive label and a short code example where relevant. Confirm that text wraps sensibly and that any necessary horizontal scrolling remains inside the relevant region. Avoid shrinking text to make the interface fit. Readers should be able to enlarge content and activate controls without precision tapping or accidentally opening a merchant destination.

Follow a source and come back

A documentation answer is only useful if the supporting article can be inspected. Test how the source link opens and whether the reader can return to the conversation without losing essential context. Record the behavior rather than assuming every mobile browser handles it the same way. Do not claim cross-device compatibility from a single screenshot or from a vendor’s responsive-design label.

Prefer a simpler entry point if needed

If a floating launcher competes with the site’s primary task, consider a clearly labelled inline entry point or a dedicated help route where the product supports it. Keep normal article navigation available. The objective is task completion, not maximum chat opens. A lower-visibility interface that readers can use comfortably may be better than a persistent overlay that interrupts every page.

• Record viewport size, text enlargement, open keyboard, answer length and source-link behavior so a later layout regression has a reproducible test.