# How to Duplicate a Flow in ZazzyAgent

Building a good flow takes time.

Once you've created one that works, you often don't need to start from a blank canvas for the next automation.

[ZazzyAgent](http://zazzyagent.com) provides flow management options that let you **duplicate an existing flow** and use it as a starting point.

## Why duplicate a flow?

Duplication is useful when two automations have a similar structure.

For example:

**Lead Qualification**

and:

**Appointment Qualification**

may both contain:

*   Welcome message
    
*   Customer information
    
*   User Input
    
*   Conditions
    
*   Labels
    
*   Confirmation
    

Instead of rebuilding the entire structure, duplicate the existing flow and modify the differences.

## When should you duplicate?

Use duplication when:

*   A new flow is similar to an existing one.
    
*   You want to create a variation.
    
*   You want to experiment without changing the production version.
    
*   You want a test version.
    
*   You want to reuse a standard structure.
    

## Open your flow list

Open the bot/flow management area in ZazzyAgent.

Find the flow you want to reuse.

The current flow-management interface provides actions for editing, duplicating, copying and exporting flows.

## Find the Duplicate action

Open the actions menu for the flow.

Choose the option to duplicate the flow.

This creates a separate copy rather than modifying your original flow.

## Rename the duplicated flow

Immediately give the duplicate a useful name.

For example:

Original:

> Lead Qualification

Duplicate:

> Lead Qualification – Enterprise

This prevents confusion later.

## Why naming matters

If you have:

*   Flow 1
    
*   Flow 2
    
*   Flow 3
    
*   Copy of Flow 2
    

you'll eventually have no idea which one is live.

Use names that describe purpose.

## Review the trigger

After duplicating a flow, check its trigger.

You may not want both flows responding to the same keyword.

For example:

Original:

> demo

Duplicate:

> enterprise-demo

This keeps the two automations separate.

## Review labels

If the original flow adds:

> Lead

you may want the new flow to add:

> Enterprise Lead

Don't assume duplicated actions are appropriate for the new use case.

## Review custom fields

Check all saved fields.

The original flow may collect:

> Product Interest

while the new flow needs:

> Service Interest

Update the destinations as necessary.

## Review API integrations

If the original flow contains an HTTP API action, check it carefully.

You may accidentally send test information to your production system.

A duplicated flow should always be reviewed before activation.

## Review external URLs

Check every CTA URL and external link.

A duplicated flow may still point to the old landing page.

## Review templates

If your flow uses WhatsApp templates, check that the correct template is attached.

A duplicate isn't automatically a reason to use the old template.

## Review human assignments

If the original flow assigns conversations to:

> Support

but the new flow is for:

> Sales

change the assignment.

## Review sequences

Check any sequence-starting actions.

You don't want a duplicated flow to accidentally enroll customers in the wrong follow-up sequence.

## Test the duplicate separately

Before activating it for real customers:

1.  Trigger the duplicate.
    
2.  Test every branch.
    
3.  Check labels.
    
4.  Check custom fields.
    
5.  Check API actions.
    
6.  Check human routing.
    

## Use duplication for A/B testing

You can also use duplication to create variants.

For example:

**Lead Flow – Version A**

and:

**Lead Flow – Version B**

Change one major element and compare the operational results.

Keep track of which version is active.

## Don't edit the original by mistake

This is one of the most important habits.

After duplication:

> Confirm which flow you're editing.

Especially when multiple flows have similar names.

## Duplicate vs copy to another bot

These are different.

### Duplicate

Creates another version within the same bot/account.

### Copy to Other Bot

Copies the flow to another connected bot.

The current platform distinguishes these flow-management actions.

## Duplicate vs export

Duplication is an in-platform reuse method.

Export creates a JSON file that can be stored or imported later.

## Example

Original:

```text
Lead Flow
   ↓
Collect Name
   ↓
Collect Email
   ↓
Label Lead
```

Duplicate:

```text
Enterprise Lead Flow
   ↓
Collect Name
   ↓
Collect Email
   ↓
Collect Company Size
   ↓
Label Enterprise Lead
```

The duplicate saves the repetitive building work while allowing you to customize the new process.

## Best practice

Before activating a duplicated flow, review:

*   Trigger
    
*   Messages
    
*   Buttons
    
*   Inputs
    
*   Conditions
    
*   Labels
    
*   Sequences
    
*   APIs
    
*   URLs
    
*   Templates
    
*   Human routing
    

A duplicate is a copy of the configuration—not a guarantee that every setting is appropriate for the new purpose.

## The basic principle

> **Duplicate the structure. Review the logic. Then activate.**

That is much safer than assuming the copied flow is ready for production.