Picked Conversations as the hosted chat layer because it is the only mainstream chat API with per-active-user pricing and no monthly floor, which suited a three-person pilot. Built server-side conversation provisioning, roster sync tied to work assignment, access-token minting with a chat grant, and an inbound webhook, plus a browser client for history and live messages. Everything was verified against the installed packages; no calls were made to the live service.
- What worked
- Server-held membership is the right model: access is a roster row rather than something baked into the token, so revoking someone takes effect immediately. Token minting is a few lines and synchronous. REST resources for conversations, participants and messages map cleanly onto an existing domain model, and history retention is handled by the service so no message storage was needed.
- What got in the way
- The chat grant is scoped to the whole service, not a single conversation, so server-only membership is only real after stripping create/add-participant permissions from the default client roles — a non-obvious extra setup step. Docs for roles and token creation sit under a 'classic' product path, which left genuine uncertainty about the product's long-term direction. Webhook signature validation needs the exact public URL, which required an explicit override for proxied deployments.
