C4UChat4U Docs
Knowledge

Manage capacity and indexed words

Understand knowledge capacity, ingestion limits, and the review required after a capacity reduction.

2 min read

Where to do this in Chat4U
  1. Project
  2. Billing
  3. Knowledge storage

Use the project Billing page to review the indexed-word allowance and current knowledge storage before importing more material.

Look forBillingKnowledge storageUsage
Open Chat4U
What you’ll accomplish

Use indexed words—not visual document length—to decide which approved material remains retrievable.

Finish with
A defensible capacity decision when your allowance changes

Chat4U measures stored capacity in indexed words: normalized indexed text divided by five characters per word. It is not the visible word count of an original document or page.

Capacity is enforced at source admission and indexing. The project may also have a daily ingestion-run limit and a rolling indexing budget. When either limit is exhausted, a new or recurring run can be deferred or rejected even if the source itself is valid.

When capacity is reduced

If the project’s new capacity is below its existing indexed use, Chat4U opens a capacity review instead of immediately deleting indexed content. Ingestion is paused while the review requires a selection.

The review presents atomic file and text sources, and page-level scopes for URL sources. It includes each scope’s indexed words and most recent indexing or retrieval time where available. Select the content to retain within the current capacity, then apply the selection. The resulting decision records retained and archived scopes.

The initial selection period is 30 days. If content is archived after an applied or expired review, it is removed from indexed availability; this changes what agents can retrieve. When capacity is restored, archived sources are returned to pending so they can be indexed again. URL sources resume through their existing schedule; file and text sources need their normal ingestion dispatch to complete.

Practical operating rules

  • Treat a capacity warning as a prioritization task, not a signal to add more sources.
  • Retain the most authoritative and frequently useful content first; use the review’s usage information as one input, not the only one.
  • Before applying a selection, check that it covers essential policies, pricing, safety, and escalation information.
  • After archival or restoration, test the affected agents again.

Last updated on