**YouTube** is an American [online video-sharing](https://en.wikipedia.org/wiki/Video_hosting_service "Video hosting service") [platform](https://en.wikipedia.org/wiki/Web_platform "Web platform") headquartered in [San Bruno, California](https://en.wikipedia.org/wiki/San_Bruno,_California "San Bruno, California")

cf3f59da-c081-4fab-99d2-f02e60e183b0.PNG

While this is on the early stages of development and is open to many ideas, this framework already covers a lot of major areas. Such as Session Handling, Response Handling, Usage of RE-Framework and Orchestrator.

RPA Facebook Chatbot Framework is just one of the solutions to revolutionise Chatbots. While this is on the early stages of development and is open to many ideas, this framework already covers a lot of major areas. Such as Session Handling, Response Handling, Usage of RE-Framework and Orchestrator.

**Session Handling**

The idea behind the interaction between the user and the chatbot is purely based on sessions (or states). The chatbot, before processing the inputs of the user, determines which session he is on. However, sessions can be bypassed once it determines the type of action he is doing; since part of the framework are to handle quick access requests and input validations. How does the chatbot handle sessions? By simply connecting the robot to a database; but in our case, we will use Excel as an alternative.

**Response Handling**

The chatbot is also based on templates. These templates are used to determine which response to send to the user. The template currently supports these types of responses: text, attachment, quick reply, and button template. The template also handles the accept types that will be used to validate the input of the user. 

**Usage of RE-Framework and Orchestrator**

The chatbot is built with RE-Framework. Modifications on the RE-Framework were made to suit the flow of the chatbot. It also uses the Orchestrator as a connector for the chatbot to send a request to the robot by using its Queue Service. The robot, however, does not need to use the Orchestrator to connect to the chatbot as it can directly send a Facebook API request.

This also assumes that the developer must be knowledgeable of the technologies and applications used to integrate with the Robot. He/She must also have the high understanding of how chatbots work and understand very well the scope and limitations of Facebook API.The idea behind the interaction between the user and the chatbot is purely based on sessions (or states). The chatbot, before processing the inputs of the user, determines which session he is on. However, sessions can be bypassed once it determines the type of action he is doing; since part of the framework are to handle quick access requests and input validations. How does the chatbot handle sessions? By simply connecting the robot to a database; but in our case, we will use Excel as an alternative.

**Response Handling**

The chatbot is also based on templates. These templates are used to determine which response to send to the user. The template currently supports these types of responses: text, attachment, quick reply, and button template. The template also handles the accept types that will be used to validate the input of the user. 

**Usage of RE-Framework and Orchestrator**

The chatbot is built with RE-Framework. Modifications on the RE-Framework were made to suit the flow of the chatbot. It also uses the Orchestrator as a connector for the chatbot to send a request to the robot by using its Queue Service. The robot, however, does not need to use the Orchestrator to connect to the chatbot as it can directly send a Facebook API request.

This also assumes that the developer must be knowledgeable of the technologies and applications used to integrate with the Robot. He/She must also have the high understanding of how chatbots work and understand very well the scope and limitations of Facebook API.

RPA Facebook Chatbot Framework is one of the ways to revolutionise chatbots. This is an initiative to interconnect the RPA solutions and Chatbot functionalities to have a smooth flow of direction

4ce2a70a-eb26-4438-9aa9-23209ccb622a.PNG

MIT License Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.