Chunks

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.

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 and click Apply.

The list shows the matching chunks. For SOP-FIN-007 you see two chunks, both Active and Chunking Result. Each card shows the chunk title, the start of its text, the document it belongs to (Project and Capex Approval Policy), and its section with a token count, for example Section 1 (466 tokens).

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

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 New Chunk in the top-left. The Add New Chunk page opens.

2. Fill in the fields:

   Field	Value for Atlas
   Document (required)	SOP-FIN-007 - Project and Capex Approval Policy
   Chunk 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, confirm Are you sure to save your changes?, and close the success message. You return to the list.

Step 4: Activate the chunk

A manual chunk is saved as Inactive. It appears in the list with the badges Inactive and 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 State: Inactive and Text Token: 0. While the chunk is inactive, the top bar offers Activate and Delete Chunk, and you can still change the fields and click Save.
2. Click Activate and confirm Are you sure to activate this chunk?.

The state 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.

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:

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 Active and 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.
• Test Automation: 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.