Tithi Mondal

Article5 min readUpdated

Chat Screen Design: In-App Chat and Customer Support

Chat screen design for apps: message layout, support screen, help centre, chatbot handoff to a person, states, sample wording and mistakes to avoid.

By Tithi Mondal, UI/UX Designer

Read inहिन्दीবাংলাमराठीதமிழ்తెలుగుગુજરાતી

Chat Screen Design: In-App Chat and Customer Support: cover illustration

A customer in Howrah paid ₹499 for a course, got an error, and now opens the app to ask for help. She finds a chat icon, types her problem, and gets "Hello, how can I help you today?" three times from a bot that does not understand. She uploads a screenshot to a social media page instead. Chat screen design exists to prevent this. A chat screen is the screen where a user sends messages to a bot or a person and reads the replies. The support screen is the entry point that decides whether the user needs a help article, a chat, a call or a person.

What is the order of a support screen?

A support screen should send users to the fastest answer first, and a person last but visible. Start with self-service, because many questions repeat.

Top to bottom, the customer support screen has these parts.

  1. Title. "Help and support".
  2. Search field. "Search for help, such as refund or delivery".
  3. Current order card. If the user has an active order, show it: "Order #4821, arriving today. Need help with this order?"
  4. Common topics. 5 to 6 rows: "Payments and refunds", "Delivery", "Account and login", "Offers and coupons".
  5. Contact options. "Chat with us", "Call us", "WhatsApp us", each with support hours.
  6. Ticket history. "Your past requests", with status labels.

Showing the current order first saves the user from explaining which order they mean. It is the single most useful touch on this screen.

How do you design a help centre?

A help centre design works when each question has a short answer and a way to continue if the answer does not help. It is a list of articles, not a library.

  • Group by task, not by department. "Where is my order?" beats "Logistics".
  • Write the question the way a user would say it: "My payment was deducted but the order failed".
  • Keep answers to 3 to 6 short steps, with one screenshot at most.
  • End every article with "Did this help?" and two buttons: "Yes" and "No, talk to us".
  • The "No" button opens chat with the article title already attached.
  • Support Hindi, Bengali or other languages your users speak. See regional language app design in India.

Keep the search tolerant of spelling mistakes and mixed languages. See search and filter UX design.

What does the chat screen contain?

The in-app chat screen is simple on purpose. Users know this pattern from WhatsApp, so do not reinvent it. The in-app chat UI has the following parts.

  1. Top bar. Back arrow, the name and photo of the agent or "Support team", and status text: "Online" or "Replies in about 10 minutes".
  2. Message area. User messages on the right in a strong colour, replies on the left in a light colour. Show time under groups of messages, and date separators such as "Today".
  3. Status on each sent message. "Sending", "Sent", "Seen". Do not show a "seen" tick unless it is true.
  4. Quick reply chips. For bot questions: "Track my order", "Refund status", "Talk to a person".
  5. Input bar. Text field with "Type your message", an attach icon and a send button. Disable send when the field is empty.
  6. Attachments. Photos and screenshots, with a preview before sending.

Text must be at least 16 pixels and the bubbles need good contrast. Long messages should wrap, not cut. Support the keyboard pushing the input bar up without covering messages.

How should a chatbot hand off to a person?

A chatbot handoff to a person should happen without making the user repeat anything. The rule is simple: the bot says what it will do, the person sees everything already said, and the user knows how long to wait.

Sample wording:

  • Bot: "I could not solve this. I am connecting you to our team."
  • System line: "Priya from support has joined the chat."
  • Waiting: "You are number 3 in line. Usual wait: 5 minutes. You can close the app and we will notify you."
  • Person: "Hello Riya, I can see your order #4821 and the payment error. I am checking it now."

Let the user ask for a person at any time with a button that never hides, not only after the bot fails three times. Trying to keep users with a bot when they are upset damages trust. Be honest about the bot. Label it "Assistant" or "Automated helper", never a fake human name.

Sensitive topics such as failed payments, refunds, harassment and safety should go to a person quickly. This is a product decision, so I mark those topics in the design and the team sets the rules.

What are the states of chat and support?

StateWhat the user sees
Empty chat"Hi Riya. Ask us anything about your orders." plus quick chips
Loading historyGrey placeholder bubbles
SendingSmall clock icon on the message
Failed to sendRed "Not sent. Tap to retry."
Agent typing"Priya is typing..."
Outside hours"We are offline now. We reply from 9 am to 9 pm. Leave a message and we will reply here."
Waiting for a person"Waiting for an agent. You can close the app. We will notify you."
Offline"No internet. Your message will be sent when you are back online."
Resolved"Is your issue solved?" with "Yes" and "No", then a rating
Ticket created"Request #2231 created. We will reply within 24 hours."

After resolution, ask for a rating. See ratings and reviews UI design. When a reply arrives, send a notification with the first line of the message. See notification UX for push, SMS and WhatsApp.

Which support screen mistakes happen most?

Most support failures come from hiding the human, not from poor visuals.

  • Burying the contact option under five levels of articles.
  • A bot that repeats the greeting after every unclear message.
  • No support hours, so users wait for a reply that cannot come tonight.
  • Making users type their order number when the app already knows it.
  • Closing the chat when the user leaves the screen, and losing the history.
  • Using only email or a form with no ticket status.
  • Replies in English only, for users who write in Bengali or Hindi.
  • Forgetting an offline state for users on weak networks. See designing for low-end phones and slow networks.

If you offer WhatsApp support, give the button a pre-filled message, such as "Hi, I need help with order #4821". That saves the user a step. For the website version of this idea, see website contact page and WhatsApp CTA.

If you want a support and chat flow designed for your app, see my UI/UX design service.

Frequently asked questions

Should an app have a chatbot or a human support agent?

Use a bot for simple, repeated questions such as order status, and a person for money, safety and anger. Always give a clear way to reach a person.

Should I use in-app chat or WhatsApp for support?

Many Indian users prefer WhatsApp because they already use it daily. In-app chat keeps the order context attached. Many apps offer both and let the user choose.

What should a help centre include?

Search, the top 5 to 8 questions, topics grouped by task, and a visible contact option. Write answers in short steps.

How should I show that an agent is typing or offline?

Show "Priya is typing..." while a person writes, and show support hours such as "We reply from 9 am to 9 pm" when no one is online.

Working on something like this?

Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.

Your details go only to Tithi and are used only to reply to you. No newsletters, no sharing.

Have a product in mind? Let us design it properly.

Tell me what you are building. I will reply with questions, a rough timeline and a quote.