Embedded Files
A new feature is added to enhance the EUP and SMS functionality. The goal is to allow the customer to self service and select which sms type they would like to opt-in for.
We will make use of the custom fields for the different message types.
To make use of this feature:
1. Create a custom field called 'SMS Message Type OPT-IN' with a set of checkbox.
2. The custom field should be type 'checkbox group'and should have options available like: Outage, Marketing, SAND (semi-madatory and hidden from the selection list), Trigger SMS (optional), Cronjob SMS (optional), Visit Notification (optional). - see fig1
Fig 1: Define Custom Field
3. Each custom field can have a label. We therefor suggest to label SAND > 'Billing Notification' (the term SAND would be confusing for the end customer - see fig2
Note: The order of options is the order they will appear in the selection list
Fig 2: Label Options
4. Under the EUP section of the custom field select 'display and edit' to allow cusomer to make their selections - see fig3
Fig 3: EUP Display Option
5. Once the custom field is defined it will be visible in SIMPLer fig4 and in the End User Portal (EUP) > under tab 'modify personal details' fig5
Fig4: SIMPLer Custom Field Checkboxes
Fig5: EUP Custom Field Checkboxes
Enable the feature:
6. This feature gets enabled when the custom field ID is assigned to the SMS gateway. Once enabled the custom field is the main driving factor for SMS opt-in / opt-out functionality and old legacy SMS_disabled ption will no longer be used. Customers are opted out by default until they opt-in using this option. fig6
Fig6: SMS gateway opt in field
Use the feature:
A few screenshot examples will show the several ways this feature can be used.
7. SIMPLer SMS mass function. Example message type outage. fig7. When the Prepare SMS button is selected the user is prompted to verify the message type shown in red on the next page fig8. At this stage the sms can also be scheduled. - See useful links section at the end of this page.
Fig 7: SIMPLer Mass SMS Interface
Fig 8: SMS verification page
8. SAND/Trigger SMS. Example trigger. fig9.
9. Email / SMS customer Cronjob . Example cronjob fig10.
10. Customer Visit Notification Cronjob. Example cronjob fig11
Fig 9: SAND / Trigger SMS
Fig 10: Email / SMS customer from Cronjob
Fig 11: Customer Visit Notification from Cronjob
Note: Once a custom field is created and an SMS module points at it, no customer will receive a SMS until the customer is configured to receive a specific type of message.
In cases where the operator makes use of vetro, it will no longer overwrite the default opt-out behavior.
The SMS options are accesible for the CSR on the customer account
When sending a SMS from the SIMPLer interface, there is an option to select the Message Type - Fig7
Published Date: 27 March 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