Community Management Replies and Escalation, Not Ads

Community management on this page is conversation ops: reply protocol, escalation, and groups or threads you will staff. It is not GBP reviews, not ASO ratings, and not SMM campaigns.

Buyers say “community” when they mean posting a calendar. Posting is social content strategy and flights are social media marketing. This H1 is what happens after someone speaks.

The SMO hub still decides whether community is in the program. Network children still own discovery objects. This page owns the ladder.

A paragraph that still works after swapping this H1 for “GBP reviews” is deleted. Maps review replies stay on Google Business Profile.

The protocol names first response owner, tone, and the escalation to legal, support, or brand. It is not a public “reply in X minutes” SKU unless the client already staffs that clock - and even then it is staffing, not a sold SLA product on this page.

Ads comments can route here; moderation as spend stays on social advertising. This page does not become Ads Manager.

YouTube comments on the organic channel can route here. In-stream comment culture on **paid YouTube inventory on YouTube ads** is not this OS.

Groups, Discord-like spaces, Facebook Groups, X communities, LinkedIn comments, IG DMs, Page Messenger: only if you moderate. Unstaffed Groups are refused as “community.”

Facebook marketing may name a Group as a discovery object. This page takes it only with a moderator RACI.

DMs that are sales are a CRM route. DMs that are abuse are legal. Do not treat every inbox as a campaign.

We will not pretend a ghost Group is a community.

Google Business Profile is Maps: hours, categories, review replies on the listing. Facebook recommendations are not that queue.

App store ratings, in-app prompts, and Console/Connect review replies are app ratings and reviews under frozen ASO.

SMM still plans flights. Community may staff a flight’s comment thread. Community will not write the campaign contract.

Influencer comments on a creator post may be staffed here if contracted; the brief stays on influencer marketing.

No purchased comments, likes, or pods. Fake engagement is refused.

Crisis and legal takedown are a route to counsel and platform tools - not a “crisis community product” with a 48-hour web promise.

No AI-citation product. No claim that replies rank Google.

If the client wants only campaigns, open SMM. If they want only Maps reviews, open GBP.

After-hours coverage is staffing, not a follower SLA.

Language coverage on replies is a ship list, not a localization SKU.

Who holds admin on each Group is access hygiene.

Keyword alerts for brand risk are a listen note, not an ads audience.

If community is dropped from the program, this page’s job ends.

Conflict logs: a public reply that contradicts Page About is a field-pass plus this child.

Pinning a reply is a network object; pinning a product flight is SMM.

User-generated content rights are legal; UGC as ads is advertising plus influencer if paid.

We will not sell “N replies per day” as a package.

YouTube Studio community tab is organic-channel UX on YouTube marketing; comment SLA can still sit here.

Review screenshots from GBP must not be answered as if they were Facebook reviews.

Play Console review replies must not be answered as if they were IG comments.

Ban and mute lists are moderation, not Campaign Manager exclusions.

The escalation phone tree is internal. It is not a public SLA badge.

Seasonal volume (launches) is a staffing forecast, not an SMM flight.

The first-response owner for exec personal accounts you stand behind must be named, or those accounts stay out.

Reply and escalation ops is the object of this page: who replies, on which staffed surfaces, when a comment becomes a ticket, and a refusal of purchased engagement. It is not Google Business Profile review management. It is not ASO ratings APIs. Reply and escalation ops is conversation, not Maps and not store stars.

GBP review queues stay on Maps. Reply and escalation ops may contrast Facebook or Instagram comments with GBP, then stop. Hours, NAP, and Maps replies are not this H1. SMO already put community in the program. This child runs the ladder after that door.

In-app review prompt APIs and Play or Apple public replies stay on app ratings and reviews inside ASO. Reply and escalation ops will not become SKStoreReviewController documentation. Store ratings are not social comments, and Maps reviews are not this ladder either.

Organic campaign planning is not reply and escalation ops. Social media marketing owns unpaid flights. Comments that arrive because a flight worked still climb this ladder. Campaign calendars do not, and neither do bio-field passes pretending to be support on reply and escalation ops.

Ads Manager comment threads are not reply and escalation ops as a spend product. Social advertising owns the paid social auction. Moderation of ad comments still uses this ladder.

Facebook Page discovery is not reply and escalation ops. Facebook marketing owns Page search versus GBP. Groups you cannot moderate stay off the engagement. Groups you staff are surfaces on this ladder, not a Page-category treatise and not a Maps hours grid.

Instagram DMs and comments you will staff sit on reply and escalation ops as surfaces. Instagram marketing still owns grid and Reels discovery.

LinkedIn comment threads on a Company Page you staff sit on reply and escalation ops. LinkedIn marketing owns Company Page organic findability. Being found is not the same as who is allowed to speak for the brand in-thread, and Showcase architecture is not this ladder.

YouTube community tab and video comments you will staff sit on reply and escalation ops. YouTube marketing owns Studio channel organic. This ladder is not playlists, not chapters, not Ads Manager, and not YouTube ads on reply and escalation ops.

X replies as discovery versus ops: X marketing may name lists and replies as findability. Reply and escalation ops owns when a reply becomes an incident. Keep the nouns apart so leftover clones cannot steal both URLs with one “engagement” essay.

The social native calendar OS may refuse to schedule a format you cannot moderate. Social content strategy owns the week. Reply and escalation ops still writes the ladder. Calendar without ops ships unstaffed risk. Ops without a week is not a content OS.

Creator comment storms still use reply and escalation ops when they land on surfaces you control. Influencer marketing owns the brief. The ladder is not a usage-rights clause, not a disclosure tag, and not a fake-endorsement product on reply and escalation ops.

The field pass is not reply and escalation ops. Social media optimization ships about fields. Updating a bio during a thread is not the protocol.

Crisis and legal takedown is a route on reply and escalation ops, not a productized legal SKU. Purchased comments, farms, and fake engagement are refused. We will not sell a volume of replies as a package, a follower SLA, or a Maps-rank claim.

The deliverable is a staffed conversation protocol with named surfaces, named escalation, a hard refusal of bought engagement, and GBP, ASO ratings, and campaign planning left on their doors.