When branch users submit content requests, they land in your Received Requests inbox. This guide walks you through viewing, acting on, and communicating about those requests from the HQ side.
Finding your received requests
Open the sidebar and expand the Requests section, then select Received. This page shows every content request that branches have submitted to your HQ team.
A badge next to Received tells you how many requests are waiting for your attention.
Understanding the request list
Each request card shows at a glance:
Title and a short description
Priority (Urgent, Normal, or Low)
Status badge (Submitted, In Progress, Completed, or Declined)
Suggested accounts the branch is requesting content for
Due date (with an "Overdue" warning if the deadline has passed)
Post count and comment count, so you can see activity at a glance
Requester name on the right side of the card
Filtering requests
Use the filter bar at the top of the list to narrow things down:
Status filter -- Show only requests with a specific status (Submitted, In Progress, Completed, or Declined). You can select multiple statuses at once.
The total count of matching requests appears on the right side of the filter bar.
Request statuses
Every content request moves through a lifecycle:
Status |
Meaning |
|---|---|
Submitted |
A branch user sent this request. It is waiting for HQ to pick it up. |
In Progress |
HQ has started working on it (or created a post from it). |
Completed |
HQ has fulfilled the request and linked at least one post to it. |
Declined |
HQ has declined the request and provided a reason. |
Requests move forward through these statuses. Once a request is Completed or Declined, no further status changes are available.
Viewing request details
Click any request card to open its detail page. The detail page has two columns:
Left side -- request information:
Priority, status, and category badges
Full description from the requester
Requester name and avatar, with the time they submitted
Target Accounts -- the branches the requester wants content for
Timeline -- whether the request is for one-time content or a date range, plus the due date
Attachments -- any media files, links, or documents the requester included (organized into tabs for Media, Links, and Docs)
Linked Posts -- posts that have been created to fulfill this request, each linking to the post detail page
Right side -- actions and comments:
Actions panel (HQ only) with workflow buttons
Comments thread for back-and-forth communication
Taking action on a request
When you open a request, the Actions panel on the right offers different options depending on the current status.
Starting work
When a request is in Submitted status, click Start Work. A confirmation dialog appears explaining that the requester will be notified. Confirm to move the request to In Progress.
Creating a post from a request
For requests that are Submitted or In Progress, click Create Post from Request. This takes you to the post creation page with the request already linked. When you save the post, it automatically appears in the request's Linked Posts section.
If the request was still in Submitted status, creating a post automatically moves it to In Progress.
Marking a request as complete
Once a request is In Progress and has at least one linked post, the Mark as Complete button becomes available. It shows the number of linked posts for reference.
Click it, confirm in the dialog, and the requester is notified that their content is ready. You must have at least one linked post before you can complete a request.
Declining a request
For requests in Submitted or In Progress status, click Decline Request. A dialog asks you to provide a reason (between 10 and 1,000 characters). The requester receives a notification and sees your reason displayed on the request detail page in a highlighted box.
Declining is final -- once declined, no further actions are available on the request.
Commenting on requests
The Comments section on the right side of the request detail page lets you communicate directly with the branch user who submitted the request.
To add a comment:
Type your message in the text field at the bottom of the comments panel.
Press Enter to send, or click the Send button. Use Shift + Enter for a new line within your message.
Comments appear in chronological order. Each comment shows the author's name, avatar, and how long ago it was posted. HQ team members are labeled with an HQ badge next to their name so the requester can easily tell who is responding.
When you comment, the requester is notified. When the requester comments, all HQ team members (admins and editors) are notified.
Tips for managing requests efficiently
Check the badge count on the Received link in the sidebar to spot new requests quickly.
Use status filters to focus on what needs attention -- filter to "Submitted" to see requests that haven't been picked up yet.
Start work early so the requester knows their request is being handled, even if you haven't created a post yet.
Use comments to ask clarifying questions before you begin, rather than declining and asking the branch to resubmit.
Create posts directly from requests using the Create Post from Request button to keep everything linked and trackable.