Event applications are designed for task flow or batch processing, and are typically invoked by events, such as scheduled times, system triggers, or external triggers.
- Self-registration – register telephone numbers using SMS; for customers who did not provide their number when signing up with the company.
- Self-services – such as looking up usage history and status of move-in activation, reporting issues, and finding offices.
- Notifications – set up notifications for overdue payments, high usage, service-outage alerts, summer-savings awareness, and so on.
- Engagement – enables customers who receive notifications to reply. For example, if customers respond to overdue-payment notifications, they automatically receive 1–2 days extension; they can also authorize automatic payments.
In this example, the company's customer relationship management (CRM) system generates a list of subscribers who have opted to receive outage notifications. The list contains customer telephone numbers (MSISDNs) and cities for which an outage-notification service is provided. This list is uploaded to Brand Mobiliser subscriber storage. When a service outage is planned for the city of Dublin, the Process Subscriber state retrieves subscribers from the list. For each subscriber:
- Get Subscriber Details retrieves subscriber attributes (city).
- Check City=Dublin filters out customers who are not in Dublin.
- Send SMS Outage Message sends a message to Dublin customers.
Invoke the application, by assigning it to an active event, and creating an event window. Event windows can be one-time or recurring. This application has a one-time event window.
An alternative to manually uploading subscribers to the database is to use an event application to fetch subscribers from the system of record, and use batch processing to upload and store them in the database.