# February 2026

### 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.

**📍 Where to find:**\
Chatbot → Published Version Analytics View → Click on Message Block's Analytics → View Failed List Analytics

<figure><img src="/files/6AN0R400T21pJs3WGbSc" alt=""><figcaption></figcaption></figure>

***

### 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.

<figure><img src="/files/qzzz1d0S2XGARYr3TQwR" alt=""><figcaption></figcaption></figure>

{% embed url="<https://help.pickyassist.com/whatsapp-commerce/instant-code/instantcode-overview-and-usage-guide>" %}

***

### February 12, 2026

## Media and Product Carousel Session Messages

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.

**📍 Where to find:**\
Chatbot Builder → Right-click → Search “Send Carousel Message” → Select the block

<figure><img src="/files/hizcqijJ4XWERdEoQwyD" alt=""><figcaption></figcaption></figure>

***

### 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.

**📍 Where to find:**\
Chatbot Builder → Right-click → Search “CTA Button URL” → Select the block

<figure><img src="/files/ym1pYtMzkZ1g93G5nR2T" alt=""><figcaption></figcaption></figure>

***

### 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.

**📍 Where to find:**\
Chatbot Builder → Settings → ⚙️ (Gear Icon) → Timeout → Actions → Search “HTTP Request”

<figure><img src="/files/1o3eG4HK5ygkYAUaQ9Xd" alt=""><figcaption></figcaption></figure>

***

### February 20, 2026

## iPhone Video Sending Issue Fix in Teambox

We’ve resolved an issue where videos could not be sent from iPhone devices (Picky CRM App) in Teambox.

This fix includes a **native video converter**, ensuring smooth video uploads and improved compatibility for iPhone users.

**📍 Where to find:**\
Mobile App (ios) → Teambox → Conversations → Send Video


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.pickyassist.com/changelog/2026/february-2026.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.