My App
AI Support

Lexul AI Support Knowledge Base

Optimized Fumadocs structure for a Lexul customer support AI agent.

Audience: Lexul customer support AI agent, onboarding team, support team, and documentation maintainers.
Use: Host this folder in Fumadocs. Configure the AI agent to retrieve only the needed group page or individual ### Knowledge Record: chunks.

What changed

This package splits the previous single chatbot training page into standalone feature-group routes. This improves retrieval efficiency because the AI agent can load only the relevant feature group instead of reading the full knowledge base.

  1. Classify the user's request into one or more intents from Schema and Routing.
  2. Match the request to a feature group page.
  3. Retrieve the top one to five ### Knowledge Record: chunks from that page.
  4. Answer using Agent Instructions and the retrieved records.
  5. Escalate when the record's escalation_rule applies or when retrieved records do not confirm the requested behavior.

Page map

PagePurpose
Agent InstructionsShort system-style behavior profile for the support bot.
Schema and Routing20-field documentation schema, intent labels, record format, and chunking rules.
Feature GroupsIndex of feature-group knowledge pages.
Source IndexLexul.com and help.lexul.com URLs used by the training records.
Ingestion and EvaluationMetadata recommendations and chatbot evaluation checklist.

Feature group retrieval sizes

Use this table to decide how much context to retrieve. Token counts are approximate and assume roughly four characters per token.

Feature groupRecordsApprox. page tokens
Customers10~7,118
Assets7~5,005
Sales4~2,968
Deals2~1,145
Contracts6~4,072
Inventory6~5,177
Equipment2~1,462
Inspections3~1,909
Receipts2~1,385
Timesheets3~2,173
Users2~1,416
Time Tracking5~3,337

Packaging notes

  • Generated: 2026-06-23
  • Content format: Fumadocs-compatible MDX
  • Chunking target: one ### Knowledge Record: per vector record
  • Best production use: retrieve by feature group first, then by record-level semantic similarity

On this page