SleekFlow Product Requests

Problem Customers receiving spam messages need a quicker way to prevent unwanted conversations from reaching their agents. Without a blocking mechanism, agents must continue seeing and handling spam manually, impacting productivity. Requested Features Manual Contact Blocking Allow agents to manually block a contact directly from the conversation view. Suggested functionality: Add a "Block Contact" button in the conversation actions. Once blocked: The contact can no longer send messages to the inbox. The conversation is marked as Blocked. Agents can optionally unblock the contact at any time. Automatic Spam Detection Introduce a rule-based spam detection mechanism. Suggested logic: If a contact sends the same message 5 times within a configurable time interval (e.g. 1–5 minutes), automatically classify the conversation as Potential Spam. Possible actions after detection: Automatically apply a Spam label. Move the conversation to a Spam folder or queue. Notify the assigned agent. Optionally block the contact automatically (configurable by the workspace admin). Benefits Reduces agent workload caused by spam conversations. Improves inbox cleanliness and operational efficiency. Helps prevent automation or bot abuse. Provides customers with better control over unwanted contacts.

In the inbox conversation list, the only way to identify a contact beyond their display name is to click into the conversation and open the contacts panel. For teams where display names alone aren't enough to distinguish customers (e.g. common names, WhatsApp names that don't match real names), this adds unnecessary clicks to every interaction. Expected behavior: Allow users or admins to configure which contact fields are visible in the inbox list view — such as customer ID, tags, or custom fields — so team members can quickly identify who they're looking at without navigating away from the list. Use case: A vet clinic where customers are identified by pet name and customer ID rather than personal name. Staff currently have to click into every conversation to confirm who the client is before responding, slowing down their workflow.

When multiple team members collaborate on the same conversations, each user's read/unread status is tracked independently. If one team member reads and handles a conversation, the others still see it as unread and have to manually open each conversation to check if it's already been dealt with. For small teams with shared responsibility over conversations (as opposed to strict 1:1 assignment), this creates unnecessary overhead and slows down response workflows. Expected behavior: An option for teams to enable shared read status, so that when any team member reads a conversation, it reflects as read for everyone on the team. Ideally this would be a toggle so teams can choose between individual or shared read state depending on their workflow. Use case: A 3-person team where all members handle incoming conversations collaboratively. Today, all three have to independently check every conversation to determine if a colleague has already responded — leading to duplicated effort and wasted time.

The "unread indicator" next to [My Inbox], [Collaborations], or [Mentioned] will only be visible when the user is assigned as the Contact owner, collaborator, or is mentioned in an internal note within the conversation. As a team admin who is neither the Contact owner nor a collaborator, the user will not see the unread indicator next to these columns; it will only appear in the conversation preview list. Suggest adding the "unread indicator" display next to each team inbox next to [Company inbox], so that team admin users will be notified whenever there is a new incoming message from the team's perspective.

In the updated UI, there is no unread count indicator (badge/number) directly visible on the "Assigned" / "Unassigned" dropdown filter menu. Previously, we could easily see at a glance if there were new incoming messages. Now, agents have to manually click into the assignment filter dropdown just to check if anyone has reached out, which significantly increases the risk of missed customer messages and delays response times. Suggestion: Please bring back the unread message count badge on the primary assignment filter tab/button so team members can instantly see pending chats without extra clicks.

I found on Meta's developer site that if a media file is too big, they send a webhook with an error code. This is the URL from Meta's site : https://developers.facebook.com/documentation/business-messaging/whatsapp/business-phone-numbers/media Can you implement this on the inbox dashboard, so when a customer sends a file over 100MB, the inbox automatically sends a warning message to us? Thank you

We would like to enhance the Customer Lifecycle Management feature by allowing users to create parent lifecycle categories with nested subcategories (child stages) instead of having all lifecycle stages displayed in a single flat list. This would provide a more organized and scalable way to manage customer journeys, especially for businesses with multiple teams, workflows, or business units. Current Limitation At the moment, Customer Lifecycle Management only supports a flat list of lifecycle stages. Every stage exists at the same level, regardless of which department or process it belongs to. As organizations grow, this creates several challenges: Long lists of lifecycle stages become difficult to manage. Similar stages from different departments cannot be grouped together. Users struggle to understand where a customer is in the overall journey. Administrators need to create naming conventions (e.g., "Sales - Qualified", "Onboarding - Training", "Support - Waiting") just to keep stages organized. Reporting and workflow management become harder because there is no logical grouping of related stages. Proposed Enhancement Allow administrators to create Parent Lifecycle Categories and Child Lifecycle Stages underneath each category.

#Problem: Currently, when a conversation is assigned to another agent, the conversation retains the original customer message timestamp in the inbox and chat preview. The assignment history only shown in the contact logs, instead of also showing in the chatroom. For example: Customer sends a message at 9:00 AM. The conversation is assigned to a sales agent at 10:00 PM. In the sales agent's inbox, the chat preview still shows 9:00 AM and is sorted based on the original message time. As a result: Newly assigned conversations can appear far down the inbox. If the conversation has already been marked as read, there is no clear indication that a new conversation has just been assigned. Sales agents may overlook newly assigned conversations, resulting in slower response times and missed follow-ups. #Expected Behavior When a conversation is assigned to a new agent; the chat preview timestamp should reflect the assignment time, not the original customer message time. Example: Customer message: 9:00 AM Assigned to Sales: 10:00 PM Chat preview displays 10:00 PM. The conversation should move to the top of the assignee's inbox, sorted by the assignment timestamp. A visible "New Assignment" notification or indicator should appear on the conversation so the receiving agent immediately knows there is new work to action, even if the conversation has previously been marked as read. Business Impact #This enhancement would: Prevent newly assigned conversations from being buried beneath older conversations. Improve agent awareness of newly assigned chats. Reduce missed or delayed follow-ups. Improve SLA and first response time. Create a more intuitive handoff experience between support and sales teams. #Customer Use Case A support team receives all incoming WhatsApp inquiries. Throughout the day, they manually assign qualified leads to different sales representatives. Currently, because the inbox is sorted using the customer's original message timestamp, sales representatives often do not notice newly assigned conversations. Competitor platforms (e.g. Qontak) treat assigned conversations as new work items, moving them to the top of the inbox based on the assignment time, making them immediately visible to the assignee.

As a SuperAdmin, I'd like to be able to set my team members' online or offline status on their behalf. Sometimes agents forget to go offline when they leave for the day, or I need to quickly take someone offline when they're unexpectedly unavailable. Having this control would help me manage my team's availability without needing to ask each person individually.

They won't show up or be manageable in SleekFlow's inbox in whatsapp coexistance