Call summaries give your team a concise account of the caller’s request and the actions taken during the interaction.

A summary may include #

• Caller name and callback details.
• Reason for calling and relevant intake answers.
• Urgency or service category based on approved rules.
• Whether a transfer was attempted, a message captured, or a booking completed.
• The next step defined by your workflow.

Summary versus transcript #

A summary condenses the conversation. A transcript is a text record of the interaction, and a recording is the audio. These are different outputs and may have different access and retention settings.

Delivery #

Business plans include email summaries to up to three approved recipients. CRM delivery, team chat, or other automation destinations must be included or separately scoped. We confirm restaurant notification destinations during implementation.

Review important details #

Summaries can contain recognition errors. Your team should verify important details before acting, particularly prices, addresses, appointments, or other commitments.