The Chunks page shows you the individual text units, called chunks, that your agent actually retrieves when answering questions. Chunks are extracted automatically when a document, website, or video is processed. You can also create them by hand for a short fact that is missing from your sources.

Navigate to Knowledge → Chunks in the left sidebar. The CMS lists this page under Knowledge; in these docs it belongs to the Fine-Tune Answer Quality stage, because it is mainly a tool for finding out why an answer is wrong or missing.

In this tutorial you inspect the chunks of SOP-FIN-007, Kirana Group's approval policy, and then fill a gap. People ask Atlas who to call when they cannot log in to the Procurement Portal, and the SOP does not say. You add a manual chunk with the help desk number, activate it, and check that Atlas answers with it.


Before you start

  • Add at least one source in Documents, Websites, or Videos, and wait until it has finished processing. Automatic chunks appear only after processing. To follow along, upload SOP-FIN-007 as described in Documents.
  • Keep Enable reference on in Retrieval. Atlas also keeps Restrict answer on, so it answers only from its chunks.
  • Have a question in mind that the agent answers badly. Searching for its key words here is the fastest way to start.

What are chunks?

When a document, video transcript, or web page is processed, it is split into smaller sections of text. Each section becomes a chunk. When a user asks a question, the agent searches across all active chunks and retrieves the most relevant ones to build its answer.

The Chunks page is the most direct way to see what knowledge your agent has, and to find out why it is not finding something.

Source badgeWhere the chunk comes from
Chunking resultCreated automatically when a document, video, or website is processed.
User entryCreated by hand on this page with Add chunk.

Each chunk also has a state badge. Only Active chunks are used in answers. Inactive chunks are ignored.


Step 1: Search the chunks

  1. Go to Knowledge → Chunks.
  2. In Search chunk text, type approval. The list updates as you type.

The table shows the matching chunks. For SOP-FIN-007 you see two chunks, both Active and Chunking result. Each row shows the chunk title, the document it belongs to (Project and Capex Approval Policy), its section, the token count in Tokens, the source, and the status.

Chunks page with the Search chunk text box set to approval, the Filters and Add chunk buttons, the Clear all link, and a table of two results from Project and Capex Approval Policy, both badged Chunking result: one titled 5 (Section 1, 123 tokens) and one titled KIRANA GROUP SOP-FIN-007 (Section 1, 466 tokens), with the line Showing 2 chunks

Read the results the way the agent would. Here the first chunk has the title 5, because the splitter took the section number of "5. TIMELINES" as its title. The text is still correct, so Atlas can use it. If a chunk's text were wrong or cut off, you would fix it here (see Edit, deactivate, or delete a chunk).

Searching and filtering

ControlWhat it does
Search chunk textMatches text inside the chunk body. The list updates as you type.
FiltersOpens a panel with Document, Chunk code, Section, Status (Active or Inactive), and Source (User entry or Chunking result). The same panel sorts the list by Status, Source, or Section.
Clear allClears every filter and shows the full list.

Step 2: Ask the question the SOP does not cover

In the preview panel on the right, click the reload button to start a fresh conversation, and ask:

I can't log in to the Procurement Portal. Who do I call?

SOP-FIN-007 says that form KG-F12 is submitted in the Procurement Portal, but it does not name a help desk. With Restrict answer on, Atlas should not guess a phone number. Expect it to say that it cannot find the contact in Kirana's SOPs.


Step 3: Add a manual chunk

  1. Click Add chunk. A side sheet opens over the list.

  2. Fill in the fields:

    FieldValue for Atlas
    Document (required)SOP-FIN-007 - Project and Capex Approval Policy
    Title (required)Procurement Portal help desk
    Section (required)Contacts
    Text (required)The Procurement Portal (where form KG-F12 is submitted) is at portal.kirana.example. For login problems, call the Procurement help desk on extension 4410, Monday to Friday 08:00 to 17:00 Jakarta time.

    Document links the chunk to an existing document, so citations show that document as the source and Section as the location. Keep the text short and self-contained: one fact per chunk.

  3. Click Save. The sheet closes and Chunk saved. appears above the list.

The Add chunk side sheet with Document SOP-FIN-007 - Project and Capex Approval Policy, Title Procurement Portal help desk, Section Contacts, and Text saying the Procurement Portal is at portal.kirana.example and that for login problems you call the Procurement help desk on extension 4410, Monday to Friday 08:00 to 17:00 Jakarta time

Step 4: Activate the chunk

A manual chunk is saved as Inactive. It appears in the list with the status Inactive and the source User entry, and the agent cannot use it yet. You have to open it and click Activate.

  1. Search for Procurement Portal and open the new chunk. The Chunk detail page shows the text, title, and section, with Status: Inactive and Tokens: 0. While the chunk is inactive, the top bar offers Activate and Delete, and you can still change the fields and click Save.
  2. Click Activate and confirm the dialog. Chunk activated. appears.
Chunk detail page of the new chunk with Delete and Activate at the top, the Details section with Document Project and Capex Approval Policy, Status Inactive, Source User entry and Tokens 0, and the Chunk section with Title Procurement Portal help desk, Section Contacts and the help desk text

The status changes to Active and the chunk is indexed. From now on the agent can retrieve it, in the Preview and on your live agent. Chunks do not need to be published.


Step 5: Ask again

In the preview panel, click the reload button to start a fresh conversation, and ask the same question:

I can't log in to the Procurement Portal. Who do I call?

Atlas now answers from your chunk: call the Procurement help desk at extension 4410, available Monday to Friday, 08:00 to 17:00 Jakarta time. The citation under the answer reads Kirana Group Finance, Project and Capex Approval Policy, Contacts: the author and the document you linked, and the Section you typed.

Atlas preview: to the question I can't log in to the Procurement Portal. Who do I call? Atlas replies Call the Procurement help desk at extension 4410. They're available Monday–Friday, 08:00–17:00 Jakarta time, with the citation Kirana Group Finance, Project and Capex Approval Policy, Contacts

Edit, deactivate, or delete a chunk

Open any chunk from the list to see its detail page. What you can do depends on its state:

StatusButtonsWhat they do
ActiveEdit, DeactivateEdit unlocks the fields; when you save, the chunk is updated and stays active. Deactivate stops the agent from using the chunk without deleting it.
InactiveActivate, DeleteThe fields are editable; click Save to keep changes. Activate makes the chunk available to the agent. Delete removes it.

Use Deactivate for an automatic chunk that misleads the agent, for example an outdated paragraph, instead of deleting the whole document. If the source itself is wrong, fix the document and reprocess it in Documents.

Manual chunks are useful for:

  • Adding short facts that are not in any document, like the help desk number above
  • Supplementing or correcting an automatic chunk without reprocessing a full document
  • Testing a specific answer before you update the source document

Check the result

  1. Search for Procurement Portal. The new chunk shows the status Active and the source User entry. If it still shows Inactive, open it and click Activate.
  2. In the preview panel, click the reload button and ask "I can't log in to the Procurement Portal. Who do I call?". Atlas should name extension 4410 and cite Contacts.
  3. Ask "Who has to approve a project worth $2.5 million?" to make sure the SOP answers have not changed.

If Atlas still cannot answer, check that Enable reference is on in Retrieval and that you asked in a fresh conversation.


Next steps

You have reached the end of the Configuring Your Agent journey.

  • Overview: look back at the full journey and pick the next thing to improve.
  • Simulation: check answer quality across many questions at once.
  • Retrieval: configure how many chunks the agent retrieves per query and how tolerant the search is.
  • Citations: how the author and section appear under each answer.