Skip to main content

​
How summaries work

  1. A call is ingested from your connected recording platform or uploaded directly
  2. The call is automatically classified into a type (discovery, demo, QBR, etc.)
  3. The summary template matched to that call type is applied
  4. AI processes the transcript alongside any available CRM context
  5. A structured summary is generated and available to your team, agents, and workflows
This happens automatically for every call — no manual trigger required.

​
Structured by call type

This is the key: every call type has its own summary template. A discovery call summary surfaces different context than a demo summary or a QBR summary. Because every call of the same type follows the same structure, you can compare consistently across reps, accounts, and time periods. That’s what makes the context useful at scale — for your team, your workflows, and your AI agents. For example: See Call Classification for the full list of call types and what each template covers.

​
Access this context anywhere

Summaries are available in the app, through the API, and to AI agents via the MCP server.

In the app

Browse, filter, and search summaries from the posts feed.

Via the API

Search and retrieve summaries programmatically. Pipe them into Zapier, n8n, or your own tools.

Via MCP

Ask Claude to find summaries — “Show me summaries from Jane’s discovery calls this week.”

​
Frequently asked questions

What does a summary include? Every summary starts with a BLUF (Bottom Line Up Front) — a one-sentence overview of what matters most. Below that, structured sections are tailored to the call type. Discovery summaries include pain themes, value hooks, and GTM-ready slices like messaging hooks, competitive landscape, and voice-of-customer quotes. Demo summaries capture feature reactions, objections, and demo moments. Renewal summaries surface renewal signals, churn risks, and decision dynamics. See example summaries for the full output. Are summaries generated automatically? Yes. Every call that flows into OnePerfectSlice — whether from Gong, Fireflies, Fathom, or uploaded directly — is automatically classified by type and summarized using the matched template. No manual trigger required. Why do different call types get different summaries? A discovery call surfaces different context than a demo or a renewal. By tailoring the template to the call type, each summary extracts the context that actually matters for that type of conversation. This also makes summaries comparable — every discovery summary follows the same structure, so you can compare across reps, accounts, and time periods. Can I create custom summary templates? Yes. Teams can create custom call types with their own summary templates tailored to specific workflows. See Call Types for details. How do I access summaries programmatically? Summaries are available through the REST API and the MCP server. You can filter by call type, date range, rep, company, and CRM fields.