How do I troubleshoot Engage or contact support?

Confirm the loader is installed once, after the correct company ID configuration. Check whether a tag manager and the site template both add it. If it is missing, review browser console errors, content security policy, script optimizers, and consent rules that may block the widget or its API requests.

Confirm the relevant source is current, approved, active, and present in the knowledge index. Check for conflicting documents, rebuild the changed source, and retry with a synthetic question. For routing or booking, verify the active destination and activity mapping rather than editing the answer to conceal a configuration problem.

Confirm the operator has the correct workspace and conversation, the channel supports replies, and the message shows an accepted or delivered state. If delivery failed, do not assume the visitor received it. Preserve the visible error and use an approved alternate contact path when the situation is time-sensitive.

Email support@ajai.pro with the product name, affected public page, approximate time, workspace identifier, and a brief description of expected versus actual behavior. Do not include passwords, one-time codes, API keys, private prompts, or full customer transcripts.