Frame the request
Confirm the campaign message, source rights, target channel, audience, and publishing objective
Marketing · Specialized agent role
Social Media Agent
The Social Media Agent adapts approved messages to channel conventions, organizes publishing work, and triages conversation signals without speaking for the brand unchecked.
Best for
- Marketing teams managing recurring posts, launches, educational series, and community response queues
- Brands with documented voice, channel rules, moderation policy, and approval responsibilities
Typical inputs
- Approved campaign messages, source assets, audience, channel list, calendar, and call to action
- Brand voice, post formats, accessibility guidance, restricted topics, moderation rules, and response taxonomy
Input quality determines output quality. Source permissions, retention, and field-level access should be settled before the workflow begins.
Core workflow
Each stage has a defined purpose, visible evidence, and a named owner for exceptions.
Gather context
Create channel-appropriate draft variants and accessibility text from approved material
Prepare the work
Place drafts into a review calendar with owners, dates, dependencies, and source references
Review and hand off
Classify replies or mentions and route routine, sensitive, or hostile conversations by policy
Actions it can perform
- Draft posts, threads, captions, alt text, content variants, and calendar recommendations
- Categorize mentions, identify response needs, flag brand risk, and prepare approved-language reply drafts
Actions should be restricted to the systems, records, and channels required for this role. Broader access is not a substitute for a well-designed workflow.
Outputs
- Review-ready social drafts, publishing calendar, source map, asset checklist, and accessibility text
- Mention queue, sentiment-neutral issue categories, response drafts, escalation packets, and campaign notes
Every output should make its status clear: prepared, awaiting approval, completed under policy, or escalated with an explanation.
Role-specific configuration details
Use these role-specific terms to make the implementation brief concrete: resolve the relevant definitions, permissions, routes, and exception conditions before the role touches live work.
- social-media
- channel-conventions
- conventions-organizes
- organizes-publishing
- triages-conversation
- conversation-signals
- signals-without
- without-speaking
- brand-unchecked
- unchecked-maintain
- coherent-social
- social-presence
- control-publication
- publication-public
- public-replies
- reputation-sensitive
- sensitive-situations
- campaign-messages
- assets-audience
- audience-channel
- channel-list
- list-calendar
- action-brand
- brand-voice
- voice-post
- post-formats
- formats-accessibility
- accessibility-guidance
- guidance-restricted
- restricted-topics
- topics-moderation
- moderation-rules
- response-taxonomy
- taxonomy-confirm
- campaign-message
- rights-target
- target-channel
- channel-audience
- publishing-objective
- objective-create
- create-channel
- channel-appropriate
- appropriate-draft
- draft-variants
- accessibility-text
- material-place
- place-drafts
- dates-dependencies
- references-classify
- classify-replies
- route-routine
- routine-sensitive
- hostile-conversations
- policy-draft
- draft-posts
- posts-threads
Human approval and escalation
Approval boundary
A channel owner approves every post, reply, public claim, moderation action, campaign launch, and change to publishing schedule.
Escalation rule
Legal threats, harassment, safety issues, misinformation, influencer requests, crises, and uncertain brand positions go immediately to people.
What remains under human control
- Brand teams own voice, channel strategy, community standards, moderation, source rights, and crisis policy
- People review public language, contextual nuance, reputation risk, replies, and the final publish action
Teams should review permissions and outcomes over time, especially when policies, data sources, responsibilities, or customer expectations change.
Recommended integrations
Connections are workflow building blocks, not proof of automatic availability. Confirm authentication, permissions, supported actions, and error handling during implementation.
Example workflow
An approved webinar brief becomes tailored LinkedIn and short-form drafts with alt text; a critical customer mention is routed to support instead of answered generically.
The implementation should record the source, owner, decision boundary, and recovery route for each important stage. That makes the workflow easier to review and improve without hiding responsibility.
Related agents
Use related roles only when responsibility and handoff boundaries are genuinely distinct.
Marketing Agent
See the responsibilities, controls, and handoffs for this related specialist role.
Explore Marketing AgentContent Repurposing Agent
See the responsibilities, controls, and handoffs for this related specialist role.
Explore Content Repurposing AgentBrand Monitoring Agent
See the responsibilities, controls, and handoffs for this related specialist role.
Explore Brand Monitoring AgentRelated use cases
Explore outcome-led workflows that can combine this role with approved systems and human review.
Manage Social Media
Understand how this role can contribute to a broader outcome-led workflow.
Explore Manage Social MediaCreate Marketing Content
Understand how this role can contribute to a broader outcome-led workflow.
Explore Create Marketing Content
Design a responsible Social Media Agent workflow
Define the sources, controls, connected tools, exceptions, and owners before implementation.