Deployment

A deployment is what happens when a Watcher is assigned to actually operate inside a customer-facing Telegram Community. Creating a Watcher Record and deploying it are two separate steps — a Watcher isn't live anywhere until it's deployed.

Deploying a Watcher into a new Community requires: the Watcher's Telegram bot actually added to that Community, Innvil verifying the bot is genuinely present there, the Project the Community belongs to, and enough remaining Watcher-slot and Community capacity on your plan.

Deployment is where the Watcher's already-configured persona, moderation, and knowledge settings actually start applying to that Community — you don't reconfigure the Watcher per deployment, you configure it once on its Watcher Record and deploy it wherever it should operate.

Deploying into a private Escalation Group uses this exact same connection flow, but is exempt from Watcher-slot and Community-allowance billing — see "The Escalation Group Slot Rule."