Conversations

Functionality Idea - Improvement to the Messages/Conversations Module
1 ️ ▼ Organization and Usability Nowadays, the conversation environment is visually confusing and mixes all types of messages (WhatsApp, SMS, Instagram, etc.) into a single flow. Proposal: Create smart tabs or filters by communication channel (WhatsApp, Instagram, SMS, Email, etc.); Allow separate viewing by connected WhatsApp number, ideal for accounts with multiple numbers; Add a column view mode (similar to service CRMs), making it easier to follow multiple conversations simultaneously; Option to “Favorite” or “Pin” important conversations at the top of the list. 2 ️ № Closing Conversations and History Today, all conversations remain open indefinitely, creating disorganization. Proposal: Add the “Finish Conversation” button, which archives the chat and removes it from the main screen; Allow you to configure automatic closing time (e.g., 24 hours after the last message); Create archived conversation history, accessible only by authorized users; Set by configuration whether only the original attendant can view previous conversations, maintaining privacy and internal control. 3 ️ ▼ Personalization and Intelligent Attribution Proposal: Implement intelligent service routing (securitization) - when a customer contacts you again, the system automatically forwards it to the same attendant that served them last time; If the attendant is offline, allow automatic redirection to another team member or waiting line; Allow transfer blocking in specific conversations (useful for sensitive cases). 4 ️ ▼ Forwarding and Sectors Proposal: Create department or sector structure (Commercial, Support, Financial, etc.); The attendant can forward the conversation to another sector or person, with an optional field for internal observation (without appearing to the customer); Create a visualization of queues by sector, so that managers can see the volume and average response time of each team. 5 ️ ▼ Automatic Rating and Feedback Proposal: After completing a conversation, the system can automatically send a satisfaction survey (NPS) via WhatsApp or e-mail; Direct integration with the CRM to record the NPS score on the contact; Generation of automatic service reports (average response time, satisfaction index, number of completed calls, etc.). 6 ️ ▼ Complementary Suggestions (to add even more value) 🔹 Customizable quick messages by sector (e.g. welcome, follow-up, farewell scripts). 🔹 Individual focus mode, where the attendant views only your active conversations. 🔹 Integration with assistive AI, suggesting automatic responses based on conversation history. 🔹 Visual indicators (icons, status, tags) to identify the conversation stage — “new”, “in service”, “waiting for a customer”, “completed”. 🔹 Team performance dashboard, showing productivity, response rate, and average time per attendant.
4
·
Enhancement
When emailing a contact, the FROM address defaults to the address of the currently logged-in HL user, when it SHOULD default to the email address specified in Settings > Email Services for the account
When emailing a contact via the HL UI, the FROM email address should always default to the email address specified in that account's Setting > Email Services configuration. Failing to do so is irrational, as defaulting to sending FROM the email address assigned to the currently logged-in user means SMTP authentication will fail, except in rare instances where it just so happens the currently logged-in user has the exact same email address as the one specified in Settings > Email Services. This is particularly egregious when one has an Agency with many subaccounts, all of whom are for different users. Example: Say my name is Bob Smith, email bob@smith.com , and I log into my account as an Agency admin. I have subaccounts for different staff members: Jim Johnson, jim@johnson.com , and Kevin Nations, kevin@nations.com . Each one of these users wants to communicate with their contacts using their own email address, so SMTP auth for each account is of course set up to use their respective email address (and, of course, their address will be used 95% of the time, since they will be the ones using the account). Because HL is configured illogically in-regards contact email FROM settings, every time I go to a specific subaccount, and attempt to send a contact an email, HL defaults to sending from bob@smith.com , my email, instead of jim@johnson.com , the email configured in Settings > Email Services.. So every single email I send to a contact on Jim Johnson's account, I have to edit the FROM field every single time. And every other user has to do the exact same thing any time they access any other subaccount that isn't their own.
47
·
Enhancement
Load More