February 2026

Enhancements and new feature introductions in February

February 05, 2026

Message Failed List option in Flow Analytics

We’ve added the Message Failed List feature to Flow Analytics.

This allows users to view and export conversations from the failed messages list, helping identify delivery issues and enabling quicker troubleshooting and resolution.


February 09, 2026

Instant Code

We’ve introduced the Instant Code feature for e-commerce customers.

Each product is assigned a unique code, allowing customers to simply send the code in chat to instantly receive the corresponding product details. This streamlines product discovery and enhances the overall shopping experience.


February 12, 2026

We’ve introduced Media Carousel and Product Carousel Session Messages to enhance interactive messaging.

  • Media Carousel Session Message: Send multiple media cards in a single swipeable message, creating a more engaging and interactive user experience.

  • Product Carousel Session Message: Showcase multiple products in one swipeable message with detailed information and action buttons, helping users make quicker decisions.

These are session messages (not template messages), allowing for more flexible and real-time interactions with users.

This update improves content presentation and makes customer interactions more dynamic and user-friendly.


February 15, 2026

CTA Button URL Block in Chatbot

We’ve introduced the ability to send CTA (Call-to-Action) URL buttons directly from the chatbot.

This feature allows businesses to guide users to specific links—such as product pages, payment links, or external resources—enhancing user engagement and driving quicker actions within conversations.


February 20, 2026

HTTP Action in Flow Timeout

We’ve introduced the ability to trigger HTTP API actions when a flow conversation times out.

This feature enables automated handling of inactive sessions, allowing businesses to perform actions such as sending data to external systems, updating records, or triggering follow-up processes when users do not respond within the expected timeframe.

Last updated

Was this helpful?