WO2022203419A1

WO2022203419A1 - Method and system for an optimized chatbot communication

Info

Publication number: WO2022203419A1
Application number: PCT/KR2022/004130
Authority: WO
Inventors: Sunil Kumar NAGARAJU; Priti Singh
Original assignee: Samsung Electronics Co., Ltd.
Priority date: 2021-03-24
Filing date: 2022-03-24
Publication date: 2022-09-29

Abstract

Present disclosure describes system and method for optimized chatbot communication. Method identifies a message type to be a payment type or a non-payment type on a chatbot interface. When message type is payment type, method adds a traffic type header to a payment link and presents payment link along with traffic type header. Method checks whether payment is successful using payment link. When payment is successful, method sends transaction identifier and/or booking information as postback message to chatbot via chatbot interface. When message type is non-payment type, method identifies a traffic type header for the information on the chatbot interface and adds traffic type header to information. Method presents information as a thumbnail image along with traffic type header, without downloading the information, when traffic type header is an advertisement. Method checks reply-type permission in chatbot interface and configures chatbot interface for user interaction with chatbot based on reply-type permission.

Description

METHOD AND SYSTEM FOR AN OPTIMIZED CHATBOT COMMUNICATION

The present disclosure generally relates to the field of communication technology. Particularly, but not exclusively, the present disclosure relates to a chatbot communication system and a method for an optimized chatbot communication.

Currently, there are various interactive agents i.e., chatbots that communicate with users through text, voice, display and the like. Certain applications require the interactive agents to communicate with users via text. Such interactive agent provides response to user's queries related to certain services via text or text-to-speech. Further, the user performs specific actions such as initiating transactions, sharing crucial information, etc. For example, while using digital platforms for performing payment related transaction, it becomes essential to know beforehand whether Uniform Resource Locator (URL) link received from the interactive agent is secure or not. Further, in the conventional systems, the user does not have flexibility to determine in advance whether the received response contains any encrypted information or is related to a payment and/or an advertisement. Due to the above-mentioned limitations, the user faces difficulty while deciding next actions to be performed based on the communication with the interactive agent, thereby, hampering user's interactive experience.

Further, in the conventional systems, when the interactive agent sends a URL link for accessing an external application to the user through messaging platforms, the user manually inputs information associated with the external application to the interactive agent. In case of URL link failures, the user needs to repeatedly send the information back to the interactive agent after each trial. The user may find this process cumbersome, thereby, resulting in an inefficient communication. Also, frequent sending of the information back to the interactive agent leads to wasteful usage of data. Further, the conventional systems provide auto-download facilities integrated with rich cards sent from the interactive agent, leading to unintended consumption of data at user end. Additionally, in the conventional systems, the interactive agent specifies a set of suggested replies and suggested actions that constitute a persistent menu, without mentioning preferred way interactive agent wants user to communicate. This leads to inefficient interactive communication.

The information disclosed in this background of the disclosure section is only for enhancement of understanding of the general background of the invention and should not be taken as an acknowledgement or any form of suggestion that this information forms the prior art already known to a person skilled in the art.

There is a need for an approach to optimize communication between user and interactive agents i.e., chatbots.

In an embodiment, the present disclosure relates to method for an optimized chatbot communication. The method comprising identifying a message type to be one of a payment type and a non-payment type on a chatbot interface based on information on the chatbot interface. When the message type is identified as the payment type on verifying presence of a payment link in the chatbot interface, the method comprises adding a traffic type header as payment to the payment link and presenting the payment link along with the traffic type header on the chatbot interface. Thereafter, the method comprises checking whether payment is successful using the payment link. When the payment is successful, the method comprises sending at least one of a transaction identifier and booking information as a postback message to a chatbot via the chatbot interface. When the payment is not successful, the method comprises sending a failure reason as the postback message to the chatbot via the chatbot interface.

The method, further comprising when the message type is identified as the non-payment type, identifying, by the chatbot communication system, a traffic type header for the information on the chatbot interface, adding, by the chatbot communication system, the traffic type header to the information; and presenting, by the chatbot communication system, the information as a thumbnail image along with the traffic type header, without downloading the information, when the traffic type header is identified as an advertisement.

According to another aspect of an embodiment, the method, wherein the non-payment type comprises the advertisement, a subscription, an encrypted message, an important message and the rating.

According to another aspect of an embodiment, the method, further comprising, when the message type is identified as the non-payment type, identifying, by the chatbot communication system, a traffic type header for the information on the chatbot interface, adding, by the chatbot communication system, the traffic type header to the information, checking, by the chatbot communication system, whether a visible window download setting is enabled, when a visible window download setting is enabled, downloading, by the chatbot communication system, only the information visible on a display screen for presenting along with the traffic type header when the traffic type header is identified as one of a subscription, an encrypted message, an important message and a rating, and when the visible window download setting is disabled, downloading, by the chatbot communication system, the information on the chatbot interface for presenting along with the traffic type header when the traffic type header is identified as one of the subscription, the encrypted message, the important message and the rating.

According to another aspect of an embodiment, the method, further comprising, checking, by the chatbot communication system, reply-type permission in the chatbot interface, and configuring, by the chatbot communication system, the chatbot interface for user interaction with the chatbot based on the reply-type permission.

According to another aspect of an embodiment, the method, wherein configuring the chatbot interface for user interaction with the chatbot based on the reply-type permission comprises, when the reply-type permission is 0, configuring, by the chatbot communication system, the chatbot interface for allowing a user to communicate with the chatbot using a persistent menu and a text box, when the reply-type permission is 1, configuring, by the chatbot communication system, the chatbot interface for allowing the user to communicate with the chatbot using only the persistent menu, when the reply-type permission is 2, configuring, by the chatbot communication system, the chatbot interface for allowing the user to communicate with the chatbot using only the persistent menu and suggested actions in the persistent menu and when the reply-type permission is 3, configuring, by the chatbot communication system, the chatbot interface for allowing only the chatbot to communicate with the user.

According to another aspect of an embodiment, the method, wherein the at least one of the transaction identifier and the booking information is generated after completion of a payment transaction using the payment link.

According to another aspect of an embodiment, the method, wherein the failure reason is generated after failed payment transaction using the payment link.

According to another aspect of an embodiment, the method, wherein the information comprises one of a payment link, an advertisement, a subscription, an encrypted message, an important message and a rating.

In an embodiment, the present disclosure may relate to a chatbot communication system for an optimized chatbot communication. The chatbot communication system comprising a processor and a memory communicatively coupled to the processor, wherein the memory stores processor-executable instructions, which on execution, cause the processor to identify a message type to be one of a payment type and a non-payment type on a chatbot interface based on information on the chatbot interface. When the message type is identified as the payment type on verifying presence of a payment link in the chatbot interface, the chatbot communication system causes the processor to add a traffic type header as payment to the payment link and present the payment link along with the traffic type header on the chatbot interface. Thereafter, the chatbot communication system causes the processor to check whether payment is successful using the payment link. When the payment is successful, the chatbot communication system causes the processor to send at least one of a transaction identifier and booking information as a postback message to a chatbot via the chatbot interface. When the payment is not successful, the chatbot communication system causes the processor to send a failure reason as the postback message to the chatbot via the chatbot interface.

According to another aspect of an embodiment, the chatbot communication system, wherein the processor is configured to, when the message type is identified as the non-payment type, identify a traffic type header for the information on the chatbot interface, add the traffic type header to the information, and present the information as a thumbnail image along with the traffic type header, without downloading the information, when the traffic type header is identified as an advertisement.

According to another aspect of an embodiment, the chatbot communication system, wherein the processor is configured to, when the message type is identified as the non-payment type, identify a traffic type header for the information on the chatbot interface, add the traffic type header to the information, check whether a visible window download setting is enabled, when a visible window download setting is enabled, download only the information visible on a display screen for presenting along with the traffic type header when the traffic type header is identified as one of a subscription, an encrypted message, an important message and a rating and, when the visible window download setting is disabled, download the information on the chatbot interface for presenting along with the traffic type header when the traffic type header is identified as one of the subscription, the encrypted message, the important message and the rating.

According to another aspect of an embodiment, the chatbot communication system, wherein the non-payment type comprises the advertisement, a subscription, an encrypted message, an important message and the rating.

According to another aspect of an embodiment, the chatbot communication system as claimed in claim 10, wherein the processor is configured to, check reply-type permission in the chatbot interface, and configure the chatbot interface for user interaction with the chatbot based on reply-type permission.

The chatbot communication system, wherein the processor is configured to, when the reply-type permission is 0, configure the chatbot interface for allowing a user to communicate with the chatbot using a persistent menu and a text box, when the reply-type permission is 1, configure the chatbot interface for allowing the user to communicate with the chatbot using only the persistent menu, when the reply-type permission is 2, configure the chatbot interface for allowing the user to communicate with the chatbot using only the persistent menu and suggested actions in the persistent menu and when the reply-type permission is 3, configure the chatbot interface for allowing only the chatbot to communicate with the user.

The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.

The present disclosure provides a method and a chatbot communication system for optimizing chatbot communication between a user and an interactive agent i.e., chatbot.

The present disclosure displays/presents a traffic type header along with a message or a response received from an interactive agent i.e., chatbot to a user. The presented traffic type header associated with the received message helps the user to differentiate type of messages received from the chatbot. This results in better user experience due to proper identification of type of received message, thereby, helping the user to promptly decide further actions.

The present disclosure enables automatically sending additional information associated with external applications to an interactive agent i.e., chatbot as postback message. This approach avoids intervention of the user for providing the additional information to the chatbot through the chatbot interface.

The present disclosure facilitates automatic download of restricted content in small size such as thumbnail and enables downloading of files with larger size based on user input on the chatbot interface. Furthermore, the visible window download setting allows user to preferentially download or restrict download, especially to files such as an image, a rich card and the like that is not visible on a display screen of the user device 101, in case of non-payment type and non-advertisement type messages. This approach reduces unnecessary data consumption/download at user end, which in turn optimizes bandwidth utilization and memory usage.

The present disclosure enables a preferred way of interaction with a user by the interactive agent i.e., chatbot based on reply-type permission. This enhances chatbot's capability to decide how user can communicate with chatbot for an optimal communication.

The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate exemplary embodiments and together with the description, serve to explain the disclosed principles. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The same numbers are used throughout the figures to reference like features and components. Some embodiments of system and/or methods in accordance with embodiments of the present subject matter are now described below, by way of example only, and with reference to the accompanying figures.

FIG. 1 illustrates an interactive chatbot interface for optimizing communication between a user and a chatbot by presenting a traffic type header indicating type of received message or response in accordance with some embodiments of the present disclosure.

FIGS. 2a and 2b illustrate interactive chatbot interfaces for optimizing communication between a user and a chatbot by sending postback for suggested reply/actions with additional information to the chatbot in accordance with some embodiments of the present disclosure.

FIGS. 3a and 3b illustrate interactive chatbot interfaces for optimizing communication between a user and a chatbot by reduced/delayed file download based on a traffic header type in accordance with some embodiments of the present disclosure.

FIGS. 4a, 4b and 4c illustrate interactive chatbot interfaces for optimizing communication between a user and a chatbot by controlling communication with the user based on reply-type permission in accordance with some embodiments of the present disclosure.

FIG. 5 shows a detailed block diagram of a chatbot communication system in accordance with some embodiments of the present disclosure.

FIGS. 6a, 6b, 6c and 6d illustrate flowcharts showing methods for an optimized chatbot communication in accordance with some embodiments of present disclosure.

FIG. 7 illustrates a block diagram of an exemplary computer system for implementing embodiments consistent with the present disclosure.

It should be appreciated by those skilled in the art that any block diagrams herein represent conceptual views of illustrative systems embodying the principles of the present subject matter. Similarly, it will be appreciated that any flowcharts, flow diagrams, state transition diagrams, pseudo code, and the like represent various processes which may be substantially represented in computer readable medium and executed by a computer or processor, whether or not such computer or processor is explicitly shown.

In the present document, the word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment or implementation of the present subject matter described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.

While the disclosure is susceptible to various modifications and alternative forms, specific embodiment thereof has been shown by way of example in the drawings and will be described in detail below. It should be understood, however that it is not intended to limit the disclosure to the particular forms disclosed, but on the contrary, the disclosure is to cover all modifications, equivalents, and alternatives falling within the scope of the disclosure.

The terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a setup, device or method that comprises a list of components or steps does not include only those components or steps but may include other components or steps not expressly listed or inherent to such setup or device or method. In other words, one or more elements in a system or apparatus proceeded by "comprises… a" does not, without more constraints, preclude the existence of other elements or additional elements in the system or method.

In the following detailed description of the embodiments of the disclosure, reference is made to the accompanying drawings that form a part hereof, and in which are shown by way of illustration specific embodiments in which the disclosure may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the disclosure, and it is to be understood that other embodiments may be utilized and that changes may be made without departing from the scope of the present disclosure. The following description is, therefore, not to be taken in a limiting sense.

The present disclosure relates to a method and a chatbot communication system for optimizing communication between a user and an interactive agent i.e., chatbot. The chatbot communication system displays/presents a traffic type header (also, referred as an icon) along with a message or a response received from the chatbot to the user. The presented traffic type header associated with the received message helps the user to differentiate type of messages received from the chatbot. This approach helps user by assisting in proper identification of type of received message, which in turn helps the user to decide further actions. The chatbot communication system provides additional information associated with one or more external applications running on a user device to the chatbot. The additional information is automatically sent to the chatbot as postback message/object. The postback message/object refer to message or object being posted back to the chatbot via a chatbot interface. This approach avoids intervention of the user for providing any additional information relating to the external applications to the chatbot. Further, the chatbot communication system enables downloading of information/content associated with message type sent by the chatbot based on user's inputs. Alternatively, the chatbot communication system enables automatic download of one or more thumbnails associated with the message type when the user does not provide any input on the chatbot interface. This approach reduces unnecessary consumption of data at user end in downloading complete content associated with the message type. Further, the chatbot communication system provides information to the user in preferred way of interaction with the user by the chatbot based on reply-type permission. This approach enhances chatbot's capability to decide how user can communicate with chatbot for an optimal communication.

In the FIG. 1, an environment comprises of a user device 101 and a display screen 103 showing a chatbot interface of the user device 101. The user device 101 includes, but is not limited to, a mobile terminal, a tablet computer, a desktop and a laptop. A person skilled in the art would understand that any electronic device with a display and a network interface for communication, not mentioned explicitly, may also be used as the user device 101 in the present disclosure. The user device 101 comprises of a chatbot interface, which is communicatively coupled to a chatbot communication system. The chatbot communication system can be configured in the user device 101 or can be communicatively coupled to the user device 101. The chatbot communication system is, also, referred as an interactive platform or chatbot platform. In one embodiment, the chatbot communication system or the chatbot platform can be a server between the user device 101 and chatbots trusted by users. The detailed description of the chatbot communication system is explained later with respect to FIG. 5. With reference to the FIG. 1, a user communicates/interacts with a chatbot (not shown in FIG. 1) via the chatbot interface on the user device 101 for availing certain services. The chatbot may, also, be referred as an interactive agent, which sends a message 105 to the user via text or text-to-speech. As an example, the user receives the message 105. In response to the message 105, the user selects one of the options 111. The user selection is displayed/presented as reference 107. Thereafter, the chatbot communication system identifies a message type to be one of a payment type and a non-payment type based on information i.e., the reference 107 on the chatbot interface. The information comprises one of a payment link, an advertisement, a subscription, an encrypted message, an important message and a rating. When the message type is identified as the payment type on verifying presence of a payment link (indicated by "BUY NOW" in FIG. 1) in the chatbot interface, the chatbot communication system adds a traffic type header as payment 109 to a payment related rich card. The traffic type header may, also, be referred as an icon. The payment related rich card along with the traffic type header i.e., payment 109 may be displayed/presented on the chatbot interface to identify the type of the received message 107. In one embodiment, when the message type is identified as the payment type on verifying presence of a payment link (not shown in FIG. 1) in the chatbot interface, the chatbot communication system adds a traffic type header as payment 109 to the payment link. The payment link along with the traffic type header i.e., payment 109 is displayed/presented on the chatbot interface to identify the type of the received message 107. The non-payment type of the received message includes, but are not limited to an advertisement, a subscription, an encrypted message, an important message and a rating. The advertisement refers to messages from advertisement companies. The subscription refers to subscription that will be enabled when clicked, for example, subscribing for newsletter, donation, and the like. The encrypted message refers to message that will be encrypted or secured. The important message refers to message that is important when there are lot of messages sent together i.e., the important message refers to message that match the requested criteria exactly. The rating refers to rating/like/dislikes for messages related to hotels, shopping items, and the like. The presence of traffic type header helps the user to distinguish the advertisement from the payment related rich card or the payment related link. Consequently, the user may not follow any link related to the advertisement and may perform payment transactions safely. Based on the traffic type header, the user determines easily whether the payment link or the payment related rich card is secure or not. In this case, the traffic type header 109 indicating payment is displayed on the payment related rich card allowing the user to decide from using the "BUY NOW" link for initiating payment transaction.

The payment type and the non-payment type of a received message comprising an advertisement, a subscription, an encrypted message, an important message and a rating may, also, be collective referred as traffic types. In the present disclosure, when a chatbot sends a message of one of the traffic types, the chatbot communication system assures traffic header type along with content and adds a Common Presence and Instant Messaging (CPIM) traffic type header with a corresponding value. For instance, when the user device 101 receives the message 105 with the traffic type header value that includes one or more suggested actions or replies, at the user end the same CPIM traffic type header and value may be added in message payload which is sent back to the chatbot. In one embodiment, verifying message type and content/link becomes mandatory when the message type is payment type that confirms a monetary/payment transaction between the user and the chatbot. In another embodiment, a chatbot may send a URL link associated with a third party to the user, and a traffic type header as a payment 109 may be displayed to the user. Thereafter, the user may perform payment transaction using the payment link.

FIGS. 2a-2b illustrate interactive chatbot interfaces for optimizing communication between a user and a chatbot by sending postback for suggested reply/actions with additional information to the chatbot in accordance with some embodiments of the present disclosure.

In the FIG. 2a, which illustrates a conventional chatbot interface, an environment comprises of a user device 101 and a display screen 201 showing a conventional chatbot interface of the user device 101. A chatbot requests a user to perform payment transaction, shown as reference 203. The user performs the payment transaction using an external application. Subsequently, the chatbot requests for an acknowledgment number or a transaction identifier related to the payment transaction i.e., Share Acknowledgment No. Conventionally, upon successful completion of the payment transaction, the user manually sends the acknowledgment number or the transaction identifier to the chatbot via the conventional chatbot interface, as shown in reference 205.

With reference to the FIG. 2b, which illustrates a chatbot interface of the present disclosure, a chatbot requests a user to perform payment transaction. A chatbot communication system (not shown in the FIG. 2b) of the present disclosure identifies a message type to be one of a payment type and a non-payment type on the chatbot interface based on information on the chatbot interface. The information comprises one of a payment link, an advertisement, a subscription, an encrypted message, an important message and a rating. When the message type is identified as the payment type on verifying presence of a payment link (not shown in the FIG. 2b) in the chatbot interface, the chatbot communication system adds a traffic type header as payment to the payment link. The chatbot communication system i.e., the chatbot platform assures the traffic-type and content before adding the traffic-type header as payment. Thereafter, the chatbot communication system presents the payment link along with the traffic type header on the chatbot interface. The user accepts the payment request received from the chatbot and visit the URL link for performing the payment transaction using an external application. Here, the chatbot is automatically directed to a payment server, and automatically receive a response from the payment server upon completion of the payment transaction. In detail, the chatbot communication system checks if payment is successful using the payment link. Based on the checking outcome, the chatbot communication system perform one of the following operations. When the payment is successful, the chatbot communication system sends at least one of a transaction identifier and booking information as a postback message to a chatbot via the chatbot interface. The postback message refer to message being posted back to the chatbot via the chatbot interface. The at least one of the transaction identifier and the booking information is generated after completion of a payment transaction using the payment link when the payment is successful. When the payment is not successful, the chatbot communication system sends a failure reason as the postback message to the chatbot via the chatbot interface. The failure reason is generated after failed payment transaction using the payment link i.e., when the payment is not successful. In the present disclosure, the transaction identifier and/or the booking information from the external application is sent to the chatbot by the chatbot communication system without intervention of the user, as shown in reference 207. Here, the external application may be, but is not limited to, internet banking, Unified Payment Interface (UPI), wallet payments, and the like.

In contrast to the conventional chatbot interface, the present disclosure enables automatically sending additional information associated with external applications to an interactive agent i.e., chatbot as postback message. This approach avoids intervention of the user for providing the additional information to the chatbot through the chatbot interface.

FIGS. 3a-3b illustrate interactive chatbot interfaces for optimizing communication between a user and a chatbot by reduced/delayed file download based on a traffic header type in accordance with some embodiments of the present disclosure.

In the FIG. 3a, which illustrates a conventional chatbot interface, an environment comprises of a user device 101 and a display screen 301 showing a file i.e., an image file. In conventional chatbot interface, files of larger size may be downloaded automatically even if a user does not click on files for downloading, as shown in reference 303. Due to auto-download feature, user data is consumed unnecessarily, which in turn increases bandwidth utilization and memory usage.

With reference to the FIG. 3b, which illustrates a chatbot interface of the present disclosure, the files are downloaded based on a message type. In details, a chatbot communication system (not shown in the FIG. 3b) of the present disclosure identifies a message type to be one of a payment type and a non-payment type on the chatbot interface based on information on the chatbot interface. The information comprises one of a payment link, an advertisement, a subscription, an encrypted message, an important message and a rating. When the message type is identified as the non-payment type, the chatbot communication system identifies a traffic type header for the information on the chatbot interface. The non-payment type comprises an advertisement, a subscription, an encrypted message, an important message and a rating. Thereafter, the chatbot communication system adds a traffic type header to the information. When the traffic type header is identified as the advertisement, the chatbot communication system presents the information as a thumbnail image 307 along with the traffic type header 305, without downloading the information. In the present disclosure, only thumbnail image gets automatically downloaded, and the file is downloaded based on user click input on the advertisement. When the user clicks on the thumbnail 307, the complete file is downloaded. Here, the file may be an image, a rich card and the like. As an example, a thumbnail 307 of an advertisement with a traffic type header 305 is displayed on the display screen 301 of the user device 101 to the user. The size of thumbnail image may be 10 kB in contrast to the size of image which may be 1 MB. When the traffic type header is identified as the advertisement, irrespective of a visible window download setting is enabled or disabled, only thumbnail image gets automatically downloaded, and the file is downloaded based on user click input on the advertisement. When a visible window download setting is enabled and when the traffic type header is identified as one of a subscription, an encrypted message, an important message and a rating, the chatbot communication system downloads only the information visible on a display screen 301 for presenting along with the traffic type header. When a visible window download setting is disabled and when the traffic type header is identified as one of the subscription, the encrypted message, the important message and the rating, the chatbot communication system downloads the information on the chatbot interface for presenting along with the traffic type header.

The present disclosure facilitates automatic download of restricted content in small size such as thumbnail and enables downloading of files with larger size based on user input on the chatbot interface. Furthermore, the visible window download setting allows user to preferentially download or restrict download, especially to files such as an image, a rich card and the like that cannot be seen on a display screen of the user device 101, in case of non-payment type and non-advertisement type messages. This approach reduces unnecessary data consumption/download at user end, which in turn optimizes bandwidth utilization and memory usage.

FIGS. 4a-4c illustrate interactive chatbot interfaces for optimizing communication between a user and a chatbot by controlling communication with the user based on reply-type permission in accordance with some embodiments of the present disclosure.

In the FIG. 4a, which illustrates a conventional chatbot interface, an environment comprises of a user device 101 and a display screen 401 showing a set of suggested replies and suggested actions that constitute a persistent menu. Conventionally, a chatbot specifies a set of suggested replies and suggested actions that constitute a persistent menu 405. This is displayed to a user on a display screen 401 of the user device 101. For instance, the user may type "Today’s News" in a text box 403. The conventional chatbot interface won't understand the user typed message in the text box and consequently, show a set of suggested replies and suggested actions that constitute a persistent menu 405. In this case, since the user is not aware of chatbot's preferred way for communication, this limits chatbot's capability to decide how user can communicate.

With reference to the FIG. 4b, which illustrates a chatbot interface of the present disclosure, a reply-type permission feature is added as a sub-property of the persistent-menu in chatbot's information JavaScript Object Notation (JSON) schema. Based on the reply-type permission, the chatbot communication system controls the way a user can communicate. In an embodiment, the chatbot communication system checks reply-type permission in the chatbot interface and configures the chatbot interface for user interaction with the chatbot based on the reply-type permission. The reply-type permission is one of reply-type permission 0, reply-type permission 1, reply-type permission 2, and reply-type permission 3. When the reply-type permission is 0, the chatbot communication system configures the chatbot interface for allowing a user to communicate with the chatbot using a persistent menu and a text box. When the reply-type permission is 1, the chatbot communication system configures the chatbot interface for allowing the user to communicate with the chatbot using only the persistent menu. When the reply-type permission is 2, the chatbot communication system configures the chatbot interface for allowing the user to communicate with the chatbot using only the persistent menu and suggested actions in the persistent menu. When the reply-type permission is 3, the chatbot communication system configures the chatbot interface for allowing only the chatbot to communicate with the user.

FIG. 4b illustrates a chatbot interface, which displays a persistent menu with reply-type permission 2 409. This enables the user only to select an option from the persistent menu 409 and suggested actions, for example, "Headlines" 407. Further, FIG. 4c illustrates a chatbot interface, which displays a persistent menu with reply-type permission 2 411. This enables the user only to select an option from the persistent menu and suggested actions in the persistent menu 411. In this manner, controlled user interaction with the chatbot is enabled using the chatbot communication system.

The present disclosure provides a preferred way of interaction with a user by the interactive agent i.e., chatbot based on reply-type permission. This enhances chatbot's capability to decide how user can communicate with chatbot for an optimal communication.

The chatbot communication system 501 includes an I/O interface 503, a processor 505, data 509 and one or more modules 515, which are described herein in detail.

The chatbot communication system 501 receives input via the I/O interface 503. The input is an information present on a chatbot interface.

The input received by the I/O interface 503 is stored in a memory 507. The memory 507 is communicatively coupled to the processor 505 of the chatbot communication system 501. The memory 507, also, stores processor instructions which causes the processor 505 to execute the instructions for optimizing chatbot communication. The memory 507 includes, without limitation, memory drives, removable disc drives, etc. The memory drives further include a drum, magnetic disc drive, magneto-optical drive, optical drive, Redundant Array of Independent Discs (RAID), solid-state memory devices, solid-state drives, etc.

The processor 505 includes at least one data processor for optimizing chatbot communication. The processor 505 includes specialized processing units such as integrated system (bus) controllers, memory management control units, floating point units, graphics processing units, digital signal processing units, etc.

In one embodiment, the data 509 is stored within the memory 507. The data 509 includes, for example, message data 511, and other data 513.

The message data 511 includes the information present on the chatbot interface.

The other data 513 stores data, including temporary data and temporary files, generated by one or more modules 515 for performing the various functions of the chatbot communication system 501.

In one embodiment, the data 509 in the memory 507 are processed by the one or more modules 515 present within the memory 507 of the chatbot communication system 501. The one or more modules 515 is implemented as dedicated hardware units. As used herein, the term module refers to an Application Specific Integrated Circuit (ASIC), an electronic circuit, a Field-Programmable Gate Arrays (FPGA), a combinational logic circuit, and/or other suitable components that provide the described functionality. In some implementations, the one or more modules 515 is communicatively coupled to the processor 505 for performing one or more functions of the chatbot communication system 501. The said modules 515 when configured with the functionality defined in the present disclosure will result in a novel hardware.

In one implementation, the one or more modules 515 include, but are not limited to, an identifying module 517, a presenting module 519, a sending module 521, a checking module 523 and a configuring module 525. The one or more modules 515, also, include other modules 527 to perform various miscellaneous functionalities of the chatbot communication system 501.

The identifying module 517 of the chatbot communication system 501 identifies a message type to be one of a payment type and a non-payment type on the chatbot interface based on information on the chatbot interface. The information comprises one of a payment link, an advertisement, a subscription, an encrypted message, an important message and a rating. When the message type is identified as the payment type on verifying presence of a payment link in the chatbot interface, the identifying module 517 of the chatbot communication system 501 adds a traffic type header as payment to the payment link. When the message type is identified as the non-payment type, the identifying module 517 of the chatbot communication system 501 identifies a traffic type header for the information on the chatbot interface and adds the traffic type header to the information. The message type as non-payment type is identified based on traffic type header received in elements of JSON body. The non-payment type comprises an advertisement, a subscription, an encrypted message, an important message and a rating.

The presenting module 519 of the chatbot communication system 501 presents the payment link along with the traffic type header on the chatbot interface when the message type is identified as the payment type on verifying presence of a payment link in the chatbot interface. In an embodiment, the presenting module 519 of the chatbot communication system 501 presents the information as a thumbnail image along with the traffic type header, without downloading the information, when the traffic type header is identified as an advertisement.

The sending module 521 of the chatbot communication system 501 performs sending at least one of a transaction identifier and booking information as a postback message to a chatbot via the chatbot interface, wherein at least one of the transaction identifier and the booking information is generated when the payment is successful or sending a failure reason as the postback message to the chatbot via the chatbot interface, wherein the failure reason is generated when the payment is not successful. The at least one of the transaction identifier and the booking information is generated after completion of a payment transaction using the payment link when the payment is successful. The failure reason is generated after failed payment transaction using the payment link i.e., when the payment is not successful. The sending module 521 of the chatbot communication system checks if a visible window download setting is enabled. When a visible window download setting is enabled and when the traffic type header is identified as one of a subscription, an encrypted message, an important message and a rating, the sending module 521 of the chatbot communication system 501 downloads only the information visible on a display screen for presenting along with the traffic type header. When a visible window download setting is disabled and when the traffic type header is identified as one of the subscription, the encrypted message, the important message and the rating, the sending module 521 of the chatbot communication system 501 downloads the information on the chatbot interface for presenting along with the traffic type header.

The checking module 523 of the chatbot communication system 501 checks if payment is successful. The checking module 523 of the chatbot communication system 501 checks if a visible window download setting is enabled. The checking module 523 of the chatbot communication system 501 checks reply-type permission in the chatbot interface.

The configuring module 525 of the chatbot communication system 501 configures the chatbot interface for user interaction with the chatbot based on the reply-type permission. When the reply-type permission is 0, the configuring module 525 of the chatbot communication system 501 configures the chatbot interface for allowing a user to communicate with the chatbot using a persistent menu and a text box. When the reply-type permission is 1, the configuring module 525 of the chatbot communication system 501 configures the chatbot interface for allowing the user to communicate with the chatbot using only the persistent menu. When the reply-type permission is 2, the configuring module 525 of the chatbot communication system 501 configures the chatbot interface for allowing the user to communicate with the chatbot using only the persistent menu and suggested actions in the persistent menu. When the reply-type permission is 3, the configuring module 525 of the chatbot communication system 501 configures the chatbot interface for allowing only the chatbot to communicate with the user.

FIG. 6a-d illustrate flowcharts showing methods for an optimized chatbot communication in accordance with some embodiments of present disclosure

As illustrated in FIGS. 6a-d, the methods 600a-d include one or more blocks for optimizing chatbot communication. The methods 600a-d may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform particular functions or implement particular abstract data types.

The order in which the methods 600a-d are described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method. Additionally, individual blocks may be deleted from the methods without departing from the scope of the subject matter described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof.

Below method 600a includes blocks for optimizing communication between a user and a chatbot by sending postback for suggested reply/actions with additional information to the chatbot.

At block 601, the identifying module 517 of the chatbot communication system 501 may identify a message type to be one of a payment type and a non-payment type on a chatbot interface based on information on the chatbot interface. The information may comprise one of a payment link, an advertisement, a subscription, an encrypted message, an important message and a rating.

At block 603, the identifying module 517 of the chatbot communication system 501 may add a traffic type header as payment to a payment link when the message type is identified as the payment type on verifying presence of the payment link in the chatbot interface.

At block 605, the presenting module 519 of the chatbot communication system 501 may present the payment link along with the traffic type header on the chatbot interface.

At block 607, the checking module 523 of the chatbot communication system 501 may check if payment is successful. Based on the checking outcome, the sending module 521 of the chatbot communication system 501 may perform one of the following operations.

At block 609, the sending module 521 of the chatbot communication system 501 may send at least one of a transaction identifier and booking information as a postback message to a chatbot via the chatbot interface, wherein at least one of the transaction identifier and the booking information is generated when the payment is successful. The at least one of the transaction identifier and the booking information may be generated after completion of a payment transaction using the payment link.

At block 611, the sending module 521 of the chatbot communication system 501 may send a failure reason as the postback message to the chatbot via the chatbot interface, wherein the failure reason is generated when the payment is not successful. The failure reason may be generated after failed payment transaction using the payment link.

Below method 600b includes blocks for optimizing communication between a user and a chatbot by reduced/delayed file download based on a traffic header type especially advertisement.

At block 621, the identifying module 517 of the chatbot communication system 501 may identify a traffic type header for the information on the chatbot interface when the message type is identified as the non-payment type in absence of a payment link in the chatbot interface.

At block 623, the identifying module 517 of the chatbot communication system 501 may add the traffic type header to the information.

At block 625, the presenting module 519 of the chatbot communication system 501 may present the information as a thumbnail image along with the traffic type header, without downloading the information, when the traffic type header is identified as an advertisement.

Below method 600c includes blocks for optimizing communication between a user and a chatbot by reduced/delayed file download based on a traffic header type especially non-advertisement i.e., a subscription, an encrypted message, an important message and a rating.

At block 601, the identifying module 517 of the chatbot communication system 501 may identify a message type to be one of a payment type and a non-payment type on a chatbot interface based on information on the chatbot interface.

At block 631, the identifying module 517 of the chatbot communication system 501 may identify a traffic type header for the information on the chatbot interface when the message type is identified as the non-payment type in absence of a payment link in the chatbot interface.

At block 633, the identifying module 517 of the chatbot communication system 501 may add the traffic type header to the information.

At block 635, the checking module 523 of the chatbot communication system 501 may check whether a visible window download setting is enabled.

At block 637, when the visible window download setting is enabled, the sending module 521 of the chatbot communication system 501 may download only the information visible on a display screen for presenting along with the traffic type header when the traffic type header is identified as one of a subscription, an encrypted message, an important message and a rating.

At block 639, when the visible window download setting is disabled, the sending module 521 of the chatbot communication system 501 may download the information on the chatbot interface for presenting along with the traffic type header when the traffic type header is identified as one of the subscription, the encrypted message, the important message and the rating.

Below method 600d includes blocks for optimizing communication between a user and a chatbot by controlling communication with the user based on reply-type permission.

At block 641, the checking module 523 of the chatbot communication system 501 may check reply-type permission in the chatbot interface.

At block 643, the configuring module 525 of the chatbot communication system 501 may configure the chatbot interface for user interaction with the chatbot based on the reply-type permission.

At block 645, when the reply-type permission is 0, the configuring module 525 of the chatbot communication system 501 may configure the chatbot interface for allowing a user to communicate with the chatbot using a persistent menu and a text box.

At block 647, when the reply-type permission is 1, the configuring module 525 of the chatbot communication system 501 may configure the chatbot interface for allowing the user to communicate with the chatbot using only the persistent menu.

At block 649, when the reply-type permission is 2, the configuring module 525 of the chatbot communication system 501 may configure the chatbot interface for allowing the user to communicate with the chatbot using only the persistent menu and suggested actions in the persistent menu.

At block 651, when the reply-type permission is 3, the configuring module 525 of the chatbot communication system 501 may configure the chatbot interface for allowing only the chatbot to communicate with the user.

The advantages of the present disclosure are listed below.

FIG. 7 illustrates a block diagram of an exemplary computer system 700 for implementing embodiments consistent with the present disclosure. In an embodiment, the computer system 700 may be used to implement the chatbot communication system 501. The computer system 700 may include a central processing unit ("CPU" or "processor") 702. The processor 702 may include at least one data processor for optimizing chatbot communication. The processor 702 may include specialized processing units such as, integrated system (bus) controllers, memory management control units, floating point units, graphics processing units, digital signal processing units, etc.

The processor 702 may be disposed in communication with one or more input/output (I/O) devices (not shown in FIG. 7) via I/O interface 701. The I/O interface 701 employ communication protocols/methods such as, without limitation, audio, analog, digital, monoaural, Radio Corporation of America (RCA) connector, stereo, IEEE®-1394 high speed serial bus, serial bus, Universal Serial Bus (USB), infrared, Personal System/2 (PS/2) port, Bayonet Neill-Concelman (BNC) connector, coaxial, component, composite, Digital Visual Interface (DVI), High-Definition Multimedia Interface (HDMI®), Radio Frequency (RF) antennas, S-Video, Video Graphics Array (VGA), IEEE® 802.11b/g/n/x, Bluetooth, cellular e.g., Code-Division Multiple Access (CDMA), High-Speed Packet Access (HSPA+), Global System for Mobile communications (GSM®), Long-Term Evolution (LTE®), Worldwide interoperability for Microwave access (WiMax®), or the like.

Using the I/O interface 701, the computer system 700 may communicate with one or more I/O devices such as input devices 712 and output devices 713. For example, the input devices 712 may be an antenna, keyboard, mouse, joystick, (infrared) remote control, camera, card reader, fax machine, dongle, biometric reader, microphone, touch screen, touchpad, trackball, stylus, scanner, storage device, transceiver, video device/source, etc. The output devices 713 may be a printer, fax machine, video display (e.g., Cathode Ray Tube (CRT), Liquid Crystal Display (LCD), Light-Emitting Diode (LED), plasma, Plasma Display Panel (PDP), Organic Light-Emitting Diode display (OLED) or the like), audio speaker, etc.

In some embodiments, the computer system 700 consists of the chatbot communication system 501. The processor 702 may be disposed in communication with the communication network 714 via a network interface 703. The network interface 703 may communicate with the communication network 714. The network interface 703 may employ connection protocols including, without limitation, direct connect, Ethernet (e.g., twisted pair 10/100/1000 Base T), Transmission Control Protocol/Internet Protocol (TCP/IP), token ring, IEEE® 802.11a/b/g/n/x, etc. The communication network 714 may include, without limitation, a direct interconnection, Local Area Network (LAN), Wide Area Network (WAN), wireless network (e.g., using Wireless Application Protocol), the Internet, etc. Using the network interface 703 and the communication network 714, the computer system 700 may communicate with the chatbot 715. The network interface 703 may employ connection protocols include, but not limited to, direct connect, Ethernet (e.g., twisted pair 10/100/1000 Base T), Transmission Control Protocol/Internet Protocol (TCP/IP), token ring, IEEE® 802.11a/b/g/n/x, etc.

The communication network 714 includes, but is not limited to, a direct interconnection, a Peer to Peer (P2P) network, Local Area Network (LAN), Wide Area Network (WAN), wireless network (e.g., using Wireless Application Protocol), the Internet, Wi-Fi and such.

In some embodiments, the processor 702 may be disposed in communication with a memory 705 (e.g., RAM, ROM, etc. not shown in FIG. 7) via a storage interface 704. The storage interface 704 may connect to memory 705 including, without limitation, memory drives, removable disc drives, etc., employing connection protocols such as, Serial Advanced Technology Attachment (SATA), Integrated Drive Electronics (IDE), IEEE®-1394, Universal Serial Bus (USB), fiber channel, Small Computer Systems Interface (SCSI), etc. The memory drives may further include a drum, magnetic disc drive, magneto-optical drive, optical drive, Redundant Array of Independent Discs (RAID), solid-state memory devices, solid-state drives, etc.

The memory 705 may store a collection of program or database components, including, without limitation, user interface 706, an operating system 707, etc. In some embodiments, computer system 700 may store user/application data, such as, the data, variables, records, etc., as described in this disclosure. Such databases may be implemented as fault-tolerant, relational, scalable, secure databases such as Oracle or Sybase.

The operating system 707 may facilitate resource management and operation of the computer system 700. Examples of operating systems include, without limitation, APPLE® MACINTOSH® OS X®, UNIX®, UNIX-like system distributions (E.G., BERKELEY SOFTWARE DISTRIBUTION® (BSD), FREEBSD®, NETBSD®, OPENBSD, etc.), LINUX® DISTRIBUTIONS (E.G., RED HAT®, UBUNTU®, KUBUNTU®, etc.), IBM®OS/2®, MICROSOFT® WINDOWS® (XP®, VISTA®/7/8, 10 etc.), APPLE® IOS®, GOOGLETM ANDROIDTM, BLACKBERRY® OS, or the like.

In some embodiments, the computer system 700 may implement web browser 708 stored program components. Web browser 708 may be a hypertext viewing application, such as MICROSOFT® INTERNET EXPLORER®, GOOGLETM CHROMETM, MOZILLA® FIREFOX®, APPLE® SAFARI®, etc. Secure web browsing may be provided using Secure Hypertext Transport Protocol (HTTPS), Secure Sockets Layer (SSL), Transport Layer Security (TLS), etc. Web browsers 708 may utilize facilities such as AJAX, DHTML, ADOBE® FLASH®, JAVASCRIPT®, JAVA®, Application Programming Interfaces (APIs), etc. The computer system 700 may implement a mail server (not shown in FIG. 7) stored program component. The mail server may be an Internet mail server such as Microsoft Exchange, or the like. The mail server may utilize facilities such as ASP, ACTIVEX®, ANSI® C++/C#, MICROSOFT®, .NET, CGI SCRIPTS, JAVA®, JAVASCRIPT®, PERL®, PHP, PYTHON®, WEBOBJECTS®, etc. The mail server may utilize communication protocols such as Internet Message Access Protocol (IMAP), Messaging Application Programming Interface (MAPI), MICROSOFT® exchange, Post Office Protocol (POP), Simple Mail Transfer Protocol (SMTP), or the like. The computer system 700 may implement a mail client (not shown in FIG. 7) stored program component. The mail client may be a mail viewing application, such as APPLE® MAIL, MICROSOFT® ENTOURAGE®, MICROSOFT® OUTLOOK®, MOZILLA® THUNDERBIRD®, etc.

Furthermore, one or more computer-readable storage media may be utilized in implementing embodiments consistent with the present disclosure. A computer-readable storage medium refers to any type of physical memory on which information or data readable by a processor may be stored. Thus, a computer-readable storage medium may store instructions for execution by one or more processors, including instructions for causing the processor(s) to perform steps or stages consistent with the embodiments described herein. The term "computer-readable medium" should be understood to include tangible items and exclude carrier waves and transient signals, i.e., be non-transitory. Examples include Random Access Memory (RAM), Read-Only Memory (ROM), volatile memory, non-volatile memory, hard drives, CD ROMs, DVDs, flash drives, disks, and any other known physical storage media.

The described operations may be implemented as a method, system or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof. The described operations may be implemented as code maintained in a "non-transitory computer readable medium", where a processor may read and execute the code from the computer readable medium. The processor is at least one of a microprocessor and a processor capable of processing and executing the queries. A non-transitory computer readable medium may include media such as magnetic storage medium (e.g., hard disk drives, floppy disks, tape, etc.), optical storage (CD-ROMs, DVDs, optical disks, etc.), volatile and non-volatile memory devices (e.g., EEPROMs, ROMs, PROMs, RAMs, DRAMs, SRAMs, Flash Memory, firmware, programmable logic, etc.), etc. Further, non-transitory computer-readable media include all computer-readable media except for a transitory. The code implementing the described operations may further be implemented in hardware logic (e.g., an integrated circuit chip, Programmable Gate Array (PGA), Application Specific Integrated Circuit (ASIC), etc.).

The terms "an embodiment", "embodiment", "embodiments", "the embodiment", "the embodiments", "one or more embodiments", "some embodiments", and "one embodiment" mean "one or more (but not all) embodiments of the invention(s)" unless expressly specified otherwise.

The terms "including", "comprising", "having" and variations thereof mean "including but not limited to", unless expressly specified otherwise.

The enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise.

The terms "a", "an" and "the" mean "one or more", unless expressly specified otherwise.

A description of an embodiment with several components in communication with each other does not imply that all such components are required. On the contrary, a variety of optional components are described to illustrate the wide variety of possible embodiments of the invention.

When a single device or article is described herein, it will be readily apparent that more than one device/article (whether or not they cooperate) may be used in place of a single device/article. Similarly, where more than one device or article is described herein (whether or not they cooperate), it will be readily apparent that a single device/article may be used in place of the more than one device or article or a different number of devices/articles may be used instead of the shown number of devices or programs. The functionality and/or the features of a device may be alternatively embodied by one or more other devices which are not explicitly described as having such functionality/features. Thus, other embodiments of the invention need not include the device itself.

The illustrated operations of FIGS. 6a-d show certain events occurring in a certain order. In alternative embodiments, certain operations may be performed in a different order, modified or removed. Moreover, steps may be added to the above described logic and still conform to the described embodiments. Further, operations described herein may occur sequentially or certain operations may be processed in parallel. Yet further, operations may be performed by a single processing unit or by distributed processing units.

Finally, the language used in the specification has been principally selected for readability and instructional purposes, and it may not have been selected to delineate or circumscribe the inventive subject matter. It is therefore intended that the scope of the invention be limited not by this detailed description, but rather by any claims that issue on an application based here on. Accordingly, the disclosure of the embodiments of the invention is intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the following claims.

While various aspects and embodiments have been disclosed herein, other aspects and embodiments will be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are for purposes of illustration and are not intended to be limiting, with the true scope being indicated by the following claims.

REFERRAL NUMERALS: 101: User device, 103, 201, 301, 401: Display screen on the user device, 501: Chatbot communication system, 503: I/O interface, 505: Processor, 507: Memory, 509: Data, 511: Message data, 513: Other data, 515: Modules, 517: Identifying module, 519: Presenting module, 521: Sending module, 523: Checking module, 525: Configuring module, 527: Other modules, 700: Computer system, 701: I/O interface, 702: Processor, 703: Network interface, 704: Storage interface, 705: Memory, 706: User interface, 707: Operating system, 708: Web browser, 712: Input devices, 713: Output devices, 714: Communication network, 715: Chatbot.

Claims

A method for an optimized chatbot communication, the method comprising:

identifying, by a chatbot communication system, a message type to be one of a payment type and a non-payment type on a chatbot interface based on information on the chatbot interface;

when the message type is identified as the payment type on verifying presence of a payment link in the chatbot interface:

adding, by the chatbot communication system, a traffic type header as payment to the payment link;

presenting, by the chatbot communication system, the payment link along with the traffic type header on the chatbot interface;

checking, by the chatbot communication system, whether payment is successful using the payment link;

sending at least one of a transaction identifier and booking information as a postback message to a chatbot via the chatbot interface when the payment is successful; and

sending a failure reason as the postback message to the chatbot via the chatbot interface when the payment is not successful.
The method as claimed in claim 1, further comprising:

when the message type is identified as the non-payment type:

identifying, by the chatbot communication system, a traffic type header for the information on the chatbot interface;

adding, by the chatbot communication system, the traffic type header to the information; and

presenting, by the chatbot communication system, the information as a thumbnail image along with the traffic type header, without downloading the information, when the traffic type header is identified as an advertisement.
The method as claimed in claim 1, further comprising:

when the message type is identified as the non-payment type:

identifying, by the chatbot communication system, a traffic type header for the information on the chatbot interface;

adding, by the chatbot communication system, the traffic type header to the information;

checking, by the chatbot communication system, whether a visible window download setting is enabled;

when a visible window download setting is enabled,

downloading, by the chatbot communication system, only the information visible on a display screen for presenting along with the traffic type header when the traffic type header is identified as one of a subscription, an encrypted message, an important message and a rating; and

when the visible window download setting is disabled,

downloading, by the chatbot communication system, the information on the chatbot interface for presenting along with the traffic type header when the traffic type header is identified as one of the subscription, the encrypted message, the important message and the rating.
The method as claimed in claim 2, wherein the non-payment type comprises the advertisement, a subscription, an encrypted message, an important message and the rating.
The method as claimed in claim 1, further comprising:

checking, by the chatbot communication system, reply-type permission in the chatbot interface; and

configuring, by the chatbot communication system, the chatbot interface for user interaction with the chatbot based on the reply-type permission.
The method as claimed in claim 5, wherein configuring the chatbot interface for user interaction with the chatbot based on the reply-type permission comprises:

when the reply-type permission is 0, configuring, by the chatbot communication system, the chatbot interface for allowing a user to communicate with the chatbot using a persistent menu and a text box;

when the reply-type permission is 1, configuring, by the chatbot communication system, the chatbot interface for allowing the user to communicate with the chatbot using only the persistent menu;

when the reply-type permission is 2, configuring, by the chatbot communication system, the chatbot interface for allowing the user to communicate with the chatbot using only the persistent menu and suggested actions in the persistent menu; and

when the reply-type permission is 3, configuring, by the chatbot communication system, the chatbot interface for allowing only the chatbot to communicate with the user.
The method as claimed in claim 1, wherein the at least one of the transaction identifier and the booking information is generated after completion of a payment transaction using the payment link.
The method as claimed in claim 1, wherein the failure reason is generated after failed payment transaction using the payment link.
The method as claimed in claim 1, wherein the information comprises one of a payment link, an advertisement, a subscription, an encrypted message, an important message and a rating.
A chatbot communication system for an optimized chatbot communication, the chatbot communication system comprising:

a processor; and

a memory communicatively coupled to the processor, wherein the memory stores processor-executable instructions, which on execution, cause the processor to:

identify a message type to be one of a payment type and a non-payment type on a chatbot interface based on information on the chatbot interface;

when the message type is identified as the payment type on verifying presence of a payment link in the chatbot interface:

add a traffic type header as payment to the payment link;

present the payment link along with the traffic type header on the chatbot interface;

check whether payment is successful using the payment link;

sending at least one of a transaction identifier and booking information as a postback message to a chatbot via the chatbot interface when the payment is successful; and

sending a failure reason as the postback message to the chatbot via the chatbot interface when the payment is not successful.
The chatbot communication system as claimed in claim 10, wherein the processor is configured to:

when the message type is identified as the non-payment type:

identify a traffic type header for the information on the chatbot interface;

add the traffic type header to the information; and

present the information as a thumbnail image along with the traffic type header, without downloading the information, when the traffic type header is identified as an advertisement.
The chatbot communication system as claimed in claim 10, wherein the processor is configured to:

when the message type is identified as the non-payment type:

identify a traffic type header for the information on the chatbot interface;

add the traffic type header to the information;

check whether a visible window download setting is enabled;

when a visible window download setting is enabled,

download only the information visible on a display screen for presenting along with the traffic type header when the traffic type header is identified as one of a subscription, an encrypted message, an important message and a rating; and

when the visible window download setting is disabled,

download the information on the chatbot interface for presenting along with the traffic type header when the traffic type header is identified as one of the subscription, the encrypted message, the important message and the rating.
The chatbot communication system as claimed in claim 11, wherein the non-payment type comprises the advertisement, a subscription, an encrypted message, an important message and the rating.
The chatbot communication system as claimed in claim 10, wherein the processor is configured to:

check reply-type permission in the chatbot interface; and

configure the chatbot interface for user interaction with the chatbot based on reply-type permission.
The chatbot communication system as claimed in claim 14, wherein the processor is configured to:

when the reply-type permission is 0, configure the chatbot interface for allowing a user to communicate with the chatbot using a persistent menu and a text box;

when the reply-type permission is 1, configure the chatbot interface for allowing the user to communicate with the chatbot using only the persistent menu;

when the reply-type permission is 2, configure the chatbot interface for allowing the user to communicate with the chatbot using only the persistent menu and suggested actions in the persistent menu; and

when the reply-type permission is 3, configure the chatbot interface for allowing only the chatbot to communicate with the user.