Daily Quo call and SMS digest in Slack

By General Input

Every weekday at 8am, get yesterday's top Quo calls, AI summaries, and unanswered SMS threads posted as a structured digest in Slack.

Integrations

  • Quo
  • Slack

Type

Agentic Task

Categories

  • Sales
  • Operations

Every weekday at 8am in my local time zone, run an agent that builds a daily digest of yesterday's Quo activity and posts it into a Slack channel I pick at setup. The trigger is a cron schedule, Monday through Friday at 8am.

Step 1. Pull yesterday's activity from Quo. Use List Calls to fetch every completed call across the workspace's Quo phone numbers for yesterday's date range. Use List Conversations and List Messages to fetch yesterday's SMS threads and the messages inside them. For any call that has a recording or AI summary available, use Get Call Summary to pull the AI-generated summary and key points.

Step 2. Cluster and prioritize. Group the activity by theme based on the summaries and message content. Typical themes are sales conversations, support issues, scheduling and logistics, and anything else that comes up. Be opinionated. Pick the two or three most important calls of the day based on signals like call duration, whether it was answered, who the participant was, and what the AI summary says happened. This is not a raw activity log, it is a prioritized brief.

Step 3. Identify unanswered SMS threads. For each inbound SMS thread from yesterday, check the most recent message. If the latest message is from the outside contact and no one on the team has replied, flag the thread as unanswered. Capture the participant's phone number and the timestamp of the last inbound message.

Step 4. Post the digest with Send a Message in Slack to the configured channel. Format it as Slack mrkdwn with this structure: a one-line headline with yesterday's date and a quick count of calls and messages, a Top calls section that leads with the two or three most important calls and includes the participant, call length, the AI summary, and any clear action items the agent extracted, a Themes section that briefly lists the other activity grouped by cluster, and a Needs a reply section that lists every unanswered inbound SMS thread with the participant phone number and the timestamp of the last message so someone can pick it up.

Keep the tone tight and skimmable. If there was no activity yesterday, post a short message saying so instead of a full digest. If the Quo plan does not return AI summaries for some calls, include the call metadata anyway and note that the summary was not available.

Related prompts

Explore more prompts
Call overdue Xero customers with an AI collections agentWin back LiveChat visitors whose chats went unansweredChat quality review board for LiveChat support leadsWin back no-show and cancelled appointments every morningLive Loop returns analytics with product-level drill-downNewsletter pre-flight and approval board for Mailjet sendsTurn a prospect spreadsheet into personalized sequence enrollmentsMailjet email delivery lookup console for support teamsCatch feature flags that never got switched on in productionKajabi customer support console for member access fixes