Question

You are building a RAG system over a corpus of customer support tickets. The tickets vary widely in length: many are short one-paragraph questions, but some are long multi-issue threads spanning several distinct problems. Users query for solutions to specific individual problems. You want each retrieved chunk to represent a coherent, self-contained unit so that retrieval returns focused answers without mixing unrelated issues. Which chunking approach best fits this requirement?

Accepted Answer

Use semantic (content-aware) chunking that splits threads at topic boundaries so each chunk captures one distinct issue

Answer

Apply a fixed-size token window (e.g., 512 tokens) uniformly across all tickets regardless of structure

Answer

Store each entire ticket as a single chunk regardless of length to preserve full context

Answer

Split every ticket into single-sentence chunks to maximize retrieval granularity