Team Collaboration ​

If multiple people manage the same account, Whisper keeps everyone coordinated. Each operator runs their own CLI session, and the system automatically distributes work so nobody steps on each other's conversations.

Adding Team Members ​

Team members are managed in the dashboard. Go to the Team page, invite someone by email, and they'll get access to all the accounts in your organization.

Each team member needs their own login. After being invited, they:

  1. Sign up at whisper.fans and get approved
  2. Accept the team invitation (from the email or the dashboard)
  3. Make sure the right organization is selected in the sidebar's org switcher
  4. Run whisper login in their Terminal
  5. All shared accounts show up automatically

Check the org switcher

If a team member runs whisper login and doesn't see any accounts, they probably need to switch to the correct organization. Open the dashboard, use the org switcher in the bottom-left of the sidebar, select the right org, and run whisper login again.

How Work Gets Distributed ​

When you type /unreads or /review, Whisper checks if another operator is currently active in any of those conversations. If someone else is already working with a subscriber, that conversation is removed from your list.

You'll see a note like:

(3 conversations active with other operators, skipped)

This happens automatically. You don't need to coordinate with your team about who handles what. Whisper figures it out.

Unreads are automatically split between operators based on who's already active.

What Happens If You Overlap ​

The system uses soft claims, not hard locks. If you do message a subscriber that another operator is actively chatting with, you'll see a warning:

[NOTE: Oscar is currently active in this conversation]

or when sending:

[NOTE: Oscar was recently active in this chat -- message sent anyway]

The message still goes through. Whisper warns you but never blocks you. Sometimes you need to jump in regardless, and the system respects that.

Claims Expire Automatically ​

When an operator reads a chat or sends a message, they're "claimed" on that conversation for 5 minutes. If they stop interacting (close Whisper, switch to a different subscriber, or just walk away), the claim expires and the conversation becomes available to everyone again.

You don't need to manually release conversations. The system handles it.

When you exit Whisper (with /quit or Ctrl+C), all your claims are released immediately.

Auto Mode With Teams ​

Auto mode respects the same claim system. If two operators both run whisper --auto on the same account, they'll automatically work on different subscribers. The unread list is split between them with zero overlap.

This is a great way to run a team at scale: each operator handles a disjoint set of conversations, and Whisper ensures complete coverage without any double-messaging.

Revoking CLI Sessions ​

If someone leaves the team or you need to cut off access, go to the dashboard overview page and use the revoke all button to invalidate all active CLI sessions. Team members will need to run whisper login again to reconnect.

You can also remove team members from the Team page in the dashboard. They'll lose access to all shared accounts.

Things to Know ​

  • Shared data: All operators on the same account share subscriber profiles, conversation history, directives, and scoring data. An edit one person makes (like updating a subscriber profile) is visible to everyone.
  • Separate style learning: Each operator's style corrections train the same skill memory. Over time, the system learns a unified voice for the account.
  • Solo operators: If you're the only person managing an account, the claims system is invisible. No filtering, no warnings, no overhead.