Skip to content

Chat Digests ​

At a glance ​

LocationChat side panel → Digests / Spun Tools → Insights → Digests
PlanAll plans, including the free tier
Related features4

Rolling, always-current summaries of chats, each driven by a named standing question ("summarize", "what opportunities appeared?", "any complaints?"). A digest covers either All chats (org-wide: every chat the org's AI read scope allows, including chats that start later) or a chosen list of up to 25 chats and groups. In the app, Settings > Digests has a "New digest" button where you pick All chats or Choose chats (a searchable picker of chats and groups, up to 25), and a chat's side panel creates a digest for that one chat ("Ask another question"). Each digest in Settings > Digests has an "All chats" switch and a "Member chats" editor to add or remove chats (same picker, same 25 cap); saving a scope change rebuilds the digest from its new chats. More than 25 specific chats is not possible; use All chats instead. A chat can carry any number of digests. Each digest keeps an evidence-backed answer that folds in only new messages on refresh, periodically rebuilds from scratch, respects the org's AI read scope, shows how many messages were analyzed and how many were cited for claims (with each citation resolvable to its exact message), and shows a token cost estimate (as a range, following current activity) before you create it or save a scope change. Next to that estimate the app shows about how many messages a month the digest will analyze. One refresh reads at most 500 messages plus up to 100 voice notes that are not transcribed yet. An ordinary refresh reads the unread messages after the last one it read, oldest first; a periodic rebuild reads the newest 500 messages in the digest's lookback window (1 to 90 days, 7 by default) and leaves the older ones in that window unread. The digest says what it read, for example "Read 500 of 3,214 messages from the last 7 days", and, when more unread messages are waiting, how many the next refresh will read. If a message the answer cited is hidden later, the answer is withheld until the digest is refreshed, which rebuilds it without that message. When the chosen chats get more messages than that, the app says how many arrive a month and that the digest runs behind the newest messages and some are never read; a bigger plan does not change this, choosing fewer chats does. Digests name voice notes and their length, and a voice note that is not transcribed yet still counts, marked as not transcribed. Digests can opt into the Daily Summary as sections, refresh on demand or on a daily schedule, and keep version history you can roll back. A digest on a daily schedule is a running workflow and occupies one of your plan's workflow slots, shared with active group monitors, check-in rules and bot trigger rules; a digest refreshed on demand takes no slot, pausing a scheduled digest frees its slot, and when every slot is in use a new scheduled digest is refused with a notice to pause one or upgrade. Connected AI apps (the Spun MCP surface, e.g. claude.ai) can list a workspace's standing questions with list_chat_summaries, read a digest's stored answer with get_chat_summary (both ride the ordinary conversation-read permission and never spend tokens), define new standing questions with define_chat_summary (scope "all_chats" or "chats" with up to 25 chat ids), and edit an existing one (rename, change the question, switch between all chats and chosen chats, change member chats, schedule, language, or daily-summary inclusion; pause and resume) with update_chat_summary. Both writes report the scope and the estimate, live under the dedicated "Define Chat Digests" key scope, and can trigger a background rebuild that spends the org's AI budget. System-managed digests such as the daily recap can be listed and read but not edited over MCP. A digest reads the messages in the chats it covers, so the chats selected decide the cost, and a broad daily digest over a set of chats costs less than several narrow ones over the same chats.

How to use ​

  1. Open Settings > Digests and click "New digest".
  2. Type a standing question (or leave it empty for a general summary), then choose All chats (org-wide) or Choose chats and tick up to 25 chats or groups.
  3. Review the estimated token cost and about how many messages a month it will analyze, then create.
  4. For a single chat, open the chat's side panel, find the Digests card and click "Ask another question".
  5. To change which chats a digest reads, open it in Settings > Digests and use the "All chats" switch or the "Member chats" editor, check the new estimate, and save.
  6. Open a digest any time to read the stored answer free of charge, or press Refresh to update it; manage edit, rebuild, pause, versions and delete in Settings > Digests.
  7. Tick "Include in daily summary" on a digest to receive it as a section of your morning Daily Summary.
  8. A connected AI app with the right permissions can list standing questions, read a stored answer, define a new one for all chats or chosen chats, or edit/pause an existing one directly.

FAQ ​

  • What are chat digests?
  • How do I get a rolling summary of a group?
  • Can I ask a standing question about a chat?
  • How much do digests cost in tokens?
  • How do I add a digest to my daily summary?
  • Can a connected AI app manage my chat digests?
  • Can a digest cover all my chats or groups?
  • How do I add or remove chats from a digest?
  • How many messages a month will an all-chats digest analyze?
Was this page helpful?

Spun Docs - the documentation for Spun, the WhatsApp team inbox by Spun Life LLC.