Widget Not Showing
The voice widget does not appear on your site, appears in the wrong place, or a visitor cannot start a call.
Symptoms
- Nothing appears on the page where you pasted the code
- An inline widget shows up in the bottom-right corner instead of where you put it
- The widget shows your old look after you changed it in Dialora
- The widget appears but the call does not start
- The Widget tab in Dialora says Not seen yet
First: read the browser console
The widget writes short messages to the browser console that start with [dialora]. Open your page, open the browser’s developer tools, choose the Console tab and reload.
| Message | What it means | What to do |
|---|---|---|
[dialora] missing_client_key | The script tag has no data-client-key attribute, so the widget did not start. | Copy the snippet again from the Widget tab and paste it unchanged. |
[dialora] container_not_found (wdgt_...) | The look is Inline, but no element with the matching data-dialora-widget ID appeared within 10 seconds. The widget floats in the bottom-right corner instead. | Add the container line from the Widget tab, with the same widget ID as the script. |
[dialora] duplicate_container (wdgt_...) | Two or more elements on the page carry the same widget ID. Only the first gets the widget. | Keep one container per widget ID, or use a different widget for the other spot. |
[dialora] config_failed (wdgt_...) | The widget could not load its settings. | Check that the widget ID is right, that your site is allowed to reach the Dialora API, and that the widget still exists. |
[dialora] recaptcha_failed | The reCAPTCHA check did not load or did not finish, so no call was placed. | See A strict Content Security Policy and the reCAPTCHA note below. |
[dialora] call_error | The call failed to start or dropped. | See The call will not start. |
[dialora] init_failed or render_error | The widget failed while starting. | Reload without extensions. If it persists, contact support with the full console message. |
The widget ID in brackets says which widget the message is about when a page shows several. Each message appears once per page load and per widget.
Common causes
- The script was not pasted, or was pasted in the wrong place: the page does not contain the script tag, or an editor removed it.
- A different widget ID in the container and the script: both must carry the same ID.
- The container is missing, or hidden: an inline widget needs the container element on the page and visible.
- A strict Content Security Policy: the page blocks the widget’s script, stylesheet, reCAPTCHA or call connection.
- Another script on the page: a second copy of the widget, or another reCAPTCHA version, interferes.
- An older copy of the script: the site still runs a copy that predates the new looks.
- The microphone is blocked: the browser or an iframe does not allow microphone access.
How to fix
Step 1: Confirm the code is on the page
- Open the page and view its source, or look at the Elements tab in developer tools.
- Search for
widget.js. The script tag should be there with adata-client-keythat starts withwdgt_. - If it is missing, paste the snippet again. Some editors and plugins strip script tags: use the platform’s custom code area (see Add the Voice Widget to Your Website).
Step 2: For an inline widget, check the container
- Search the page for
data-dialora-widget. - Its value must equal the script’s
data-client-key. - Make sure the element is not hidden with CSS and is not inside something with a CSS
transformif the widget is floating. - If your site adds content after the page loads, the widget waits 10 seconds for the container. A container added later than that still works: the widget moves in from the corner as soon as it exists.
A page can show different widgets side by side, each with its own widget ID, but a widget ID only once. If a second widget does not appear, check that its container line carries its own widget ID, not a copy of the first one. Two floating widgets in the same corner overlap, so give them different corners.
A strict Content Security Policy
If the console shows messages such as “Refused to load the script”, “Refused to connect” or “Refused to apply inline style”, your page’s Content Security Policy blocks part of the widget. The console message names the blocked address. Allow it in your site’s CSP. The full list the widget needs is in Add the Voice Widget to Your Website.
The call will not start
- Microphone: the browser asks for microphone permission when the call starts. If it was blocked before, click the lock icon in the address bar and allow the microphone. If your page is inside an iframe, the iframe needs
allow="microphone". - reCAPTCHA: the widget uses Google reCAPTCHA. A page that loads a different reCAPTCHA version may conflict with it. Try the widget on a page without other reCAPTCHA code to see if that is the cause.
- Credits: a web call uses call credits like any other call. Check your balance in Dialora.
- Test the agent itself: open the agent’s Playground and start a web call (see Test Your Agent Before You Publish). If that fails too, the problem is the agent, not the website.
The widget still shows the old look
- Reload the page without the cache (Ctrl+Shift+R, or Cmd+Shift+R on a Mac).
- The widget loads your settings when the page loads and refreshes them about every minute.
- A site running an older copy of the widget script shows the classic look (a round button that opens a card) regardless of the look you chose, until that copy updates. If the old look stays after a reload, contact support.
The Widget tab says Not seen yet
The “Seen on” line only updates when a visitor’s browser loads your page with the widget, at most once an hour. Reload your live page (not a local file or a preview that blocks outside requests), then refresh the Widget tab after a minute. It is informational and can be wrong if a browser does not send the information it is based on.
Prevention Tips:
- Always copy the snippet from the Widget tab instead of typing it
- Use each widget ID once per page, and the same widget ID in a widget’s container and its script line
- Test on the live page after every site change, and look at the console
- Add the widget’s addresses to your CSP before you turn on a stricter policy