Skip to content
ContractSpec
Start here

reference

SupportOS teams and queues

Revision-fenced, tenant-scoped team and queue administration for SupportOS routing.

field.key.label
docs.customer-support.routing-administration
field.version.label
field.type.label
field.title.label
SupportOS teams and queues
field.tags.label
supportos,routing,teams,queues
field.owners.label
field.stability.label
public

Team and queue administration is scoped exclusively by authenticated tenant, workspace, and actor authority. Mutations use caller-stable idempotency keys, expected revisions, server timestamps, and immutable evidence receipts. Exact replays return the original projection; changed input fails closed.

Queue team references and fallback queues must resolve inside the same workspace. Self-fallback and fallback cycles are invalid. Archiving a referenced team or queue is rejected until dependants are migrated. Lists use stable- watermark keyset pagination and expose opaque references only.