LeadsForge meeting prep brief in Slack when a call is booked

By General Input

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.

Integrations

  • LeadsForge
  • Google Calendar
  • Slack

Type

Agentic Task

Categories

  • Sales

Build 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.

Related prompts

Explore more prompts
Call overdue Xero customers with an AI collections agentWin back LiveChat visitors whose chats went unansweredChat quality review board for LiveChat support leadsFront desk appointment confirmation board for the next 3 daysWin back no-show and cancelled appointments every morningLive Loop returns analytics with product-level drill-downNewsletter pre-flight and approval board for Mailjet sendsTurn a prospect spreadsheet into personalized sequence enrollmentsMailjet email delivery lookup console for support teamsCatch feature flags that never got switched on in production