Short answer: Count tokens first, chunk long documents below the model limit, summarize each chunk, and reduce the results into one validated CRM action set.
A long sales-call transcript should cross the model boundary in four explicit stages: count tokens, split below the context limit, summarize chunks, then reduce those summaries into validated CRM actions. Keep a small sliding overlap when a decision crosses a chunk boundary. The important handoff is clear: transcription and storage produce text; the summarization runtime consumes bounded text and returns structured actions.
Boundaries matter.
In a CRM call, the dangerous sentence is rarely the first one in a chunk. A prospect may reject a renewal on page 18, name a replacement stakeholder on page 19, and agree to a date on page 20; a naive character split can separate the decision from the evidence that makes it actionable.…