Bug fix
12 Jul 2026

Latest bug fixes

Facebook Messenger conversations get an answer
On Facebook Messenger, conversations handed to a bot could fail to start: the shopper got no reply and the conversation closed on its own after some 35 minutes. These conversations now start and answer.

FAQ answers reach the Assistant from your Knowledge Base
A question covered by a FAQ record in your Knowledge Base got a generic answer instead: the record was never handed to the AI Shopping Assistant, which treated the question as ordinary conversation. FAQ records are served again.

FAQ links stay clickable in the Assistant's answers
When a FAQ source held a link written in HTML, the AI Shopping Assistant dropped the address and showed the link text in bold. These links are now clickable in the answer.

The keyboard comes back in the Shopping Panel on iOS
On iOS, a shopper who hid the keyboard and then tapped the message field again did not get it back, and could no longer write. The keyboard now opens on every tap.

The assistant triggers a personalised action when Product Discovery is disabled
On accounts where product discovery is not enabled, a shopper asking for a product ("I am looking for a washing machine") kept the conversation with the AI Shopping Assistant, so no transfer was triggered. These requests now trigger the pre-configured action in the assistant builder which is usually a transfer to humans.

Navigation time is right in the visitor panel
In the Navigation tab of the visitor panel, the navigation time showed a value of about 56 years instead of how long the shopper had been on the site. Agents see the real duration again.

Closed conversations leave the Ongoing tab of the Production report
A conversation closed in the database could keep showing in the Ongoing tab of the Production report for several days after it ended. The tab now reflects what is really open.

A product option without a name no longer blocks PrestaShop indexing
A PrestaShop product knowledge source stopped indexing as soon as a product option came back without a name, and manual updates changed nothing. These catalogs now index.

Time conditions read in seconds in the Engagement Strategy list
In the Engagement Strategy list, time conditions were displayed in minutes as a decimal, so a 29-second condition read 0.48. The list now shows seconds, like the strategy editor.