Capacity Integration Progress

Bot Override Logic on Incoming Messages

Because the first point of entry in our system is incoming message handling, we needed to add new override logic at the very beginning to evaluate if the customer line had the BotEnabled flag or not. If the line was BotEnabled, then we need to publish an event to push all of the incoming message processing and specific logic over to the ChatBot Microservice. Once passed to the ChatBot Microservice, we evaluate what type of Bot it is, e.g. a catch-all for all incoming, or a keyword-specific trigger and then process.

If the line is not BotEnabled, then it will process as normal, creating or adding to an existing live conversation, sending notifications, etc.

Setup Incoming Message Processor for ChatBot Microservice

Piggybacking off of the above, we needed to create the Incoming Message Processor for this specific microservice and add the appropriate logic for handling what needs to take place. This will do things like, determine if there is already an open conversation to post the message to and if not create one, and validate that the conversation is an active bot session.

Setup Public API Endpoint to Handle Capacity Responses

This is the first "public" endpoint for communication between Textel and Capacity. We have created a controller just for our interactions with Capacity. This particular endpoint is going to be used to handle the responses posted to us by Capacity. These would be the responses generated as part of the Guided Conversation flow that we would then need to take in and send as an SMS response to the mobile contact.