Social / Posts / Detail: Inbound Signals
17h+6 SLABack to parent list
Listening Triage Moderation Decision AE Escalation
Social Post
Collapse / Expand
Social Post is the operational workspace for social posts within social operations, where teams manage concrete records, dependencies, and execution decisions rather than static summaries. The business and compliance goal is to keep post detail aligned with approved claims, consent controls, market rules, and audit evidence at every step. This page presents role-scoped actions, linked downstream impacts, and policy-aware guardrails so users can work quickly without violating promotional or safety obligations. Next, use this social posts workspace to execute governed tasks and route outcomes to connected teams.
Access Boundaries
SSO + RBAC/ABAC controls are evaluated by brand, market, function, agency zone, and risk tier before actions are enabled.
Field Surfaces: Approved-only enforcedExternal Partner: Submit-onlyRisk Tier Scope: Low/Moderate/High/Critical
Social / Posts / Detail: Moderation Throughput
24h+2 SLASocial / Posts / Detail: Policy Flags
31h-2 SLASocial / Posts / Detail: Archive Completeness
38h-6 SLASocial / Posts / Detail: AE Mentions
45h+7 SLASocial / Posts / Detail: Escalation SLA
4h+3 SLAPOST SOC-0006
Status
Draft
Market
ES
Risk Tier
High
Owner: Medical
Operational Focus
- Triage inbound interactions by risk.
- Route potential AE signals to safety.
- Maintain moderation audit evidence.
What To Do Next
- Process pending moderation items.
- Escalate high-risk signals.
- Close resolved threads.
Social Operations Studio
Operate listening, moderation, and archive workflows with compliance and PV escalation controls.
| ID | Title | Market | Owner | Status | Risk | Related |
|---|---|---|---|---|---|---|
| SOC-0001 | Social / Posts / Detail · Listening signal 1 | IT | Community Ops | Escalated | Moderate | Moderation QueueAE Intake |
| SOC-0002 | Social / Posts / Detail · Moderation decision 2 | ES | Compliance | Draft | High | Moderation QueueAE Intake |
| SOC-0003 | Social / Posts / Detail · Publishing item 3 | JP | PV Liaison | In Review | Critical | Moderation QueueAE Intake |
| SOC-0004 | Social / Posts / Detail · Archive record 4 | AU | Community Ops | Approved | Low | Moderation QueueAE Intake |
| SOC-0005 | Social / Posts / Detail · Listening signal 5 | BR | Compliance | Active | Moderate | Moderation QueueAE Intake |
| SOC-0006 | Social / Posts / Detail · Moderation decision 6 | MX | PV Liaison | Blocked | High | Moderation QueueAE Intake |
| SOC-0007 | Social / Posts / Detail · Publishing item 7 | SG | Community Ops | Escalated | Critical | Moderation QueueAE Intake |
| SOC-0008 | Social / Posts / Detail · Archive record 8 | US | Compliance | Draft | Low | Moderation QueueAE Intake |
| SOC-0009 | Social / Posts / Detail · Listening signal 9 | CA | PV Liaison | In Review | Moderate | Moderation QueueAE Intake |
| SOC-0010 | Social / Posts / Detail · Moderation decision 10 | UK | Community Ops | Approved | High | Moderation QueueAE Intake |
| SOC-0011 | Social / Posts / Detail · Publishing item 11 | DE | Compliance | Active | Critical | Moderation QueueAE Intake |
| SOC-0012 | Social / Posts / Detail · Archive record 12 | FR | PV Liaison | Blocked | Low | Moderation QueueAE Intake |
Page-Specific Data
Social data combines listening streams, moderation outcomes, and escalation traces. Current page path: /social/posts/SOC-0006.
Relationship Graph
Linked entities are enabled so users can traverse parent-child dependencies and downstream impacts without manual lookup.
Social Tools
Classify inbound social signals.
Record moderation outcome and reason.
Route potential AE mentions to safety.
| Execution Step | Owner | ETA |
|---|---|---|
| Validate input | Ops | 5m |
| Policy checks | Compliance | 8m |
| Route next action | Workflow | 3m |
Social Listening + Moderation
Streams aggregate comments, DMs, and forms with triage routing to compliance and PV where required. Moderation decisions are logged with outcome and timestamp.
Governance Notes
- Every approval, publication, policy block, and AI output writes an audit event.
- Consent and frequency caps are evaluated before deployment packaging.
- Expiry and withdrawal controls maintain cross-channel evidence status.
- Safety routing is always flag-and-route with human adjudication.
Geo Coverage
US1,820 active
UK640 active
DE550 active
JP730 active
BR500 active
AU320 active
Seed Coverage Summary
brands: 8campaigns: 30briefs: 200assets: 6,000components: 20,000claims: 2,500references: 8,000markets: 12localizationJobs: 1,500mlrPackages: 15,000reviewSteps: 60,000annotations: 200,000interactionsRollup: 2,000,000socialSignals: 50,000aeSignals: 1,500experiments: 5,000reports: 3,000connectors: 250auditLog: 300,000