LeadsForge meeting prep brief in Slack when a call is booked
When a prospect books a call through LeadsForge, an agent builds a one-page prep brief with discovery questions, blocks prep time, and DMs the rep.
LeadsForge
Google Calendar
SlackSalesMeeting WorkflowsNotifications & AlertsBuild an agent-based workflow that turns every new LeadsForge booking into a fully prepped meeting so the rep walks in cold-outreach-ready.
Trigger: a LeadsForge outgoing webhook subscribed to the meeting_booked event. When it fires, use the thread ID, sequence ID, prospect details, and meeting time from the webhook payload as the starting inputs.
On each fire, the agent should:
1. Call LeadsForge Get Thread on the booking's thread to pull every prior message between us and the prospect.
2. Call LeadsForge Get Sequence for the sequence the prospect was enrolled in, so the agent knows exactly which pitch and cadence they responded to. Handle both single-channel sequences and multichannel sequences.
3. Draft a one-page prep brief containing: who the prospect is (name, title, company, email); which LeadsForge messages they actually engaged with and what their replies said; notable objections, questions, or interest signals from the thread; 3 to 5 discovery questions tuned to what they seemed most interested in. Keep it scannable with short paragraphs and bullets, not long prose.
4. Call Google Calendar Create Event on the rep's primary calendar to block a 15-minute internal prep window on the day of the meeting (about 30 minutes before the meeting itself), with the full brief in the event description and a title like "Prep: <prospect company>".
5. Call Slack Send a Message to DM the assigned rep with the brief, the meeting time in the rep's timezone, and the prospect's email so it lands in their inbox before the call.
The real value of the agent is reading the thread and picking the right discovery questions and pitch context, not just relaying the booking. If the thread is empty or the sequence lookup fails, the agent should still produce a brief from available contact fields and clearly note that thread context was missing rather than inventing objections.
Additional information
What does this prompt do?
- The moment LeadsForge fires a meeting booked notification, the agent reads the entire outbound thread and the sequence the prospect was on.
- It writes a one-page prep brief covering who the prospect is, which messages they engaged with, notable objections, and 3 to 5 tailored discovery questions.
- It blocks a 15-minute prep window on the rep's Google Calendar the day of the meeting, with the full brief in the event description.
- It DMs the assigned rep in Slack with the brief, the meeting time, and the prospect's email so it lands before the call.
What do I need to use this?
- A Salesforge or LeadsForge workspace with an API key (both products share the same key).
- A Google Calendar account for the rep who owns the meeting.
- A Slack workspace so the agent can DM the rep.
- The rep's email or Slack handle so the agent knows who to prep and message.
How can I customize it?
- Change the number of discovery questions, tone of the brief, or add sections like competitors and pricing anchors.
- Swap the 15 minute prep block for 10 or 30 minutes, or move it to the morning of the meeting.
- Route the Slack message to a shared sales channel instead of an individual rep, or copy a manager in on high value bookings.
FAQs
What if the booking has no real LeadsForge thread history?
Does this work with both single channel and multichannel LeadsForge sequences?
Who does the Slack message come from?
Can I add more attendees to the calendar prep block?
How fast does the brief show up after a meeting is booked?
Related templates
Every weekday morning, an agent reviews your open Dynamics 365 pipeline and privately DMs each rep only the deals that need attention today.
Every hour we compare the 30 minutes before and after each release, and only speak up when a deployment genuinely degraded speed or reliability.
Every weekday morning, every account balance is logged to a spreadsheet, and you only hear about it in Slack when one drops below the limit you set.
After every recorded sales call, an agent updates the right deal in Dynamics 365 and posts a Slack recap of exactly what changed.
Every contact sales form submission lands in Dynamics 365 as a clean lead, updating the record you already have instead of creating a second one.
Every New Relic alert opens a Jira bug with the full context and a Slack heads up, then closes itself with the incident duration when it recovers.
Never walk into a booked meeting cold again.
Connect LeadsForge, Google Calendar, and Slack once, and every new booking arrives with a prep brief already in your DMs.