Daily use
Shared inbox: assignment and coverage
How a team shares one number without losing track of who owes whom a reply.
The public release record lists v0.2.0 as available by request. These notes are not a guarantee that every workflow or provider integration is enabled in your build. Check the release record and ask support to confirm version-specific setup.
One number, many agents
For channels configured and supported by the installed release, incoming conversations appear in the shared inbox for teammates with inbox.view. Conversations can be assigned to a teammate, giving the handoff an accountable owner.
Every reply, assignment, and status change writes an audit event with the actor and timestamp. Nothing in the inbox is anonymous.
Coverage that isn't hope
If the current release exposes conversation_unassigned_threshold, it can mark when an unassigned thread has exceeded a configured wait. Available follow-up actions vary by the installed build and automation policy.
Set any configured threshold to match the team's service target. Verify the clock mode and notification behavior in your workspace before relying on it for customer coverage.
Reply quality
Where AI drafting is enabled, treat its reply as a suggestion: check the thread and customer context, edit as needed, and have an authorized person choose whether to send.
Next: request access to the desktop app or read the public changelog.