Cross-client campaign cloning

Every campaign already has a Duplicate action, in its overflow menu, that copies it within the same workspace. Agency Groups extend that exact same action with an optional destination: pick a different client workspace, under the same agency, to clone into instead.

Duplicating a campaign

Choosing Duplicate opens a small modal: a name field pre-filled as {campaign name} (Copy), a Keep steps toggle, and — only when the account has access to at least one other workspace to clone into — a destination workspace picker.

Cloning into another workspace shows a confirmation toast: Cloned to "{destination name}" — switch workspaces to view it. — the clone lands in the destination workspace immediately, you don't switch into it automatically.

Requirements

• Same agency, no exception. The source and destination workspace must both belong to the same Agency Group. Attempting to clone across two different agencies (or into a standalone workspace) is rejected outright.
• You need access to the destination too. Belonging to — or even owning — the Agency Group isn't enough on its own; the person cloning must already be a member of the destination workspace, the same requirement every other workspace-scoped write in ForgeSend already has.
• Same-workspace duplication is unchanged. Leaving the destination picker on the current workspace (or never seeing it, if there's nowhere else to clone into) behaves exactly as ordinary same-workspace duplication always has.

What copies over

Sender inboxes don't transfer because they belong to one specific client — an inbox connected in Client A's workspace has no meaning in Client B's. A campaign cloned into another client's workspace arrives without a sender pool assigned; it needs one picked for that destination workspace before it can be launched there.

Where to go next

Next: Agency API keys

• Sequences and steps
• Suppression across clients
• Agency Groups overview