One agent, one deployment
Tars creates a deployment for each agent when you create the agent. A duplicated agent gets its own deployment as well, so the copy keeps working if you delete the source. There is no button to create one, because the agent brings it along. The deployment carries the agent’s name. In Conversations, under Settings and Inboxes, the same deployment appears as the agent’s inbox, where admins set its members, routing, and working hours. See Set up inboxes.The Distribute page
Open an agent and select Distribute in the builder sidebar. The page header shows the agent name with Distribute under it, and an Agent Builder link takes you back to the flow. The left rail has two groups, Web and Channels, and each entry opens one view.
The four Web views are different doors to the same agent. Whichever one an end user comes through, they talk to the same published version and appear in the same conversations list.
Appearance is not set here. The Design page in the builder sidebar styles the conversation window and the launcher for every web surface. See Design the widget.
The published version is what runs
The link, the embed code, and the mobile snippets exist as soon as the agent exists, so you can copy them before the first publish. Until you publish, an end user who opens the link sees Agent not published yet. After the first publish, every surface serves the newest published version, and edits in the builder stay invisible until the next publish. See Drafts and publishing.Deployments and channels
The Web views need no account setup. WhatsApp runs through a connected number, which is a channel account that lives in Settings and is assigned to a deployment. The WhatsApp view under Channels shows that assignment from the agent’s side.
Picking a number from Connected to another agent asks you to confirm, because that agent stops receiving WhatsApp messages on the number. Open conversations stay in the inbox. Only admins can connect, change, or disconnect a number. Other members see Contact your admin.
One deployment can serve Web and WhatsApp conversations with the same flow. For number health, templates, and the Settings side of the assignment, see Channels overview and Connect WhatsApp.