SleekFlow Product Requests

I would like to suggest an improvement to the Kanban view for contacts in SleekFlow. Currently, when performing a bulk edit, it is possible to correctly update the Lead Stage and add labels to multiple contacts. However, even after applying these updates, the contacts do not automatically appear in the Kanban view as expected. For example, after updating 1,180 contacts and assigning them to a specific lead stage and label, the Kanban view only displayed a small number of contacts. Even when using advanced filters by list and label, the Kanban view did not reflect the full filtered contact base correctly. This makes it difficult for users to track leads visually by campaign, list, label, or lifecycle stage, especially when working with a large number of contacts. A possible improvement would be to allow the Kanban view to better support: * Contacts filtered by specific lists; * Contacts filtered by labels; * Automatic updates after bulk editing Lead Stage; * Accurate contact count per Kanban column; * Saved Kanban views based on lists, labels, or lifecycle stages. This improvement would help users manage leads more efficiently, reduce manual work, and provide a clearer visual overview of contacts throughout each stage of the customer journey.

I’d like to propose adding a "Saved Filter" feature to our Contacts page to help streamline our workflow. As marketers, we frequently perform routine checks by filtering contacts across different segments. Currently, I find myself manually selecting and searching through complex criteria every time. For example, as shown in attachment, I often need to filter out more than 36 specific labels. Since we have over 300 labels in our database, manually rebuilding these complex queries is quite time-consuming. Having a "Saved Filter" option would allow us to store these frequent segmentations and apply them with a single click, significantly increasing our efficiency. I’d love to hear your thoughts on the feasibility of this!

Request to add a new variable shipping_address.primary_phone that returns a processed version of the shipping address phone number. shipping_ address.phone is currently used as-is from Shopify and may not include a country code, which causes issues in downstream processes that require a valid international phone format. While order.primary_phone is already normalized, it may come from order.phone , customer.phone , or customer.default_ address.phone , and may not reflect the shipping recipient’s phone number. This makes it unsuitable for cases where the shipping address contact must be preserved as the source of truth. The new variable should take shipping_ address.phone as the source and automatically apply the correct country code based on the contact's original phone number/shipping address country etc. when it is missing, returning a standardized phone number ready for use in flows.

Certain customers may have 0 interactions with us, thus didn't enroll in any flow with any auto-assign labels. It would be great, if there was a way for us to select the as RULE : Empty. From there, we can see all contacts with 0 labeling so we can delete these contacts to save space. (certain companies may have more than 50 labels, clicking them 1 by 1 is very inefficient. 2nd, LAST CHANNEL should include : does not contain... Since theres so many channels, we cant find customers who are not from certain channels.

Description A public API endpoint that allows for the programmatic retrieval of contact-level activity logs (audit trails) using a unique identifier (such as user_profile_id). Currently, while this data exists within the system, it is not accessible via the public documentation. Exposing this would allow for: Automated Data Exports: Enabling users to sync audit logs with their own internal databases or reporting tools without manual intervention. Programmatic Compliance: Allowing users to verify contact history and activity sequences through external integrations. Self-Service Data Access: Reducing the need for manual support requests by empowering users to pull their own historical activity data directly. Desired Outcome Include a dedicated "Audit Trail" or "Activity Logs" section in the public API documentation with GET methods to fetch chronological history for individual contact profiles.

Currently, the contact list does not support arrangement of sequence and only allows pinning contacts list. Allowing users to arrange the contact list according to their preferences would enhance the user experience. Thanks

This feature would allow users to export the contact activity log directly from the platform. By having access to a downloadable record of contact activity, users can more effectively monitor changes, maintain accurate records, and perform their own audits for better oversight and security.

Use the API to programmatically delete custom objects from SleekFlow, enabling developers to manage and clean up custom data structures as needed.

Import the past 6 months of chat history when contacts are synced via WhatsApp Business Co-existence, and ensure the "Last Contact from Customer" property accurately reflects a contact's most recent interaction accordingly, even for messages that occurred before the WhatsApp Business Co-existence connection date was established.

Store and manage contact names as a single full name field, ensuring consistency between how names are displayed in the interface and how they are stored in the system.