Widget changes are not showing on my site

Wait a minute, then hard-refresh

The widget reads its configuration through a cache, so changes you save in the dashboard reach live sites within about 60 seconds. If you refresh your site straight after saving, you are usually looking at the old configuration, not a failed change.

• Save your change in the dashboard.
• Wait a full minute.
• Hard-refresh the page so your browser does not serve its own cached copy: Ctrl+F5 on Windows, Cmd+Shift+R on Mac.

Most "my change disappeared" reports are just this delay. If the change still has not appeared after a minute and a hard refresh, work through the checks below.

Confirm you edited the right bot

Every embed script carries a data-bot-id attribute that ties the widget on a page to one specific bot. If your workspace has more than one bot, it is easy to edit one bot in the dashboard while the page you are looking at embeds another.

• Open the bot you edited and go to the Installation tab. Note the data-bot-id value in the embed script shown there.
• View the source of the page where the widget is installed and find the Matram script tag.
• Compare the two ids. If they differ, either make your edits on the bot the page actually embeds, or update the script on the page.

A new conversation starter is not appearing

You can save up to 12 conversation starters on the Conversation Starters tab, but the widget shows at most 6 of them. If you already have six or more enabled, adding another one does not guarantee it appears.

Each starter has an on/off toggle. Turn off the ones you can live without so that the starters you care about are within the six the widget can show.

The watermark does not change with appearance settings

The "Powered by Matram" watermark on the widget is removed only by the paid remove-branding add-on. Standard and Pro advertise branding removal. No appearance setting removes the watermark from a live site, so if it is still showing after you have restyled the widget, that is expected behaviour rather than a caching problem.

See plans and usage limits for what each plan includes.