Skip to content

Turn support gaps into better articles

Use Quality to find missing or outdated knowledge. Suggestions still need an Editor's judgment.

Find gaps

Open Quality > Knowledge gaps to inspect recurring unanswered questions from customer messages shared with the team. Cluster gaps with AI can group related questions. Review the retained evidence before choosing a topic.

Private Sidekick history and unshared customer content are not a general source for these reports. A report may cover a bounded sample. Read the scan count before treating it as the whole support workload.

Create a proposal

  1. Choose Article proposals.
  2. Choose Ticket, Translation or Maintenance as appropriate.
  3. Enter the permitted source article or resolved ticket. Select ticket message IDs when required.
  4. Enter a specific instruction and generate the proposal.
  5. Check every product fact. Remove personal and customer-specific information.
  6. Give it a title and save the reviewed proposal as a private AI-excluded draft.
  7. Complete the normal access, review and publication steps before AI use.

Maintain existing knowledge

Maintenance and Find conflicts with AI can identify review dates, possible duplicates, contradictions and stale variants. Choose the authoritative advice with the product owner. Do not publish both conflicting instructions simply because they were generated successfully.

Check the result

The adopted article exists as a draft. It is not automatically published or enabled for AI. Source restrictions and source changes can still block a proposal derived from that content.