Outbound requests let HQ teams ask branches for information or content -- things like updated photos, inventory counts, feedback, or anything else you need from the field. You create one request and send it to as many branches as you like in a single step.
Who can do this? Only HQ users with an admin or editor role can create outbound requests. Branch-only users will not see this option.
Getting started
In the sidebar, navigate to Sent under Requests.
Click the New Request button.
You will land on the New Outbound Request form, which has two main sections: request details and target branches.
Filling in request details
Title (required)
Give your request a clear, concise title that tells branches exactly what you need. For example: "Submit updated storefront photos" or "Q2 inventory count."
Maximum length is 200 characters.
A character counter below the field shows how many you have used.
Description
Use the Description field to add context or specific instructions. This is optional, but the more detail you provide, the easier it is for branches to respond accurately.
Priority
Choose a priority level from the Priority dropdown:
Urgent -- needs immediate attention
Normal -- standard turnaround (selected by default)
Low -- no rush
Priority helps branches understand how to triage your request alongside their other tasks.
Category
The Category field is a free-text label that helps you organize requests. Type something descriptive like "Photos," "Inventory," or "Feedback." Categories are optional but make it easier to find and filter requests later.
Due date
Click the Due Date picker to set a deadline. This is optional. When a due date is set, branches can see exactly when their response is expected.
Send reminders
The Send reminders toggle is turned on by default. When enabled, Rool will automatically remind branches that have not yet responded to the request. Toggle it off if you prefer to follow up manually.
Selecting target branches
The second section of the form is Target Branches (your organization may use different terminology, such as "Locations" or "Accounts").
Choosing branches individually
Each branch in your organization appears as a selectable card with a checkbox. Click a branch card (or its checkbox) to include it in the request.
The branch name is shown along with any tags assigned to it.
If your organization has address display enabled, the branch location appears below the name.
Selecting or clearing all branches
Use the Select All button in the top-right corner to add every visible branch at once. Use Clear to deselect all branches and start over.
Filtering branches by tag
If you have a large number of branches, use the Tag Filter at the top of the branch list to narrow the list. Select one or more tags to show only matching branches. When you have two or more tags selected, you can switch between:
Any -- show branches that have at least one of the selected tags
All -- show only branches that have every selected tag
This is especially useful when you only need a response from a specific region, brand, or group.
Selection count
As you select branches, a counter at the bottom of the list shows how many branches are selected out of the total -- for example, "Selected 5 of 12 branches."
Sending the request
Once you have entered a title and selected at least one branch, the Create Request button at the bottom-right becomes active.
Review your details and branch selections.
Click Create Request.
Rool creates the request and sends an in-app notification (and an email, based on each recipient's preferences) to the managers of every selected branch.
You are automatically taken to the request detail page where you can track responses.
To abandon the form without creating anything, click Cancel (or the back arrow at the top of the page) to return to the Sent requests list.
What happens next
Each branch receives the request with a Pending status.
Branch managers can respond, decline, or fulfill the request from their side.
You can monitor progress on the request detail page, which shows a breakdown of how many branches are pending, have responded, have declined, or have fulfilled the request.
Tips
Be specific in your title and description. The clearer the ask, the faster and more accurate the responses.
Use categories consistently. Settling on a small set of category names (e.g., "Photos," "Inventory," "Compliance") makes filtering and reporting easier over time.
Set a due date for time-sensitive requests. Combined with automatic reminders, this helps ensure nothing falls through the cracks.
Use tag filters for targeted requests. If only certain regions or branch types need to respond, filter by tag instead of manually selecting each branch.