const loginSupport = () => YundaDesk.login({
  getToken: () => fetch('/support/identity', { credentials: 'same-origin' })
    .then(response => {
      if (!response.ok) throw new Error('Identity request failed');
      return response.json();
    })
    .then(({ token }) => token),
});
if (window.YundaDesk?.login) loginSupport();
else window.addEventListener('yundadesk:ready', loginSupport, { once: true });

<script src="https://cdn.yundadesk.com/widget.js" data-yd-key="yd_widget_main" async></script>

Deactivation, disconnection, and deletion have different effects. Choose the action that matches whether you intend to pause the plugin, move the site, or remove the integration.

Understand each lifecycle action#

To disconnect, open Settings → YundaDesk, select the disconnect action, and wait for confirmation before deleting the plugin. If WooCommerce was authorized, also open WooCommerce → Settings → Advanced → REST API and remove the YundaDesk key after disconnection.

Disconnecting one site does not disconnect other WordPress sites in the same YundaDesk workspace.

Disconnect in WordPress in YundaDesk's site list opens WordPress Admin; it is not a direct platform disconnect. While disconnection is incomplete, the site remains visible as Disconnecting. Wait for completion, or return to WordPress to retry if it remains pending. Once complete, the site leaves the everyday management list without deleting conversation history. Temporarily unreachable, deactivated, or authorization-failed current sites remain visible and must not be treated as disconnected.

After all sites finish disconnecting, the app cards return to their original official installation entry without an installed status. When available, Install on WordPress opens the WordPress.org plugin directory directly in a new tab, not a connection-instructions dialog. You do not need to reinstall an existing plugin; you can also reconnect directly from Settings → YundaDesk in the intended WordPress Admin.

Export personal data#

1. In WordPress Admin, open Tools → Export Personal Data.
2. Enter the verified requester's email address.
3. Send or confirm the request using the normal WordPress process.
4. Generate the export after WordPress marks the request confirmed.

The YundaDesk exporter returns support data associated with the current connected site. Data that belongs independently to another connected site is not included.

Erase personal data#

1. Open Tools → Erase Personal Data.
2. Enter the verified requester's email address.
3. Complete the normal WordPress confirmation process.
4. Run erasure and review the result from every participating plugin.

The YundaDesk eraser applies only to the current site's connection. A remote deletion that cannot finish is reported as incomplete so the administrator can retry it. Site administrators must verify the requester and decide whether any data must be retained for legal reasons.

Move the site to another domain#

After WordPress uses its new website address, open Settings → YundaDesk at that address. If it still shows Connected, disconnect the current site and wait for confirmation, then select Connect YundaDesk. On Confirm the site address change, check the previous address, current address and chat channel, select Update and connect, then Return to WordPress. The original channel and past conversations are kept; you do not need another channel.

If the previous connection is already disconnected, follow Reconnect or restore a previous site to choose the correct target. Do not rely on a matching address alone, reuse old pairing links, or copy another site's connection settings.

Afterward, verify a new storefront message. If you use WooCommerce, separately renew read-only access and check an order from the current store.

Troubleshooting#

The Widget does not appear#

• Confirm that the site says Connected under Settings → YundaDesk.
• Test a public page rather than WordPress Admin, a login page, a feed, or a REST response.
• Clear page and CDN caches after connecting.
• Confirm that the site's content security policy allows the YundaDesk API and Widget loader listed in Data and permissions.

WooCommerce is not detected#

• Confirm that WooCommerce is active on the same WordPress site.
• Upgrade WooCommerce to version 8.2 or newer.
• Reload Settings → YundaDesk.

Reauthorization is required#

Select the read-only WooCommerce connection again and approve Read. Do not create and paste a Consumer Key or Consumer Secret into YundaDesk.

Several previous sites appear when reconnecting#

Check the workspace, previous site address, channel, and last connection time to identify the website you intend to restore. If unsure, ask your workspace administrator first. Do not select the first option arbitrarily or delete other historical sites.

WordPress is connected, but orders remain unavailable#

Check the site connection and WooCommerce authorization separately. Complete read-only authorization for the current site, then follow Verify order lookup to check the store, customer email, and order. Retry later if the page reports a temporary issue. If it persists, contact support without sharing store keys.

Synchronization or events are degraded#

Open Settings → YundaDesk, refresh the status, and retry the supported recovery action. If the problem continues, record the site address, approximate time, YundaDesk plugin version, WordPress version, WooCommerce version, and the non-sensitive error shown on the page before contacting YundaDesk Support. Never send passwords, API keys, customer addresses, or full order records in a support ticket.