v2026.7.3
Release date: July 7, 2026
✨ New Features
Follow-up Response Rate
You can now track the effectiveness of automatic follow-ups sent by your flows — whether triggered by a response timeout ("Wait for Response" node) or by an AI Agent reschedule. Interflow automatically counts how many customers reply after receiving a follow-up and shows this rate in reports and on the sales funnel.
What is it for?
- Measure how many customers reply after an automatic follow-up
- Compare follow-up effectiveness by flow and by origin node
- Track the response rate over time
- Get a summarized indicator right on the sales funnel
How to use it?
- No setup is required to get started: every follow-up triggered by an "Wait for Response" timeout or an AI Agent reschedule is now tracked automatically
- To see the detailed report, open the flow in the Flow Builder and click "Follow-up Analytics" at the top of the editor
- To see the summarized indicator, go to the Sales Funnel (CRM) — the response rate card appears at the top of the screen
- (Optional) Adjust the response window — how long the system waits after the follow-up before considering the customer didn't reply:
- Global default: in Settings → Organization, set the default window (48h by default)
- Per flow: in the flow settings (⚙️), override the default window for that specific flow
💡 What counts as a response? Any message sent by the customer within the configured response window, starting from when the follow-up was dispatched.
Full guide: Follow-up Response Rate
🔄 Improvements
Flow test using unpublished draft
When testing a flow directly from the Flow Builder, the test now uses your draft changes (not yet published), letting you validate changes before publishing. When a test is started from an AI Agent action (in Prompts), it keeps using the published version, as expected.
More thorough test reset
When clicking "Restart" in the flow test, besides clearing the conversation messages, the system now fully removes the previous flow session linked to the chat — preventing leftover data from an old session from interfering with the new test.
Notifications disabled during testing
Messages sent during a flow test no longer trigger push notifications to the team (assigned agent/collaborators), since it's a simulation and not a real conversation.
Visual progress indicator during testing
While testing a flow in the Builder, the edge leading to the active node is now highlighted with an animation, making it easier to visually follow the conversation's path.
🐛 Bug Fixes
Timeout checker performance
The routine that processes "Wait for Response" (Input node) timeouts was optimized: sessions are now processed in batches with controlled concurrency, and the check keeps running immediately until the pending queue is drained, instead of waiting for the next scheduled cycle. This eliminates delays of up to 20-30 minutes that could occur with large queues.
Node incorrectly highlighted in the Flow Builder
Fixed an issue where more than one node could appear highlighted (green border) at the same time while testing a flow — even after reloading the page. The cause was leftover test data that had been incorrectly saved into the flow; affected flows have already been fixed, and an extra safeguard prevents this from happening again.
🎯 Benefits
- ✅ Real visibility into the effectiveness of automatic follow-ups
- ✅ Data to fine-tune re-engagement campaigns and messages
- ✅ Response window configurable globally, with a per-flow override option
- ✅ More reliable flow tests that match what will actually be published
- ✅ Timeout processing up to tens of times faster on large queues