Embedded Files
A new feature has been added to enhance the Auto-Payment Group Trigger. This works in the scenario when an operator has two sets of customer groups each with different notication and disconnect settings.
It is mostly used to control notifications to customers who signed up for auto-payment. For these customers no payment reminders are sent, only a disconnect notice.
This feature is developed to allocate one sets of customers (based on group label) and assign them to their specific auto-pay-notification-off group. The other sets of customers (no label) are assigned to another auto-pay-notification-off group.
To make use of this feature:
1. Determine if customer base has more than one set of customers with different notification and disconnect settings. To illustrate we'll state the operator has a postpaid and prepaid customer base who sign up for auto-payment. SAND settings for prepaid customer is set under SPID settings, for the postpaid customer it is set under a seperate customer group > Legacy.
2. Once the two sets of customer is determined, two customer groups need be created. One for prepaid and one for postpaid customers; under Setting > Groups, provide a meaningful name and description - fig1.
Fig 1: Postpaid Group (Legacy) and Prepaid Group
3. Copy all settings of the Legacy postpaid group to the group Auto-pay-notification-off Legacy, except SAND settings. Under SAND settings the notification days are blank and only disconnection date is set.
As the prepaid group takes SPID SAND settings, no settings need to be copied over to the group Auto-pay-notification-off Prepaid. Here also under SAND settings the notification days are blank and only disconnection date is set.
leaving the notification fields blank ensures no email and/or sms notificaiton is send - fig3.
IMPORTANT: set the groups priority to 1. The settings in the highest priority group - in this case 1 - will be applied over lower priority - fig4. * as a side note: verify if groups of the other groups are of lower priority 2 - 10.
Fig 3: Group Disconnection date
Fig 3: Group Priority Attribute
4. Once the groups are created, the triggers need to be set. Note group ID is 15 for postpaid customers and Group ID 16 for prepaid. We can do this from Settings > External API (triggers) page.
Change 'Customer Auto-Payment Change' to Queue - fig4.
Fig 4: Trigger - Customer Auto-Payment Change
5. Create 3 conditions for each group of customers. One to assign customer to the notice-off group for credit card auto-payment sign up another one for direct debit sign up and the third one to remove customer from the group, when they are no longer on auto-pay.
Fig 5: Condition customer_in_group
6. One set with condition customer_in_groups=2 - It means: if customer belongs to group "Legacy (postpaid)" assign / deassign them to/from AUTO-NOTIFICATION OFF (Legacy) - above is one of the examples:.
Fig 6: Description
7. One set with condition customer_not_in_groups=2 - It means: if customer does not belong to group "Legacy (postpaid)" assign / deassign them to/from AUTO-NOTIFICATION OFF (Prepaid) - above is one of the examples:
Published Date: 22 May 2025
Engineer: PD
Contact Azotel Support:
Need more help? Save time by creating a maintenance ticket to Azotel through your instance or email support@azotel.com.
Page updated
Report abuse