One and Two-Way Alerts

M-Com's alerting capability is currently in use for a broad range of alerts with financial institutions and is categorized into three broad alert types; threshold, scheduled and event-based alerts.

Some implemented and live examples include:

  • scheduled and threshold balance alerts
  • transaction history alerts
  • bill arrival, payment reminder and overdue alerts
  • loyalty point alerts
  • online banking exception notifications
  • payment threshold alerts
  • share / equities / portfolio threshold alert
  • various process alerts (e.g. 'gone, no address' notifications)
  • security and fraud alerts

M-Com's alerting capabilities support one-way and two-way (or 'actionable') alerts, and can be integrated into the enterprise's infrastructure via a variety of methods, including:

  • Web Services,
  • Bulk File delivery, both automated and manual,
  • Pull-based polling,
  • Email,
  • Custom API's.

M-Com's mobile alerting capability utilizes a three-stage 'pipeline architecture', with each stage of the pipeline handling a distinct aspect of the end-to-end alerting process. The stages are; a) triggering, b) composition, and c) delivery.

The driver behind this architectural position is to enable retail banks that already have portions of the alerting process or sub-processes in place (e.g. for email alerts) to effectively and efficiently interface into the appropriate stage of the bank's end-to-end alerting process.


Beyond Alerts – Resilient Messaging

We don't just deliver alerts; we provide tools for financial institutions to communicate with their customers in a robust and reliable way. Resilient Messaging is about high performance, reliability and safety alerting capabilities.

.

Not all alerting products were created equally. We think rigor, robustness and resilience matter when it comes to alerting. If you want to know why Resilient Messaging makes our alerts capability better, please Contact Us.

Alerts in Action