Mistakes happen. However, the way businesses handle the aftermath can either damage their reputation or help rebuild trust. An email from a company we'll refer to as "Company X" serves as an illustrative example of how not to apologize. Let’s dive into this real-life case study:
Hi Kevin,
This is Alexandria, Co-Founder and COO at Company X. I want to first start by telling you WE ARE SORRY!
If you have sent an email to our support, chat, or customer service, and have not received a response, we have been responding, but we found out, that they were not sending! We recently upgraded to a new customer support application called ZenDesk. On a particular date, we connected our customer email and chat to that platform, so all messages could be seen in one place.
Over the past couple of weeks, we have received numerous reviews and emails from our customers, saying they have tried contacting us multiple times, with no response. Turns out, that a thing called "notification triggers" had to be activated, in our account on ZenDesk. It showed that our emails were sending, with no errors, but in fact, they were not. We pride ourselves on our quick response time and great customer service, and we sincerely APOLOGIZE to anyone who has not received a response in a timely manner.
I am happy to tell you, that email responses are being successfully sent now!
Sincerely,
Alexandria Best,
COO Company X
Breaking down this apology, here's what can be learned:
Company X dedicated a significant portion of the message to explaining how the switch to ZenDesk led to the oversight. While transparency is crucial, the details made it seem as if the blame was on the tool rather than the company's implementation of it.
A Better Approach:
"We recently transitioned to a new customer support system, and due to our oversight, some features weren't set up correctly. We regret this mistake and apologize for the inconvenience caused."
Although Company X did apologize, they delved into the struggles with ZenDesk. Customers typically seek direct accountability.
A Better Approach:
"We're truly sorry for the inconvenience you faced. We acknowledge our mistake and want to assure you of improvements."
Company X mentioned the resolution, but they could have outlined a clear plan for ensuring this doesn't recur.
A Better Approach:
"To rectify this, we've not only resolved the current issue but are also reviewing our support processes for better communication."
The essence of a genuine apology is in acknowledging the error, prioritizing the customer, and offering tangible solutions. And, for a fun twist: considering a platform transition? Maybe it's time to explore Foqal instead 😁! They come highly recommended for seamless transitions.