Chatbot User Interface on Phones: Designing for Thumbs, Keyboards and Slow Networks

Chatbot user interface guides usually start on a laptop, but most of your visitors will meet your chat on a phone, often a budget handset on a patchy mobile connection. This guide designs from the phone outwards: thumbs instead of mice, an on-screen keyboard eating half the screen, and pages that must load before the visitor loses patience.

yourshop.in Β· Chat
πŸ€– ShopHi! Ask about delivery, sizes or your order πŸ‘‹
cod available?
πŸ€– ShopYes, cash on delivery is available up to β‚Ή5,000.
Track my order
Talk to a person

⚑ In short

  • Design for one thumb: important controls within easy reach, tap targets about 48 pixels.
  • When the keyboard opens, the latest message and the input box must stay visible.
  • Short bubbles, readable text (15–16px), no sideways scrolling.
  • Keep the widget light so it doesn’t slow your page on a weak connection.
Chatbot user interface in LiveChatBot: chat widget appearance settings with colour and welcome message
How it looks in LiveChatBot: chat widget appearance settings with colour and welcome message.

Why phones first

The phone changes almost every design decision

On a laptop, a chat window is a small box in the corner of a big screen. There’s room for long messages, a mouse can hit tiny buttons, and the keyboard never covers anything. None of that is true on a phone. The screen is narrow, the visitor is using one thumb, and the moment they tap the input box, an on-screen keyboard covers roughly half of what they could see.

In India especially, many visitors browse on affordable Android phones with modest memory, on mobile data that can drop from fast to slow as they move. A chatbot user interface that feels fine on a designer’s laptop over office Wi-Fi can feel cramped, laggy and confusing in those conditions.

Designing phone-first means testing every decision against that reality first, then checking that it still works on a larger screen. It’s the opposite of how many chat windows are built, and it’s why so many of them feel awkward on mobile. If you’d like the full anatomy of the chat window first, start with our chatbot UI guide; this page focuses on what changes on a phone.

Thumbs

Designing for one hand

Most people hold their phone in one hand and tap with their thumb.

πŸ‘

The easy zone

The lower-middle part of the screen is easiest to reach. Put the input box, send button and quick replies there.

↗️

The stretch zone

Top corners are hard to reach one-handed. Fine for the close button, which people need rarely.

🎯

Big targets

Aim for tap targets around 48 by 48 pixels with space between them, so a thumb doesn’t hit two buttons at once.

🧱

Stacked quick replies

On narrow screens, quick-reply buttons should wrap onto new lines. Options hidden off the side of the screen are never tapped.

πŸ‘†

Swipe safely

Don’t rely on swipe gestures inside the chat. They clash with the browser’s own back gesture on many phones.

πŸ“

Launcher placement

The launcher sits in the easy zone too, which is why it must never cover your ‘Add to cart’ or ‘Book’ button.

The keyboard

Half the screen disappears when the visitor starts typing

The on-screen keyboard is the single biggest difference between desktop and phone chat. When it opens, it can cover about half the screen. A chatbot user interface that doesn’t plan for this hides the very things the visitor needs while typing: the input box and the bot’s last message.

What must stay visible

– The input box, directly above the keyboard, so the visitor sees what they’re typing. – The most recent message, so they can refer to it as they reply. – The send button, inside easy thumb reach.

Common failures

– The chat window is a fixed-height box, so the keyboard pushes the input off screen. – The page behind the chat scrolls instead of the chat itself, and the conversation jumps around. – The visitor taps the input, the keyboard opens, and the latest message is hidden behind it.

What good looks like

On a phone, the chat should open full-screen, and the message list should shrink as the keyboard opens, keeping the latest message just above the input. LiveChatBot’s widget opens full-screen on phones for this reason. Test it on your own site by opening the chat, tapping the input, and checking what’s still visible.

Reading

Making messages readable on a small screen

Text size

Body text in bubbles should be at least 15–16 pixels. Smaller text forces pinch-zooming, which breaks the chat layout on many phones.

Bubble width

Bubbles should use most of the screen width (around 80%), not a narrow column. Narrow bubbles turn three sentences into twelve lines.

Message length

On a phone, two or three short sentences per bubble is plenty. A paragraph that looks reasonable on a laptop becomes a scroll on a phone.

Contrast

Phones are used outdoors, in bright light. Low-contrast pale grey text on white becomes unreadable in sunlight. Choose strong contrast between text and bubble.

A desktop-sized answer on a phone
🚩 Too long on a phoneThank you for contacting us. Our standard delivery time for orders within India is between three and five working days, depending on your location. Orders over β‚Ή999 qualify for free delivery, while orders under that amount are charged a flat fee of β‚Ή60. You will receive a tracking link by SMS once your order ships.
βœ… Phone-friendlyDelivery takes 3–5 working days. It’s free over β‚Ή999, otherwise β‚Ή60. You’ll get a tracking link by SMS.

Slow networks

Keeping chat usable when the connection isn’t

Mobile connections vary. A visitor might be on fast 4G one minute and in a lift with one bar the next. Your chat should cope gracefully with both, and above all it shouldn’t make the rest of your page slower.

Load the widget without blocking the page

The chat script should load after your page content, so your product page appears first and the chat bubble a moment later. Visitors come for your content; the chat is a helper. A widget that delays the page’s first paint costs you visitors who never see either.

Show that a message is sending

On a slow connection, a message can take a moment to send. A small ‘sending’ state, then a tick when it’s delivered, stops visitors from tapping send repeatedly and creating duplicates.

Recover from drops

If the connection drops mid-chat, the conversation should still be there when it returns. Visitors shouldn’t lose what they typed or what the bot said.

Keep images light

If your bot sends images (product photos, maps), use compressed versions. A 3 MB image in a chat bubble can take many seconds on a weak connection.

What you control

With a hosted widget, the loading and reconnection are handled for you; what you control is content. Keep messages short, keep images small, and don’t add extra scripts that load alongside the chat. The customisation guide covers what you can change.

Phone patterns

Three interface patterns that work well on mobile

πŸ’¬

Floating launcher β†’ full-screen chat

πŸ’¬ Chat with us Β· we reply in minutes

Bottom bar on key pages

πŸ’¬ Ask about this course
Type your question…

Inline chat inside a page

Floating launcher, full-screen chat

The standard pattern. A small launcher in the corner; tapping it opens a full-screen chat with a clear close button. Works everywhere.

Bottom bar

A slim bar along the bottom of the screen reading ‘Chat with us Β· we reply in minutes’. It’s more noticeable than a bubble and sits in the easy thumb zone, but it takes space, so use it on pages where chat is a main action, such as contact or support pages.

Inline chat

The chat lives inside the page, such as on a ‘Contact us’ page, instead of floating. LiveChatBot’s inline mode does this with a container you choose. It’s great where chat is the main way to get in touch, and avoids anything covering other content.

Accessibility on phones

Making the chat usable for everyone

Phone accessibility features are widely used: larger system text, screen readers such as TalkBack on Android, high-contrast modes and voice typing. A chat interface should work with all of them.

  • Respect larger text. If a visitor has set their phone to a larger font size, chat text should grow with it rather than stay fixed.
  • Label controls. The send, attach and close buttons need names that screen readers can announce, not just icons.
  • Announce new messages. Screen reader users need to know when a reply arrives, without having to search for it.
  • Allow voice typing. The input box should work with the keyboard’s microphone button. Many visitors, especially those more comfortable speaking than typing in English, use it.
  • Don’t rely on colour alone. If an option is highlighted only by colour, some visitors won’t see the difference.

The W3C accessibility guidelines give the full picture. For most businesses using a ready-made widget, the practical step is to test with TalkBack and with large text switched on.

Test plan

A 15-minute phone test for your chatbot user interface

Borrow a budget Android phone if you can. It shows problems that flagship phones hide.

Phone test

The other side

Your team’s interface on the phone

The visitor isn’t the only one on a phone. In many small businesses, the person replying to chats is also on a phone: the shop owner between customers, the clinic receptionist, the salesperson out on a visit. Their interface matters too.

LiveChatBot’s Android app gives your team new-chat alerts, the conversation list, visitor details and replies from the phone, so handovers don’t wait until someone is back at a desk. Saved replies help here: typing long answers with a thumb is slow, and a saved reply for common answers keeps replies quick and consistent. The Android app guide shows setup in a few minutes.

Everything on this page, widget and app, runs on the free plan for two websites. Start on livechatbot.in, then run the 15-minute phone test above.

Frequently asked questions

What makes a good chatbot user interface on mobile?

A full-screen chat that keeps the input and latest message visible above the keyboard, short readable messages, large tap targets and a launcher that doesn’t cover important buttons.

Should the chat open automatically on phones?

No. On a small screen, a chat that opens by itself covers the whole page. Use the launcher with a short attention card, or a proactive message after the visitor has had time to read.

Does a chat widget slow down my site?

A well-built widget loads after your page content so visitors see the page first. Avoid adding extra scripts alongside it, and keep any images in chat compressed.

Can my team reply from their phones?

Yes. The LiveChatBot Android app shows alerts and lets your team reply, see visitor details and use saved replies.

How do I test on a slow connection?

Use a budget phone on mobile data, or your browser’s network throttling in developer tools, and check that the page and chat still load and recover.

Keep reading

Related guides

πŸ“˜

Chatbot User Experience, Mapped: The 7 Moments a Visitor Goes Through and How Each One Feels

Read the guide β†’

🧭

Chatbot UI Anatomy: The 7 Parts of a Chat Window and How to Get Each One Right

Read the guide β†’

πŸ› οΈ

Chatbot Examples From 10 Industries: Opening Lines, Conversations and Why They Work

Read the guide β†’

Make your chat feel at home on a phone

Install the widget free on livechatbot.in and run the phone test in 15 minutes.