Clone a Dunning Schedule

Cloning a Dunning Schedule lets you start from an existing schedule instead of building a new one from scratch. It copies the steps and messaging so you can make quick adjustments for a new product scope, collection method, or business scenario.

When you clone a schedule, Advanced Billing duplicates:

  • The sequence of steps (days, actions, retry settings, and message delivery settings).
  • The email templates tied to each step, so you can edit them without changing the original schedule.

When Cloning is Useful

Here are common real-world reasons to clone a Dunning Schedule:

  • Different product scope, same process
    You already have a proven dunning cadence for one product family and want to apply it to a new product without re-entering every step.
  • Seasonal or promo variations
    You want a shorter dunning window for a limited-time offer while keeping your standard schedule intact.
  • Regional policy differences
    You need a slightly different sequence of reminders for customers in a new market or business unit.
  • Testing improvements
    You want to experiment with a new sequence of steps (emails, retries, cancellation timing) without disrupting your current live schedule.

How to Clone a Dunning Schedule

  1. Go to Retries & Dunning in your Advanced Billing settings.
  2. In the Dunning Schedules list, find the schedule you want to copy.
  3. Open the Actions menu (ellipsis) and select Clone.
  4. Update the schedule details (name, collection method, and scope) as needed.
  5. Review the steps and messaging, then Save the new schedule.

Tips

  • Give the cloned schedule a unique name so it is easy to identify later.
  • After cloning, check Advanced Settings and any Additional Triggers to make sure they match your intended use case.
  • If you are cloning for a new collection method (for example, moving from Credit Card to ACH), review the steps to ensure they align with that payment flow.
Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.