Article5 min readUpdated
Reduce Customer Support With Design: A Practical Guide
Learn how to reduce customer support with design: clear order status, in-app help, better error messages and fewer WhatsApp questions, with an example.
How can design reduce customer support?
Design reduces customer support by putting the answer on the screen. Self-service design means a customer can finish a task alone, without calling or sending a message. Every repeated question you receive points to a screen that failed to answer it.
Imagine a cloud kitchen owner in Kolkata. Each evening, 60 customers message on WhatsApp: "Where is my order?", "Did my payment go through?", "Can I change my address?" The owner answers each one. The kitchen is not slow. The app simply does not tell customers what they want to know.
This article is about fixing those screens. For the wider cost of confusion, read the cost of bad design.
Which support questions are really design problems?
Most repeated questions are design problems. A real support issue needs a person: a missing item, a refund, a special request. A design problem is a question the screen should have answered.
Look at your last 50 messages and sort them into two piles. The same few questions repeat in most products:
- Where is my order or booking?
- Did my payment succeed?
- How do I cancel or change something?
- What is the delivery charge, and why?
- Why was I asked for this detail?
- How do I log in again?
Each of these can be answered by a screen. If the same question arrives ten times a week, the screen has a gap. Fix the gap once and the questions stop.
How should order status be shown?
Show order status as a short list of steps, with the current step marked and a time estimate. The customer should see the answer in one glance, without scrolling or tapping.
A good order status screen has these parts:
- Steps in plain words: Placed, Confirmed, Packed, Out for delivery, Delivered.
- The current step marked clearly, so the customer sees where the order is.
- A time estimate, such as "Arriving by 8:30 pm", updated when it changes.
- The name and phone button of the delivery person, once the order is out.
- A help link at the bottom, for the case where something is wrong.
Do not make the customer guess. If the order is late, say so on the screen. A late order with a clear message causes fewer messages than a late order with silence.
For the full layout, read order tracking and returns page design.
Where should help content live inside the app?
Help should sit next to the place where the customer gets stuck. A separate help page is read by few people. A short line under a confusing field is read by almost everyone who reaches it.
Place help in these four spots:
- Beside the field. Under "Pincode", write "6 digits, as on your address". Under "Landmark", write "Optional, helps the delivery person".
- In error messages. Instead of "Invalid input", write "Phone number needs 10 digits. You entered 9."
- On empty and waiting screens. When a cart is empty or a list is loading, say what the customer can do next. Read empty states, loading and error screens.
- After payment. Show a clear "Payment received" screen with the amount and a reference number. Customers who see nothing will message you.
The words matter as much as the layout. Read UX writing and microcopy for apps for how to write short, clear lines.
What about fewer WhatsApp questions on a website?
The same logic works on a website. Put the facts people ask about on the page where they decide: price, delivery area, timing, payment methods, return rules.
A small business often receives messages like "What is the price?" and "Do you deliver to my area?" A short table on the product page answers both. A visible line that says "Delivery within 10 km, 1 to 2 days" removes a whole class of messages.
Keep a WhatsApp button for people who prefer to chat. In many Indian towns, customers trust a human reply more than a form. Self-service design does not remove the human option. It reserves the human for the questions that need a human. See website contact page and WhatsApp button design.
What is a worked example of the saving?
Here is a hypothetical example. The numbers are invented to show the method.
Suppose the cloud kitchen gets 60 support messages a day. Suppose each takes 4 minutes to read and answer.
- Time per day: 60 × 4 = 240 minutes, which is 4 hours.
Suppose a clear order status screen and a "Payment received" screen remove 35 of those messages.
- Messages left: 60 − 35 = 25.
- Time left: 25 × 4 = 100 minutes.
- Time saved: 240 − 100 = 140 minutes a day, about 2 hours 20 minutes.
Suppose an hour of the owner's or staff's time is worth ₹150.
- Daily value: about 2.33 hours × ₹150 = about ₹350.
- Over 26 days: 26 × ₹350 = ₹9,100 a month.
The saving in rupees is modest. The bigger gain is quieter. The owner stops being interrupted during cooking. Customers who were anxious now feel informed. Whether this is worth a design fee depends on your own volume. At 60 messages a day it is worth a serious look. At 5 a day it may not be.
When is it not worth designing for fewer support calls?
It is not worth it in some cases, and a fair article should say so.
- Low volume. If you receive a few questions a week, answer them yourself.
- The conversation is the product. If you sell consultations or custom work, talking to the customer is part of the service.
- The cause is not on screen. If customers ask "Where is my order?" because deliveries really are late, no status screen fixes the delay. It only makes the delay visible, which is still honest and useful.
- Customers prefer calling. In some places, and for some older customers, a phone call is the preferred route. Keep it available.
For first-time internet users the picture is different. Clear steps matter even more.
Where do you start?
Start with the one question you receive most. Find the screen where the customer should have learned the answer. Add the answer there, in plain words. Then count the messages again after two weeks.
A support chat inside the app is also part of this. Read in-app chat and support screen design. If you want help finding which screens cause your repeated questions, I describe how I approach that on my UI/UX design page.
Frequently asked questions
What is the quickest fix to reduce support messages?
+
Add a clear order or booking status screen with steps and a time estimate. Questions about where something is are usually the most common.
Should I remove the WhatsApp button to cut messages?
+
No. Keep it, but answer common questions on the screen first. The button then serves the questions that truly need a person.
How do I know which screens cause support questions?
+
List your last 50 messages and group them by topic. Each repeated topic points to a screen that did not give the answer.
Does self-service design work for older or first-time users?
+
Yes, if the steps are short and the words are plain. Keep a phone or WhatsApp option as well.
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.