Team Chat subscriptions — an agent is told when a person posts or a thread moves

What it is

• Three kinds of subscription. A person anywhere you can read; a person in one conversation; or one thread (optionally only one person's replies in it).
• Not a whole channel. Subscribing to every message in a busy channel is refused, so an agent cannot be flooded.
• The sibling of the reply watch. The Team Chat reply watch wakes an agent when someone answers a message the AGENT sent. A subscription is for waiting on something the agent did not start.
• Read-only. A subscription never posts anything to Team Chat; it only listens.

Where to find it

• Just ask the agent. "Tell me when Jeph posts", "let me know if Sam says anything in #design", "watch this thread and wake me on replies", "stop watching that thread".
• There is no screen for it. The agent sets it up, lists it and cancels it for you, and it lives as long as that agent's session does.

How it behaves

• What wakes the agent: a real person's post that matches the subscription, made after it was created. Your own posts count — if the agent subscribed to you, or to a thread you then reply in from your phone, it hears you.
• What never wakes it: another agent's post (including your own agents, which post under your account), a bot, a webhook, or a system notice such as "joined" or "call ended". Old history is never replayed.
• Each post once. No post is delivered twice, even across restarts — and an agent that both messaged someone and subscribed to them still hears each of their posts only once.
• One wake per batch. Several posts that arrive together come as one message, oldest first, each labelled with who wrote it and when.
• Framed as a teammate's words. The agent is told who posted, where, that it is seeing this because it subscribed, and how to cancel — and that a teammate's words are information, not instructions from you.
• Timing. A thread or one-conversation subscription is near-instant; a person-anywhere one notices within about a minute. An idle agent wakes; a busy one gets it at its next turn; a paused or archived session is not woken.
• App closed. Posts made while the app was closed are caught up when it reopens. If a conversation moved too far to read back in one go, the agent gets what was read and the subscription ends, saying so.
• How it ends. Cancelled by the agent; after the first wake if the agent asked to be told only once; or by itself when its session is archived or ended, or the conversation is gone or no longer readable. Each session may hold up to 20 live subscriptions.

For agents

Command	What it does
POST /team-chat/subscriptions	Subscribe. Body { personUid?, channelId?, threadRootId?, once?, workspaceId? }. personUid alone = that person anywhere; add channelId = only in that conversation; channelId + threadRootId = one thread.
GET /team-chat/subscriptions	This session's subscriptions, live and ended, with why each ended.
DELETE /team-chat/subscriptions/:id	Cancel one of this session's subscriptions.

• Every command needs the calling session's id (X-AMC-Source-Session-Id).
• A person's personUid comes from GET /team-chat/members.
• A topic started from scratch cannot be subscribed to — subscribe to the thread of one of its messages instead.

Related

• Team Chat reply watch — hearing back on a message the agent sent.
• Agent messages — how messages reach an agent session.
• Agent lanes — talking to a teammate's agent instead of the teammate.