How to Collect and Use Customer Feedback to Improve Your Bangladesh Business

Most Bangladeshi business owners hear from customers every week. It might be a Facebook comment about a late parcel, a voice note on WhatsApp, a rider reporting a refused cash-on-delivery order, or a shopkeeper telling your sales rep that a rival offers better credit terms. Customer feedback in Bangladesh is rarely in short supply. What is usually missing is a system that captures it, makes sense of it, and checks whether anything improved.

This guide is about building that system. Loyal, repeat buyers are the result you want at the end, and our guide on customer retention in Bangladesh covers that side in depth. Here the focus is the input: the comments, complaints, ratings, and behavior that tell you what to fix next.

You will learn how to choose channels and timing, write neutral questions in Bangla and English, sample customers fairly, keep a privacy-safe feedback log, prioritize and measure fixes, handle complaints within the law, and close the loop with customers.

What Customer Feedback Means for a Small Business

Customer feedback is information customers give you, directly or through their actions, about their experience with your product, price, service, or delivery. For a small business, it is a low-cost source of customer insight, though collecting, reviewing, and acting on it still takes staff time.

Three kinds of records, and why to keep them apart

It helps to separate what you log into three types:

• Direct feedback: what a customer says. A complaint, a rating, a suggestion, a review.

• Behavioral signals: what a customer does. A return, a cancellation, a repeat purchase, months of inactivity.

• Operational events: what happened on your side. A late delivery, a stockout, a failed payment, a slow support reply.

Link them where you can, but do not treat one as proof of another. A refused cash-on-delivery parcel tells you what happened, not why. The customer may have been unhappy, may have found a cheaper option, or may simply not have been home with cash. A customer who stops ordering could be reacting to price, seasonality, or a change in personal circumstances. Behavior is a reason to investigate, not an answer.

Complaints are useful, but not the whole story

Not every unhappy customer complains, and the ones who do are not always typical. A complaint is a chance to diagnose a specific problem. Whether it reflects a wider pattern is something you find out by counting and comparing, not by assuming.

How to Collect Customer Feedback in Bangladesh: Channels to Test

There is no single best channel. Preferences vary by customer, product, and sales channel, so treat each option below as something to test against your own response numbers.

WhatsApp or Messenger follow-up

If customers already order or confirm through WhatsApp, a short follow-up there is a natural fit. Ask only customers who have given you their number for order updates, keep the message short, and make it easy to opt out. Our guide to WhatsApp marketing covers permission-based messaging in more detail.

Offer voice notes as an option for people who prefer speaking to typing, but do not assume everyone does.

Phone calls to a small, varied sample

Calls give depth: you can follow up on vague answers and hear what a rating alone cannot tell you. Surveys give breadth. They answer different questions, so many businesses use both. Be aware that people often soften criticism on a call to avoid seeming rude, so ask neutral questions and make it clear that negative answers are welcome.

Social media comments and reviews

For sellers who trade mainly through a Facebook page, comments and reviews act as public feedback. Record the substance of useful comments in your feedback log rather than storing screenshots with names and profile pictures you do not need.

Frontline staff and delivery riders

Riders, cashiers, and sales reps hear comments that never reach the owner. Ask them briefly each week what customers raised, and log it. Remember that staff can also miss or reinterpret feedback, so treat their reports as one input among several.

Short link surveys

A two- or three-question form, offered in Bangla and English and shared by SMS or WhatsApp, works well for collecting scores you can track over time. Longer surveys tend to reduce completion, so ask only questions you will actually use.

Post-service ratings

Many service apps ask for a rating as soon as the service ends, which you have likely seen if you have used ride-hailing services such as Pathao. The useful lesson is contextual timing: ask when the customer can judge the experience, which is not always immediately.

Field visits and B2B conversations

Business customers rarely fill in web forms. Feedback comes through visits, calls, and conversations at the counter. Give field staff a short checklist so observations reach you in a usable form, and remember that one contact may not speak for the whole business (more on that below).

Timing and Sampling: Who to Ask, and When

Match timing to the experience

• Immediately: a completed ride, appointment, class, or support call

• A day or two later: delivery quality and product condition, once the customer has opened the parcel

• Weeks later: results that take time, such as a skincare product, a training course, or a software tool

Do not ask everyone, every time

Asking after every interaction can cause survey fatigue. Instead, sample. For example, send a feedback request to one order in five, and make sure no customer is asked more than once a month.

Choose a fair mix for calls

If you call ten customers a week, rotate across groups so you do not hear only from the happiest or angriest buyers:

• New customers

• Repeat customers

• Customers who returned an item

• Customers who complained

• Customers who have stopped ordering

Note in your log how each person was selected. If your sample changes, your scores can move even when customer experience has not.

Watch for response bias

People with very good or very bad experiences are more likely to reply. Do not judge your whole customer base from a handful of answers. Compare feedback with operational data, such as return rates and on-time delivery, and keep the selection method consistent from week to week.Use one score plus one open question

The score lets you track a trend. The open question tells you why it moved. Keep the wording neutral: "What did you think of the packaging?" rather than "How much did you like our new packaging?"

Ask about a specific moment, such as the delivery, the product condition, or the support call, rather than "How was everything?"

Sample messages you can adapt

Post-delivery request (Bangla):

"[নাম], আপনার অর্ডারটি গতকাল পৌঁছেছে। ডেলিভারি নিয়ে ১ থেকে ৫ এর মধ্যে আপনি কতটা সন্তুষ্ট? চাইলে একটা কারণও লিখতে পারেন। উত্তর দেওয়া ঐচ্ছিক। এ ধরনের মেসেজ না চাইলে STOP লিখুন।"

Post-delivery request (English):

"Hi [name], your order arrived yesterday. On a scale of 1 to 5, how satisfied are you with the delivery? Feel free to add a reason. Replying is optional; reply STOP if you would rather not get these messages."

Complaint follow-up (Bangla):

"[নাম], আপনি প্যাকেট লিক হওয়ার কথা জানিয়েছিলেন। আমরা প্যাকেজিং বদলেছি। পরের অর্ডারে কোনো সমস্যা হলে সরাসরি এই নম্বরে জানাবেন।"

Customer who has stopped buying (Bangla):

"[নাম], অনেকদিন আপনার অর্ডার পাইনি। আমাদের কোন জিনিসটা ঠিক করলে আবার অর্ডার করার কথা ভাবতেন? উত্তর দিতে না চাইলে কোনো সমস্যা নেই, আমরা আর জিজ্ঞেস করব না।"

If someone replies STOP, mark them in your order system so nobody on your team messages them again; an opt-out you do not honor is worse than none. Accept replies in Bangla, English, or Banglish, and log them as written.

For NPS, scores of 9 or 10 are promoters, 7 or 8 are passives, and 0 to 6 are detractors. NPS is the percentage of promoters minus the percentage of detractors. It measures what people say about recommending you, not actual referrals, retention, or satisfaction with a specific order. A 1 to 5 satisfaction rating is not NPS.

Pair any score with operational measures. A delivery business, for example, might track CSAT per delivery, complaints per 100 orders, on-time delivery rate, and complaint resolution time. Each answers a different question, and no single score replaces them.

Be careful with small numbers. If only 15 people answered this week, two unhappy replies can swing your score sharply. Look at trends over several weeks, and report how many responses each score is based on.

Turning Raw Feedback Into Decisions

Set up a privacy-safe feedback log

A shared spreadsheet is enough to start. Suggested columns:

For severity, agree on plain definitions so two people tag the same issue the same way. For example: Low means a minor annoyance, Medium means the customer lost time or money, High means a refund or lost customer is likely, and Safety means anyone could be harmed.

Keep phone numbers and addresses in your order system, not in the feedback sheet. Limit access to the staff who need it, decide how long you keep entries, and redact identifying information before sharing examples with your team.

If you use WhatsApp Business, chat labels (for example, "feedback" and "complaint") make it easier to find conversations during your weekly review before you copy the substance into the sheet.

Tag every entry by theme

Most entries fall into a few buckets: delivery, product quality, price, packaging, staff behavior, payment, and website or app problems. Tags are what let you count instead of relying on memory.

Prioritize with more than frequency

Rank issues using:

1. Severity of harm or safety risk

2. Whether the problem is still happening

3. Number of customers affected

4. Legal or contractual urgency

5. Likely recurrence and business impact

6. Effort required to fix it

Escalate safety risks, suspected fraud, exposure of customer data, and formal legal complaints immediately rather than waiting for the weekly review.

Hold a weekly review with an effectiveness check

Set one fixed slot each week. For each issue you choose to tackle, record:

• The baseline measure (for example, late-delivery complaints per 100 orders)

• The change you are making

• The owner and due date

• What success looks like

• The date you will check the result

At the next review, check whether the measure actually moved. Implementing a fix is not the same as solving the problem. Writing this routine down as one of your standard operating procedures helps it survive busy weeks and staff changes.

Simple formulas to track

• Response rate = completed responses ÷ feedback requests delivered × 100

• Complaint rate = complaints ÷ completed orders × 100

• Resolution rate = complaints resolved ÷ complaints received × 100

Decide your unit and stick to it. One customer may send three complaints about one order, so state whether you are counting complaints, orders, or customers.

Test feature requests before building them

When customers ask for something new, such as a subscription option or a new pack size, check whether the request repeats across different types of customers, then test demand with a small pilot, the same way you would validate a startup idea.

Bangladesh Context: Applying This Locally

Mobile access is a practical starting point. BTRC data reported by BSS recorded 135.94 million internet subscriptions at the end of June 2026, including 120.84 million mobile internet subscriptions. Subscriptions are not the same as unique users, and they do not tell you which apps your customers use, but the figures support designing any digital feedback request to work well on a phone screen. Choose channels based on your own customers' access and preferences.

Consider how feedback timing varies by sector. In grocery delivery, the kind of service Chaldal offers, problems like a missing item or bruised produce are visible as soon as a bag is unpacked, so a quick check makes sense. Recording which order, route, and packing batch each report relates to makes it easier to find patterns.

Education is different. A student may only know whether a course helped weeks later, after an exam. Public lesson platforms, such as the one Ayman Sadiq built, also show how open comment sections can surface confusing topics, though public comments come from a self-selected group.

B2B feedback involves several people. In a pharmacy chain or a distributor, the person who orders, the person who uses the product, the accounts team that handles invoices, and the owner who decides on reorders may each have a different view. Ask who uses the product, who approves purchases, who handles payment, and who decides whether to buy again. One contact's opinion may not represent the whole business.

Handling Complaints Within the Law

Legal information in this section was last reviewed in October 2026. Laws and guidelines change, so check the official text before relying on it.

A complaint workflow that does not drop anything

1. Acknowledge the complaint and give a reference number.

2. Classify urgency: safety, fraud, data exposure, or legal complaints go straight to the owner.

3. Investigate the order, route, product batch, or staff involved.

4. Communicate the next step and a realistic timeline.

5. Resolve or explain the outcome clearly.

6. Record the root cause in your feedback log.

7. Verify at the next review that the fix worked.

Online stores must record and address complaints

The Ministry of Commerce's Digital Commerce Operation Guidelines 2021 set out obligations for digital commerce businesses, including online pages and stores run through social media or websites. They require a way for consumers to complain, and complaints must be recorded and addressed within 72 hours. Marketplaces also have to display a phone number, email, or other contact method for complaints. Read the guidelines yourself to confirm which obligations apply to your setup. Even where a specific rule does not apply, an easy-to-find complaint channel is good practice for any business.

Know the formal route customers can take

Under section 60 of the Consumers' Right Protection Act, a complaint about an anti-consumer-rights practice made to the Director General or an authorized officer must be filed within 30 days of the cause of action arising. That deadline applies to this complaint route, not to every possible legal remedy. Where a fine is imposed and realized, the Act provides for 25 percent to be paid to the complainant. Consumers can also use the 16121 hotline or DNCRP's complaint channels.

A fast, fair internal response usually costs far less than a formal case, so make it easy to complain to you first.

Respond publicly, resolve privately

When a complaint appears in a public comment, reply politely in public, then move the details to a private message or call. If a complaint starts spreading fast, follow your crisis management plan rather than improvising.

Handle feedback data lawfully

The Personal Data Protection Act, 2026 (Act No. 63 of 2026) replaced the Personal Data Protection Ordinance 2025 and is now the main law governing personal data in Bangladesh. Not every provision necessarily applies from the same date, so check the commencement rules in the official text. Section 5 sets out the lawful bases for processing personal data. Consent is one basis, but it is not the only one, and the right basis depends on what you collect and why.

In practice, for a feedback system:

• Tell customers why you are asking and how you will use their answers

• Collect only what you need, and keep contact details out of the feedback sheet

• Restrict access and protect the file

• Set a retention period and delete what you no longer need, after checking the Act's record-keeping rules so you do not delete records you are required to keep

• Take extra care if feedback touches health or other sensitive matters, for example from pharmacy or clinic customers, since sensitive data faces stricter conditions

• If your sheet or survey tool stores data on servers abroad, check the Act's rules on transferring personal data outside Bangladesh

• Keep marketing opt-ins separate from service feedback requests

For anything beyond routine service feedback, such as profiling customers or sharing data with third parties, get legal advice on the correct basis.

Closing the Loop: Show Customers You Listened

Feedback systems lose momentum when customers never see a result.

Reply to the individual. When you fix a problem someone reported, tell them, as in the complaint follow-up message above.

Share changes, not people. A "You asked, we changed" post on your page can describe themes ("several customers mentioned leaking packaging, so we switched suppliers") without naming anyone. Get permission before publishing an identifiable comment or testimonial.

Reward responses, not ratings. If you thank customers with a small reward, give it for responding, whatever they say. Rewarding only positive reviews hides the problems you need to see.

Share themes with your team. Discuss anonymized examples at your weekly meeting so staff understand what customers notice, without passing around personal details.

Start With Ten Calls and One Spreadsheet

A customer feedback system does not need expensive software. It needs a routine: ask at the right moment, sample fairly, log responses without unnecessary personal data, prioritize carefully, and check whether each fix worked.

Start this week. Set up a sheet with the columns above, pick ten recent customers from different groups, and ask them one score question and one open question. Next week, hold your first review, choose one issue, record its baseline, and assign an owner. At the following review, check whether the number moved.

Over a few months, this process can show you which problems keep recurring, which fixes actually helped, and where your customers' experience is getting better or worse. That gives you something more reliable than guesswork to base the next decision on.