A call summary can change what a business believes happened. A customer says a delivery has not arrived; the summary says the courier failed. A consultant offers to investigate a refund; the customer record says the refund was approved. Neither change needs to be dramatic to send the next colleague in the wrong direction.
Design the summary as an evidence-labelled working record. It should show what participants said, which statements have been checked elsewhere, and what remains an interpretation. Readability matters, but a shorter account is only useful when it preserves the distinctions that determine the next action.
Treat reported information as reported information
The first distinction is between a fact about the conversation and a fact about the world. If the caller says an invoice was paid, the conversation supports "caller reports payment". It does not establish that the payment cleared or was allocated to the correct account.
Use separate fields for reported circumstances, independently checked information, proposed actions and unresolved questions. Label any interpretation explicitly. A suggestion that the caller may need a billing specialist belongs under a proposed next step, not under confirmed facts.
Record the basis for a checked statement. A payment status retrieved from the finance system should include its lookup time and record reference. Keep that separate from the caller's account, especially when the two conflict. The summary should preserve a disagreement for resolution rather than choose whichever version sounds more plausible.
Make evidence easy to inspect
Attach a transcript passage or recording timestamp to consequential statements. Prioritise amounts, dates, cancellation requests, commitments and changes to contact details. Reviewers should be able to inspect the relevant passage with enough surrounding conversation to understand qualifications.
Do not let a timestamp imply certainty about the words or speaker. Give the reviewer an explicit way to mark unclear audio, uncertain attribution or incomplete capture. Where only a transcript is available, state that limitation. A reviewer cannot resolve an audio dispute by repeatedly reading the same transcription.
Keep quotation and paraphrase distinct. Quotation marks should indicate words checked against the available source, not an elegant reconstruction. If the workflow cleans up grammar, removes repetitions or translates a statement, present the result as a paraphrase and preserve access to the original wording for authorised reviewers.
Preserve the strength of commitments
Consider this hypothetical call to a Johannesburg equipment supplier. A customer asks whether a replacement can arrive on Thursday. The adviser replies, "I can ask dispatch; Thursday might work if the stock check is clear." Later, the customer asks for an update by Wednesday afternoon.
A useful summary records the requested Thursday delivery, the unresolved stock check and the requested Wednesday update. It does not announce a confirmed delivery date. If the adviser explicitly accepts the update deadline, that becomes a commitment; otherwise it remains a request awaiting ownership.
Use a small commitment checklist during extraction: who offered the action, whether they accepted responsibility, what conditions apply, and whether a deadline was agreed. If any part is missing, preserve the gap. Do not fill the owner from a team directory merely because someone usually handles that type of work.
This hypothetical example also needs separate records for the customer's preference and the supplier's promise. Combining them into one "next delivery" field would erase the most important uncertainty.
Keep interpretations out of automatic account changes
Decide which summary fields are descriptive and which can trigger work. An observed request for a callback may create a review item. An inferred intention to cancel should not close an account or change its status.
Avoid turning tone into a personality judgement. For example, in a hypothetical billing dispute, "caller repeated the request for a written explanation" is inspectable. "Caller is unreasonable" is an assessment that adds little operational value. If prioritisation needs an urgency reason, capture the stated deadline or operational interruption instead.
Require a separate authorised step before changing account data, issuing a credit or sending a promise to a customer. The summary can prepare the evidence, but the surrounding integration workflow should make the proposed change visible before it reaches the business system.
Design recording and access decisions first
Before enabling capture, have the organisation's responsible teams determine which calls may be recorded, how participants are informed, what alternatives exist and how long each artefact should be kept. Do not treat the arrival of a summarisation tool as permission to record every conversation.
Define access separately for recordings, transcripts and summaries. A support colleague may need a short operational recap without needing unrelated personal details discussed during the call. A quality reviewer may need the source evidence, but that does not make it appropriate to circulate the whole recording with every escalation.
Provide a correction route when someone disputes the record. Preserve the original and corrected versions according to the approved retention approach, identify who made the correction, and make superseded summaries visibly outdated. These are workflow design choices to review with the responsible privacy and records teams, not a guarantee of legal compliance.
Review by consequence, not by writing quality
Give reviewers a focused comparison: proposed statement, supporting passage, uncertainty label and any downstream action. Ask them to check meaning before improving wording. A polished sentence about the wrong customer or amount should never pass because the overall recap reads well.
Route ambiguous commitments and conflicting evidence to someone who can resolve them. When clarification requires another call, create a clarification task rather than ask the model to select a likely answer. Specify who owns that task and what happens if the customer cannot be reached.
Keep review statuses meaningful. "Draft", "source checked" and "approved for account update" describe different stages. Do not use one green tick to represent all three. A supervisor approving the wording of a summary should not accidentally authorise every action mentioned inside it.
Test the distinctions before expanding capture
Build a small set of authorised or synthetic calls with deliberate traps: a corrected amount, a request declined later, an interruption during a deadline, an unnamed speaker and a conversation that ends before agreement. Include the language switching and terminology your team expects to encounter, and have suitable reviewers check the meaning.
Score unsupported statements, lost conditions, wrong attribution and unconfirmed commitments separately. Review omissions too: leaving out a dependency can be as misleading as adding a promise. Include cases where the correct result is an incomplete summary requiring follow-up.
Start with one call type whose next steps are well understood. Track the time needed to reach an accepted record, the corrections reviewers make and any mistaken downstream changes. Use those findings to revise the fields and review rules before increasing volume.
The release decision should answer a practical question: can the next colleague distinguish evidence from interpretation without replaying the whole call? If not, improve the record structure before making the prose more concise.