Requests

I understand that it is possible to link a dialog to a specific TAG and trigger it via API. However, in my case, I have more than 40 TAGs that I need to enter per API, which would require creating 40 different dialogs. Additionally, this configuration needs to be replicated to more than one number. If an endpoint already existed that allowed you to trigger the TAG directly using your ID, this would make the process much simpler and more efficient.

Feature to import contact lists in CSV format.

I hired the platform with the promise that it would be possible to send pre-recorded audios that would be displayed to the client as if they had been recorded directly in the conversation. However, the functionality doesn't work. I carried out several tests, with different devices and with the support of several ChatGuru collaborators, who confirmed that this was an “error” on the platform, with no solution. I emphasize that this functionality was a decisive factor for my hiring and was widely publicized in the materials, articles, and commercial presentation. Therefore, this is misleading advertising, since the delivery does not match what was offered. I request help solving this problem. I await return.

Currently, for integration with the platform, it is necessary to enter the user_id of the users. However, this information must be obtained manually through the platform interface, which creates significant operational dependency. I would like to request the creation of a user query endpoint via API, in which, by entering a standard and fixed data such as the user's email, the system could return the respective user_id. This functionality is extremely important to avoid code maintenance issues in hiring scenarios or changes to IDs. Endpoint suggestion: • Method: GET • Suggested route: /users? email= {email} • Expected response: { “user_id”: “123456", “e-mail”: " usuario@email.com “, “name”: “Username” } If creating the endpoint is not possible, I would like to understand if there is any other feasible way to use a standard identifier, such as email, to link users via API, instead of the fixed user_id.

The funnel module could have more contact information, with icons that demonstrate their service status, personalized fields, photos, and even opportunities for us to have an overview

We are setting up our own system to read the ChatGuru JSON return with this information, maybe every 10 minutes, what we need is: • Department • Open Chats • Customer Chats • Waiting Chats • And all of Chats It would basically be the Department, the number of chats in each status and the total number of chats, with an update interval of 10 minutes, because then our own system would read this data and show it on our monitor.

The Customer would like to filter for reports that have not been used for a long time in order to reduce the number of dialogs created in the chatbot and that are 'weighing' the processing of the page, and that somehow it could extract this data.

When building a user report, the list of names is not in alphabetical order, nor is it possible to consult by name, making it difficult to build the report when you have a large user base.

A suggestion for improvement would be to add new lead reports, leads that went to each salesperson, leads that were serviced daily, by each salesperson.

It would be extremely useful if the history indicated which ChatBot or dialogue delegated (or removed the delegation), in order to identify errors in the construction of the bot or the conditions for them to be met.