Fix common Support AI problems
Start with the organization, current state and visible error. Avoid changing several settings at once.
The module is missing from the menu
Check the user's personal Editor assignment, base seat, active membership and organization coverage. Role navigation cannot override a missing licensed capability. Freshdesk also requires Admin status.
Sherpa will not activate
Check for published knowledge, verified website origins and an accepted representative quality run. Save the bot draft before publishing. A stale version needs a reload. Read the actual blocker rather than disabling review or access controls.
Sherpa does not use my article
Check the published revision, audience, Customer AI flag, all-AI exclusion, preparation state and source filters. Imported source-policy holds can block an otherwise published article. Test a question the article actually answers.
The website widget does not appear
Check the snippet, exact website origin, DNS verification, published bot version, public master switch and widget switch. Check website content-security rules. The hosted Help Center has a separate switch.
No human joins
Check office hours, holidays, timezone, the default queue, current eligible processor availability and capacity. Waiting is not acceptance. After timeout, use ticket follow-up, continued waiting or cancel as offered.
An import has issues
Read the affected items. Check mappings, owner access, source permissions, customer matches, storage and schema changes. A partial run can already have created records. Resolve exceptions before repeating work.
A save says the version changed
Reload and review the newer values. Do not overwrite another person's work blindly. Retention previews and import approvals also expire or become stale.
AI usage is unavailable
Check the organization's token and runtime capacity and any provider pause. Use permitted knowledge reading or manual support while the cause is addressed. Creating a metadata edit does not restore AI capacity.
If the problem remains, record the screen, time, error code and relevant article or job ID. Use a fictional example when possible. Do not include API keys, signing secrets or unnecessary customer data.