SleekFlow Product Requests

Currently, the service is only available for 1 to 1 conversation. For businesses like ours, we will need to include sometimes both parents or even the child together in one group to manage the conversations.

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.

As a business operating primarily in the US market, I would love to see native iMessage integration supported. Currently, if we want to text our customers using a US number, we are often forced to jump through hoops to obtain toll-free numbers or pivot to alternative, less seamless channels. Supporting iMessage would give us a native way to reach Apple users right where they already are. Business Impact: Allows businesses to engage customers through a familiar native messaging experience on Apple devices. Reduces operational barriers for customers who do not wish to obtain a toll-free number. Expands channel options for US-based businesses. May improve customer reach and response rates among iPhone users.

Customers using SleekFlow for advanced reporting and need programmatic access to journey progression and funnel performance data. Currently: Contact Properties are available via API. Labels are available via API. Conversation Analytics are partially available via API. However: Conversion Analytics are not available via API. Lifecycle Stages are not available via API. This creates a gap for customers who want to build external reporting dashboards, perform deeper analysis, or combine SleekFlow data with CRM. Requested Enhancement: Conversion Analytics API: Expose conversion event data through the Public API, including: Conversion event types Event timestamps Event counts Funnel progression data Contact-level conversion event history (where applicable) Example use cases: External funnel reporting. Journey drop-off analysis. AI/chatbot performance reporting. Cross-platform attribution analysis. Lifecycle Stages API: Expose Lifecycle Stage data through the Public API, including: Current lifecycle stage. Lifecycle stage history. Lifecycle stage transition timestamps. Ability to filter/query contacts by lifecycle stage. Example use cases: Customer journey reporting. Lead management dashboards. Dormancy and re-engagement analysis. CRM synchronization. Business Impact: Customers increasingly use external tools and internal reporting platforms. While labels can be used as a workaround, native API access to Conversion Analytics and Lifecycle Stages would provide a much cleaner and more scalable reporting architecture.

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.

1) It would be great to see all the flows in 1 page rather than flipping to the other page. 1-10 / 11 - 21 / etc to infinite scroll. All in one page is easier to manage the flows. 2) Allow us to enable / disable which flow without entering the flow itself and press "save as draft"

In the current inbox, when I filter by User, it shows both Contact Owner and Collaborator, which makes it unclear how to track the chat quality of my teammate, who is the Contact Owner.

For the data source from AI Assistant reply, I would like to have both the URL link and File Name to be shown and the URL link should be clickable for user to easily cross check with the data source

Recommended dark mode palette with grey base and SleekFlow blue as accent Base / neutral colors Main background: #111B21 Secondary background: #202C33 Card / panel background: #1F2A30 Hover / active surface: #2A3942 Border / divider: #374248 Text colors Primary text: #E9EDEF Secondary text: #AEBAC1 Muted / disabled text: #8696A0 Accent colors inspired by the SleekFlow logo Primary accent blue: #0568FE Accent hover blue: #1C78FF Soft accent blue: #4F94E0 Suggested usage Use grey/charcoal tones for the overall interface background, sidebar, cards, and chat surfaces Use blue only for primary actions such as buttons, selected tabs, links, highlights, and key interactive elements Avoid using blue as the full-page background to keep the UI cleaner and more balanced i believe most of the dark mode in any application such as WhatsApp, facebook n instagram they try to keep the UI in a dark mode with a neutral grey base, while using their own inspired color only as the accent color for branding and interaction

This feature allows the AI to automatically transcribe incoming voice messages into text. Users benefit by receiving these transcriptions as internal notes, making it easier to quickly understand and manage customer communications without needing to listen to the audio.