# Deployments

> Put an agent on web chat, WhatsApp or a phone number, edit each deployment's settings, move it to another number, disable, enable or remove it, and read usage by touchpoint.

Source: https://docs.amomic.in/build/deployments

---

A **deployment** puts an agent on one touchpoint: your website's chat widget, one WhatsApp Business number, or one phone number. Each touchpoint is answered by one agent at a time. One agent can be deployed to many touchpoints.

This page covers the agent's **Deployments** tab: deploying, the settings each deployment carries, disabling and removing, and usage by touchpoint.

**Who can do this:** workspace **owners** and **admins**. Your plan decides which channels you can deploy to and how many deployments you can have. See [Limits and plans](/operate/limits).

## What a deployment holds

A deployment joins three things:

| Part | What it is |
|---|---|
| The agent | What it says and does: its persona, knowledge and tools. |
| The touchpoint | The website, WhatsApp number or phone number customers reach. You connect these on the **Channels** pages. |
| The channel settings | What differs per touchpoint, listed below. |

A deployment always serves the agent's **saved** settings. When you save a change to the agent, every deployment uses it from the next message or call. You do not redeploy after editing or publishing an agent. See [When your changes reach customers](/build/agents#when-your-changes-reach-customers).

The channel settings, by contrast, live on the deployment, and you change them on the deployment:

| Channel | Settings on the deployment |
|---|---|
| Web | Allowed domains, the widget's name, look, welcome message, suggested questions and lead capture |
| WhatsApp | Which sender number answers, plus that number's WhatsApp business profile |
| Phone | Which number, call language, the language the call opens in, opening line, conversation engine and voice, background sound, recording |

An agent must be **published** once before its first deployment. Until then every tile on the Deployments tab says *Publish this agent before deploying it.* See [Versions](/build/versions).

## The Deployments tab

Open the agent and choose **Deployments**. Each channel has a tile: **Web** (*A chat widget on your website.*), **WhatsApp** (*Replies on your WhatsApp Business number.*) and **Phone** (*Answers calls on your phone number.*).

![The Deployments tab of Veloria Support: the Web tile with the veloriahome.in widget Live, and the WhatsApp tile with +91 73530 18420 Live](https://docs.amomic.in/screens/agents/deployments-grid.light.webp)

*Each row is one touchpoint this agent answers on.*

A tile's badge reads `{n} live`, or `Not live` when it has deployments but none is serving. Each row shows the touchpoint's name, its short public ID, a state badge, a pencil (**Edit settings**) and a **⋮** menu.

| Row badge | Meaning |
|---|---|
| `Live` | Serving. Customers on this touchpoint reach this agent. |
| `Disabled` | You disabled it. Its settings are kept, and it is not answering. |
| `Error` | The channel reports a problem with the touchpoint. Check its page under **Channels**. |
| `Not live` | Created but never switched on, usually because it did not pass the checks. Open **Edit settings** to complete it, or **Remove** it. |

The **Agents** page shows the same deployments as chips on the agent's card. There, a disabled deployment reads `Paused`, as in `Phone · Paused`.

### When a tile cannot deploy

An empty tile says *Not deployed here yet.* and how many touchpoints are free, with a **Deploy here** button. Otherwise it tells you what is missing:

| Message | What to do |
|---|---|
| *Publish this agent before deploying it.* | Publish from **Overview** or **Versions**. |
| *Your plan doesn't include this channel yet.* (badge `Upgrade`) | Choose **View plans**. |
| *Connect a WhatsApp Business number first.* | Choose **Connect WhatsApp**. See [Set up WhatsApp](/channels/whatsapp). |
| *Get a phone number first.* | Choose **Get a number**. See [Numbers and KYC](/channels/phone-numbers). |
| *Every connected number already has a deployment.* / *Every number already has a deployment.* | None of your numbers is free for this agent. Connect or get another number. |

When a tile already has deployments, **Add another** (or **Add another site** on Web) deploys to one more touchpoint.

## Deploy to WhatsApp or a phone number

::: steps

::: step Open the deploy dialog

On the Deployments tab choose **Deploy here** on the WhatsApp or Phone tile. You can also use **Deploy** in the studio header (or on the agent's card) and choose **WhatsApp** or **Phone number**.
:::

::: step Choose the number

The dialog, **Deploy to WhatsApp** or **Deploy to Phone**, lists your numbers. Each has a badge:

| Badge | Meaning |
|---|---|
| `Available` | No agent answers on it yet. |
| `In use` | Another agent answers on it. Deploying here *Replaces the agent currently deployed here*. |
| `This agent` | *Already reaches this agent*. |
| `Unavailable` | It cannot be used, with the reason: *Connection disabled*, *Verification required*, *Connection has an error* or *Connection is degraded*. |

**Get another number** or **Connect another WhatsApp account** takes you to the channel page if the number you want is not listed.
:::

::: step Deploy

Choose **Deploy agent**. The console creates the deployment, checks it, and switches it on in one go. You see *{agent} is live on Phone* (or WhatsApp). Choose **Done**.
:::

:::

![The Deploy to Phone dialog listing Veloria's phone numbers with Available and In use badges, one selected](https://docs.amomic.in/screens/agents/deployments-deploy-phone.light.webp)

If a check fails, the agent is not switched on and the console shows the first problem, for example *Verify the channel connection.* The half-made deployment stays on the tile as `Not live`. Fix the problem (usually on the number's page under **Channels**) and deploy again, then **Remove** the `Not live` row.

A new phone deployment starts with sensible defaults: the opening line *Hello! You're speaking with {agent name}. How can I help you today?*, a call language that matches the agent (**Multilingual** if the agent is Multilingual, English otherwise), and recording off. Change them with **Edit settings**.

## Deploy to the web

The Web tile's **Deploy here**, **Add another site** and **Edit settings** all open the **Deploy to the web** wizard, a full page with five steps: **Website**, **Knowledge**, **Identity**, **Appearance** and **Install**. It is covered step by step in [Web chat](/channels/web-chat).

The console runs one web widget per workspace. **Add another site** reopens that same widget, so to put the widget on a second site, add that site to its allowed domains. Deploy web chat from one agent only: running the wizard from a second agent replaces the first agent's web deployment instead of adding a second widget.

## Edit a deployment's settings

Choose the pencil on a row, or **Edit settings** in its **⋮** menu.

### Phone: Voice settings

![The Voice settings dialog scrolled to Conversation engine, with Support desk selected and its voices listed](https://docs.amomic.in/screens/agents/deployments-voice-settings.light.webp)

The **Voice settings** dialog holds everything a caller hears on that number: **Phone number**, **Call language**, **Greet callers in**, the **Opening line**, **Conversation engine** and voice, **Office background sound**, **Natural hesitations** and **Record calls**. Each field is explained in [How voice works](/channels/voice) and [Languages](/channels/voice-languages).

Choose **Save settings**. The console confirms *Voice settings saved — the next call uses them.* Saving creates a fresh deployment on the number and retires the old one, so every configuration a number has served is kept. Calls already in progress finish on the old settings.

### WhatsApp: WhatsApp settings

![The WhatsApp settings dialog with the Sender number and the Business profile: photo, display name, About, Description, contact email, website and address](https://docs.amomic.in/screens/agents/deployments-whatsapp-settings.light.webp)

| Setting | What it does |
|---|---|
| **Sender number** | The WhatsApp Business number that reaches this agent. Choose another and **Move to this number** to move the deployment. |
| **Profile photo** | **Change photo** uploads a square JPEG or PNG, at least 192×192 and under 5 MB. |
| **Display name** | Read-only. Meta reviews every display-name change, so it can only be changed in **WhatsApp Manager**. |
| **About** | The short line under the business name, up to 139 characters. |
| **Description** | Shown on the business profile page, up to 512 characters. |
| **Contact email**, **Website**, **Address** | Shown on the profile. The website must start with `https://` (or `http://`). The address takes up to 256 characters. |

Choose **Save profile**. *WhatsApp profile updated — customers see it on your number.* Profile changes go to WhatsApp straight away. They belong to the number, not the agent, so another agent deployed to the same number shows the same profile.

The dialog's footer shows the number's quality rating, when there is one. Templates and connection health are on the [WhatsApp channel page](/channels/whatsapp).

### Move a deployment to another number

In **Voice settings**, pick a different **Phone number** and save. In **WhatsApp settings**, pick a different **Sender number** and choose **Move to this number** (*This agent now answers on the selected number.*).

Either way the agent is deployed on the new number and the deployment on the old number is disabled. If the new number already had an agent, this agent replaces it there. The old number stops answering until you deploy an agent to it again.

## Disable, enable and remove

All three are in the row's **⋮** menu.

| Action | Shown when | What happens |
|---|---|---|
| **Disable** | The row is `Live` | The touchpoint stops reaching this agent straight away: the widget stops serving your site, calls are no longer answered by the agent, or WhatsApp messages are no longer answered. Settings, conversations, tickets and contacts are kept. |
| **Enable** | The row is `Disabled` | It serves again at once, with the same settings. Refused with *Enable the channel connection before resuming this deployment.* if the touchpoint itself was disabled on its channel page. |
| **Remove** | The row is not `Live` | Asks *Remove this deployment?* The touchpoint stays connected and past conversation history is kept. Confirm with **Remove deployment**. |

The confirmation toasts say *paused* and *resumed*, for example *Deployment paused — this agent stops answering calls.* They mean **Disable** and **Enable**.

![A Disabled phone deployment with its menu open, showing Edit settings, Enable and Remove](https://docs.amomic.in/screens/agents/deployments-row-menu.light.webp)

Things to know:

- **Disable before you remove.** A live deployment cannot be removed. The menu hides **Remove** until it is disabled.
- **Disable is the fastest stop.** If an agent is saying something harmful on one channel, disable that deployment first and fix the agent after. To undo a bad change everywhere at once, [roll the agent back](/build/versions#roll-back-to-an-earlier-version) instead.
- **Removing does not release anything.** Removing a phone deployment keeps your number, and removing a WhatsApp deployment keeps your WhatsApp connection. You can deploy an agent there again later.
- **Archiving an agent** needs every one of its deployments disabled first. See [Archive and restore an agent](/build/agents#archive-and-restore-an-agent).

## Deployment limits

Your plan sets how many deployments the workspace can have. Deployments that are serving, disabled or not yet live all count. Removed deployments, and the earlier deployments left behind when you change voice settings, do not. At the limit, deploying is refused with *Your plan includes {limit} deployment(s). Upgrade to add more.* See [Limits and plans](/operate/limits).

## Usage by touchpoint

Below the tiles, **Usage by touchpoint** shows how much each deployment of this agent is being used. It appears once the agent has at least one deployment.

![Usage by touchpoint over 7 days: Where traffic lands, with the website widget, WhatsApp number and an Unattributed row, and Conversations over time by channel](https://docs.amomic.in/screens/agents/deployments-usage.light.webp)

Pick a range: `24h`, `7 days`, `30 days` or `90 days`.

- **Where traffic lands** lists each touchpoint with its share of the agent's traffic.
- **Conversations over time** shows the trend, split by channel.

| Channel | Figures shown |
|---|---|
| Phone | Calls, Minutes, Callers |
| WhatsApp and web | Chats, Messages, Visitors |

A touchpoint that has had more than one deployment, for example after you changed its voice settings, has **Show deployments**. It breaks the traffic out per deployment with the agent version each started on.

::: note `Unattributed` is history, not an error
An **Unattributed** row counts traffic from before per-deployment tracking, or from a touchpoint that can no longer be identified. It is kept so the totals stay honest, and it shrinks as older traffic leaves the range.
:::

Conversations from the **Test** tab are not counted. The same 5,000-conversation ceiling per range applies as on the Analytics page. See [Before you trust a number](/console/analytics#before-you-trust-a-number).

## Troubleshooting

| What you see | Why | What to do |
|---|---|---|
| No **Deploy** button in the header | The agent has never been published. | Publish it. See [Versions](/build/versions). |
| A number shows `Unavailable` · *Verification required* | The number has not finished verification on its channel. | Finish it on the channel page under **Channels**. |
| A row is `Not live` | The deployment never passed its checks. | Open **Edit settings**, complete it and save, or **Remove** it. |
| A row shows `Error` | The channel reports a fault, for example an expired WhatsApp authorisation. | Open the number's page under **Channels** and reconnect. |
| *Connection changed since it was loaded.* | Someone else changed this touchpoint while you had the page open. | Reload and try again. |
| I changed the agent but the phone greeting is the same | The opening line is a deployment setting. | Change it in **Voice settings**. |
| **Enable** fails | The touchpoint is disabled on its channel page. | Enable it there first. |

## Where to go next

::: cards

::: card Publish before you deploy
[Versions](/build/versions): publish, compare and roll back.
:::

::: card Check it first
[Testing & publishing](/build/testing): the Test tab and readiness checks.
:::

::: card Put it on a phone number
[How voice works](/channels/voice) and [Numbers and KYC](/channels/phone-numbers): numbers and per-deployment voice settings.
:::

::: card Put it on WhatsApp
[Set up WhatsApp](/channels/whatsapp): connecting and verifying a number.
:::

:::