Needs You
One triage queue for every decision your agents have escalated. Needs You gathers the calls that need a human, answered in place. Clear the desk and the work resumes.
Agents run on their own, but some calls are genuinely yours to make: which approach to take, whether to ship, how to resolve an ambiguity. Needs You is the single place those decisions land. It's a card-based queue of everything your agents have escalated, each answered in place: pick an option, add a note, and the agent picks the work back up.
It's the steer loop in Concierto's agent loops: the agent parks, you answer, it continues. And it's a workspace-level surface, so a decision raised on any track shows up in the same queue.
Needs You shares one bell surface with the Inbox, as the default tab of the segmented Needs you | Inbox register — decisions that block work on one side, awareness notifications on the other. Its badge counts pending decisions.
Two viable layouts for the payment step. Which should I build out?
The legacy plan has no annual equivalent. How should I map it on migration?
Resolved
What a card carries
Each card is built so you can answer without hunting for context:
- Who's asking: the agent's role icon and name, so you know which teammate raised it.
- Which track: cards are grouped by their track, with the longest-waiting ask surfaced first (the one most likely blocking its agent).
- The decision: the agent's question with numbered option pills. Pick one (or more, where allowed) and optionally add a note; the agent resumes immediately.
- Quick actions: send it back, or re-assign the work to a different agent or runtime if it's better handled elsewhere.
Answer order is a wait-time proxy: oldest pending first, within and across tracks. The longest-waiting steer leads because it's the one most likely holding its agent up.
Clearing the desk
Needs You is designed to feel like clearing a physical desk: answer a card, it resolves and slides into the resolved history below, and you move to the next. The history keeps a compact, collapsed record (who asked, the question summary, and the answer you gave) so a past call is one click away without cluttering the live queue.
A decision can also be deep-linked: a mention or inbox row that points at a specific request scrolls straight to that card and briefly rings it, whether it's still pending or already resolved.
Next
- Agent Stage, watch the agents that raise these decisions
- Inbox, where mentions and subscriptions surface
- Chat, talk to an agent directly instead of waiting for it to ask