Bad customer service on social media looks different from bad service on the phone: it happens in public, it is screenshotted, and it outlives the complaint. The examples below are real, public cases where a brand’s handling of customers on X (formerly Twitter), Facebook or YouTube made things worse. For each one we set out what happened, what went wrong, and the reply that would have worked.
In most of the eight, the complaint itself was not the damage. The response was. If your team handles complaints on public channels, our guide to handling negative feedback on social media covers the day-to-day method, and our broader list of bad customer service examples covers everyday failures on the phone and by email.
1. Lufthansa tells a customer his answer will not “magically change” (X, 2026)
What happened. In September 2026 a passenger posted on X that Lufthansa had approved his compensation claim months earlier, but the money had never arrived, and asked the airline to resolve his case. According to Aviation A2Z, Lufthansa’s account replied: “We’ve already responded to you numerous times via DM on different social media platforms. The response isn’t going to magically change just because you’re asking the same question on X now.” The reply drew more than 1.5 million views within about 24 hours, and Lufthansa later acknowledged its tone did not match how it wants to treat passengers.
What went wrong. The agent answered the frustration, not the problem. A customer who repeats a question on a new channel is telling you the first answer did not work. Scolding him in public turned one unpaid claim into a story about how the airline treats people. For the reply itself, our guide on how to respond to negative tweets sets out the sequence on X.
The better reply. “We’re sorry this is still open. An approved payment should have reached you by now. We’ve passed your case to our refunds team today and will DM you by Friday with the payment date.” Short, specific, with a next step and a time.
2. US Airways sends an obscene image to a customer (Twitter, 2014)
What happened. In April 2014 a US Airways agent replying to customer complaints on Twitter meant to share a link to the airline’s customer feedback page. CBS News reported that an explicit photo was shared instead, and that the same link went to a second traveler. The airline apologized: “We apologize for an inappropriate image recently shared as a link in one of our responses. We’ve removed the tweet and are investigating.”
What went wrong. A process failure. An agent working through complaints pasted the wrong link. Nobody checked a public reply before it went out.
The better reply. The apology was fast and plain, which limited the damage. The fix sits upstream: saved replies for common links, no copying links out of the inbound feed, and a second look before anything with an attachment or URL is posted.
3. United’s CEO apologizes for having to “re-accommodate” customers (Twitter, 2017)
What happened. In April 2017 a passenger was forcibly removed from an overbooked United Express flight, and videos of it spread across social media. Money reported that CEO Oscar Munoz’s first public statement said: “This is an upsetting event to all of us here at United. I apologize for having to re-accommodate these customers.” An internal letter to staff said a passenger “refused” to deplane. The phrase “re-accommodate” was widely mocked. A second statement on Tuesday said: “I deeply apologize to the customer forcibly removed and to all the customers aboard. No one should ever be mistreated this way.” Money reported the stock fell as much as 4% that Tuesday before closing down 1.1%.
What went wrong. The first statement was written in company language and centered the company’s feelings. It apologized for a procedure, not for what people had watched happen.
The better reply. The second statement, sent first. On social media the first version is the one people quote, so it has to be the one that names the person affected and says what will change.
4. Applebee’s argues with its own Facebook page overnight (Facebook, 2013)
What happened. In early 2013 an Applebee’s server was fired after posting a customer’s receipt online. Applebee’s posted a statement on Facebook, and the comments piled up. A photo essay by blogger R.L. Stollar, which captured the page through the night, shows the company posting a long reply as a comment at 2:53 a.m., then pasting the same response again and again while tagging individual commenters. Users said their comments were being deleted and they were being blocked. Applebee’s spokesman told NBC News: “At no point was this done to mislead or delete comments, we simply couldn’t keep up,” and called it “a learning experience for us.”
What went wrong. Three things. Arguing in the comments. Copy-paste replies that read as a bot. And moderation that looked like censorship, whatever the intent.
The better reply. One clear update posted as its own status, pinned, and then silence in the comment thread except for genuine questions. If a thread cannot be staffed, say so in the post rather than letting replies stop at random. The same rules apply to reviews, which our guide on how to handle negative reviews on Facebook covers.
5. Amy’s Baking Company fights its critics on Facebook (Facebook, 2013)
What happened. After Amy’s Baking Company appeared on Gordon Ramsay’s Kitchen Nightmares in May 2013, the owners answered critics on the restaurant’s Facebook page. HuffPost reported that the posts were aggressive and insulting. Once the posts were removed, the owners said their accounts had been hacked. CBS News covered the follow-up, including the hacking claim and an announced grand reopening.
What went wrong. The owners took criticism personally and replied as themselves, in anger, on a business page. Then they denied it, which made the story last another news cycle.
The better reply. Owners should not run the account in a crisis. A single calm post acknowledging the feedback, and no replies to individual attacks, would have let the attention pass.
6. Nestlé’s moderator tells critics “it’s our page, we set the rules” (Facebook, 2010)
What happened. In March 2010 Greenpeace campaigners protested Nestlé’s palm oil sourcing on the company’s Facebook page, many using altered Nestlé logos as profile pictures. Salon reported that the page’s moderator warned that posts using altered logos would be deleted, told one commenter “Consider yourself embraced”, and wrote “it’s our page, we set the rules, it was ever thus.” The moderator later posted that they had “stopped deleting posts, and I have stopped being rude.”
What went wrong. Sarcasm and threats to delete, from an account that speaks for a global brand, during an organized campaign. It gave the campaign a second story.
The better reply. Acknowledge the concern, point to the company’s position or commitments in one post, apply community rules quietly and consistently, and never be sarcastic. The subject of the campaign was a sourcing question. The moderator made it a question about how Nestlé treats its critics.
7. McDonald’s invites stories and gets complaints (Twitter, 2012)
What happened. In January 2012 McDonald’s promoted the hashtag #McDStories, hoping customers would share happy memories. ABC News reported that users filled it with complaints about food quality and service instead. The company’s social media director said “#mcdstories did not go as planned” and that it was pulled after less than two hours of promotion.
What went wrong. The brand asked an open question on a public channel without asking what its unhappiest customers would say. Every complaint was now filed under the brand’s own hashtag.
The better reply. McDonald’s did the right thing afterward: it pulled the promotion quickly and spoke plainly about it. The lesson is before launch. A support team that reads the brand’s mentions every day knows what people will post when invited.
8. United Breaks Guitars (YouTube and Twitter, 2009)
What happened. Musician Dave Carroll’s guitar was damaged in United’s baggage handling at Chicago O’Hare in 2008. NBC News reported he tried for months to get United to pay the repair cost, estimated at $1,200, and was refused. In July 2009 he posted a song about it on YouTube. Harvard Business School’s Working Knowledge reports the video had 4.6 million views by the end of that month. United then responded on Twitter: “This has struck a chord w/us and we’ve contacted him directly to make it right.”
What went wrong. A $1,200 claim was handled by the rules for months and only taken seriously once it went public. The failure was in the private channel. Social media is where it surfaced.
The better reply. The one United eventually gave, much earlier. Any complaint that has bounced between departments for weeks should go to someone with authority to settle it, before the customer finds a bigger audience.
What the eight have in common
| Case | Channel | Core mistake |
|---|---|---|
| Lufthansa | X | Scolding a customer for repeating an unresolved complaint |
| US Airways | No check on a public reply | |
| United, 2017 | Twitter and statements | Corporate language instead of an apology |
| Applebee’s | Arguing, copy-paste replies, moderation that looked like censorship | |
| Amy’s Baking Company | Owners replying in anger, then denying it | |
| Nestlé | Sarcasm and threats to delete | |
| McDonald’s | An open invitation without reading the room | |
| United Breaks Guitars | YouTube | A private complaint left unresolved until it went public |
Read together, they point to a short list of rules for any team answering customers in public:
- Answer the problem, not the tone. Angry customers usually have a real, unresolved issue underneath.
- Be specific. A case number, a named next step and a date do more than any apology phrase.
- Move details to private messages, but keep the public reply useful. Anyone reading the thread later should see that the brand responded properly.
- Never argue, never be sarcastic, never delete criticism that is within the rules.
- Check before posting. Links, attachments and anything written in a hurry.
- Escalate anything that has already failed once. A repeat complaint is a signal, not a nuisance.
- Staff the channel for the hours your customers post. Many of these failures happened at night or in the first hours of a story.
Our guide to how to handle customer complaints goes further on the private side of the process, and social media customer service strategies covers staffing and tone.
How Atidiv handles social media support
Atidiv runs social media customer support for consumer brands in the US, UK and Australia: trained agents who answer comments, mentions and messages across your channels, with complex replies routed through your approval workflow. Across our customer experience work we hold an average QA score of 98% and a 4.8 average CSAT, and deliver a 60% cost saving against an in-house team. Coverage extends to messaging support and the wider customer experience program, and the work is integrated into your wider CX processes.
Frequently asked questions
What counts as bad customer service on social media?
Ignoring complaints, replying slowly, arguing or being sarcastic, deleting criticism, sending copy-paste replies that do not answer the question, and posting without checking. The worst cases usually combine a real unresolved problem with a reply that makes it public and personal.
Should a brand delete negative comments on social media?
Not if they are within the platform’s and the page’s published rules. Deleting fair criticism tends to create a second complaint about censorship, as Applebee’s and Nestlé found. Remove only spam, abuse or private data, and apply the rules the same way every time.
How fast should a brand reply to a complaint on social media?
As fast as the channel’s audience expects, and within the hours customers are posting. Set a response target per channel and staff to it, including evenings and weekends if that is when complaints arrive.
Should complaints be moved to direct messages?
Yes for account details and personal data, but the public reply should still acknowledge the issue and say what happens next. Lufthansa’s case shows the risk of treating a DM thread as closed when the customer’s problem is still open.
What should a brand do after a social media complaint goes viral?
Post one clear, human statement that names the problem and the fix, then follow through where people can see it. Do not argue in the replies, and do not issue a corporate statement first and an apology second.
Ayushi leads Customer Experience services at Atidiv with a strategic/operations-focused mindset. Her primary objective is to increase how well businesses deliver service and retain customers. She evaluates customers' journeys through marketing impact, performance metrics, and gaps to develop improved systems and processes. With a reputation for curiosity and structured thought processes.