Conversation Hub Extension July 16, 2024 15:39 Updated Index: Introduction How it Works? Instalation and Configuration Usage Examples Support Introduction The CONVERSATION HUB is an extension that allows you to store the history of your BLIP DESK conversations forever and retrieve any ticket, with all data preserved, including photos, videos, audios, or files, without losing the ease of consulting on screen. You can search by customer name, phone number, or ticket ID. Additionally, it offers data export to PDF, making the solution even more practical. By storing BLIP DESK conversations indefinitely, you can find the entire history of a specific customer's interactions as long as you have the plugin installed on BLIP. This is very useful for any company using BLIP and wanting uncomplicated access to BLIP DESK conversation history, needing to retrieve history for research, auditing, or even legal protection of the company. Imagine your support team completed a negotiation or sale where your customer gave an “AGREEMENT,” accepting what was offered. A year later, they return wanting to dispute or undo the previous agreement. It's important to have this history preserved. You will be able to view everything that was discussed, and also export the data for any need or audit. How it Works? The CONVERSATION HUB offers the following features: Stores the history of human conversations. Allows retrieval and access to stored texts , audios , videos , images , and documents. Search by contact name, phone number, or ticket ID, as well as by date range. Data visualization on screen or export to PDF. It is supported on the following channels: ALL CHANNELS AVAILABLE ON THE BLIP PLATFORM. Instalation and Configuration When you activate the extension from the Blip Store, it should be installed on the HUMAN SUPPORT bot (it can be added to multiple chatbots in your contract). After activation, you should: 1. Access the Builder of your human support chatbot and insert a box after the human support block. This box should be inserted as an immediate exit condition for successfully closed tickets (exit conditions: “ticket closed by the agent” and “ticket closed due to customer inactivity)”. a)Insert an "HTTP Request" action, which should be filled out as follows: Method: POST URL: https://api.aspinservices.com/v1/tickethistory Headers: Key: Content-Type Value: application/json Body: { "ticket": "{{input.content@id}}", "auth": "Key <appkey >" } The auth property can be checked in the connection information of your human support chatbot. Note: The condition "ticket closed by the customer" should be handled first with the standard BLIP ticket closing routine. After the ticket is closed, just direct it to the history recording box. 2. To use the extension, simply access the extensions area: The home screen is loaded. After that, just search by the available fields: Usage Examples Since the CONVERSATION HUB extension allows data to be stored indefinitely, if one of your customers files a complaint with PROCON against the company or accesses Reclame Aqui and leaves a formal complaint, you will have alternatives to verify and audit. It can be crucial to extract all your customer's service history effortlessly. Imagine you need to check an informed price, or a negotiated interest rate, retrieve the signed contract... It is important to be able to access the history and extract information. It is protection for your customer, but mainly for your company. Support If you have any questions or encounter any issues with the extension, please contact us at suporte@aspin.inf.br or chat with our support chatbot on WhatsApp. For more information, join the discussion on our community or watch the videos on our channel. 😃 Related articles Overview Screen of the Analysis Module Extension Bot Backup How to save human service history via Blip Integration with Google Drive Service History How to add a bot to an Android application using Blip Chat