> ## Documentation Index
> Fetch the complete documentation index at: https://clearskies.cc/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Post-call Follow-through

> When a call ends: the follow-up drafted, action items captured, next steps set. Every call, without the rep remembering to do it.

The call goes well. Then the rep has three more calls, and by evening the recap is a half-remembered note. The follow-up goes out two days late, or not at all. Action items live in one person's head. Post-call follow-through closes the loop the moment a call ends: a recap of what was said, the action items and commitments pulled out, a follow-up email drafted and waiting, and the next step written down.

## Data Sources

| Category         | Required | Recommended |
| :--------------- | :------- | :---------- |
| Calls            | ✓        |             |
| CRM              | ✓        |             |
| Email + Calendar |          | ✓           |
| Messaging        |          | ✓           |

**Starter** (required only): a recap of the call, the action items and commitments made, and a suggested next step, tied back to the right deal.

**Full** (required + recommended): the same recap, plus a follow-up email drafted in the rep's own mailbox and posted to the account's Slack channel so the wider team sees it. Same workflow, more of the loop closed.

See the [Context Graph](/docs/unifying-gtm-data/customer-context-graph) for how each source feeds the recap.

### Choose your path

| Path                       | Best for                                                                        | Output is delivered                           |
| :------------------------- | :------------------------------------------------------------------------------ | :-------------------------------------------- |
| Build in Clearskies        | Teams whose daily surface is Slack                                              | To Slack DMs or channels, plus an email draft |
| Build in Claude or ChatGPT | Teams whose daily surface is Claude or ChatGPT, or RevOps testing before deploy | In the Claude or ChatGPT conversation         |

## Build in Clearskies

For teams whose daily surface is Slack. Build the workflow once and every customer call on every rep's calendar produces a recap and a drafted follow-up. No rep action required to start it.

### The Workflow

In the Clearskies app, open the workflow builder and describe what you want in plain language:

```text theme={null}
When an external customer meeting ends, generate a recap using the
Clearskies Context Graph. Pull what was discussed, the action items and
who owns each, any commitments made, and the agreed next step. Post the
recap to the account's Slack channel and draft a follow-up email in the
meeting owner's mailbox.
```

The app configures the trigger (meeting ended), the data pulled (your connected sources), and the destinations (a Slack channel or DM, and an email draft).

Meeting workflows always start with a filter. Every calendar event counts as a meeting, including out-of-office blocks and internal syncs, so the filter is what narrows the run to real customer calls. Test the workflow against a real call before you publish: test runs are always dry, so nothing posts or drafts while you are still refining.

Email drafting requires a connected Google integration. Drafts land in the rep's own mailbox for them to read, edit, and send. Nothing goes to a customer without a person pressing send.

### Deploy to Slack

Once published, the account channel gets this within minutes of the call ending:

```text theme={null}
Post-Call Recap — Acme Corp
Call: Renewal + expansion review, 45 min
Attendees: Sarah Kim (Champion), David Park (Sales Ops), Daniel (AE)

What was discussed
Renewal terms are settled. The expansion into the analytics module is the
open question. Sarah wants it in the same paper as the renewal; David
raised whether his team has capacity to onboard before Q4.

Action items
• Daniel — send the analytics module onboarding timeline (committed to
  Thursday)
• Daniel — introduce David to the implementation lead
• Sarah — confirm internally whether procurement needs a fresh security
  review for the added module

Commitments made
We committed to a 30-day pilot of the analytics module at no charge if
onboarding capacity is the blocker.

Next step
Follow-up call Thursday with the implementation lead on the call. Not yet
on the calendar.

Flagged
Mark Chen (economic buyer) was not on this call and has not been on one in
9 days. The expansion increases deal size; his sign-off has not been
confirmed.
```

A follow-up email lands in Daniel's drafts at the same time, written from the recap and ready to edit.

### Customize the rollout

* Choose where the recap goes: the account's Slack channel, the rep's DM, a team channel, or all three
* Turn email drafting on or off, and decide whether the draft goes to the rep or to their manager first
* Require human review before anything posts or writes, so a person approves each one for the first few weeks
* Tailor what gets extracted: action items only, or commitments and risk flags too
* Chain it with [CRM updates](/docs/use-cases/crm-updates) so the same call also fills in the CRM fields

## Build in Claude or ChatGPT

For teams whose daily surface is Claude or ChatGPT: reps 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.

```text theme={null}
Using the Clearskies Context Graph, process my call with Acme from today.

Give me:
- A recap of what was actually discussed
- Every action item, with an owner
- Any commitments we made
- The agreed next step, and whether it is on the calendar
- A follow-up email I can send, in my voice

Flag anything that changed the shape of this deal.
```

Claude or ChatGPT returns the recap and the drafted email in your conversation. Refine the prompt to fit how your team works deals.

### Make it yours

* Add `Write the CRM summary I should paste into the opportunity record` to cover the hygiene half.
* Add `Compare what was said today against what was said on the last call` to catch shifts in position.
* Add `Score this deal against MEDDPICC and flag any gaps the call exposed` for qualification-aware follow-through. Worth testing against your methodology before relying on it.

### The Skill (Claude)

The `clearskies:post-call` skill in the Clearskies plugin for Claude runs the same workflow on demand: it extracts action items, drafts the follow-up, and flags what needs to change in CRM, all from the call transcript in your Context Graph.

#### Trigger phrases

* "Process my call with \[account]"
* "Draft the follow-up from my \[account] call"
* "What were the action items from \[account]"

#### Customize it for your team

* Match the recap format to your team's standard
* Set which commitments always need a manager's eyes
* Chain it with pre-call prep so prep and follow-up share the same structure

<Tip>
  Want this packaged for your team? [**Reach out**](mailto:support@clearskies.cc) and we'll help you customize the skill to your workflow.
</Tip>

## 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 →**](https://calendly.com/pouyan/new-meeting)

## Next steps

1. [Sign in to Clearskies](https://app.clearskies.cc/)
2. Connect your data sources
3. Get your [Clearskies MCP server](/docs/building-with-clearskies/mcp-server) and try with [Claude](/docs/building-with-clearskies/mcp-clients/claude) or [ChatGPT](/docs/building-with-clearskies/mcp-clients/chatgpt)