Next 6-week cycle v2 · briefs that know which call this is
Automated Call Brief
From a document that grows longer every call — to a game plan built from what the prospect actually said.
GOAL 1
Know the call
Every brief is generated for a specific call — Call 1, Call N, or Welcome — with a stated objective and a net-new Slack canvas, not an appended one.
GOAL 2
Learn from the last call
Agentforce reads the Vinton transcript of the prior conversation and surfaces what the prospect values, what's unresolved, and what we committed to.
GOAL 3
Learn from every call
Across all transcripts, discover which conversations lead to a close and which don't — and recommend the plays that work, call by call.
Three goals, six weeks, one implementation partner. Click through to see how they fit together. →
Where We Are
V1 already moved the brief from a Word doc to a living canvas.
Before: Conga generated a Word doc from Salesforce data, research coordinators and MDAs polished it by hand, and the finished brief lived in email and shared drives — never back in Salesforce. V1 replaced that chain with Agentforce and Slack.
Before · Conga era
☁️
Salesforce data
Account, contact, opportunity
➜
📄
Conga template
Merged into a Word document
➜
🧑💻
RC + MDA polish
Research, augment, reformat by hand
➜
📎
Word doc shared
Emailed and filed — never returns to Salesforce
Today · V1 (built with Kicksaw)
🤖
Agentforce
Generates the Call 1 brief and does the RC/MDA research itself
➜
🟪
Slack canvas
Brief lands in Slack; a Slack skill transforms it into shape
➜
🧑💼
MDA deems it ready
Reviews, then shares with the sales director
➜
💬
Interrogate in Slack
Slackbot answers follow-ups against the brief
V1 solved production: the Call 1 brief writes itself. What it didn't solve is what happens on Call 2, Call 3, and beyond.
The Problem
Today's Call 2 brief is the Call 1 brief — with more stapled on.
The MD reuses the same document and appends what happened last time: the price quoted, concerns raised, members the prospect knows, current challenges. The brief gets longer with every call — which is the opposite of what a sales director walking into a close wants.
"They want the brief to look at what works and what doesn't — and get them to a close on this call, or at worst the next one."
Longer isn't sharper. Every appended section buries the one thing that matters for this call under everything that mattered for the last one.
The Vinton transcript already holds what was said — the brief should be derived from it, not manually re-typed on top of the old one.
Goal 1 · Know the Call
Every call has a purpose — and it is almost always the close.
The prospect journey is simple: Call 1, then follow-up calls until there's a close, then a Welcome Call that hands the new member from sales to memberships. A v2 brief starts by knowing which of these it's for.
1
Call 1
First conversation. Establish fit, learn what they care about, earn the next step.
Goal: close · earn Call 2
N
Call N
Follow-ups. Move what's unresolved, answer the objection, bring the right proof.
Goal: close
✓
Close
The prospect becomes a member.
Won
👋
Welcome Call
Sales hands off to memberships. Onboarding — not selling.
Goal: onboard
What changes when the brief knows the call
Call 1 leads with fit and discovery. Call N leads with what moved last time and what's still in the way. The Welcome Call leads with the member's stated priorities so memberships picks up exactly where sales left off — no re-discovery.
Call type comes from the opportunity's call history in Salesforce and the Vinton recording sequence — Agentforce infers it; the MDA can override.
Goal 2 · Learn From the Last Call
The transcript is the input. Agentforce reads it so no one has to re-type it.
Vinton records every sales conversation inside Salesforce, so Agentforce has the transcript natively. Before Call N, it reads the prior call(s) and pulls out the signals that should shape the next conversation.
Vinton transcript · Call 1 · illustrative
Prospect: Honestly, the thing I'm wrestling with is how to scale our transformation office without doubling headcount.
Sales Director: A couple of members are living that exact problem right now.
Prospect: I know Priya at Abbott — we were on a panel together. Is she in the group?
Sales Director: She is. Let me come back to you on how to make that connection.
Prospect: And the number you mentioned is a bit higher than I budgeted — I'd need to take that to my CFO.
Sales Director: Understood. I'll send over the peer roster and we can regroup in two weeks.
🎯
What they actually care about
Scaling the transformation office without adding headcount — the brief leads with this, not with company boilerplate.
🤝
Members they know
Priya at Abbott — social proof already in hand; the brief suggests the intro.
⚠️
Open concern
Price vs. budget; CFO is now in the loop. The brief frames the value conversation accordingly.
📌
What we committed to
Peer roster + regroup in two weeks. Was it sent? The brief checks and says so.
The prospect already told us what a good Call 2 looks like. V2 makes the brief a by-product of what was said — instead of a document someone has to remember to update.
Goal 1 + 2 · A Net-New Canvas Per Call
Not the same brief, longer — a new brief, sharper.
Same Slack workflow as V1: Agentforce drafts, the Slack skill shapes it, the MDA deems it ready, the sales director gets it. What changes is the canvas itself — built for this call, from the last one.
Call 2 brief · today
v1 · appendedCompany snapshotRevenue, HQ, segment, news — unchanged since Call 1
Executive bioTitle, tenure, background — unchanged since Call 1
World 50 fit & peersGroups and member peers — unchanged since Call 1
Suggested talking pointsGeneric Call 1 openers — no longer relevant
Notes from Call 1 (added by MD)Price quoted · concerns · knows Priya at Abbott · challenges…
…and by Call 3, another section is stapled on.
Call 2 brief · v2
net-new canvas🎯 This call: Call 2 · Objective: closeMove the CFO budget concern; convert the Priya intro into momentum.
What moved last timeProspect's real problem: scale transformation office without headcount.
What's still in the wayPrice vs. budget — CFO involved. Roster sent ✓ · regroup on schedule ✓
✅ Recommended plays (from what works)Lead with a peer story on headcount leverage; offer the Priya intro before price comes up.
The askAgreement to bring the CFO to a 20-min value call — or close today.
Snapshot and bio available on request via Slackbot — not repeated.
The sales director reads one screen: why this call, what happened, what's open, what to try, what to ask for. Everything else stays one Slackbot question away.
Goal 3 · Learn From Every Call
Across all transcripts, discover what actually leads to a close.
One transcript improves one brief. All of them, paired with outcomes, tell us which conversations end in a membership, which earn another call, and which go nowhere. Part of v2 is discovering those plays from the transcripts — not assuming them.
Where each play leads · illustrative — real numbers come from the transcript corpus
Closed
Earned another call
No next call
🔍
Discover
Cluster what sales directors said and what prospects responded to across the Vinton corpus.
🔗
Connect to outcome
Tie each conversation pattern to what happened next: close, another call, or silence.
📣
Recommend
The v2 brief suggests the plays that work for this call type and this kind of concern.
🔁
Improve
Every new call is a new transcript and a new outcome. The recommendations get better on their own.
The brief becomes strategy. Not "here's everything we know" — but "here's what has worked when a prospect sounds like this."
How It Runs
The v2 workflow — one loop, from call to brief to call.
The human checkpoint stays exactly where it is. Vinton's field agents already write the call's facts back to Salesforce, so the brief doesn't need to — the custom object from V1 holds the record.
🎙️
Vinton
Records the call; transcript lands in Salesforce; field agents update the record
Salesforce
➜
🤖
Agentforce
Infers call type · reads prior transcript(s) · pulls plays that work · drafts the brief
Kicksaw builds
➜
🟪
Net-new canvas
Slack skill shapes it for this call — nothing appended
Slack
➜
🧑💼
MDA deems it ready
Reviews, adjusts call type or plays, shares
Human checkpoint
➜
📞
Sales director calls
Interrogates via Slackbot before; runs the play on the call
Vinton records again
outcome + transcript feed the next brief
"What did the prospect push back on last time — and which play worked with prospects like this?"
Same people, same Slack workflow, same checkpoint. The difference is what flows through it: context, not accumulation.
The Plan
Six weeks, three tracks, one shippable slice at a time.
Kicksaw extends what it built in V1. MD stakeholders supply the call-type definitions and judge the briefs. Vinton transcripts are the raw material from day one — no new data source to stand up.
Wk 1
Wk 2
Wk 3
Wk 4
Wk 5
Wk 6
Shape Call types · objectives · what a good Call N brief contains
Build · Goal 1 + 2 Call-type inference · transcript synthesis · net-new canvas
Build · Goal 3 Play discovery across transcripts · outcome linkage · recommendations
Pilot Live Call 2 / Call 3 briefs with MDAs and sales directors
Welcome Call Handoff brief for memberships
Skateboard first. A Call 2 brief that reads one transcript and states one objective ships before any play library exists — then Goal 3 layers on.
Not in scope yet: success metrics and Salesforce write-back of the brief. Vinton's field agents own the record; metrics come after the pilot shows what to measure.
The End State
Every call gets the brief that call deserves.
A system where what gets said on the call becomes the strategy for the next one.
🎙️
What was said
Vinton transcripts — every sales conversation, captured in Salesforce, read by Agentforce.
🎯
The right brief
Net-new, for this call, with an objective, the open thread, and the play that works — MDA-approved.
📈
What works
Outcomes flow back. The plays sharpen. Sales directors close sooner — or at worst, earn the next call.
6
Weeks
3
Goals
1
Screen per call
0
Sections stapled on
Call Brief v2: stop describing the prospect — start planning the close.
Built with Kicksaw on Agentforce, Vinton, and Slack. Reviewed by the MDA. Shaped by the sales team.