Most widget issues come from duplicate scripts, cache, wrong domain, blocking optimizers or unclear position settings. On WordPress and agency sites, the script is often loaded through theme, plugin and tag manager at the same time.
Check one active embed, allowed domain, cache/CDN, consent blockers, lower-left or lower-right position and stable chat state after reloads.
Start with a narrow boundary: which website, space, file, recipient or decision is affected? This makes the task reviewable instead of turning it into a broad catch-all request.
A useful work order is: “Create a LeadOS widget troubleshooting list for duplicate scripts, cache, domain, consent, position, reload and notification.” For important cases, add that uncertainties must be marked visibly instead of being filled in silently.
Pay special attention to script duplicates, cache, CDN, consent, position, reload and allowed domain. These points decide whether the result is only useful for the moment or can be found, checked and continued by the team later.
Do not use theme file, snippet plugin and tag manager together until it is clear which embed is active.
A clean embed makes the widget stable and reduces support before the first real lead arrives.