Use Group Requests when several requests need the same answer, the same assignee, or the same outcome. You group them once and then reply, assign, change priority, resolve, or snooze across all of them from a single overlay, while each requester keeps their own private conversation.
Prerequisites
- An admin or agent role with permission to act on the requests you want to group.
- The requests already exist in your inbox or in `Views → All`. You group existing requests, you do not create a group from scratch.
- No plan gating or extra configuration. Grouping is available to every workspace.
1. Group existing requests from the list
Open any view that shows the requests you want to combine, for example `Views → My open` or `Views → Unassigned`.
1. Select the requests using the row checkboxes. You can select across pages with `Select all`.
2. In the bulk action bar at the bottom of the list, click `Group`.
3. Name and confirm the group. Siit creates a Group Request and the selected rows collapse into a single stacked row labelled with the `Group request` channel.
[SCREENSHOT: bulk action bar with Group button, request list with selected rows]
.png?width=670&height=302&name=CleanShot%202026-06-01%20at%2014.46.14@2x%20(1).png)
> [!TIP]
> The group inherits the most recent activity time across its children, so it lands wherever the most active request would have landed in the list.
2. Add a request to an existing group
You can add a new request to a group at any time, either from a single request or from the list.
- From a request: open the request, click the `...` menu in the sidebar, then `Add to group` and pick the target group.
- From the list: select one or more requests and click `Add to group` in the bulk action bar, then pick the target group.
.png?width=670&height=413&name=image%20(270).png)
3. Open the group and read the timeline
Click the stacked row in the list to open the Group Request overlay. The overlay shows:
- A combined timeline of every group event from every child, in chronological order.
- The list of child requests on the side, with each requester, ID, title, status, service and priority.
- A detailed list of every requester.
The overlay looks distinct from a standard request conversation on purpose, because what you type here will reach several requesters at once.
## 4. Reply or add a note to the whole group
Use the composer at the bottom of the group overlay the same way you would on a single request.
1. Write your reply, or switch to `Note` for an agent-only message.
2. Use requester variables, message templates, mentions, and attachments as usual.
3. Send. Siit broadcasts the message to every child request, and each requester sees a normal one-to-one message in their channel.
> [!NOTE]
> Each requester only ever sees their own thread. The grouping is invisible to them, so write the message as if you were answering one person.
If a child cannot receive the broadcast (for example, the channel is no longer reachable), Siit will show the list of children that received the message.
5. Apply key actions to the whole group
From the group sidebar, change any of the following and Siit applies the change to every child at once:
- `Status`: update status for every child.
- `Assignee`: reassigns every child to the chosen agent or inbox.
- `Service`: moves every child to the chosen service.
- `Priority`: sets the same priority on every child.
- `Followers`: add or remove anyone as follower of every child.
- `Tags`: add tags to every child.
- `Snooze`: snoozes every child until the chosen date.
- `Read`: read all child at once.
Each change appears on every child's timeline as a normal event, with the same audit trail you would see on a single request.
6. Run bulk actions on a group from the request list
You do not have to open the group to act on it. You can tick the group row in the list like any other row, and mix it with ungrouped requests in the same bulk selection.
1. In any view, tick the group row and any other request rows you want to include.
2. Use the bulk action bar at the top of the list (assign, set priority, set status, add tags, snooze, resolve, etc.).
3. Siit applies the action to every selected ungrouped request, and to every child of every selected group.
> [!WARNING]
> When a group is part of the selection, the action applies to **every child** of that group, not only the children that match the current view's filters. A child the current view filters out still receives the action. Open the group overlay first if you want to confirm the full child list before acting.
7. Open a single child from the group
You can drill into any child without leaving the group.
1. In the group overlay, click the child request in the side list.
2. The child opens in its own overlay on top of the group.
3. Navigate to the next or previous child using the arrows in the child overlay header.
4. Close the child to return to the group.
[SCREENSHOT: child overlay opened on top of group overlay]
> [!NOTE]
> When you are on the group, you can only run group-level actions. To act on a single child in isolation, open the child's own overlay first.
8. Remove a request from a group
If a request no longer belongs in the group, dissociate it.
- From the child overlay, click the `...` menu and pick `Dissociate`.
- The child returns to the list as a standalone request and stops receiving broadcasts.
If you remove the last child, Siit deletes the group automatically. You do not need to delete the empty container.
Verify the setup
Open `Views → All` and confirm the following:
- The Group Requests appear as a single stacked row with the `Group request` channel, not as individual rows.
- The unread dot on the group is on if any child is unread.
- Replying from the group lands in every requester's normal thread on their channel.
FAQ
Can a requester see that their request is grouped?
No. Each requester sees a standard one-to-one conversation on Slack, Microsoft Teams, the portal, or email. The group is admin-only.
What happens to SLAs on children inside a group?
Each child keeps its own SLA clock and its own pause and resume behavior. Grouping does not pause or merge SLAs.
Can I bulk-select Group Requests from the table to run more bulk actions?
Yes. You can tick the group row in the list like any other row, and mix it with ungrouped requests in the same bulk action. The action applies to every child of the group, even children that do not match the current view's filters. See step 7.
You cannot select children individually from the list, because they sit inside the group row. To act on a single child without affecting the others, open the child overlay from the group and run the action there.
What if children have different assignees, priorities, or services before I group them?
Siit keeps each child's current values until you change the assignee, priority, or service on the group. The group surfaces a mixed-state indicator so you know the values diverge before you align them.
Can I group requests across different inboxes or services?
Yes. The group is a coordination layer, not a routing rule. The children keep their inbox or service membership unless you change it from the group.
Can I request approval on a whole group?
No. Approvals stay on individual children. If a request inside a group needs a sign-off, open that child from the group and start the approval there. The group composer does not broadcast approval requests.
Does the group appear in views and filters?
Yes. Any view that would have matched at least one child shows the group. Filters like priority, assignee, service, and tag treat the group as a match if any child matches. The child requests themselves no longer appear individually as long as they are grouped.
What to do next
- Set up message templates in `Settings → Templates` so you can broadcast standard replies across a group in one click. See Create and manage message template
- Save a Grouped view by filtering on the `Group request` channel in `Views → All. See Manage your views