Event Correlator intends to unleash the ability to write flows, orchestrate existing APIs and build new process driven applications in weeks instead of months to develop, debug, maintain, modify and recycle.
In call center, imagine a white glove (high net worth) customer is speaking to a banker on his way home and the conversation drops as he drives over 280. The conversation may have been completed but what if it wasn't? Can our application give the banker an option to call back the same customer ? Imagine how valued the customer feels if he gets a call back from the exact same banker or agent saying “sir / madam sorry we got disconnected, lets continue our conversation”, without having to dial back, listen to prompts, go through self identification three different ways and send the code received in SMS.
Insurance quote application for generating insurance quotes based on data collected online. There is a form designer that lets users create a pretty form (like Figma) and the information submitted is stored in a backend data store. This is a fairly straightforward application being built since the days of Oracle forms, HTML, JSP and Servlet days. However, what happens when the person who filled the quickly generated form, comes back to the website or chats with an agent on the app or (yes still true in 2022) makes a phone call to the 800 number. Does the agent get a full context about the customer profile from the app or website?
One easy way to explain this concept is using a simpler mortgage application process. The retail banker and customer interact multiple times to gather stipulations (documents), validate the application and kick off the loan process by payment of appraisal fees. However, the most critical resource, the underwriter is assigned only after all of these interactions have finished. This ability to interpret that execution has to wait as there is a possible live path upstream is a fairly complex problem in graph theory.