Team Workflows
Coordinate the book across a team without stepping on each other.
Once more than one person works the book, you need a little structure so nobody messages the same company twice and the best Accounts don't sit untouched.
Roles that work
For a small team, one person owning the loop is enough:
- Owner — reviews new Accounts daily, claims the top ones, keeps the Audience sharp.
- Reviewers — other team members who pick up assigned Accounts and run their own outreach.
For an agency, one operator per client Product is the usual split. See Multi-Product and Agencies.
A daily rhythm
- Owner opens Accounts, default sort (score).
- Top 3–5 get Working state set, opener sent same day.
- Each person sends from their own account with the extension.
- Anything snoozed or dismissed gets actioned same-day so the book stays a live queue.
Fifteen focused minutes per day beats a two-hour cleanup once a week. Signals go cold.
Account states keep collisions away
The five states (New / Working / Snoozed / Dismissed / Won) are how the team stays out of each other's way. Before opening any Account, check the state. After working, update it. See Account States.
| State | Meaning |
|---|---|
| New | Nobody has claimed this |
| Working | A teammate is on it — the assignee chip shows who |
| Snoozed | Deferred; will auto-wake on a strong fresh signal |
| Dismissed | Not a fit; hidden from default view |
| Won | Closed deal |
Single-claim in v1
In v1, an Account in Working is single-claim — one assignee, who can reassign. Multi-claim, round-robin assignment, and reassignment workflows are post-v1 features.
Seats and access
| Tier | Seats |
|---|---|
| Trial | 1 |
| Growth | 2 |
| Scale | 8 |
| Enterprise | Custom |
Everyone in the workspace sees the same Accounts and states, which is what makes coordination honest.