SUMMARIZATION
Agent-Built Objection Battlecards from Closed-Lost Calls
On a monthly schedule, an agent reviews transcripts and notes from recently closed-lost Salesforce deals.
How it runs
The automated pipeline, trigger to output.
- TriggerMonthly battlecard review schedule
- ActionGather closed-lost deal transcriptsSalesforce
- ActionSynthesize battlecard drafts with OpenAIOpenAI
- LogicReconcile drafts against existing playbook
- OutputPublish updated playbook to NotionNotion
What it does
Mines your lost deals each month for the objections that actually killed them and turns them into living battlecards in a Notion playbook your reps can pull up mid-call.
When to use it
Use this when you want to learn systematically from losses and keep a curated objection-handling playbook current instead of letting hard-won knowledge die in call notes.
How it works
- 1A monthly schedule starts the review cycle.
- 2The agent queries Salesforce for deals marked closed-lost in the period and gathers their call transcripts and notes.
- 3OpenAI synthesizes the recurring loss-driving objections, the strongest counters that worked elsewhere, and proof points into battlecard drafts.
- 4The agent reconciles drafts against the existing Notion playbook, updating cards that exist and adding new ones.
- 5The refreshed objection battlecard playbook is published to Notion with a changelog of what changed this month.
Set it up
What you configure once, before turning it on.
- 1Connect SalesforceAccounts, opportunities, cases.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect NotionPages, databases, comments.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Summarization workflows
On-submit Loom standup roll-up archived to Confluence
When a standup video is submitted via webhook, transcribes it, generates a per-person written summary, and appends it to a running team standup page in Confluence.
Front Escalation Handoff Doc in Notion
When a Front escalation closes, drafts a structured handoff document in Notion capturing the resolution, customer commitments, and open follow-ups, then alerts the AE in Slack.
Front Escalation War-Room Brief to Slack
On a Front escalation, posts a concise threat-assessment brief to a Slack channel only when the AI judges the situation high-severity.
VIP Front Escalation Instant Exec Page-Out
Detects escalations from VIP accounts in Front, generates a one-paragraph executive recap, and pages the named account exec via Slack and Salesforce task within minutes.
Release health note per Vercel deploy
When a Vercel deploy goes live, summarizes the Sentry errors observed in the release window into a plain-English health note that separates brand-new error classes…
Rollback recommendation when a deploy spikes errors
When a Sentry alert fires for an error spike, attributes it to the most recent deploy, summarizes whether the spike is dominated by new error classes introduced by that release.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.