Content requests let branch teams ask HQ to create social media content on their behalf. Instead of creating posts yourself, you describe what you need and HQ takes it from there.
This is useful when your organization's HQ team handles content creation centrally -- branches can submit requests for campaigns, promotions, seasonal content, or anything else they need posted to their social accounts.
How Content Requests Work
At a high level, the flow looks like this:
A branch user submits a content request describing what they need.
HQ receives the request and reviews it.
HQ creates one or more posts based on the request.
The branch user is notified when the content is ready.
When to Use a Content Request vs. Creating a Post Directly
Scenario |
What to do |
|---|---|
You want HQ to create content for your branch |
Submit a Content Request |
You already have the copy and media ready to go |
Create a Post directly |
You need a specific campaign but aren't sure about the creative direction |
Submit a Content Request with a description of what you're looking for |
You have editing permissions and want full control over the post |
Create a Post directly |
Content requests are ideal when you'd rather hand off the creative work to HQ or when your organization requires that HQ produces all social content.
The Request Lifecycle
Every content request moves through a series of statuses. Here is what each one means:
Draft -- You've started filling out the request but haven't submitted it yet. Drafts are auto-saved so you can come back and finish later.
Submitted -- The request has been sent to HQ. They'll see it in their Inbox and can begin reviewing it.
In Progress -- HQ has started working on your request. You'll receive a notification when they pick it up.
Completed -- HQ has finished creating the content. At least one post has been linked to your request and it's ready for review.
Declined -- HQ was unable to fulfill the request. A reason will be provided so you understand why.
Once a request is Completed or Declined, it's considered closed and no further status changes can be made.
What's Included in a Content Request
When you create a content request, you'll provide:
Title -- A short, descriptive name (e.g., "Holiday Social Media Campaign").
Description -- Details about what content you need, key messages, target audience, and any specific requirements.
Category -- An optional label to organize your request (e.g., promotion, event, seasonal).
-
Priority -- How urgently you need the content:
Urgent -- Needs immediate attention.
Normal -- Standard timeline.
Low -- When time permits.
Timeline -- Either a single due date or a date range for when the content is needed.
Target accounts -- Which of your branch locations the content is for.
Attachments -- Supporting materials such as uploaded images or videos, assets from your organization's library, external links, or documents.
Where to Find Your Content Requests
Content requests are accessible from the sidebar:
Sent -- View all requests you've created, along with their current status. You can filter by status, priority, or type.
Inbox -- HQ team members see incoming requests here. Requests also appear in the unified inbox alongside approvals and other notifications.
Communicating with HQ
Each content request has a built-in Comments thread. Use it to:
Ask questions or provide clarification.
Share additional context after submitting.
Discuss feedback on drafted content.
Comments from HQ team members are labeled with an HQ badge so you can easily tell who is responding.
What Happens After HQ Completes Your Request
When HQ marks a request as Completed, one or more posts will be linked to it. You can view these linked posts directly from the request detail page. Depending on your organization's workflow, the posts may go through an approval process before being published.
Next Steps
Creating a Content Request -- Step-by-step guide to submitting your first request.