Social Media Customer Service

Support with an audience

Every other support channel is a private conversation. Social media is a support conversation other customers are reading, and often screenshotting.

That changes the economics of a single interaction. A well-handled public complaint demonstrates to everyone watching that you fix things. A badly handled one - or worse, an ignored one - becomes the evidence people cite. The same failure that costs you one customer by email can cost you the confidence of thousands here.

RHI provides dedicated agents handling social media support with the escalation discipline that public channels require.

Support, not community management

These are different jobs and conflating them serves neither well. Community management is about building an audience: content, campaigns, tone of voice, engagement. Social media support is about resolving the problems that arrive in your mentions and inbox.

We do the second. We handle inbound contact - questions, complaints, faults, order queries - across the platforms you use, and we work to your escalation rules on anything that touches reputation. We do not write your content, run your campaigns or manage your posting schedule.

Where you have a marketing team owning the account, we work alongside them with a documented split: which contact types we answer, which we route to them, and who speaks when something becomes a public issue rather than a support case.

The public-to-private rule

This is the single most important thing to get right.

Some things should be answered publicly. A question about opening hours, a general how-to, a widely reported fault - answering in the open helps everyone watching and reduces further contacts. Answering that privately wastes the opportunity.

Other things must move private immediately. The moment a conversation needs an account number, an address, an order reference or any personal detail, it moves to a direct message before those details are requested - not after. Customers will happily post an order number and a postcode in a public reply if asked, and the mistake is the agent's for asking.

The rule we train is: acknowledge publicly, resolve privately, and where the resolution is useful to others, close the loop publicly without the personal detail. That last step is frequently skipped and it is what turns a resolved complaint into visible evidence that you resolve complaints.

What the team handles

• Mentions and comments - including on posts you did not make.
• Direct messages - where most actual resolution happens.
• Reviews and recommendations - where the platform supports them.
• Complaints - captured against your process, with the public thread and private resolution linked in one record.
• Order, delivery and account queries - the routine volume.
• Escalation to phone or email - where a case has outgrown the channel.

Response time expectations

Public channels are less forgiving on timing because the delay is visible. An unanswered complaint from four hours ago sits there with a timestamp on it, and other customers draw conclusions from the gap.

Volume arrival is also spikier than any other channel, because it follows events rather than routine: an outage, a promotion that went wrong, a delivery failure at scale, or a post that got attention. Coverage designed only for average volume will be visibly absent on the days that matter, which is why social benefits from overflow arrangements more than most channels - see after-hours and overflow support.

Escalation and reputational risk

Agents need clear, trained rules for the contacts that are not really support cases. We agree before launch what happens with an allegation of serious harm, a legal threat, press or influencer contact, a coordinated campaign, a safeguarding concern, and anything alleging discrimination or safety failure.

Those escalate immediately to a named person on your side rather than being handled by the agent, regardless of hour. The rule for the agent is deliberately simple: acknowledge without commenting on substance, and escalate. An agent improvising a response to a legal threat in public is a bad afternoon for everyone.

We also agree what we do not do - abuse and trolling get a documented threshold for when to stop engaging, and agents are not asked to absorb it indefinitely.

Platforms, systems and languages

Our teams work across the major platforms' business inboxes, and in your social management or help desk platform wherever you have one, so social contacts sit in the same customer record as phone, chat and email - see technology and omnichannel support.

From India we staff English, Hindi, Hindi-English bilingual, Bengali, Nepali and Punjabi, with further Indian languages on request. Written register matters especially here: a public reply is read by people who are not the customer, so tone carries further than usual.

Quality and reporting

Reporting covers first response time on public and private separately, resolution rate, public-to-private conversion, escalation volume by category, and sentiment trend. Public-to-private conversion is the one we watch hardest: if personal details are appearing in public threads, the rule is not being followed and that is a data protection issue rather than a style problem.

Interactions are sampled and scored against an agreed scorecard, with the public-to-private rule scored pass-or-fail. See quality assurance. Figures published elsewhere on this site are historical or representative and campaign-dependent.

Getting started, and what it costs

Priced per dedicated agent per month with a five-agent minimum, in the same band as chat and email - published rates and what moves them.

Bring your current mention and message volume, your worst recent spike, and your existing escalation contacts. The spike is the number that determines whether overflow cover is worth arranging. Related: WhatsApp support, live chat support. Talk to us.