Customer Service on X (Twitter): A Small-Team Playbook

Customer service on X means working three inbound streams — @mentions and replies, quote posts, and DMs — using the platform's own notification and search tools, because X gives you no ticket queue, no assignment system, and no shared status on a conversation. For a two-person team the goal is not to monitor everything, but to build a handful of filters and habits that surface the messages needing a human within a few hours and let the rest wait without anyone feeling ignored.

Most advice here assumes you have bought a support suite. This playbook assumes the opposite: two people, native X only, a shared phone rota. The moving parts are notification filters, a twice-daily search sweep, a snippet file, a clean public-to-DM handoff, and enough proactive posting that the queue shrinks before it forms.

What "responsive" means on X

A public complaint on X is visible immediately to anyone who checks your handle, and quote posts let it travel without ever landing in your mentions. Customers who post to a brand here expect same-day acknowledgement, and the already-angry ones expect it within hours — not because X publishes a rule, but because everyone can see how long your last reply took.

You cannot staff every hour, so pick targets you can hit on a bad day and publish them. A line in your bio — "Support: Mon–Fri, 9–18 CET, usually within a couple of hours" — beats quietly trying to be instant. A workable table for two people:

The number customers feel is acknowledgement, not resolution. "On it — checking your account now, back to you within the hour" buys you real time. Silence spends it. If you want the platform-agnostic version of this discipline, our broader social media customer service playbook covers SLAs, tone, and escalation across every network.

Step 1: Make X notifications usable

The default Notifications tab mixes likes, follows, and reposts into the same stream as the person telling you their order never arrived. Fix that first.

• Work the Mentions tab, not the main feed. As of July 2026, X separates mentions into their own tab. That tab is your queue; the main feed is something you check when you have time.
• Turn on the quality filter and advanced notification filters. Under Settings → Notifications → Filters you can mute notifications from new accounts, accounts with a default profile photo, and accounts that have not confirmed an email or phone number. These catch most bait waves without hiding real customers, who tend to have real profiles.
• Mute words that generate noise but never need support — giveaway spam, crypto shilling, whatever bot phrase attaches to your niche. Muted words can be set to expire, useful during a campaign.
• Push notifications on one phone at a time. The person on shift gets mentions and DMs pushed; the other turns them off. Two people half-watching is how a message sits for six hours while each assumes the other has it.

Aggressive filters will occasionally hide a genuine customer with a new account. That is why the next step exists.

Step 2: A twice-daily sweep for what notifications miss

Plenty of people complain about a brand without tagging it — they type your name, misspell it, or reference the product without the handle. None of that reaches your mentions. Two native tools close the gap.

Search, saved. Run searches for your brand name without the @, your product names, and the two most common misspellings. Add -from:yourhandle to strip out your own posts, and sort by Latest rather than Top. X lets you save a search from the results menu, so build them once and tap through them. Our guide to monitoring brand mentions on X goes deeper on query construction and triage.

A private List of the accounts that matter — frequent posters about you, power users, resellers, partners, and the two or three industry accounts whose complaints travel. A List gives you a chronological feed no algorithm reorders; how to use X Lists walks through setup and pinning.

Ten minutes in the morning, ten in the afternoon, both people knowing which slot is theirs. Not glamorous, and the highest-yield habit here.

Step 3: Snippets, because X will not give you macros

Native X gives ordinary accounts no saved-reply library and no shared canned-response store. Build your own in whatever both of you can reach in two seconds — a pinned note, a shared doc, a text expander with short triggers. Write these seven first:

• Holding reply — acknowledges, sets a time, promises a follow-up.
• Account lookup — asks them to check DMs, never asks for personal details in public.
• Known issue — plain-language status plus where updates will appear.
• Refund or returns process — the steps, with the link.
• "We don't do that, here's what we can do" — the graceful no.
• Feature request thanks — genuine, no false promises.
• Escalation holding — what happens next and by when.

Two rules keep snippets from sounding like a bot. First, rewrite the opening line every single time with their name and their specific problem; the snippet supplies the middle, not the greeting. Second, store a short public version and a longer DM version of each, since a public reply has to fit the post limit while a DM has far more room — our social media character limits reference has the current numbers per platform.

Step 4: The public-to-DM handoff

First, check that DMs are actually open: Settings → Privacy and safety → Direct Messages, allow message requests from everyone. Replying "DM us!" when non-followers cannot message you is a self-inflicted wound, and it happens constantly. Then the sequence:

1. Reply in the public thread first. Acknowledge, apologise if one is owed, say you have sent a DM.
2. Send the DM immediately — same minute, not after lunch. The public reply is a promise with a short shelf life.
3. Resolve privately, where you can ask for an order number or email without publishing it.
4. Leave the public thread ending on action, not on your unanswered request.

Move to DM when you need personal data, when you are offering a resolution you do not want every future complainer to see, or when a public back-and-forth is drawing a crowd. Stay public when the answer helps everyone reading — shipping timelines, compatibility, "yes, that's included." Our guide to managing DMs and comments has the wider workflow.

Step 5: Shrink the queue before it forms

The cheapest support ticket is the one nobody sends. Two kinds of posting do that work.

Status posts. When something is broken, late, or changing, post it before the mentions arrive and pin it. One clear post kills a large share of duplicate questions and changes the tone of the rest from "is anyone there?" to "any update?"

FAQ posts. Take the questions you answer every week and write each as a standalone post. Your reply then becomes a sentence plus a link, not a retyped paragraph. Rotate them so newer followers keep seeing them.

This is where a scheduler earns its keep, and where I should be straightforward about what SocialKit is: a publishing tool, not an inbox. There is no unified social inbox, no listening feed, no comment-moderation queue — mentions and DMs stay in X, handled natively as above. What it does do is let you batch a quarter of FAQ posts in one sitting, drop them onto a visual calendar, and auto-publish across the 11 platforms it supports, customising each caption so the X version reads like X (scheduling X posts covers the mechanics). Live outage updates still get typed by hand, but the FAQ backbone can be built months ahead — and it doubles as growth content, since the tactics in growing on X and your support posts are largely the same material written twice.

Step 6: Know where support ends and crisis begins

Individual replies stop working past a certain point, and two people can burn a day failing to notice. The signals:

• Several unrelated accounts raise the same issue within an hour.
• A quote post travels well beyond your normal reach.
• A large account or journalist picks it up.
• The replies stop being about the problem and start being about you.

Switch modes then: stop replying individually, publish one clear statement, pin it, and point every reply at it. Assign one voice — the other person handles everything unrelated so normal service does not collapse. Our social media crisis management guide covers holding-statement structure and the decisions worth making before you need them.

Two standing rules at any scale: never argue in public, never reply to bait. You will not win either exchange, and the audience is scoring grace, not accuracy.

Two people, actual coverage

Coverage fails on handoffs, so write the handoff down — three lines at the end of each shift: public threads awaiting a reply from us, DMs waiting on us versus waiting on the customer, and anything simmering that could grow overnight.

Then a 20-minute weekly review: inbound counts by type, which question repeated enough to deserve its own FAQ post, which snippets are landing badly, and what recurring complaint belongs in front of whoever builds the product. Ten identical complaints are not ten tickets — they are one operations problem wearing ten costumes.

Start here: your first week

1. Monday — Turn on the quality filter and advanced filters, mute your top three noise phrases, make the Mentions tab your queue.
2. Tuesday — Confirm DMs are open to everyone; publish your support hours in your bio.
3. Wednesday — Build four saved searches and one private List, then run the first sweep.
4. Thursday — Write the seven snippets, public and DM versions.
5. Friday — Draft ten FAQ posts from this week's questions and schedule them across the next month.
6. Following Monday — Agree the shift rota, the three-line handoff, and the weekly review slot.

None of this needs a support platform, a seat licence, or a third person. It needs a decision about what you respond to, how fast, and who is holding the phone. If the scheduling half of that week is the part you would rather not do by hand, SocialKit runs a 7-day free trial and every plan includes all 11 platforms with unlimited scheduled posts — plans and pricing are flat as of July 2026, from €29/month for Solo (€17.40/month billed annually).