Your meeting brief should be in Slack one hour before the meeting starts.
Your first brief lands tomorrow at 9 AM. Setup is 60 minutes. A Slack teammate pulls cross-stack context and DMs a 1-paragraph brief before every external meeting.
Your meeting brief should be in Slack one hour before the meeting starts.
Your first brief lands tomorrow at 9:00 AM. Setup is 60 minutes. No engineering ticket. No calendar plugin to install.
| TL;DR |
| What it does. Watches the calendar. Pulls cross-stack context. DMs a 1-paragraph brief 60 minutes before each external meeting. |
| Setup. 60 minutes. No Outlook plugin. No calendar app to install. |
| Why it is safe. Every read of CRM, email, and call history runs under the meeting owner's own OAuth session. |
| Where it ships today. Salesforce, HubSpot, Attio, Zoom, Google Meet, Email, Granola, Fireflies + 2,000+ services. |
The scene this fixes
It is 9:55 AM. A VP of Sales is wrapping a forecast call. Her next meeting is at 10:00, with a director at Globex she has met once, two months ago. She has not opened the account. She has not read the SDR's notes. She has not looked at what marketing sent them last week. She joins cold and spends the first six minutes asking questions she could have answered herself. I have watched this scene at every sales org I have shipped Runbear with. The prep matters; the prep does not happen. The window between "the next meeting is in an hour" and "the meeting starts" is the window the AE never has free. Proactive meeting briefing is the fix.
What is proactive meeting briefing?
An AI agent runs on calendar triggers, pulls the relevant context for each upcoming meeting (account record, last contact, recent emails, call history, marketing engagement, news about the company), composes a one-paragraph brief, and DMs it to the meeting owner exactly when they can act on it. The trigger is the calendar, not a person asking. The shift versus 2024 retrieval tools is timing: a search box answers when you ask; a proactive teammate answers before you would have known to ask. People read briefs that arrive unbidden far more often than they open briefs they have to fetch.
How it works
A meeting is scheduled. Sixty minutes before it starts:
- Calendar trigger fires. The teammate scans external meetings on the next 24 hours of the team's calendars (anyone on the invite outside the company domain).
- Context assembly. It pulls the matching Salesforce account and opportunity, the last 30 days of email with attendees, the most recent Gong call summary, the HubSpot engagement timeline, and a news search for the company.
- Slack DM with the brief. One paragraph: attendees and roles, deal stage, last meaningful contact, recent marketing engagement, two things the attendee likely cares about, one suggested opener.
The AE opens Slack five minutes before the call, scans the brief, and walks in warm.
Ship it in 60 minutes
You add this as a new event trigger to your @Runbear teammate in Slack. No Outlook plugin. No calendar app. The teammate watches the calendar, fires the brief 60 minutes before each external meeting.
Paste this at @Runbear in #sales-ops:
@Runbear new event trigger: every 15 minutes, scan the calendar for upcoming external meetings starting in the next 60 to 75 minutes. For each: (1) Identify the matching Salesforce account and opportunity by attendee email domain. (2) Pull the account record, last 30 days of email with the domain, most recent Gong call summary, HubSpot engagement timeline, and a news search for the company name. (3) Compose a one-paragraph brief covering attendees and roles, deal stage, last meaningful contact, recent marketing engagement, two things the attendee likely cares about, and one suggested opener. (4) DM the brief to the meeting owner (calendar organizer if internal, otherwise the deal owner per Salesforce). (5) If there is no matching account, send a shorter brief covering attendee LinkedIn snapshots and prior calendar history. (6) If the meeting is internal, skip silently.
How this compares to alternatives
| Approach | When the brief lands | Coverage | Per-user permissions |
| No prep | In-meeting, asking the questions you should have answered | Whatever you remember | Native |
| Manual prep (yourself or chief of staff) | When you have time, often skipped | Limited by available time | Native |
| AI teammate in Slack (Runbear) | 60 minutes before, automatic, every external meeting | Full stack | Per-user auth on shared agent |
Connect Salesforce, HubSpot, or Attio to Slack with per-user authentication
The structural piece that makes this safe at scale is per-user authentication on shared agents. One Slack identity. The DM goes to the meeting owner. Behind it, every Salesforce, Gmail, Gong, and HubSpot read runs under that owner's own OAuth session. The brief never contains data the owner could not legitimately see. SSO and SCIM tie into the existing identity stack. I have watched teams try to build this with a shared service account and a cron job. On day thirty they realize every brief contains data the recipient should not have. The per-user-auth layer is the piece DIY cannot match in a weekend.
What sales leaders ask first
Will my reps actually read the briefs?
The answer is the timing. A brief that arrives 60 minutes before the meeting, in the surface the AE is already in, with a length they can scan in 20 seconds, gets read. In the first month, AEs open roughly nine of ten briefs. In the second month, they start replying to the bot with follow-ups, signaling the surface has earned trust. The first measurable effect is a drop in time-to-rapport on the call.
How is this different from Gong's pre-call summary?
Gong's pre-call summary is built off call history. It does a good job on call surface, weakly on email, not at all on CRM stage, marketing engagement, or company news. Runbear is the cross-stack briefing layer; Gong is the call-history layer. Most teams run both.
Your first 60 minutes
- 0 to 10. Install the Runbear teammate in Slack. SSO in.
- 10 to 25. Connect Salesforce, Gmail, Google Calendar, Gong, and HubSpot via per-user OAuth.
- 25 to 40. Paste the prompt at @Runbear in #sales-ops. Tune brief length and format.
- 40 to 55. Wait for the next external meeting on your own calendar 60 minutes out. Watch the brief land in your DMs.
- Minute 60. Tell three AEs to expect their first brief tomorrow morning. You are live.
Week 1 follow-on
- Day 2. Add a news-search source so the brief includes recent company news.
- Day 4. Add the internal-meeting variant. Most teams turn on a separate prep for pipeline reviews where the teammate briefs the manager on each AE's deals.
- Day 7. Open the per-agent observability dashboard. Check the brief-open rate (target 85% or higher) and the time-to-rapport delta.
What it delivers
I have watched a few dozen sales teams ship this pattern, and the shape is the same. It lands at ten-to-two-hundred-AE and SE orgs running back-to-back external meetings where the prep cost is real but the prep window is always missing. AEs receive three to eight briefs per day. Brief-open rate runs above 85%. Sales managers report time-to-rapport drops noticeably in the first month, and meeting recaps improve because the AE walked in warm.
What to automate next
The most common follow-on is the post-meeting recap teammate. It listens to the call, drafts the recap email to the customer, the next-steps note to the CRM, and the deal-channel update in Slack. The pre-meeting and post-meeting bookends become the same teammate.
See the full Sales solution page for the rest of the stack.
About the author
Snow Lee is the founder of Runbear, the team AI adoption layer for Claude-buying mid-market companies. She has personally shipped AI teammates with sales orgs ranging from ten-person founder-led teams to two-hundred-person mid-market sales floors, and writes here from those rollouts directly.