The Loops dashboard
How the Loops dashboard surfaces what's drifting and how to dig into a single loop.
What the dashboard shows
The Loops dashboard renders every loop your team has open, with the connections already drawn. It shows live counts, status filters, assignee, days open, and a projected break date (for example, "breaks in 3 weeks"): the same artifacts and timestamps as your source tools, just connected. Activity is shown over 7-day and 30-day windows, with a net change indicator and breakdowns by status.
Acting on a loop from the dashboard
The dashboard isn't just a view; you can resolve loops from inside it. Opt in on any open loop and Astell proposes the Astell Action that closes it: assign the owner, set the due date, draft the follow-up, schedule the meeting. A confirmation card shows exactly what will change in the source tool before anything runs, and the action executes on your behalf once you approve. Actions from the dashboard are priced the same as actions triggered from chat and are available on paid plans.
The loop detail view
Each loop has a detail view that pulls together everything related to it: the artifacts (Slack messages, tickets, calendar events, docs), the people involved, the deadline, days open, current status, and suggested next steps. Each artifact links back to its source tool (the Notion call notes, the Linear ticket, the Gmail thread), so the evidence trail is one click away.
Citations: sourced to the sentence
Every loop claim is sourced to the sentence that proves it. When Astell says "Maya asked for a custom export by July," it shows the Notion call notes with the exact sentence highlighted, the Linear ticket it was supposed to deliver against, and the Gmail check-in that re-raised the request. No paraphrase you can't verify: every claim is one click from its source.
The calendar view
The calendar view annotates every meeting with the loops it touches. A 1:1 shows the loops that person owns; a customer call shows their open promises; an engineering planning meeting shows the tickets in scope. Calendar slots become a working surface, not just a schedule. Clicking a meeting expands its relevant loops and artifacts.