A long automated conversation can leave a human agent searching for the few facts needed to continue. A structured summary prevents that burden by combining a short text summary with selected metadata in predefined fields. section 12.1.2
Think of it as a compact handoff record, not a transcript. Fields may contain collected identifiers, supplied context, session counts, or sentiment, but inclusion depends on the use case and the receiving agent’s needs. section 12.1.2
Medical claim handoff
A caller provides a provider tax ID, member ID, date of birth, name confirmation, and service date. The assistant finds claim #111222333, then transfers the caller. The agent-facing summary can highlight the verified member ID, provider ID, and claim ID, while backend integration supplies additional claim details. section 12.1.2
Design a useful structured summary by:
- Selecting only information the next participant needs; not every closed-form answer belongs in the summary. section 12.1.2
- Storing important context variables during the conversation so they can be retrieved when the summary is created. section 12.2.3
- Displaying the result in agent software as a screen pop, with links or integrations for deeper records. section 12.1.2
- Minimizing sensitive data collection, retention, and storage, then reviewing those choices with legal specialists. section 12.2.3
