> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.youratlas.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.youratlas.com/_mcp/server.

# Clone Campaign

## Cloning Process

1. Select the campaign to clone and click "Clone"
2. Rename and change type from Outbound to Inbound
3. Choose whether to clone the backing agent (see [Cloning the agent](#cloning-the-agent) below)
4. Add a phone number to the new campaign
5. Activate

**Cloned:** Script, call forwarding, calendar, SMS tools, enrichment settings, backing agent (see below).
**Not cloned:** Phone number (must be manually added).

After cloning, the campaign list scrolls to the new campaign and plays a brief entrance animation, so it is easy to spot.

## Cloning the agent

If the campaign you're cloning is backed by a Marketplace or workbench agent, the clone modal shows a **Clone agent** toggle, on by default:

* **On** — the source campaign's agent is cloned into a new, independent agent in **My Agents**, and the cloned campaign is pointed at that new agent. This gives the clone its own editable copy, so script or voice changes on one campaign's agent don't affect the other.
* **Off** — the clone reuses (shares) the original campaign's agent. Changes made to the shared agent afterward affect every campaign using it.

The toggle is locked on, with an explanatory note, when the source campaign isn't backed by a marketplace/workbench agent — there's nothing to clone in that case.

Either way, the campaign-level Agent configuration (the per-campaign runtime call settings) is copied to the new campaign.