Floating Chat Widget Not Visible

If the Dragwyb Click to Chat floating widget is missing, first check whether the channels module is enabled and whether the current page, device, and channel meet the saved display rules. The frontend can intentionally omit the widget when these conditions do not match.

1. Confirm the Channels module is enabled

In WordPress admin, open Click to Chat and review the module setup area.
Confirm the Channels module is enabled and save the setting.
Open the Channels settings and confirm at least one channel is enabled with its required contact value configured.
For channels that support an embedded chat widget, confirm that channel’s chat-widget option is enabled when you expect an in-page chat window rather than only an external contact link.

2. Review display rules and site scope

Open Click to Chat → 3. Triggers & Targeting and check Display Rules & Site Scope. The widget can be configured to display across public pages and posts or only on selected post types. In selected-post-type mode, the widget is omitted when no types are selected or the current singular page is not an allowed type.

3. Check desktop and mobile visibility

In the same Triggers & Targeting area, check Device Target Visibility:

Enable Show on Desktop if the widget should appear on desktop devices.
Enable Show on Mobile Devices if the widget should appear on mobile devices.
Also check the device visibility for the specific channel. A globally visible widget can still omit a channel that is disabled for the current device.

4. Check the display delay

The Display Time Delay setting delays the widget’s appearance after page load by the configured number of seconds. Wait for the configured delay before concluding that the widget failed to render, and test with a delay of zero on staging when isolating the issue.

5. Understand editor previews and shortcode behavior

The automatic footer-injected widget is intentionally not rendered in Elementor preview mode. Check the public page outside the Elementor editor before diagnosing it as missing. The plugin also registers the [dctc-widget] shortcode for manually placing the widget; shortcode rendering bypasses the automatic post-type display-rule check, but it still depends on the Channels module being enabled.

6. Check page output and script conflicts

Test the published page in a private browser window, not only in the logged-in editor.
Clear page, CDN, and browser caches after changing visibility settings.
Inspect the browser console and network panel for JavaScript errors or failed plugin assets.
Temporarily test without script-defer, combine, or minification features on staging if the widget markup appears but does not work.
Check the theme’s footer hooks if the automatic widget is missing across the site; the plugin injects its widget through the WordPress footer action.

7. Test one condition at a time

Enable the Channels module and one correctly configured channel.
Set site scope to all public pages and posts, if that is the intended behavior.
Enable both desktop and mobile visibility at the global and channel level.
Temporarily set display delay to zero.
Check the published page outside page-builder preview and clear caches.
Restore your intended display rules after identifying the cause.

Related guides

Testing note: These checks follow the inspected source implementation. The public page, theme footer, and script behavior still need to be tested on your live site.