Choose the right timing
- During a conversation: a note or email tool can use information already collected. It cannot summarize the remaining conversation.
- After the call: a post-call receiver can use the call’s
call_summary,full_transcript, and configuredextractionswhen those fields are available.
Build the post-call workflow
- Configure a receiver using Call webhooks.
- Capture a real completed test call and identify its
call_id,location_id, andcontact_id. - Require a nonempty
call_summarybefore creating a summary message. Handle missing analysis by queuing a review or skipping the message, rather than sending a blank or old contact-field value. - Resolve the recipient explicitly. A customer email, internal team address, and phone number are different destinations; select the intended one before sending.
- If you store the summary in a contact field, wait for that write to succeed before triggering a message that reads the field.
- Record the call ID with the sent message so a repeated event does not produce duplicate notifications.
Verify it works
Complete a call with a distinctive test detail. Confirm the correct summary is stored on the correct contact, then check the recipient’s inbox or phone for that detail. Inspect the provider’s delivery result if the message is missing. An accepted send request is not confirmation of receipt. Also test a call without a transcript or summary, a missing recipient, and a repeated event.Troubleshooting
- Previous call’s summary was sent: trigger from the new completed-call data and associate it with
call_id. - Empty message: check that the workflow waited for a nonempty summary.
- Wrong recipient: inspect the mapped contact and destination before enabling automatic sending.