Practical operating guide
What an AI call summary should send to your CRM
By ByTomorrow · Published
The call summary says the conversation went well. The employee opening it still cannot tell what the caller needs or what the receptionist promised.
A polished paragraph can hide an unanswered question, a failed booking or an assumption the caller never confirmed.
Diagnosis
A summary is not an action receipt
Inferences look like facts
A summary may interpret a caller's words. Store what the caller stated separately from a reviewer's classification, and keep unknown details unknown.
The analysis arrives later
Retell documents that post-call extraction happens after the call ends. The call_analyzed event contains analysis; call_ended does not. Custom fields may be absent when no conversation occurred. A missing field should not become a negative answer.
Working worksheet
A sample CRM record for a service inquiry
Caller statements
Illustrative record: caller asked whether an evening consultation is available; prefers email; has not chosen a date. Store these as statements from the call, not as a confirmed appointment or a promise of availability.
Information still needed
Record: requested service is unclear; exact availability is unknown; email address needs confirmation. Each missing item should become a specific question for the next responder, rather than a guessed default.
Actions actually completed
Record: appointment identifier absent; quote not issued; follow-up task identifier absent until the CRM write succeeds. Replace those entries only with the relevant system receipt. A conversational success label does not provide that evidence.
Commitments made to the caller
Record the actual promise and who made it. If the agent said a person would review the request, do not rewrite that as a guaranteed callback time. A promise that exceeds the approved script needs review.
Ownership and provenance
Record the call identifier, call time, summary generation time, linked inquiry, assigned owner and review status. Link to the authorized source record where useful. Keep recordings and transcripts within the access rules that apply to the business.
Use the worksheet
Put it into practice
Define the fields before the summary
Choose fields that change what a responder does: request, unanswered question, completed action, promise and owner. Treat free text as supporting context.
Check the summary against a synthetic call
Make a test call with a deliberate unknown and an uncompleted request. Verify the summary preserves both, rather than inventing a positive outcome.
Confirm the CRM write
Read back the actual customer relationship management record, or CRM record, and its linked task. Check that a repeated delivery of the same call analysis does not create duplicate tasks.
Questions
Straight answers.
It can record the model's classification under defined criteria. Keep that classification separate from verified bookings, accepted handoffs and completed work.
No. Send the minimum context the responder needs and link to the authorized record. A broad notification channel may not be an appropriate place for the full conversation.
Sources and further reading
- Retell post-call extraction overview
Supports analysis timing, call_analyzed versus call_ended, missing custom fields for calls without conversation and configurable success classification.
Checked .
Define what the next person needs
A sample call and the next employee's task are enough to begin a useful field-mapping discussion.
Discuss your workflow