Team

The Team tab is Forepost’s read on the people doing the work. It surfaces three things: who’s online, how loaded they are, and which agents you’ve flagged for review.

​

What the page shows

A table with one row per agent: The page header reads:

• All agents on track. if no flags are set, or
• N agent(s) flagged for review. if any are. A red pill in the top-right shows the flag count.

​

Flagging an agent

You can flag an agent two ways: Manually. In Settings → Team → Update team, tick Flag for review next to any agent. An optional note field appears — use it for the why (“3 escalations this week”, “first month, mentoring”) so the next time you (or anyone else) opens the page, the context is right there. Automatically — Forepost auto-flags. When an agent’s CSAT trajectory sustains falling across 3+ weeks with a drop of 2pp or more, Forepost takes three coordinated actions:

1. Flips the flag in the Team view and writes a note in the form “Forepost flagged: CSAT sustained falling across 4 weeks (-5pp)”. An “Auto” pill renders next to the agent’s name so it’s clear the flag came from Forepost, not from you.
2. Posts to Slack (if delivery is on) with the flag headline AND a drafted five-point 1:1 agenda you can paste into your notes. See Slack delivery for the message structure.
3. Queues an action into your Daily Brief follow-through (“Coach Sarah this week — CSAT sustained falling…”) so the next morning’s brief surfaces it alongside any other live calls. Tick it taken when you’ve had the conversation; dismiss if you’d rather Forepost stay out of it.

If you clear an auto-flag in Settings → Team, Forepost respects your decision and stays quiet on that agent for 30 days before re-evaluating. The queued action stays in your brief until you tick it taken or dismissed — that’s a separate state from the flag, because the flag is “is this agent on the watchlist” and the action is “have I had the conversation”. Auto-recovery. If the agent’s CSAT trajectory tips back (no longer falling, magnitude no worse than -1pp across the current 4-week window), Forepost clears the flag itself, marks the queued action dismissed, and posts to Slack — “Forepost cleared Sarah’s flag — CSAT recovered.” No action needed from you. If you’d already had the 1:1 manually and ticked the action taken yourself, this is a no-op. If you still want the conversation despite the recovery, just toggle the flag back on or re-queue the action by hand. The toggle for the whole loop (flag + recovery + Slack posts) is in Settings → Delivery → Agent CSAT alerts, on by default. Flagged agents:

• Get a red avatar and a “Watch” status pill on the Team tab.
• Appear in the Agent review queue derived signal on the Watchlist.
• Are included verbatim in the system prompt that generates the Daily Brief, so the brief can comment on them when relevant.

​

How Forepost uses the team in briefs

The brief lists each agent inline:

Kian is carrying 73 tickets against Ish’s 12, with agent utilisation sitting at 50% overall. The load is not being shared.

The names + ticket counts + CSAT + flag state + note are all available to the model. Brief content is generated only from these structured fields, no message bodies, no PII beyond what you’ve typed.

​

Per-agent trajectories

Once you have at least two weekly snapshots for an agent, a small trajectory line shows up under their name in the Team view:

CSAT sustained falling across 3 weeks (-4pp / 3w) · tickets sustained rising (+12 / 3w)

Same shape heuristics as the Weekly Watch — sustained / step change / choppy / flat — applied per agent. The line reads “no agent trajectory yet” by being absent: if there’s only one snapshot on file (a teammate just added), nothing renders rather than fabricating motion. The brief and Weekly Watch receive the same trajectory facts and use them in the prose where they change the read. “Sarah’s CSAT has been falling for 3 weeks” reads sharper than “Sarah’s CSAT is 78%” — and lets the model surface the right teammate without you having to flag them manually.

​

Removing an agent

In Settings → Team → Update team, click the × on the right of any agent row. Their data is removed immediately. The next brief reads from the new team.

​

Departments

Each agent row has a Department field (e.g. Tier 1, Billing). It’s optional for the Team tab, but if you’ve invited Members to your workspace, departments are how their view is scoped. See Teammates.