Owner, trigger and scope
The community manager on shift works the inbox from start to finish and is the only person who closes items in it during that shift. The customer service lead takes every service case the inbox passes on, from a late order to a faulty product, and owns it until it is resolved. The social media lead decides escalations under the crisis plan and is the named decision owner when something looks bigger than the routine.
The trigger is the start of each working shift on the brand's social accounts. The procedure also starts outside a shift when an alert from listeningMonitoring public conversation about a brand, its category, competitors and the problems it solves, away from the brand's own accounts. or a colleague flags a comment, mention or message that needs someone now. The social media management hub gives community work one daily row in its routine table; this page is what that row looks like when one person runs it.
The scope is the brand's own accounts and the conversation that reaches them. Neighbouring jobs belong to other pages:
| Situation | Where it is handled |
|---|---|
| Writing the response standards, moderation rules and escalation paths | Community management guide |
| A problem that has outgrown the routine | Social media crisis plan |
| An error in a post, an ad or a page the brand published | Live ad and page error response SOP |
| Approving a reactive post or a statement | Social media approval workflow |
| Anything else that recurs on a schedule | The SOP library |
| Running a hosted group or forum | Running a brand community group |
| Asking to reuse a customer's post | User-generated content guide |
If the inbox shows signs that an account itself has been taken over, such as posts or messages nobody on the team sent, stop the routine and tell the social media lead at once; the compromised marketing account response SOP takes over from there.
Before you start: inputs and access
| Input | Owner | Notes |
|---|---|---|
| The unified inbox or each platform's notifications | Community manager | Every account the brand runs, including comments on ads |
| The published moderation rules and response standards | Social media lead | The written rules the audience can read and the team's own response commitments |
| The library of saved replies | Customer service lead | Built and reviewed as the saved replies tutorial describes |
| The escalation route and the crisis plan's severity levels | Social media lead | Names and deputies for the shift, including out of hours |
| The log or tags for contact reasons | Customer service lead | The same reason list the service team uses |
The tools differ by platform. Meta's Business Help Centre documents the inbox, automated reply and moderation tools on its platforms, and other platforms keep their own in their help centres; this procedure does not quote their screens, which change with each release. Whatever the tool, the community manager needs permission to reply, hide and remove on every account, and a way into the service team's queue and the lead route without asking anyone for access mid-shift.
The procedure
Open the inbox and read the last shift's handover note
Before answering anything, read the note the previous shift left: open threads, anything promised to a customer, items waiting on another team and anything being watched. Then check every account is connected and the filters are on, since a disconnected account is an inbox nobody is reading. The community management guide sets the cover hours and what the out-of-hours reply promises; the first replies of a shift usually honour that promise.
Sort each item: question, complaint, praise, lead, abuse or a possible issue
Work through every unread item and give it one of the six categories before replying to any of them. Sorting first shows the shape of the shift: a run of the same complaint, a burst of praise for a post, or a cluster that might be an issue. The community management guide's response standards table explains how each category is treated; this step only decides which row applies. When an item fits two categories, such as praise that contains a complaint, treat it as the more serious one.
Reply to questions and praise from the saved replies, adapted to the person
Answer questions in public where the answer helps others reading the thread, and link to the page that answers in full. Use the library of saved replies for facts and tone, then edit each one for the person: a reply that could have gone to anyone tells them nobody read their message. Thank people for praise in their own words, in the brand voiceThe consistent personality a brand expresses in its words across channels, with tone adjusting to the situation and the audience.. If a customer's post is worth sharing, ask permission through the user-generated content guide rather than reposting it.
Moderate by the published rules and record what was hidden or removed
Hide or remove only what breaks the published rules: spam, scams, abuse, threats, other people's personal details and the other categories the community management guide lists. Criticism stays up and gets an answer. Prefer hiding where the platform supports it and the rules allow, report scams to the platform, and release anything the filters caught by mistake. Record every decision in the moderation log with the rule it broke; threats and harassment of staff go straight to the named escalation owner, not to the next step.
Move complaints to a private channel and to the service team
Acknowledge the complaint in public, briefly and specifically, and offer a private route; then move the conversation to a direct message and open a case for customer service. The service recovery guide sets the principle: acknowledge in public, resolve in private, never argue or reveal order details in a thread. Saved replies are not used unchanged for complaints, and the customer service tone guidelines set the register. The case carries the thread link, the customer's words and what was promised.
Pass sales enquiries to the lead route
A request for a quote, a trade account, a booking or stock is a lead, not a service case. Reply so the person knows who will contact them, take their details in private and pass them to the route the inbound lead handling playbook describes, so the enquiry is assigned by the same lead routingRules that assign each new lead to an owner, queue or next step based on territory, segment, score or source. rules as a form and carries social as its source. Do not quote prices or terms the sales team has not published. A creator asking for free product or paid work is not a sales lead; tag the message and pass it to whoever owns creator work, following the guide to answering creator requests for free product and paid work.
Escalate anything that matches the crisis plan's triggers
Compare what the sort showed with the triggers in the social media crisis plan: the same complaint from people who do not know each other, a journalist or well-known account joining, any mention of safety, injury or personal data, or a post travelling beyond the brand's followers. When one matches, tell the social media lead directly, with links and a count of what you have seen, and follow the plan's first actions for your level, which may include pausing scheduled posts and using an approved holding statementA brief first public response in a crisis that acknowledges the issue, tells affected people what to do now and says when more will follow.. The RACI matrix in the plan says who decides; the inbox does not decide alone. Alerts from the listening set-up are checked against the same triggers.
Tag reasons, log the shift and write the handover note
Tag every item with its contact reason from the shared list, as the tutorial on tagging support contacts by reason describes, so social contacts are counted with the service team's. Complete the shift log, then write the handover note: open threads with links, anything promised and to whom, cases and leads passed on and still waiting, and anything being watched. The next shift starts from that note, so write it for someone who was not there.
A brewery's Saturday shift (illustrative)
A launch weekend, a damaged delivery and a faulty batch
Crembulay Brewery, an invented craft brewery, launched a new pale ale on Friday evening. Its weekend community manager opened the inbox at 10am to a handover note listing 2 open threads and 1 promised call-back. The sort found 64 items: 31 comments praising or asking about the new beer, 9 questions about stockists, 1 complaint about a damaged delivery, 1 enquiry from a pub asking to stock the range, 18 spam comments under the launch post and 4 posts about the same faulty batch of an older beer. The questions were answered from 6 saved replies, each edited for the person. The complaint was acknowledged in the thread, moved to a direct message and opened as a service case with the order details taken privately. The pub's enquiry went to the sales lead route tagged as social. The spam was hidden and logged under the rule on unsolicited promotion. Three of the batch posts came from people with no connection to one another, which matched the crisis plan's first trigger, so the community manager sent the social media lead the links within minutes. The lead set the plan's first level, paused a scheduled post promoting the older beer and approved a holding reply. The handover note listed the service case, the lead, the batch thread and the paused post.
QA checks
At the end of each shift the community manager confirms every check below before writing the handover note. Anything that fails goes into the note as an open item with a name against it.
- Every item in the inbox is answered, routed, moderated or deliberately left, with nothing unread.
- Removed or hidden content is recorded with the rule it broke.
- Complaints moved to private have a service case and an owner.
- Escalations went to the named decision owner, not to a group chat.
- The handover note lists open threads and anything promised.
Hand-offs and records
Customer service receives each complaint as a case with the thread, the customer's words and what was promised in public, and posts a public note when the case is resolved if the customer agrees. Sales receives each enquiry through the lead route with social as its source. The social media lead receives escalations directly, with the evidence, and decides the next step under the crisis plan. The next shift receives the handover note.
The record is the shift log: items by reason tag, replies sent, content hidden or removed with the rule, cases passed to service and sales, escalations raised and the handover note. Over a month the log shows which questions deserve a better saved reply or a clearer page, which moderation rule is used most, and which complaints recur. Those patterns go to the community health measures in the community management guide and to the owner of the saved replies library, rather than being fixed one reply at a time.
Common mistakes
Each of these turns a busy shift into a public problem or a lost customer.
- Replying before sorting. The pattern that signals an issue is only visible when every item has been read.
- Sending saved replies unchanged. A reply that ignores what the person wrote invites a second, angrier one.
- Arguing with a complaint in public. Acknowledge, move to private and resolve; the thread is read by everyone.
- Removing criticism. Only content that breaks the published rules comes down, and every removal is logged.
- Leaving a lead in the comments. A sales enquiry answered with a friendly reply and nothing else goes cold.
- Escalating to a group chat. Escalations go to the named decision owner, who may not be reading the chat.
- Skipping the handover note. Promises made on one shift are broken on the next when nobody wrote them down.
