Handling Customer Complaints in Rwanda: What to Do in the First Hour

Introduction

How to handle a customer complaint in Rwanda: what to do in the first hour, how to reply to a bad review in public, and how to fix the cause.

A complaint is a customer who is still talking to you. A bad review is usually a complaint that nobody answered in time. That is the whole difference, and it is why the first hour after something goes wrong matters more than anything you write afterwards.

This guide is for owners and managers in Rwanda dealing with the ordinary version of this: a guest whose booking was lost, a patient sent back to reception twice, a customer whose transfer failed and who has now written about it in public. It covers what to do in the first hour, how to reply where everyone can read it, and how to tell a one-off from a pattern that will keep producing the same review every month.

The first hour: own it before you explain it

Most complaints in service businesses are not really about the original failure. They are about what happened next. A delayed order is an inconvenience; a delayed order where three people each said it was another department's problem is the story that gets told to other people.

So the sequence that works is short and it is almost always the same:

• Acknowledge the fact before you investigate it. "Your booking is not in our system and I can see that is our error" costs nothing and ends the argument the customer was preparing for.
• Take ownership of the case, not just the conversation. The person who hears the complaint should stay attached to it until it is closed. Transferring a customer and their problem together is the single most common way a small failure becomes a public one.
• Say what happens next, with a time on it. Not "we will look into it". "I will call you before four o'clock today, and if I do not have an answer by then I will still call."
• Do the thing you said, at the time you said it. A missed promise made during a recovery is worse than the original failure, because it confirms what the customer had begun to suspect.

None of that requires authority to give discounts. It requires that one named person is accountable for the outcome and that the customer knows who that is.

Replying to a review in public

A public reply is not written for the person who complained. They already know what happened. It is written for the next reader, who is deciding whether to risk their money on you, and who will read the complaint and your reply as a pair.

That changes what a good reply looks like. It is short, it is specific, and it does not argue:

• Name the failure in your own words. A reply that restates the problem accurately proves you understood it. A reply that talks around it proves the opposite.
• Say what changed because of it. "We have moved the check-in list off paper" is worth more to a reader than any apology, because it is checkable and it is about them, not about your feelings.
• Take the detail off the platform, not the resolution. Ask for the reference number by phone or email. Do not ask the customer to continue the substance of the complaint privately, which reads to everyone else as an attempt to make it disappear.
• Never offer anything in exchange for removing a review. It is the fastest way to turn one unhappy customer into a screenshot, and on a platform where reviews are tied to real people it is treated as manipulation rather than as service.

If you are not sure how the reply will land, read it as though you had never heard of the business. Most defensive replies are obvious from the outside and invisible from the inside. Our guide on how customers actually read reviews and ratings covers what that reader is weighing.

One-off or pattern: the question that decides what to fix

Every complaint feels like a one-off to the person handling it, because they only see it once. The way to tell is to stop reading complaints as stories and start counting them as events.

Take a month of them and write each one as the thing that happened, not the theme it belongs to. Not "communication problems" but "the customer was not told the room was on the third floor with no lift". Themes cannot be fixed by anybody. Events can: they name a step, a shift, or a piece of information that was missing.

When you have thirty of them written that way, the pattern is usually embarrassing in how narrow it is. Two or three specific moments produce most of what people complain about, and they are almost never the moments the business worries about. Collecting them systematically is a job of its own, and we have written separately about how to collect customer feedback and get more reviews rather than waiting for the loud ones to arrive on their own.

Fixing the cause: a standard, then competence

Once you know which moments fail, there are two things to fix and they are usually confused with each other.

The first is the standard: what is supposed to happen at that moment, written down clearly enough that two members of staff on different shifts would do the same thing. Most service failures in small and mid-sized businesses are not motivation problems. They are the absence of a decided answer, so each person invents one and the customer experiences the variation.

The Institute of Service Excellence publishes its service excellence standard at ise.rw in full and without an account, and its clause on complaint handling and service recovery is a reasonable place to start even if you never certify anybody against it. It sets out what a customer is entitled to expect when something has gone wrong, which is exactly the thing most internal procedures leave to judgement.

The second is competence: whether the people at that moment can actually do it under pressure, with a queue behind them and an angry customer in front of them. That is a different problem from knowing the rule, and it is why a one-day workshop rarely survives contact with a busy Friday.

The officer-level syllabus ISE teaches is published in full, and three of its twenty-one modules deal with precisely this ground: handling complaints professionally, service recovery and problem resolution, and managing difficult customers. You can read the whole CSEO syllabus at ise.rw before deciding anything, which is a fair test of any training you are considering: if you cannot see what is taught before you pay, you are buying attendance rather than capability.

Where the difference has to be provable to somebody outside the business, the Certified Service Excellence Officer certification at ise.rw is assessed against that published standard and issued with a number anyone can check. For teams rather than individuals, we have covered the wider question of how to train and certify a customer service team in Rwanda in its own guide.

How you know it worked

The measure is not that complaints go down. Complaints going down can simply mean people have stopped bothering to tell you, which is the state immediately before they stop coming.

Better signs, in order of how much they are worth:

• The same failure stops repeating. Count the specific event, not the total.
• Complaints arrive earlier. A customer who tells you at the counter rather than in a review is a customer who believes you will act.
• Recovery gets faster. Time from the complaint being made to it being closed, measured on the cases you would rather not count.
• Reviews start mentioning the recovery. "Something went wrong and they sorted it" is a better advertisement than a review from a customer who never had a problem.

You can see how businesses in your sector are being described right now on the Trusted Rw directory, including which specific moments customers keep raising. It is a cheaper way to find your own weak points than discovering them one review at a time.

The pages referred to above

The Institute of Service Excellence (ISE) is the certification body referred to in this guide. Its relevant pages are public and need no account:

• The service excellence standard, including the complaint handling and service recovery clause: https://ise.rw/standard/
• The full CSEO syllabus, whose modules 10 to 12 cover complaints, service recovery and difficult customers: https://ise.rw/courses/certified-service-excellence-officer/
• The CSEO certification itself: https://ise.rw/certifications/certified-service-excellence-officer/
• Checking a certificate number: https://ise.rw/verify/