iAdvize Changelog

With a custom role, managers can access new actions

2026-10-05T00:00:00Z

Custom roles, built on the Manager role, define which parts of the administration managers can access. The Engagement section, AI Shopping Assistant, Knowledge and the management of other managers used to be reserved for administrators.

A custom role can now grant both. With access to Engagement, a manager works on campaigns, distribution and the widget editor, as well as custom data and scoring settings. With peer management, a manager creates, edits and deletes other managers in their group: administrators remain out of reach, and no one can delete their own account.

Both permissions are disabled by default. Open a custom role in Settings > User Management > Custom Roles to grant them.

It is still possible to assign one or more projects/SIDs per manager (see User Management > Expertise > Projects)

Related articles
Custom roles and permissions

Latest bug fixes

2026-10-05T00:00:00Z

AI Shopping Assistant

On a product page, the AI Shopping Assistant no longer shows a product card that contradicts its answer

Support Desk

In the Support Desk, the Analyze button no longer disappears from Maestro answers with formatting or a link on WhatsApp and Messenger

Administration

In the Overview report, revenue from projects in different currencies is no longer added together

In the Conversations report, agent names in the message thread now follow the same permissions as in the table

In the Conversations report, managers can now block or unblock the shopper from a conversation's details

Accented characters no longer come out garbled in the FAQs generated from your knowledge sources

The "Some conversation starters are not displaying" alert names each strategy and its rate

2026-10-02T00:00:00Z

The "Some conversation starters are not displaying" alert appears in the notification center of your administration when Starters trigger without showing on your site. It used to fire below an 85% display rate and listed the widgets concerned, without saying how many triggers were lost or why.

The alert now targets one cause: the Starter's CSS selector could not be found on the page. It fires when a strategy drops below a 75% display rate for that reason, over at least 100 triggers in the last 48 hours, and clears on its own once every strategy is back at 5% of lost triggers or less. The notification gives the number of strategies concerned. On the strategies list, each one is named with its rate and a link to its position tab. On the previous engagement interface, the widgets list gives the same detail.

Follow the link of the strategy flagged to check its CSS selector.

Related articles
Your Administration Alerts

Isolate the sales made on desktop, mobile or tablet in your Sales report

2026-10-01T00:00:00Z

The Sales report shows the orders and revenue that follow your conversations. It could not tell a sale that started in a conversation on a phone from one that started on a computer.

A Device type filter now keeps only the sales from conversations started on desktop, mobile or tablet, one device or several. It applies to the sales linked to a conversation, in the indicators as in the product and category tables, not to your website's total sales. Device is known for conversations started from 1 October 2026: before that date, conversations only count when no device is selected.

In the Sales report, add the Device type filter from the filter bar.

Related articles
Reports - Sales

The Respondents filter of your Conversations report adds an Only mode

2026-09-28T00:00:00Z

The Respondents filter of your Conversations report keeps every conversation where the respondents you picked took part. It said nothing about the others: a conversation your AI Shopping Assistant opened and an agent finished came back in the same list as one the assistant carried from end to end.

The filter now opens on two modes. Contains works as before. Only keeps the conversations where no respondent type other than the ones you picked took part, so a conversation passed to an agent drops out of the list. The names follow the vocabulary you see elsewhere, AI Shopping Assistant and Workflow, in the filter as in the performance table, and conversation details list every respondent, including the users you have deleted. Open the Respondents filter of your Conversations report to pick a mode.

Related articles
Reports - Conversations

Latest bug fixes

2026-09-28T00:00:00Z

AI Shopping Assistant

In the Shopping Panel, a message that had finished typing no longer replays its animation when a shopper switches tabs

Engagement Widgets

A widget scoped to one kind of page no longer appears for a moment on the next page

Administration

A conversation where the shopper only sent an image is no longer counted as unanswered

Transaction lines carrying a product reference now match that product in your catalog

A knowledge source whose file lost a mapped column now reports an update error instead of failing silently

Saving a user who has no spoken language selected no longer returns an error page

In your reports, an hourly chart covering several days now shows the date, on the axis as on hover

Conversation export filenames now carry the year of the period you selected

A campaign whose targeting rule holds an older action now opens instead of failing to load

Opening an existing engagement strategy no longer leaves you on the loading screen

Opening a campaign in the campaign builder no longer reports that its skill could not be found

Check your product catalog quality when you import it

2026-09-28T00:00:00Z

Your product catalog is the source your AI Shopping Assistant answers from when a shopper asks about a product. Until now, nothing told you whether the file you had just mapped was good enough to work with: the quality score only existed in the onboarding funnel, so a catalog added later was set up blind.

That quality grid now sits under your CSV file or your Google Shopping URL, with a clue telling you whether the catalog can be used as it stands. It runs when you import a file, when you change a column mapping, when you open a source you had already saved, and as soon as a Google Shopping URL validates. Nothing to switch on, add or open a product catalog source to see it.

Related articles
The CSV file for your product catalog

An input field replaces the "Ask a question" button on your integrated Starters

2026-09-22T00:00:00Z

Integrated Starters appear on your pages and suggest questions to shoppers. To ask a different one, shoppers had to click an "Ask a question" button first, which opened the field. Most shoppers who clicked the button dropped off before sending their question.

The number of steps is now reduced: this button becomes an input field, and shoppers can type their question directly from the starter. You can choose the text that appears inside it, up to 30 characters, along with two colors: the bar's background and its send button.

Go to the Style tab in your widget editor to customize it.

Related articles
The different widgets

Your AI Shopping Assistant remembers products discussed and suggested

2026-09-21T00:00:00Z

Until now, the AI Shopping Assistant only knew the product on the page and the ones it had just recommended. A shopper returning to a product mentioned earlier in the conversation had to name it again to get an accurate answer.

It now remembers the products discussed in the conversation and the ones it suggested, up to the last fifteen, and works out which one is being referred to. A question about two products gets an answer covering both, where only one used to be taken into account. Each product it reviews carries its brand, color, price and availability, enough to tell apart two variants of the same model.

This memory also makes it possible to compare a product currently being discussed with one mentioned earlier in the conversation, and to point out the differences between the two.

This behavior is rolled out for all customers. Nothing to set up on your end.

Screen readers now skip the emojis in your conversations

2026-09-21T00:00:00Z

Shoppers who follow the conversation with a screen reader heard every emoji read out under its full technical name, enough to lose the thread of a message.

Emojis are now hidden from screen readers and other assistive tools: the reading runs through the message without stopping on them, and they stay visible on screen for everyone else. One more criterion of the accessibility audit is met, after the ones your Shopping Panel already covers.

This applies to every conversation, with nothing to set up.

Latest bug fixes

2026-09-21T00:00:00Z

Engagement Widgets

Conversation Starters no longer answer with product details from before your last catalogue update

Administration

The Shopping Assistant report names the suggested products again instead of showing them all as deleted

A conversation closed a day or more after a product was discussed now counts towards that product

The "Missing information or transfer" filter no longer empties the chart and the total of your reports

Your Shopping Panel now works with a keyboard and a screen reader

2026-09-14T00:00:00Z

The Shopping Panel and the classic chatbox are where your shoppers talk to your Assistant. Parts of them could not be used without a mouse: links with no visible focus, fields whose only label was the grey text inside them, feedback buttons that announced nothing to a screen reader.

They now follow the RGAA and WCAG 2.1 criteria covered by the accessibility audit. Links carry their own name, keep an outline that stays visible on a dark background and warn when they open a new window, and a product card offers one named link instead of three stops in the tab order. The comment box of a survey, the email field and the message box carry a real label, an invalid email address is announced out loud instead of turning a line red, and the rating buttons say what they are and which one is selected.

This applies to every Assistant.

Your Conversation Starters are generated from your catalog

2026-09-14T00:00:00Z

Conversation Starters are the questions suggested on your pages to open a conversation. They were written from the text read on the page itself, so a page showing an old price or an old description produced questions that did not match your catalog.

When a page matches a product sheet in your knowledge base, that sheet now comes before the page content. A page with no product sheet behind it behaves as before.

Your shoppers add a product to the cart from your app

2026-09-14T00:00:00Z

The Assistant already recommends products inside a conversation. In your mobile app, a shopper still had to leave that conversation to buy one.

Tapping Add to cart now hands the product to your app, which puts it in the cart, and the Assistant confirms it in the conversation. A product sold in several sizes or colours opens a panel first, listing the criteria that product carries: size, colour, gender, material, condition, brand. The picture, the title and the price follow the selection as it changes, and your app receives the exact variant chosen. A product with a single variant is added straight away. A combination you do not sell or that is out of stock shows Not available on a button that cannot be tapped, and the button itself only appears on products you have in stock.

This works on all four platforms the iAdvize SDK supports: iOS, Android, React Native and Flutter. Your developers update the SDK (iOS 3.2, Android 3.2.1, React Native 5.2, Flutter 3.2) and write the handler that adds the product to your cart. Until they do, the conversation keeps its current View product button.

The confirmation message can also carry a Go to cart button. Give your cart address to your iAdvize contact and intercept the tap in your app.

The same SDK versions also improve long conversations: a shopper who scrolls up to re-read an answer now sees a button as soon as the conversation is no longer at the bottom, and one tap returns to the latest message. The chatbox in your app behaves like the Assistant on your website on this point.

Shoppers see when an AI is answering them

2026-09-14T00:00:00Z

The AI Act asks you to tell a shopper when an AI is answering. Nothing in the conversation said so.

The Shopping Panel and the classic chatbox now carry "You're chatting with an AI" in their footer, for as long as the Assistant is the one replying. The line appears once the conversation reaches the Assistant and goes away when the conversation is passed to one of your agents, so what the shopper reads always matches who is on the other side. Hiding the iAdvize logo does not hide it: the two are separate settings now, and the notice stays either way.

Nothing to switch on, it shows on every conversation your Assistant handles.

Latest bug fixes

2026-09-14T00:00:00Z

AI Shopping Assistant

The Assistant no longer slips characters from another alphabet or pieces of its own draft into its answers

A shopper no longer gets a fallback answer when the FAQ holds a usable one

A conversation left without a reply now closes after five minutes instead of thirty

In your Android app, the Retry button appears again when the network drops

Engagement Widgets

A widget closed by a shopper no longer comes back on the same page

Support Desk

Your agents see the shopper's name and details in the profile panel again

Manager users reach canned answers, offers, links and tags again

Administration

The waiting conversations counter no longer counts an assigned conversation twice

All your conversations appear in your reports again, including those carrying a recent kind of system message

Report pages open again for managers and administrators whose group was deleted

Connecting a WhatsApp number no longer stalls when Meta has already checked it

Follow-Up and Closing Improvements for Product Info

2026-09-14T00:00:00Z

Two changes shipped for the Product Info use case, both aimed at cutting dead ends in the assistant's conversations.

Graceful closing. The assistant now caps itself at two targeted follow-up questions per product. If the need is still unclear after that, it stops probing and closes with an open question instead of forcing a binary choice. No more endless digging.

Honest pivot on mismatch. When a shopper asks about a characteristic the product doesn't have, the assistant says so directly and redirects to a characteristic it can actually help with, rather than quietly steering the conversation toward a dead end. Before suggesting an alternative, it now checks the catalog first. If nothing in the catalog has it, it doesn't get suggested.

Create multiple AI Shopping Assistants on the same project (Admin V2)

2026-09-14T00:00:00Z

Until now, a project supported only one AI Shopping Assistant (Admin V2), the one from its initial setup.

You can now create several from the admin, and each engagement strategy specifies which one responds: an AI Shopping Assistant field, mandatory when saving, with knowledge sources limited to those of the selected Assistant. The strategy list shows the Assistant for each one and can be filtered by Assistant, a strategy whose Assistant is disabled is marked inactive with the reason, and a message warns of the impact before disabling or deleting an Assistant.

Available on the new admin interface (Admin V2). Open an engagement strategy and choose its Assistant in the Widget section.

Related articles
Engagement strategies

Apple Messages for Business: iOS 27 rule changes

2026-09-14T00:00:00Z

With iOS 27, Apple tightens its rules on Messages for Business. Content that breaks them is not delivered: the card or the image never arrives, and nothing says why.

Your messages are brought in line automatically: images are converted and resized to the format Apple expects, overlong titles are shortened, and the text of your messages is never touched.

One action on your side: Apple now only accepts https links. Replace any http links you still send on this channel.

AI Suggest is now using the same agentic architecture as the AI Assistant

2026-09-07T00:00:00Z

In the Support Desk, the replies suggested to your agents now come from the same AI agentic architecture that answers your shoppers. It answers the question directly, searches your catalog when the conversation calls for it, and hands your agent a draft reply ready to send.

The Copilot side panel for agents also works the same way with the new agentic architecture.