Short answer
Save an X search that pairs your brand name, handle and domain with problem words such as "not working", refund, broken or "worst", exclude your own posts, and open it on the Latest tab several times a day. Add a second search for replies sent to your support account, and answer the most visible complaints first.
Key takeaways
- Many complaints don't tag you, so search the brand name and domain too.
- Pair the brand with problem words in one OR group to cut the noise.
- to:yoursupport shows every reply sent to your support account, answered or not.
- Triage by visibility and urgency: answer what others can see and what blocks a customer.
- Move details to DMs or email, but answer the public post first.
A complaint on X is public by default. A small one answered within the hour usually ends with a thank-you. The same complaint left alone for two days can turn into a quote post with thousands of views. The trick is seeing complaints early, including the many that never tag your account.
Why do you miss so many complaints on X?
Because notifications only show posts that tag your handle, and many unhappy customers just type your brand name.
People write "Acme's checkout is broken again" without @acme. Some link to your site. Some misspell the name. None of those reach your notifications. Searching is the only free way to catch them, which is also the starting point in our guide to monitoring brand mentions.
Which search finds complaints?
Pair your brand terms with a group of problem words, and exclude your own account.
(acme OR @acme OR url:acme.com) ("not working" OR broken OR refund OR "worst" OR "can't log in" OR cancel) -from:acme
Swap in your names and the words your customers actually use. Look at a few weeks of past complaints and copy their wording. Tips for the word list:
- Use phrases in quotes for multi-word problems:
"won't load","charged twice". - Keep the OR group in parentheses, or it will swallow the rest of the query.
- Add product names if people talk about a product more than the company.
- Exclude noise words with a minus, for example
-giveaway.
The query builder fills in the parentheses and minus signs for you and opens the result on the Latest tab.
How do you see everything sent to your support account?
Search to:yoursupport -from:yoursupport, which lists replies sent to the account, including ones you never answered.
The to: operator only matches replies, so this search shows every customer who replied to your support account's posts. Add a date to review a period: to:acmehelp -from:acmehelp since:2026-11-01. It's a fast way to find conversations that slipped through on a busy day. The operators cheat sheet explains to:, since: and until: in more detail.
How should you triage what you find?
Answer first what is most visible and what blocks a customer from using your product.
| Priority | Example | Response |
|---|---|---|
| 1. Blocking and visible | Can't log in, post getting replies | Public reply now, then DM |
| 2. Blocking, low visibility | Charged twice, few views | Reply within hours |
| 3. Annoyed, not blocked | Slow shipping, small bug | Same-day reply |
| 4. Venting or jokes | "Acme again 🙄" | Optional; watch for patterns |
To spot visible complaints quickly, run the same search with min_replies:5 or min_faves:20 added. Those are the posts other people are already reacting to.
If several complaints describe the same failure at the same time, you may have an outage, not a run of unhappy customers. The guide to tracking outage reports covers that case.
How do you reply to a complaint on X?
Acknowledge it publicly, move personal details to a private channel, and follow up in the same thread when it's fixed.
- Reply in public: thank them, say you're looking into it, and give a next step.
- Ask them to DM or email for account details. Never ask for order numbers, emails or payment details in a public reply.
- Fix the problem or explain what will happen.
- Come back to the original thread with a short update. Others who saw the complaint see the resolution too.
Keep replies human. Copy-pasted apologies read as automated, and X's automation rules don't allow automatically replying to posts found through keyword searches anyway.
How do you keep the complaint search accurate?
Review it every few weeks: add words customers use, remove words that only bring noise.
Language drifts. A new feature brings new ways for it to break, and new slang for being annoyed. Once a month, read through the complaints you found and the ones you heard about elsewhere, such as support email or reviews. If customers used a word your search doesn't include, add it. If a word keeps pulling in unrelated posts, remove it or exclude the context with a minus. Keep a copy of the old query in your notes so you can compare results before and after a change.
How often should you check for complaints?
Several times a day for active brands, at least once a day for small ones, at fixed times.
Save the search on X so it sits one tap away in the search box on every device. Assign it to one person per day, so it doesn't fall between people. A short daily log of what came in and what was done helps you spot recurring problems that should go to the product team, not just the support inbox.
Questions
Why don't I see complaints that don't tag my account?
X notifications only cover posts that mention your handle. Untagged posts that use your brand name or link to your site only show up if you search for them.
Should we reply publicly or by DM?
Reply publicly first so others can see the complaint was acknowledged, then move account details to DMs or email. Never ask customers to post order numbers or personal data in a public reply.
How fast should we respond to complaints on X?
As fast as your team can sustain. Many small teams aim for the same business day. Whatever you pick, say it on your support account's bio so people know what to expect.
Can we auto-reply to complaints that match our search?
No. X's automation rules don't allow automated replies to posts found by keyword search alone. A person should read and answer each one.