Dunning actions

Concept

Now that you have defined the general settings for the Dunning feature, let’s start by defining the templates that you will use for some specific actions (that you will define just after).

Before starting, let’s quuickly resume the way a Dunning policy works in Opencell :

A dunning policy is an object that has several levels. Each level has one or several actions linked to it. Some actions can be automatic or manual, and for some action types, a template will be used to automate the flow.

All these different notions are objects in Opencell, and the way to create a dunning policy is to start from the most granular object, and work your way up to the actual Dunning policy.

This is best represented below:

Templates, actions, levels and policies are all independent objects linked to one another.

Accessing Dunning Actions in Opencell

In Opencell, you can manage Dunning Actions within the Customer Care module.

How to Navigate to Dunning Actions

1. Log in to your Opencell environment.

2. Go to Customer Care → Configuration → Dunning → Actions .

The Dunning menu follows the logical order of configuration steps required to implement dunning policies. All dunning-related submenus are accessible under the Customer Care module.

Dunning Actions Overview

Upon accessing the Dunning Actions page, you will find:

• Predefined Actions that can be used as they are, modified, or deleted based on your needs.

• A search bar to quickly find actions by name.

Creating a Dunning Actions in Opencell

You can create your own Dunning Actions from the Actions List View by clicking the “+” button in the top-right corner of the page.

1. Accessing the Actions Creation Page

Once you click “+”, you will be redirected to the action creation page:

2. Configuring Your action details

On this page, you can define key action settings, including:

• Action Name → Assign a name for easy identification.

• Action Description→ Assign a description for easy identification.

• Action Type → Specifies the type of action : Retry payment , Script, Send notification

• Action Mode→ Determines the execution mode: automatic or manual

1. Configuring every type specifications

2. For the script action we must choose a dunning script which must be developed before policy configuration. as explained in the dunning concept part.

   

3. The retry payment doesn’t need any configuration

   

4. The send notification have multiples details:

   1. email, letter or call as notification channel

   2. template for email and letter as definied in the dunning tempaltes

   3. Assigned user for manual action, we use a dummy user as explaine on concept part.