Team collaboration

Run a team inbox with one contact graph.

Fan shared-address mail into member inboxes, share contact cards, add thread notes, and preserve relationship context across the team.

Token first

Make sure the agent has these scopes.

Create a new token or update the agent's current token before trying the calls below.

Required token scopes

contacts:read contacts:write email:read email:write context:read

Outcome

What this gives you.

Work can move between people and agents without forcing the sender to repeat context.

Use when

The operational shape.

  • A team uses a shared address but needs per-inbox ownership and records.
  • Contacts and relationship history should follow the work across team members.
  • Internal notes and assignment should stay invisible to the outside sender.

API sequence

The calls to make.

01

Create the team address

POST/v1/distribution-lists/

Use a tenant admin session to create the shared address that fans inbound mail into member inboxes.

Default example
Use this as the default shape for this step.
{
  "address": "team@mail.example.com",
  "name": "Team intake"
}
02

Add member inboxes

POST/v1/distribution-lists/{list_id}/members/

Use a tenant admin session to register each member inbox as a recipient for the shared address.

Default example
Use this as the default shape for this step.
{
  "inbox_id": "inb_account_manager"
}
03

Share the contact card

POST/v1/contacts/shares/

Offer or request the contact record so the next owner starts with context.

Default example
Use this as the default shape for this step.
{
  "type": "offer",
  "to_inbox_id": "inb_account_manager",
  "contact_id": "ctc_123"
}
04

Assign and annotate the thread

POST/v1/messages/threads/{thread_id}/notes/

Add internal notes and assignment context without exposing them to the sender.

Default example
Use this as the default shape for this step.
{
  "body": "Assigned to account manager. Customer asked about renewal timing and pricing guardrails."
}

Controls

Review points.

  • Distribution lists move mail; contact sharing and thread notes move context.
  • Keep one shared address for intake while preserving per-inbox ownership downstream.