- Insights — the same slice charts and tables you get from a View’s Insights panel, scoped to one of the team’s Views. Read-only, so nothing you click reassigns or reroutes a thread.
- Members — the team roster with live auto-dispatch data overlaid on it: presence dots, active-thread counts, and per-member availability toggles you can flip on someone’s behalf.
Who sees Team Home
Open Team Home
Open a team in the left rail
Select Home
Insights
The Insights panel on Team Home is the same one that lives inside a View — the same slice set (Priority, Status, Owner, Company, Create Date, plus Sentiment and XLA where enabled), the same first-page-of-200 thread limit, the same charts and tables. The differences are:- It’s scoped to one of the team’s Views. Use the View picker in the panel header to switch between any View that belongs to the team. The picker shows the thread count for the current View next to its name.
- Slice with the Slice picker. Pick a dimension from the Slice dropdown to change the chart. Team Home defaults to Priority.
- It’s read-only. Clicking a bar, segment, or row on Team Home doesn’t drill into the underlying threads or change what the View shows. Open the View itself if you want to drill in and act on threads.
Members
The Members table lists every active member of the team, with a role badge, a search box, and — for teams in an active auto-dispatch profile — dispatch data on each row.
Auto-assign (push) teams
For teams whose profile uses Auto-assign, the Members table adds:- Presence dot on each avatar — green if the member is available for this team’s dispatch, grey if offline. This is the same presence signal you see next to avatars in the left rail.
- Active threads — the member’s current active count over the profile’s Max threads limit (for example,
3 / 10). The active count is semibold, and turns red when the member is at or over capacity. The math matches the push dispatcher exactly, so the number you see here is the number Auto-assign is using to decide who gets the next thread. - Available — a toggle you can flip on the member’s behalf to make them available or unavailable for Auto-assign. See Who can toggle another member’s availability for the rules.
- Excluded members render faded, with the toggle disabled and an Excluded from auto-dispatch tooltip on hover. Excluded members are set in the profile — see Auto-dispatch profiles.
Next thread (pull) teams
For teams whose profile uses Next thread (self-serve), the Members table shows a single dispatch column:- Pulled last 24h — how many threads each technician has pulled in the last 24 hours.

Sync now
The Members table refreshes automatically every few minutes. A footer under the table shows Last synced N minutes ago and a Sync now button you can hit at any time to refetch immediately. Sync now is disabled while a member’s Available toggle is still flipping — a mid-toggle refetch would clobber the optimistic state.Who can toggle another member’s availability
Flipping the Available toggle in the Members table changes another member’s push-dispatch availability on their behalf. Thread authorizes the change with a team-manage policy:Teams without an auto-dispatch profile
If the team isn’t part of any enabled auto-dispatch profile yet, Team Home still opens, and the Members table still lists the roster — just without the dispatch columns. A dismissible Get started banner at the top of the Members section links to the auto-dispatch admin so you can create or attach a profile:Let auto-dispatch handle thread assignments for this team. Get startedDismiss the banner from its
× control if you’d rather run the team without auto-dispatch. It reappears the next time the team is loaded until a profile is attached.
Action when no tech is eligible
Auto-assign profiles let you choose what happens when a thread is ready to dispatch but no technician is available. You pick the behavior in the profile’s Technician assignment section, under Action when no tech is eligible.
- Retry assignment (default) — Auto-assign holds the thread and re-checks every minute. As soon as a tech becomes available, the highest-priority waiting thread is dispatched first; ties are broken by oldest thread. The thread stays in its current status and no internal note is added until a tech is successfully assigned.
- Apply a status change — Auto-assign moves the thread to a status you pick per board instead of waiting. Use this if you’d rather have unassigned threads drop into a dispatcher queue than sit in retry.
FAQ
Why is a member's Available toggle disabled?
Why is a member's Available toggle disabled?
Why does the Active threads count sometimes look different from what I see on the board?
Why does the Active threads count sometimes look different from what I see on the board?
Can I click into an Insights chart on Team Home to see the threads?
Can I click into an Insights chart on Team Home to see the threads?
How often does Retry assignment check for available techs?
How often does Retry assignment check for available techs?
What happens to threads while they're waiting in Retry?
What happens to threads while they're waiting in Retry?
Do I still need a Fallback status?
Do I still need a Fallback status?