 |
Many banking operations provide opportunities to publish events which are of interest to other application owners or users within the bank.
Consider the following scenario. A registered customer has logged in to your bank’s website and while browsing gets interested in a product, like a loan offering or a deposit scheme. She may just read a few details, click on something else and move on, forgetting the product or scheme that had initially interested her. In effect, the bank has lost out on an opportunity to take the customer’s interest to the next level and create meaningful
business interaction.
Now consider altering the situation a little. The bank’s applications support Event Driven Architecture (EDA).The customer’s interest is captured as an event by the system, and it proceeds to take a series of further action:
- It records the visitor as a prospect for the product or scheme that interested her, and creates an opportunity in the CRM system.
- It sends out communication to the visitor’s registered e-mail address with relevant details about the product or scheme.
- It alerts the bank’s product sales team about the visitor’s interest in the product and forwards her contact number, to the team, for further action.
|
