Daily sales call debrief digest in Slack from Dialpad

Every weekday at 6pm, roll up the day's Dialpad calls into a Slack digest grouped by rep, with flagged calls and concrete follow-ups.

Agentic Task
DialpadSlack BotSalesOperationsDaily DigestsAI ReportsMeeting Workflows
PromptCreate

Every weekday at 6pm in the configured timezone, pull the day's completed Dialpad calls and post a sales debrief digest to Slack.

Use Dialpad List Calls to fetch the calls that started or ended today, filtered to completed calls. For each call id, use Dialpad Get Call to pull the AI recap, transcript, direction, duration, and participants. A single Get Call returns all of these together, so one Get Call per call id is enough, no separate transcript or recap calls needed.

Skip any call shorter than the configured minimum duration (default 60 seconds) so misdials do not clutter the digest. If there are zero qualifying calls after filtering, do not post to Slack at all, just exit quietly.

Group qualifying calls by the internal Dialpad user (the rep). For each rep, flag the calls that mattered: new logos or first-time external numbers, unusually long calls versus that rep's own day, callbacks explicitly requested by the caller, and calls whose transcript or recap contains deal-stage language (pricing, contract, procurement, security review, next steps, decision maker, POC, pilot, renewal, redlines, MSA). Summarize themes across the whole day, including recurring objections, competitors named, and product feedback that came up on more than one call. Pull out the concrete follow-ups the reps committed to on the calls.

Post one message to the configured Slack channel using Slack (bot) Send a Message. Format the message with three sections: a single headline line summarizing the day (total qualifying calls, active reps, count flagged); a per-rep block with the rep's name and bullet points for their flagged calls (duration, who they spoke to, one-line takeaway from the AI recap); and a top follow-ups section listing the concrete next actions across the team.

Let the user configure the Slack channel to post into, the timezone the 6pm schedule runs in, and the minimum call duration in seconds to include (default 60).

Additional information

What does this prompt do?
  • Pulls the day's completed calls from Dialpad and drops anything shorter than the minimum duration you set.
  • Groups calls by rep and flags the ones that mattered: new prospects, unusually long conversations, callback requests, and calls where deal-stage language came up.
  • Summarizes the day's themes, recurring objections, and competitors named across calls so the team spots patterns fast.
  • Posts one clean Slack message with a headline, a per-rep breakdown, and the top follow-ups to chase tomorrow.
What do I need to use this?
  • A Dialpad account with permission to read call history and the AI recap and transcript for completed calls.
  • A Slack workspace and the channel you want the digest posted in (public or private).
  • The timezone your sales team works in, so the 6pm cutoff lines up with the end of your day.
How can I customize it?
  • Point the digest at any Slack channel, including a private manager-only channel.
  • Set the timezone the schedule runs in so 6pm matches when your team wraps.
  • Raise or lower the minimum call duration to filter out misdials (default 60 seconds).

Frequently asked questions

What happens on days when nobody made any calls?
The workflow skips posting entirely on days with zero qualifying calls, so your channel stays quiet on holidays and slow days instead of pinging with an empty digest.
Will short calls and misdials clutter the digest?
No. Any call shorter than the minimum duration you set (60 seconds by default) is filtered out before the digest is built. You can raise the threshold if 60 seconds still feels noisy.
Do I need Dialpad Ai enabled for this to work?
The digest is much richer with Dialpad Ai turned on because it uses the AI recap and transcript to flag important calls. It will still work without Ai, using direction, duration, and participants, but the highlights will be shallower.
Can I post to a private channel or a DM?
Yes. Point it at any Slack channel the bot has been added to, including private manager-only channels. You can even direct message a single sales leader.
Can I run this weekly instead of daily?
Yes. The schedule is fully editable after setup, so you can switch to a Friday afternoon weekly wrap-up or any other cadence you prefer.

Related templates

Daily Braintree declined-payment recovery digest to Slack

Every weekday at 8am, your billing team gets a Slack rundown of yesterday's failed Braintree charges, the revenue at risk, and who to chase first.

Braintree
Slack Bot
Agentic Task
Weekday Azure DevOps sprint standup digest in Slack

Every weekday morning, roll up your sprint's work items into a clear per-person standup summary and post it to your team's Slack channel before you meet.

Azure DevOps
Slack Bot
Agentic Task
Track new Braintree disputes before the deadline slips

Every three hours we scan Braintree for new disputes and chargebacks, open a tracked ticket with a tailored evidence checklist, and alert your team in Slack before the response deadline slips.

Braintree
Zendesk
Slack Bot
Agentic Task
Daily Databricks data health check with Slack alerts

Every weekday morning we check your most important Databricks tables for freshness and data problems, and ping Slack only when something actually looks wrong.

Databricks
Slack Bot
Agentic Task
Monday morning employee breach exposure briefing in Slack

Every Monday, automatically find which employee accounts on your company domain turned up in data breaches and get a plain-English briefing in Slack.

Have I Been Pwned
Slack Bot
Agentic Task
Instant Slack alert when an Azure DevOps build fails

When a pipeline build fails, we post a tight Slack card naming who pushed, the likely cause, and a link to the build so on-call can triage in seconds.

Azure DevOps
Slack Bot
Agentic Task

Stop losing track of what happened on today's sales calls.

Get an end-of-day Slack recap of every meaningful call your team ran, with the follow-ups already pulled out for tomorrow morning.