Skip to main content
Every rep joins every call with the full picture — deal history, recent emails, past call highlights, and open items. Pulled from every source, delivered where your team works. Your reps join calls without context. Some prep well. Most don’t have time to get to it. The result is inconsistent customer conversations, missed signals, and deals that stall because the rep didn’t see what changed since the last touchpoint. Pre-Call Brief gives every rep a complete brief before every meeting — pulled from every source, delivered where your team works.

​
Data Sources

CategoryRequiredRecommended
CRM✓
Calls✓
Email + Calendar✓
Messaging✓
Starter (required only): a useful brief covering deal stage, key contacts, and the last call’s highlights and open items. Full (required + recommended): the same brief, plus important context such as recent email threads, who’s gone quiet, and any Slack flags from your team. Same workflow — significantly more context. See the Customer Context Graph for how each source feeds the brief.

​
Choose your path

PathBest forOutput is delivered
Build in ClearskiesTeams whose daily surface is SlackTo Slack DMs or channels (today)
Build in Claude or ChatGPTTeams whose daily surface is Claude or ChatGPT, or RevOps testing before deployIn the Claude or ChatGPT conversation

​
Build in Clearskies

For teams whose daily surface is Slack. Build the workflow once in the Clearskies app and every meeting on every rep’s calendar comes with a brief — delivered to Slack, no rep action required.

​
The Workflow

In the Clearskies app, open the workflow builder and describe what you want in plain language: 
Before every customer meeting on a rep's calendar, generate a brief using
the Clearskies Context Graph. Pull deal stage, contacts, the last call's
highlights and open items, recent emails, and any Slack flags. Post the
brief to the rep's Slack DM 30 minutes before the meeting starts.
The app configures the trigger (each rep’s calendar), the data pulled (your connected sources), and the destination (Slack DM or a team channel — your choice). Review and refine before deploying.

​
Deploy to Slack

Once deployed, every rep sees this in their Slack DM before each meeting: 
Pre-Call Prep — Acme Corp
Meeting: 2:00 PM with Sarah Kim (Champion) and David Park (new stakeholder)

Where it stands
Two-track conversation: standard renewal plus expansion into the analytics
module. Champion is bought in. Economic buyer (Mark Chen, VP Sales) has
been quiet for 9 days — last touchpoint May 1.

Who you're meeting with
• Sarah Kim — primary champion. On every call. Tone shifted slightly more
  cautious on May 6 after legal asked about data retention.
• David Park — new to the conversation. Joined Acme three weeks ago as
  Director of Sales Ops. Wasn't on previous calls.

Last call (May 6)
You agreed to send a pricing one-pager (sent May 7). Sarah mentioned
procurement may want a security review. You committed to a 30-day pilot
if needed.

Since then
May 9 — Sarah forwarded the one-pager internally with "let's discuss."
No reply since.
May 10 — AE Daniel flagged in Slack that legal raised questions about
data residency.

The one thing
Get an answer on whether Mark Chen is still the economic buyer, or
whether David Park's arrival changes the decision path.

​
Customize the rollout

  • Choose who receives briefs (per-rep DM, per-team channel, manager cc)
  • Adjust timing (30 min before each meeting, night-before digest, morning-of)
  • Tailor the brief format to your team’s coaching framework or methodology
  • Flag specific risk signals you want surfaced — champion dark, no economic buyer access, stage-velocity drift

​
Build in Claude or ChatGPT

For teams whose daily surface is Claude or ChatGPT — sales leaders working in either, or RevOps testing the workflow before deploying it to the team. Output appears in your conversation.

​
The Prompt

Open Claude or ChatGPT with the Clearskies MCP connected and paste this (or modify to your needs). Replace the account name with your own. 
Using the Clearskies Context Graph, prep me for my call with Acme tomorrow.

Pull together:
- Where the deal stands and how we got here
- Who I'll be meeting with and what we know about each of them
- The last call's highlights, open items, and any commitments made
- What's happened on email or Slack since the last touchpoint
- The one thing most worth learning or moving in this call

Be direct. Flag anything that suggests this deal is at risk.
Claude or ChatGPT returns a brief structured like the Slack example above, generated from your data and formatted as a chat response. Refine the prompt to fit how your team works deals.

​
Make it yours

  • Add Right after the call, draft a follow-up email I can send to the customer to chain prep with follow-up.
  • Add Compare what's in CRM to what's actually happened to surface hygiene gaps.
  • Add Score this deal against MEDDPICC and flag any gaps for qualification-aware prep — worth testing against your methodology before relying on it.

​
The Skill (Claude)

The clearskies:call-prep skill in the Clearskies plugin for Claude runs the same workflow on demand: account snapshot, last call summary, open items, contact context, a suggested agenda, and one key opening question — all from your Context Graph.

​
Trigger phrases

  • “Prep me for my call with [account]”
  • “What do I need to know before my [account] meeting”
  • “Call prep for [account]“

​
Customize it for your team

  • Match the brief format to your team’s standard
  • Add risk signals your team cares about
  • Chain it with a post-call workflow so prep and follow-up share the same structure
Want this packaged for your team? Reach out and we’ll help you customize the skill to your workflow.

​
The Plugin

Ready to make this part of your team’s workflow? We’ll set up the Clearskies plugin with you — Clearskies workflows, Claude skills, all tailored to how your team works. Book 15 minutes →

​
Next steps

  1. Sign in to Clearskies
  2. Connect your data sources
  3. Get your Clearskies MCP server and try with Claude or ChatGPT