Classify the incoming request

Separate routine product questions, complaints, billing issues, safety concerns and abusive content. Define which questions can be answered publicly and which require identity verification or sensitive details.

Never request account numbers, payment details or private health information in a public comment. Acknowledge the issue in plain language and explain the next secure step without promising a resolution you cannot deliver.

Make the handoff explicit

Use a short public response that names the appropriate private channel and what the customer should include. Where platform messaging is unreliable, offer a secure website form or established support channel.

Create an internal case identifier and link the public interaction to the private conversation without copying unnecessary personal data. Confirm who owns the case after the move.

Protect expectations and consent

Tell the customer when they can expect a response and what the channel is for. A support DM is not automatic consent to marketing messages or retargeting.

Use minimum necessary information, role-based access and a documented retention process. If the case involves threats, fraud or impersonation, route it through the escalation procedure instead of an ordinary marketing inbox.

Set response rules

Create templates for acknowledgement, verification, escalation and closure, but leave room for a human response. Staff should not debate private account details in public or copy-paste generic apologies repeatedly.

Define service windows and escalation triggers. If the issue cannot be solved in social messaging, hand it to the support system with a named owner and a clear next action.

Measure resolution rather than activity

Track first-response time, handoff completion, unresolved case age, repeat contacts and customer-confirmed resolution. High reply volume is not evidence of good service if cases keep reopening.

Sample cases weekly to identify missing context, duplicate tickets and customers who were told to DM but never received a reply. Review quality alongside speed.

Prepare for incidents

Maintain an escalation route for public misinformation, privacy exposure and rapidly spreading complaints. Preserve necessary evidence securely, coordinate with the relevant team and avoid deleting legitimate criticism merely because it is uncomfortable.

Review the playbook after staffing changes and platform inbox updates. The aim is to help a person reach the right team while keeping the public record accurate and the private exchange appropriately protected.

Support handoff example

A customer posts publicly that an order has not arrived. Acknowledge the concern without asking for an order number in public, then direct the person to an approved private support channel. The support agent verifies identity and owns the follow-up.

If the conversation is transferred again, retain the case context securely. Measure whether the customer received a resolution, not simply whether the social team sent a response.