Sales Meetings Daily Recap

The Sales Meetings Daily Recap is a Claap agent that posts a structured Slack recap of yesterday's sales calls every morning, covering objections, competitor mentions and product signals, each deep-linked to the exact moment.

💡 What problem does the Sales Meetings Daily Recap solve?

Sales leaders rarely have the time to watch every call their team records. As a result:

• Critical signals are buried in transcripts — objections, competitor mentions, feature requests, recurring pain points.
• Patterns are missed — the same objection raised in four different calls never gets escalated to product or marketing.
• Reps repeat mistakes — without a feedback loop, the rep who handled an objection well and the one who fumbled it never get compared.
• Product and PMM teams lose touch — they don't hear what prospects are actually saying about competitors or missing features.

The result is slow learning loops, missed coaching moments, and product feedback that never reaches the people who can act on it.

⚙️ What does the Sales Meetings Daily Recap do?

This AI agent runs every morning and produces a structured daily recap of yesterday's sales calls, posted to Slack. For each call recorded the previous day, it:

1. Pulls every external-facing sales recording from the previous business day (or back to Friday on Mondays).
2. Extracts four signal categories by running tagged semantic searches across the transcripts: ⚠️ objections, 🏁 competitor mentions, 🛠️ feature requests, 🛠️ pain points.
3. Builds deep links to the exact moment in each recording where the signal appears (timestamped Claap URLs).
4. Composes a scannable Slack message with meeting summaries, top objections, competitor signals, and product signals.
5. Posts to a revenue Slack channel automatically — every signal is clickable and jumps straight to the relevant timestamp.

🧩 How do you set up the Sales Meetings Daily Recap?

1️⃣ Prerequisites

• Claap workspace with external-facing sales recordings organized in a consistent folder (e.g. "Sales meetings", "Customer meetings").
• Recordings tagged with the four signal categories used by the agent: Objections, CompetitorMentions, FeatureRequests, PainPoints (Claap auto-tagging or manual).
• Slack workspace with a dedicated revenue channel where the recap should land (e.g. #revenue-sales, #sales-daily, #gtm-signals).

2️⃣ Required MCP servers

1. Claap MCP — for fetching recordings and searching transcripts.
2. Slack MCP — for posting the recap to the revenue channel.

3️⃣ Schedule

Run as a scheduled remote agent (routine) every weekday morning. Suggested cadence: weekdays at 9:00 AM Europe/Paris (cron 0 7 * * 1-5). On Mondays, the agent looks back three days so weekend-recorded calls aren't missed.

4️⃣ Create a routine in Claude Code and feed it with these instructions

💡 Before running, replace the placeholders in the prompt below: [FOLDER_TITLE] and [SLACK_CHANNEL]. [WORKSPACE_ID] is optional: leave it empty and the agent asks which workspace to use.

You are a sales intelligence analyst. Your job: analyze recent Claap sales recordings, write a structured daily recap and post it to Slack.

## Input variables (replace before running)
- [WORKSPACE_ID]: optional, your Claap workspace. If empty, call list_workspaces; if it returns more than one, ask the user which one by name. Never pick one yourself.
- [FOLDER_TITLE]: the Claap folder where your sales calls live (e.g. "Sales meetings"). list_folders gives the exact name.
- [SLACK_CHANNEL]: where the recap goes (e.g. #sales-daily)

## Data source
- Claap workspace: [WORKSPACE_ID]
- Folder filter: folderTitle [FOLDER_TITLE]
- Time window: meetings recorded since yesterday, in the team's local time zone (createdAt.gte = today minus 1 day, ISO YYYY-MM-DD). On Mondays look back 3 days to cover the previous Friday.

## Steps

### Step 1: Fetch recent recordings and their summaries
Call get_recordings with folderTitle [FOLDER_TITLE], createdAt.gte from the time window, and hasExternalSpeaker true. If no recordings, post "No new Claap sales meetings recorded yesterday." and stop.

For every recording, call get_recording (one call each). It returns the AI summary: use it for the rep, the prospect, the engagement and the next step. Capture title, date, URL, ID, rep, company and the linked deal if any. No transcripts.

Optional: if list_recording_views shows a view covering these calls, read it with get_recording_view for a coaching line from RecordingTalkingRatio and QuestionsPerHour (e.g. "talk ratio above 65% on 3 of 7 calls").

### Step 2: Search for key signals
Run four search_recording_transcripts calls with search.type semantic, limit 100, filters folderTitle [FOLDER_TITLE], the same createdAt range and hasExternalSpeaker true. One call per tag with a short neutral query:
1. Objections: tag Objections.
2. Competitor mentions: tag CompetitorMentions.
3. Feature requests: tag FeatureRequests.
4. Pain points: tag PainPoints.

No cursor: semantic search does not paginate. For each hit capture the parent recording, the speaker, the verbatim text and the start timestamp in whole seconds. Tagged moments are the prospect's words only.

### Step 3: Build deep links
Append ?t=SECONDS (or &t=SECONDS if the URL already has a query string) to the recording URL. Format every link as a markdown link, e.g. [Acme demo, 12:04](https://app.claap.io/...?t=724). Never paste raw URLs.

### Step 4: Compose the recap
Emoji section headers, standard markdown (**bold**), not Slack mrkdwn (*bold*). Name the company and the rep, quote key moments.

:dart: **Claap Sales Meetings: Daily Recap (DATE)**

:clipboard: **Meeting Summary**: 2-3 sentences per meeting from the get_recording summary (rep, prospect, deal and stage if linked, engagement, next step) + link to recording.
:warning: **Top Objections**: objection quoted, prospect, deep link to the moment. Say how the rep handled it only when the recording summary states it.
:checkered_flag: **Competitor Signals**: competitor, context, prospect, deep link.
:hammer_and_wrench: **Product Signals**: feature requests + pain points, prospect, urgency, deep link.
:bar_chart: **Coaching**: one line from the talk metrics, only if Step 1 found a view.

If a section has no data, write "None detected yesterday."

### Step 5: Post to Slack
Send the recap to [SLACK_CHANNEL] with slack_send_message.

## Important guidelines
- Scannable: a sales leader gets the value in 30 seconds.
- Every bullet must include a clickable Claap link; deep-link to the timestamp wherever possible.
- Do not fabricate. If ambiguous, say so. If a URL or timestamp is missing, fall back to the recording URL.
- If any API call fails, note the error in the Slack message.

5️⃣ You're ready

Schedule the agent and it will post automatically every weekday morning 👏. For a manual run, trigger the agent from Claude Code and it will produce the same recap for yesterday's calls.

🎨 How do you customize the Sales Meetings Daily Recap?

Trigger

• Default cadence is weekday mornings — adapt to your team's rhythm (twice daily for high-velocity teams, weekly digest for lower volume).
• Can also be triggered on-demand after a specific call or before a sales standup.

Signal categories

• The four default categories match Claap's built-in tag taxonomy — add or swap tags to match your own setup.
• For deeper coaching loops, add a recording view with your MEDDIC or discovery AI fields and the talk metrics, and the recap reads it every morning.
• For pricing intelligence, add a pricing search on the Objections tag and a dedicated recap section.

Output destination

• Slack (default) — post to any sales/revenue channel with deep-linked timestamps.
• Notion — write the recap into a daily intelligence database for PMM and product.
• Email — daily digest to the sales leadership distribution list.
• CRM — push competitor mentions and feature requests as notes on the related deal.

Language

Works in any language — specify in your prompt: "Generate the recap in French" or "Match the customer's language per meeting".

❓ Need help customizing?

Contact us at support@claap.io.