SUMMARIZATION
Closed-Lost Deal → Objection Post-Mortem Agent with Battlecard Update
When a Salesforce Opportunity flips to Closed Lost, an agent reviews the deal's call recordings, diagnoses which unhandled objections lost the deal.
How it runs
The automated pipeline, trigger to output.
- TriggerOpportunity moves to Closed LostSalesforce
- ActionCollect linked call transcriptsZoom
- ActionDiagnose unhandled objections + loss driver
- LogicExisting battlecard covers it?
- ActionDraft/revise battlecard in ConfluenceConfluence
- OutputSend rep a Slack post-mortem summarySlack
What it does
Runs a focused post-mortem the moment a deal is lost. An agent gathers the recordings tied to that Opportunity, condenses them into the objections that went unresolved, decides which one most likely killed the deal, and proposes a concrete battlecard improvement so the loss teaches the whole team.
When to use it
Use this for closed-lost analysis where you want more than a transcript summary — you want a reasoned diagnosis and an actionable enablement artifact. Best when objection battlecards live in a Confluence space the team maintains.
How it works
- 1**Trigger** — a Salesforce Opportunity changes stage to Closed Lost.
- 2**Action** — collect the call recordings/transcripts linked to the Opportunity.
- 3**Action** — the agent diagnoses unhandled objections and ranks the likely loss driver.
- 4**Logic** — branch on whether an existing battlecard already covers that objection.
- 5**Action** — draft a new or revised battlecard in Confluence.
- 6**Output** — send the rep a Slack post-mortem summary with the proposed battlecard link.
Set it up
What you configure once, before turning it on.
- 1Connect SalesforceAccounts, opportunities, cases.
- 2Connect ZoomMeetings, recordings, transcripts.
- 3Connect ConfluenceSpaces, pages, blueprints.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.