Replying to customer complaints on X as a small team

A prospective customer who sees a complaint and a fast, honest reply learns two things: the product has bugs, like every product, and the person behind it shows up. The second lesson outweighs the first. A complaint with no reply teaches the opposite, and a defensive reply teaches something worse.

The rules for a small team are different from a brand account's. You can say "that's on me". You can give a time estimate. You can refund on the spot. Use that freedom. The reply should sound like the person who built the thing, because it is, and that is exactly what a corporate support voice can never offer.

First reply, in public, within the hour: That's on me. I can reproduce it, the fix goes out this afternoon and I'll reply here when it's live. DM me your email if you'd like this month refunded either way. Same thread, when it ships: Fixed and deployed. Thanks for the clear report; the test now uses your exact steps.

• A bug you can reproduce

  Copy

  That's on us, sorry. I can reproduce it. Fix going out within the hour; I'll reply here when it's live so you don't have to check.

  Why it works:

  Ownership, confirmation, a time, and a promise to close the loop in public. Four things in two lines.

• Cannot log in

  Copy

  Sorry about that. Can you DM me the email on the account? I'll look right now. Not asking for anything else, just that.

  Why it works:

  Moves the private detail to DM and says exactly what you need, which reassures a customer who is already annoyed.

• Numbers look wrong

  Copy

  Thanks for flagging. The follower count comes from the platform's API and lags by about a day. If it's off by more than that, something's wrong on our side. Which is it for you?

  Why it works:

  Explains the likely cause, states the threshold where it becomes your bug, and asks a question that sorts the two.

• It is slow

  Copy

  You're right, imports over a few thousand posts are slow right now. It's the top thing I'm working on. Expect it fixed by month end; I'll post when it is.

  When:

  A known limitation, not a surprise.

  Why it works:

  Agrees without hedging, says where it sits in the priorities, and commits to a public update rather than a private one.

Billing complaints carry more heat than bugs because money moved. Resolve the money first, explain second. A refund issued before the explanation is finished is the strongest sentence in the reply, and it is one a small team can actually say.

• Too expensive

  Copy

  Fair. It's $19 because every account costs me real API money each month. If it isn't worth that for you yet, cancel from Settings with no questions, and come back when it is.

  Why it works:

  Accepts the opinion, gives the honest reason for the price, and makes leaving easy. Making leaving easy is what makes people stay.

• Charged after cancelling

  Copy

  That shouldn't happen and I'm sorry. Refunding now; you'll see it in a few days. DM me the account email and I'll confirm it's done and find out why.

  Why it works:

  The refund is the first action, not the last. Then the follow-up and the promise to find the cause.

• Why is there no free plan

  Copy

  Because the API bill arrives whether or not you pay me. The trial is a week with everything turned on. If that isn't enough time to decide, tell me what you'd need.

  Why it works:

  A real reason instead of marketing language, and a question that treats the complaint as feedback.

Some complaints arrive as rants, some as accusations. The temptation is to correct the tone. Do not. Find the legitimate problem inside it, address that in full, and treat the rest with the calm of someone who has nothing to hide. Readers judge the reply, not the rant.

• A public rant

  Copy

  I read the whole thing and most of it is fair. The export bug cost you an afternoon and that's on me. Fixing it this week. The rest I'd like to hear more about, by DM or here, your choice.

  Why it works:

  Signals you read it, concedes the specific, commits to the fix, and leaves the channel choice to them.

• "This is a scam"

  Copy

  Not a scam, but I understand how a double charge looked like one. Both refunded. If you want to see the receipt I'll send it. Sorry for the scare.

  When:

  An accusation driven by a billing error.

  Why it works:

  Denies the accusation in two words, then spends the rest on the fix and on acknowledging how it felt.

• Threatening to leave

  Copy

  I'd rather you stayed, but go if it isn't working for you. If you tell me the one thing that would have kept you, I'll build it or tell you honestly why not.

  Why it works:

  No begging, no discount, a genuine question with an honest promise attached. Many people stay after this one.

• "Why can't it do this?"

  Copy

  It can't yet, and you're the fourth person to ask this month, which moves it up the list. Not promising a date. I'll reply here when it ships.

  Why it works:

  Honest about the gap, shows the request is being counted, refuses to promise what you cannot, commits to a public update.

• "The other tool does this better"

  Copy

  They do that better, honestly. What we do instead is read your own posts before suggesting anything. If the first thing matters more to you, they're the right pick.

  Why it works:

  Concedes the competitor's strength and states yours without a pitch. Recommending the competitor when they fit is the most trust-building thing you can say in public.

The follow-up is the reply most small teams skip and the one that does the most work. Coming back to a complaint thread to say it is fixed closes the loop for the customer, shows every later reader that complaints here get resolved, and turns a negative post into a small advertisement for how you operate.

• It is fixed

  Copy

  Fixed and live. Your import should finish in under a minute now. Thanks for the report, and sorry again for the afternoon.

  Why it works:

  Confirms, states the new behaviour, thanks and apologises in one line each. The thread now ends on a resolution.

• Checking in a week later

  Copy

  Following up on the login issue from last week: has it stayed fixed for you? If anything's off I'd rather hear now than find out when you leave.

  Why it works:

  Almost nobody does this. It costs one sentence and tells the customer, and the readers, that you remember.

1. 01Reply in public within the hour, even if the fix will take a week. Silence is read as absence.
2. 02Own the problem in the first line. "That's on us" or "You're right" before any explanation.
3. 03Give one fact: the cause, the time to fix, or the action you just took. One.
4. 04Move private details to DM and say exactly what you need from them.
5. 05Come back to the thread when it is fixed. Set a reminder; this is the step everyone forgets.

Support replies are a special case of a more general skill, taking pushback in public, and the broader version is in responding to criticism on X. For the founder's wider reply habit, the examples in X replies for founders cover the conversations that happen outside your own threads. And when a complaint turns out to be bad faith rather than a real problem, replying to trolls covers when to stop.