Disable an Unused Click to Chat Module

Disable a Click to Chat module in WordPress, save the setting, verify its Disabled status, and check which features and workflows will stop running.

Disable a Click to Chat module when your WordPress site no longer needs that feature. In Dashboard → Click to Chat → Settings → 1. General, the Feature & Module Management area lets you switch off the Social Channels Widget, AI Assistant & Autonomous Chatbot, or Support Center & Helpdesk Ticketing independently. Save the change and verify the module status before leaving the page.

Open Feature & Module Management

  • Sign in to WordPress with an account permitted to manage Click to Chat settings.
  • In the admin sidebar, open Click to Chat → Settings.
  • Select the 1. General tab.
  • Find Feature & Module Management. Each module has its own switch and status badge.

Choose which Click to Chat module to disable

Switch off only the module you no longer want to run. The card’s status changes to Disabled, and its module-specific configuration drawer closes. The three controls are independent:

  • Social Channels Widget: Stops the floating or embedded social/contact widget. Its configuration includes the [dctc-widget] shortcode.
  • AI Assistant & Autonomous Chatbot: Disables the AI assistant and related chatbot functionality. Its configuration includes the [dctc_ai] shortcode.
  • Support Center & Helpdesk Ticketing: Disables the support workspace and customer portal functionality. The portal shortcode is [dctc_support_portal].

Screenshot to add: Add a real screenshot of Click to Chat → Settings → 1. General showing one module switched off and its Disabled badge. Keep the exact module labels readable and hide private site information. The image above is a placeholder, not a screenshot.

Save the change and verify the status

  1. After changing the switch, click Save Settings in the settings page header.
  2. Wait for the Settings saved successfully! confirmation and automatic page reload.
  3. Return to Click to Chat → Settings → 1. General if needed.
  4. Confirm that the selected switch remains off and its badge reads Disabled. Other modules should retain their own settings and status.

What happens when a module is disabled?

The plugin readme states that turning a module off stops its associated scripts, styles, assets, and background queries from loading. The source also checks module status in relevant frontend and admin flows. This is a feature toggle, not a plugin uninstall.

  • Social Channels Widget: The frontend widget is suppressed while the Channels module is disabled, and the channel-management screen is unavailable through its normal module route.
  • AI Assistant & Autonomous Chatbot: AI features guarded by the module status are disabled, and the AI admin area is restricted while the module is off.
  • Support Center & Helpdesk Ticketing: The support workspace and customer portal are unavailable while Support Center is disabled.

Disabling a module should not be treated as deleting its stored data. The module-toggle code updates its enable setting; it does not run the separate uninstall-cleanup options. The source reviewed for this guide does not establish that disabling deletes existing settings, tickets, conversations, or leads. Do not use 3. Privacy & Uninstall to switch off an individual module.

Check pages and workflows that depend on it

  • If you use [dctc-widget], check pages and templates where the social widget is embedded. Visitors will no longer have that widget while the module is disabled.
  • If your site relies on the AI chatbot or knowledge-base answers, make sure visitors have another route for those questions before turning off the AI module.
  • If customers use [dctc_support_portal] or your staff use the support ticket workspace, arrange an alternative support route before disabling Support Center.

Re-enable a Click to Chat module later

To restore a feature, return to Click to Chat → Settings → 1. General, switch the relevant module on, and click Save Settings. Wait for the confirmation and reload, then check that its status badge reads Active. Review that module’s configuration and test the related visitor-facing workflow before relying on it again.

Related setup guides