Share a prospect brief to Slack before a team sales call
Images on this page are for illustrative purposes only. Example outputs are based on Lusha data, with personal details masked or abbreviated for privacy.
This Claude prompt posts a pre-call brief to Slack before any multi-person prospect call. Google Calendar pulls the attendees. Lusha validates every external contact and scans the account for signals. The brief lands in the channel before anyone joins — who’s in the room, what changed, one thing to align on, and who owns what on your side.
Tools: Claude, Lusha, Slack, Google Calendar
The prompt
This prompt may contain placeholders — look for [BRACKETS] and fill them in.
<context>
I have a prospect call coming up that multiple people from our side are joining. Instead of each person researching separately, I want one brief posted to our team's Slack channel before the call — who's attending from their side, what's changed at the account, and the one thing we should align on before we join.
My call:
- Company: [COMPANY NAME]
- Meeting type: [DISCOVERY / DEMO / QBR / NEGOTIATION / OTHER]
- Our team on the call: [NAMES AND ROLES — e.g. AE, SE, VP Sales]
- Slack channel to post to: [CHANNEL NAME — e.g. #deal-name or #team-sales]
- Who I expect from their side: [NAMES AND TITLES — or "pull from the calendar invite"]
- What I sell: [PRODUCT / SOLUTION]
</context>
<task>
1. Pull the meeting from Google Calendar and get the full attendee list — both our side and theirs.
2. For each external attendee, use Lusha to validate:
- Current verified title and that they're still at the company
- Tenure in current role
- Seniority read: decision-maker / influencer / end user
- Flag anyone whose role has changed or who is new to the meeting
3. Use Lusha's signals layer to scan the account:
- Any structural change in the last 30 days: exec departure, funding, M&A, headcount shift
- Any signal that changes how the team should approach this call
4. Build a pre-call Slack brief and post it to the specified channel:
Format for Slack — use *bold* for key fields, under 200 words total:
*Pre-call brief: [Company] — [time]*
*Who's joining from their side:*
Each external attendee with verified title and one-line seniority note
*Account check:*
Clean or flagged — specific signal if any
*One thing to align on before we join:*
One specific point the team should agree on before the call starts
*Who owns what on our side:*
Who leads, who demos, who handles commercial questions
5. Tag the AE or deal owner in the Slack message.
</task>
<constraints>
- Post to Slack — don't just return the brief as text.
- Under 200 words in the Slack message. If it's longer, the team won't read it before joining.
- ONE THING TO ALIGN ON must be specific to this meeting — not "be prepared" or "know your pitch."
- If the signal changes who should lead the call, say so explicitly.
- Format for Slack: *bold* key fields, line breaks between sections, no markdown headers.
</constraints>What you'll get back
The situation: An AE at a sales intelligence platform has a demo in 45 minutes. The AE, an SE, and the VP of Sales are all joining. Nobody has prepped. She runs the prompt and the brief lands in #halcyon-deal before anyone asks.
Output: One Slack message, 187 words, posted to the channel. AE tagged. Everyone aligned before the call loads.
Slack message — posted to #halcyon-deal
Pre-call brief: Halcyon Ventures — 2:00pm
Who’s joining from their side: J.K., Chief Revenue Officer — 18 days in role, decision-maker. First CRO hire, previously founder-led sales. Still forming opinions on the stack. D.K., Head of Sales Operations — 14 months in role, influencer. Knows the existing setup well. Main eval driver day-to-day. Unknown: a.smith@[halcyon].com — not in Lusha. Confirm who this is when we join.
Account check: Sales team grew 34% last quarter — 8 open AE/SDR roles posted now. No M&A, no other exec changes. Live hiring signal.
One thing to align on before we join: J.K. is 18 days in and evaluating the whole stack. D.K. is the technical gatekeeper. Don’t skip D.K. to get to the CRO — get D.K. on side first. Agree on who handles which before we join.
Who owns what on our side: @sarah.ae leads and handles commercial. @tom.se runs the demo and technical questions. @vp.sales — let AE drive, step in if CRO pushes on pricing authority.
— @sarah.ae this is yours
(187 words)
Attendees validated via Lusha connector. Calendar pulled from live session. Slack message posted to #halcyon-deal. Details masked for privacy.
Why it works
A multi-person sales call where each person prepped separately — or nobody prepped — is a coordination problem as much as a research problem. The SE doesn’t know the CRO is 18 days in. The VP doesn’t know there’s an unknown attendee on the invite. The AE doesn’t know D.K. is the technical gatekeeper who needs to be won before the CRO matters. The Slack brief solves all three in one message, posted before the call, where the team already is. The “who owns what” section is what turns the brief from intelligence into coordination — it tells everyone their role before the call starts, not during it.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
Who should run this — the AE, the manager, or RevOps?
The AE or deal owner runs it — they know the channel name and the team joining. It takes 2 minutes and the output goes directly to whoever needs it. RevOps can set a standard that this runs for any call with 3+ internal attendees.
What if the Slack channel doesn't exist yet?
Create a deal channel first, then run the prompt. Most teams using this play have a per-deal Slack channel already — #[company-name] or #deal-[stage]. If not, post to a shared team channel and tag the deal owner.
Can I run this for customer calls, not just prospect calls?
Yes — works the same way for renewals, QBRs, or exec reviews. Change the meeting type field and the brief adjusts: customer calls get a different “one thing to align on” than prospect demos, based on the relationship context Lusha returns.
What if one of our team members' roles changes before the call?
The “who owns what” section is based on the roles you put in the context field — it doesn’t pull internal titles from a system. Update the context field if the team composition changes and rerun.
How is this different from the daily meeting brief?
The daily meeting brief is for one person covering all their calls for the day — it returns a personal brief. This prompt is for a team call — it posts to Slack so everyone gets the same brief, adds the coordination layer (who owns what), and is designed for multi-person calls specifically.
Ready to build this?
Get started with Lusha and set up this play in minutes.
