Existing is not yet launch-ready
An inherited workflow can be real while its setup, edge cases, and customer journey still need a Chatflow launch check.
Launch preparation in progress · no release dates promised
See what already exists in Chatflow's foundation, what is being built for the connected customer journey, and which ideas are still being explored.
The path ahead
No release dates are promised. A feature moves forward when the customer journey works and the live result is verified.
These workflows exist in the inherited application. Availability for a new Chatflow customer depends on connection setup, a complete journey check, and launch verification.
Shared threads, assignment, and role checks exist in the inherited product. The full team workflow and Chatflow connection setup are still being checked for launch.
Explore this featureThe dashboard, owner review, follow-ups, and reminders provide a starting point. Chatflow is reviewing their coverage and clarity before inviting customers in.
Explore this featureSaved drafts, versioned publication, test runs, a run debugger and measured outcomes are available for supported visual steps. Third-party connectors and arbitrary code execution remain unavailable.
Explore this featureThese capabilities are on the current product checklist. Some have a starting point in the existing app; the full experiences described here still need to be built or improved and verified.
Account setup, WhatsApp Embedded Signup, connection health, and number limits are on the launch checklist. Each connection must work with a customer's own business account.
Conversation analysis and editable reply drafts use the configured provider. Staff review suggestions; autonomous knowledge agents and their handoff remain planned.
Explore this featureAgent Studio remains planned for knowledge-based assistants. Visual Bot Studio supports saved flows, testing, debugging and measured outcomes, with unsupported steps clearly marked.
Explore this featureSaved segments, Excel/CSV import, reviewed campaigns, schedules and drip sequences are implemented. Customer sending depends on connected numbers and approved templates. AI campaign handling and commerce outcomes remain planned.
Explore this featureLead links and QR references attribute incoming conversations and labels. Campaigns report delivery and reply outcomes. URL clicks, revenue and optional catalog connections remain unmeasured or planned.
Explore this featureThese directions need more customer learning or a separate scope decision. They are not part of the current launch commitment.
A combined inbox for WhatsApp, email, phone, and Instagram, plus voice campaigns, belong to a later phase.
Topics, sentiment, quality review, and a combined chat-and-call view remain ideas to evaluate before a build decision.
Advanced retargeting, click-to-WhatsApp attribution, and further AI actions need customer use cases and a scope decision first.
An inherited workflow can be real while its setup, edge cases, and customer journey still need a Chatflow launch check.
Feature detail pages describe intended workflows. They do not imply those workflows are available to customers today.
Future directions will be assessed against real customer needs before they become release commitments.
Decide what the feature should help a business do and what a complete journey includes.
Check the interaction, permissions, connection behavior, and the states a customer will actually encounter.
Confirm the released experience works for the intended customer before calling it available.
This roadmap is a view of current product direction, not a delivery promise. Chatflow's WhatsApp and other connected services must be configured and tested for the new customer workspace before a complete live journey can be claimed. We will update feature status as implementation and verification progress.