Creating a future state design
With our new understanding of the current state and the pain points of the accounting team, we can start with creating a future state design of the automation. Since this automation requires no human interaction, creating a future state design for this use case is generally straightforward, as depicted in the following screenshot:
Figure 9.6 – High-level future state design
For this use case, automation will have the responsibility of monitoring the accounting team's shared inbox. The automation can run in the background in an attended or unattended scenario, scanning the shared inbox for new emails. Once an email is received, the automation will retrieve the email, read its contents, and classify the email as spam or not spam based on the contents of the email body. Lastly, based on the classification, the automation will route the email to a corresponding folder where an accounting analyst can review it. The folders...
