Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Contact Us
English (US)
CO Spanish (Colombia)
US English (US)
  • Home
  • wvx Digital Interaction

How to troubleshoot widget loading issues on the client's website?

Discover effective solutions to resolve widget loading problems on web pages.

Written by Sandra Ocaña

Updated at September 16th, 2026

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • wvx Digital Interaction
  • wvx Voice Interaction
  • wvx Conversational AI
  • wvx Control Interactions
  • wvx CRM
  • wvx Agent
  • wvx Studio
  • Cibersecurity and Compliance
  • Release
    wolkvox Manager release wolkvox Agent release wolkvox CRM release
  • Partner Portal
+ More

Symptom / Need

The client reports that the widget does not load on their website, so it is not possible to view or interact with it on screen.

Context / Scenarios

This issue directly affects the client's website where the widget code has been integrated. The problem may be related to an omnichannel service outage, errors in code insertion, or server infrastructure updates.

Answer / Solution

Minimum information required

To properly document the ticket, manage the case, or escalate it (if necessary), it is essential to collect the following data:

  • Name of the operation.
  • Operation server.
  • Customer website where the new loading feature is presented.

Initial Validations and Troubleshooting

To identify the cause and resolve the widget display failure, the service desk analyst performs the following technical troubleshooting procedure:

Step 1 (Service Status): Verify that the Web Chat service is fully active within the operation in the omnichannel section, that the widget is properly created and that it has not been deleted.

Step 2 (Code Review): Go to the webpage provided by the client and open the browser console to review and confirm that the widget's " code " is correctly embedded on the site.

Step 3 (Cross-Operation Testing): Perform functionality tests of the widget in another operation located on the same server to rule out a generalized node failure.

Step 4 (Controlled Environment Testing): Generate functional tests of the widget in a controlled environment using the Cubic Factory web application or by pasting the code directly into a notepad.

Step 5 (Server Analysis): Check if any updates have been performed on the server assigned to the operation.

Step 6 (Wolkvox Verification): Validate the behavior of other widgets that are configured on Wolkvox servers.

Escalation

If, after meticulously executing each step of the troubleshooting protocol, the widget still does not appear on the client's website, the analyst proceeds to document the case with the minimum required information and evidence of the validations and tests performed, in order to escalate the ticket to Level 3 (Digital Team).

widget troubleshoot

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • WhatsApp templates with dynamic URLs arrive empty or with broken links
  • How to troubleshoot SMS sending issues with your transaction?
  • What is WhatsApp Voice and What Do You Need to Activate It in wolkvox
  • How to Send a Contact Card via WhatsApp from a Chatbot

2026 Wolkvox

Information security policy | Privacy Policy

Expand