SleekFlow Product Requests

Request to add a notification when the message has failed to sent.

Currently, we can only view the total number of MAC usage without any supporting details to verify its accuracy. Clients are unable to identify which contacts contribute to the MAC usage, as only a monthly aggregate is provided. There is no option to review MAC usage by day. The following features would greatly benefit all clients: Ability to view MAC usage by daily date. Access to a contact list to validate which contacts are included in the MAC usage. Clarification on how each contact triggers MAC consumption, such as whether it is initiated by incoming messages, outgoing messages, actions from the flow builder or other ways. MAC usage breakdown by message channel; for example, they are connected to seven channels and able to know the MAC usage for each channel. Thank you.

Background Meta now supports up to 4 quick reply buttons on WhatsApp message templates. We tested a 4-button template and it works end to end: it displays correctly in WhatsApp Web, the WhatsApp mobile app, and the SleekFlow inbox, and the button options work in Advanced Flow Builder. Problem Templates with 4 quick reply buttons can currently only be created in Meta Business Manager. Users have to leave SleekFlow, build and submit the template in Meta, then wait for it to sync back. This adds steps for CS and clients, and it is easy to get wrong. Request Allow up to 4 quick reply buttons in the SleekFlow template creation UI. Keep the button limit aligned with Meta as it changes (for example, if Meta later allows more than 4). Use case Menu-style first replies, such as "AI / WhatsApp Connection / Customer Services / Facebook Connection", where 4 options are needed in a single message instead of splitting them across two. Impact Fewer steps for clients and the CS team, and less dependency on Meta Business Manager.

I would like to be able to view my MAC usage for a specific date range directly within Subscription Usage. It would be helpful to: Filter MAC usage by a custom date range. View usage broken down by month. Review historical MAC usage to better understand consumption over time. This would make it easier to monitor MAC usage, track trends, and manage usage against my subscription without needing to contact the Customer Success team.

Currently the only way for us to find label added history is to check the individual contact history. This takes too much time and having a search filter in the "All Contacts" window is better. It helps us check backlogs and history, give us a way to verify if things are working as intended during the label entry date.

WhatsApp Flows (Forms) setup is quite simple on other platforms. It would be great to have a similarly easy setup experience on SleekFlow.

Currently, a low-credit banner is shown in the platform when the WhatsApp credit balance falls below USD 20. However, users may not notice the banner if they are not actively logged in to the platform. Please consider adding an email notification when the WhatsApp credit balance falls below the low-balance threshold. The email could remind users to top up their balance or check their auto top-up settings before message delivery is affected. This would help teams monitor their credit balance proactively and reduce the risk of broadcasts or other WhatsApp messages being interrupted due to insufficient credit.

Feature request: Automatically route new conversations to the user with the fewest open conversations. Expected functionality: Monitor the number of open conversations assigned to each available user. Automatically assign new conversations to the user with the lowest current conversation volume. Recalculate the workload whenever a new conversation is assigned or an existing conversation is closed. Apply routing only among users who are available and eligible to receive conversations. Provide admins with the option to enable or disable load-based routing. Use case: Load-based routing would help balance workloads automatically by prioritizing users with fewer open conversations, reducing the risk of some agents becoming overloaded while others have available capacity.

Feature request: Allow admins to set a maximum number of open conversations that can be assigned to each user. Expected functionality: Define a maximum number of open conversations per user. Prevent new conversations from being assigned to a user who has reached their limit. Automatically route new conversations to other available users who are below their limit. Allow admins to configure different limits based on team, user, or role. Provide visibility into each user's current conversation volume and remaining capacity. Use case: Some users can become overloaded with too many open conversations while other team members have available capacity. Conversation volume limits would help distribute workloads more evenly and ensure that new conversations are routed to users who have the capacity to handle them.

IT team requires a persistent banner displayed across all pages of the platform to show standard compliance, copyright, and data safety statements. This ensures our team is continuously reminded to handle personal information and internal chats with appropriate care. It would be great to have an admin-configurable banner setting in the UI where we can customize the text and toggle its visibility.