@GOWTHAMALLU It is absolutely possible for customers to create their own channel. The process, however, could be a bit daunting as it should be because you're creating an entirely new integration between provider and platform.

1. At the outset, the first thing you need to do is create classes where your configuration and interaction cases live. (all rules preferably live in <ChannelName>Channel ruleset like FacebookChannel)

   1. Data-Channel-Configuration-<channel name> is used to store configuration and extensions for your UI like access tokens that the provider exposes.

   2. Work-Channel-Interaction-<channel name> is used to store interaction of the user until the timeout expires.
2. Then, you'll need to create endpoint Services and Connectors for back and forth between your bot and the platform.
3. You'll also need to set up authentication so that incoming user can be mapped to an existing operator or create new operator and call pxChannelAuth activity.
4. pxProcess is the meat of MCP. Before calling you need to prepare input for it and after it ends you can use output to build text that your bot understands.
   1. You'll need to map incoming message into pyInteractionCase.pyInboundMessage
   2. The output of pxProcess is pyInteractionCase.pyOutboundMessage() pagelist which you can use to construct string (like JSON in FB) that channel provider understands.

You can get FB component from Exchange and see how you'd go onto modify behavior for your channel. Please post here if you have issues. 

@GOWTHAMALLU It is absolutely possible for customers to create their own channel. The process, however, could be a bit daunting as it should be because you're creating an entirely new integration between provider and platform.

1. At the outset, the first thing you need to do is create classes where your configuration and interaction cases live. (all rules preferably live in <ChannelName>Channel ruleset like FacebookChannel)

   1. Data-Channel-Configuration-<channel name> is used to store configuration and extensions for your UI like access tokens that the provider exposes.

   2. Work-Channel-Interaction-<channel name> is used to store interaction of the user until the timeout expires.
2. Then, you'll need to create endpoint Services and Connectors for back and forth between your bot and the platform.
3. You'll also need to set up authentication so that incoming user can be mapped to an existing operator or create new operator and call pxChannelAuth activity.
4. pxProcess is the meat of MCP. Before calling you need to prepare input for it and after it ends you can use output to build text that your bot understands.
   1. You'll need to map incoming message into pyInteractionCase.pyInboundMessage
   2. The output of pxProcess is pyInteractionCase.pyOutboundMessage() pagelist which you can use to construct string (like JSON in FB) that channel provider understands.

You can get FB component from Exchange and see how you'd go onto modify behavior for your channel. Please post here if you have issues.