Motivation

The core idea came from our own experience initiating an automated customer retention system for one of Indonesia's leading telecommunications companies. At certain times, new memos appeared almost every week. While many remained drafts, some were worth trying. Yet implementing each one required engineering work hence the delays or even cancellations. Meanwhile, most changes require no programming expertise at all.

Monitoring and organizing customer retention workflow presented another difficulty. For instance, a workflow may need to be modified while customer records are being processed and scheduled to be transferred to another workflow at a later stage. In some situations, manual intervention may require the forcible transfer of some records to a new workflow before the current process is completed. On another occasion, certain records may also appear in multiple workflows which is acceptable, but sometimes it creates conflicts that must be resolved by removing the records from all but one workflow.

The difficulty of performing business performance analysis is largely a consequence of this complexity. Many present solutions are either incapable of processing medium-sized information effectively on local machines or demand unnecessary expensive infrastructure. Such tasks can already be handled by modern data technologies, albeit there are still few accessible graphical user interfaces for business users.