> For the complete documentation index, see [llms.txt](https://docs.omnichat.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omnichat.ai/en/release-note/nov-4-2026.md).

# Nov 4, 2026

Hello, dear Omnichat users!

🚀 Here are the latest  feature updates:

1. [OmniClaw can now read and analyze Customer Journey performance](#omniclaw-can-now-read-and-analyze-customer-journey-performance)
2. [Chat to Order now supports self-service Stripe / Global Payments integration and payment method settings](#chat-to-order-now-supports-self-service-stripe-global-payments-integration-and-payment-method-settin)
3. [View messages from any time range in Inbox](#view-messages-from-any-time-range-in-inbox)
4. [SurveyCake survey links are now generated per channel, with more accurate respondent identification on LINE](#surveycake-survey-links-are-now-generated-per-channel-with-more-accurate-respondent-identification-o)
5. [Coupons now clearly show a “Redeemed” status on the customer-facing page](#coupons-now-clearly-show-a-redeemed-status-on-the-customer-facing-page)
6. [Set up WhatsApp Webhook forwarding yourself in the platform](#set-up-whatsapp-webhook-forwarding-yourself-in-the-platform)
7. [WhatsApp BSUID improvements](#whatsapp-bsuid-improvements)
8. [Open API: API and AI Agent integration updates](#open-api-api-and-ai-agent-integration-updates)

### **OmniClaw can now read and analyze Customer Journey performance**

Want to check a journey’s triggers, read rate, CTR, revenue or ROAS? You used to have to look them up one by one in the platform. Now, **just ask OmniClaw to check the performance of your journeys and each of their nodes!**&#x20;

The numbers match your journey data in the platform, and OmniClaw can also help explain what each metric means.

#### **Highlights**

1. Check the performance of journeys and each node, filtered by time range, channel or platform
2. Get explanations of metric definitions and calculations, e.g. LINE message nodes report open rate, not read rate
3. Compare up to 5 journeys at once and export performance data
4. Summarize node data for a single journey and get suggestions for improvement

{% hint style="warning" %}
OmniClaw **can’t currently create, edit, pause or delete journeys, or export** a journey’s order data.
{% endhint %}

<figure><img src="https://2848678129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3u2I1osIy6mEi07X1z46%2Fuploads%2FrM0skOqgzRAFyoTwj1ER%2FScreenshot%202026-11-04%20at%204.28.17%E2%80%AFPM.png?alt=media&amp;token=fcf9e653-d3dd-4d6c-8734-02642bdf7588" alt=""><figcaption></figcaption></figure>

### **Chat to Order now supports self-service Stripe / Global Payments integration and payment method settings**

☑️ Applicable to: OMO Chat to Order Module, WhatsApp Commerce Module

Connecting a payment gateway used to require help from Omnichat. Now, **you can connect payment gateways yourself and manage online and offline payment methods in Chat to Order’s basic settings.**

#### **What’s changed**

1. **Stripe integration (HK / SEA)**: enter your Secret Key and Signing Secret to **connect on your own**
2. **Global Payments integration (TW / HK / SEA):** available after your Global Payments application is approved and Omnichat has enabled it for you. Supports switching between test and live mode. In test mode, orders can be created but no payment is actually charged

\
📍Settings > App Integrations

<figure><img src="https://2848678129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3u2I1osIy6mEi07X1z46%2Fuploads%2FIWF4DWj0UpkMhCNlbMq2%2Fimage.png?alt=media&amp;token=714dd13c-29fe-4718-b7ac-c7a20b6827ba" alt=""><figcaption></figcaption></figure>

1. **Online payment settings**: choose a connected payment gateway and set the payment name your customers will see (supports Traditional Chinese, Simplified Chinese and English)
2. **Pay in-store settings** : add cash, bank transfer, cheque or custom payment types, e.g. set up multiple banks for transfers
3. **Pickup settings** now let you select the payment types you’ve set up, e.g. “Online payment - Credit card” or “Pay in-store - Cash”

📍Sales > General Setting

<figure><img src="https://2848678129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3u2I1osIy6mEi07X1z46%2Fuploads%2FTNLFiXTgLUZLOUuTcbzZ%2FScreenshot%202026-11-04%20at%204.43.26%E2%80%AFPM.png?alt=media&amp;token=d74670d9-13f5-421b-9547-c901db0fca57" alt=""><figcaption></figcaption></figure>

***For detailed steps, see the guide below ⬇️***

{% embed url="<https://docs.omnichat.ai/en/features/she-ding/integrations/app-integrations/integrate-with-stripe>" %}

###

### **View messages from any time range in Inbox**

With our message storage now optimized, **viewing messages in conversations is no longer limited to the past two years!** You can now view messages from any time range.

The following two features still have time limits:

1. Conversation search: each search still covers up to **365 days** of data, but there’s no longer a limit on which time range you can select
2. Conversation export: still limited to data **from the past two years**. To export older data, please contact your Omnichat consultant.

### **SurveyCake survey links are now generated per channel, with more accurate respondent identification on LINE**

Previously, all channels shared the same survey link, so when a LINE customer forwarded the link to a friend, the friend’s responses were recorded under the original recipient.&#x20;

Now, **survey links are generated separately for each channel, and LINE surveys open via LIFF**, so tags and completion times are synced to the person who actually filled out the survey.

#### **What’s changed**

1. LINE: select one or more LINE Official Accounts, and a separate LIFF link is generated for each. If the link is forwarded, responses are recorded under the actual respondent, and **the link can now be added to your LINE Rich Menu**
2. Other channels (Messenger, Instagram, WhatsApp): continue to use links with parameters. WhatsApp customers who only have a BSUID can now have their tags synced correctly
3. Prerequisite: your LINE Official Account must first be linked to a LIFF ID under “Channel Integration” before a link can be generated
4. Old links still work, but aren’t protected against forwarding. We recommend replacing old links on bot card buttons with the new LIFF links

### **Coupons now clearly show a “Redeemed” status on the customer-facing page**

Previously, a redeemed coupon only showed a grey “Redeemed on YYYY/MM/DD” button, making it hard for store staff to tell whether redemption was successful. Now, **successful redemptions are shown in a green status block with a check icon**, along with the redemption date, so staff can confirm at a glance.

<figure><img src="https://2848678129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3u2I1osIy6mEi07X1z46%2Fuploads%2Ffwx8PjRrzdIVos7hWLT8%2Fimage.png?alt=media&amp;token=48b79a22-6771-47ef-b38e-4827d7f24cdf" alt="" width="375"><figcaption></figcaption></figure>

### **Set up WhatsApp Webhook forwarding yourself in the platform**

Setting up a WhatsApp Webhook used to require help from Omnichat. Now, **you can set up Webhook forwarding yourself in the platform**, forwarding WhatsApp messages received in Omnichat (including Coexistence) to a third-party URL of your choice.

📍  Settings > Channel Integration > WhatsApp channel > Actions > Set Webhook Forwarding (up to two endpoints)

### **WhatsApp BSUID improvements**

1. BSUID column added to conversation report exports: the event-level CSVs for Average Response Time, Average First Response Time and Missed Messages now include BSUID
2. When a customer only has a BSUID and no phone number, the contact list and chat header now show just the contact’s name, instead of “null”

<figure><img src="https://2848678129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3u2I1osIy6mEi07X1z46%2Fuploads%2FrPu4JXWLudTPqDnarX96%2F1793778711724.jpg?alt=media&amp;token=a460ecf3-81ba-4985-87db-ab14dfb26dad" alt=""><figcaption></figcaption></figure>

### **Open API: API and AI Agent integration updates**

1. **Get Tag Logs v2 is now available**: uses cursor-based pagination (parameters `cursor` and `limit`), returns data sorted from oldest to newest, and returns `time` as a timestamp. **v1 is scheduled to be retired on 2027/1/21**, so please migrate to v2 as soon as possible ([API docs](https://developers.omnichat.ai/reference/get-tagging-log-records))
2. **AI Agent API error message update**: when an API call is rejected because the conversation isn’t in AI Chat status, the error now returns `INVALID_REQUEST_BODY` / `The room status is not supported`. This affects four APIs: To Human Agent, Close Chat Room, Trigger Auto Assign and Send Agent Messages
3. **More trigger conditions for the `ai-session:close` event**: when a conversation leaves AI Chat status (e.g. a human agent takes over, the conversation is closed, or the customer taps a transfer-to-agent button), the system now sends an `ai-session:close` event to the AI Agent ([API docs](https://developers.omnichat.ai/reference/get-tagging-log-records))
