Chatbots, as a means of customer interaction, are taking the financial sphere by storm as more bots are launched weekly. Established financial institutions, mostly in the retail-banking sector, investment management and wealth management sectors, are jumping on the bandwagon and experimenting with bots. Financial institutions have embraced this trend and experts predict that, within five years, bots will replace conventional online interfaces such as websites or mobile apps.
To give you a head start, we’ve built a starter kit to help you better serve your clients (something that digs a layer deeper than just saying innovation) The Watson Conversation based Wealth Management Chatbot starter kit enables you to query your investments, to analyze the effect of various scenarios on them, and to switch between a web interface and a Twilio interface.
Once you deploy, check out the recommended next steps to build on the starter kit. For example, you can build support for additional market scenarios or add the Twilio interface. Here’s an example architecture and details on how the code works:
Set up multiple communication channels (for example, WebUI or Twilio). The application listens for messages from either channel.
The Conversation API takes in natural language input and breaks and maps it to intents and entities that it has been trained for. The app makes a call to the respective financial service based on the intent that was identified. Train Conversation for additional intents and entities to make for a more robust conversation experience.
The context of the conversation is saved to Cloudant DB so that the Conversation API is able to save the state and track the conversation flow of the user.
The Portfolio Investment API is called if there is a query asking for information around the holdings or portfolio. An asynchronous call is made through a “Promise Request” to make the query and return the results. Subsequently, the results are parsed and formatted in a response object that is sent back to the Conversation interface.
The Simulated Analytics API is called if the intent is identified as “impact analysis.” This call initially requires issuing an asynchronous “Promise Request” querying the name of the holdings currently owned using the Portfolio Investment API. This is stored in an object that is subsequently sent to the Simulated Instrument Analytics service (SIA). SIA pulls the base and conditional price out of the object in order to compare against the potential market changes and return a measure of the impact to the holdings in this scenario. (In this use case, the change scenario is querying how the portfolio would perform if the S&P 500 drops by 5%. Results are parsed and formatted in a response object that is sent back to the Conversation interface.