> ## Documentation Index > Fetch the complete documentation index at: https://docs.parsalink.io/llms.txt > Use this file to discover all available pages before exploring further. # Daily Digest > An LLM-written daily summary of what's happening in your CRM — tasks due, overdue work, pipeline movement, and any custom sections you wire up.
DIGEST

A conversational morning briefing of what matters most in your workspace today — written by an LLM, sent on whatever cadence you set, and shaped by your own custom sections and instructions.

## What the Digest Includes By default the digest covers: * **Today's tasks** — what's due, what's overdue, who owns it * **Recent activity** — opportunities that changed stage, contacts that moved through your pipeline * **Open work** — top open opportunities, urgent cases, anything assigned to you that's been quiet If you're on a **manager** digest, it also includes a per-team-member breakdown so you can see at a glance whose plate is overloaded. The digest writer is an LLM (the `digest-writer` prompt template), which means the wording adapts each day — it isn't a static template. You can steer it with `custom_instructions` (see below). *** ## Configuring Your Digest Go to **Settings → Digest**. Choose **Daily** or **Disabled**. Daily is the default; weekly is on the roadmap. **Individual** focuses on the work assigned to you. **Manager** adds a per-team-member breakdown showing each person's accomplishments, open tasks, and overdue items. Hour of day (UTC, 0–23) when the digest should land in your inbox. Most teams pick early morning local time. Free-text steering for the LLM writer. Example: *"Include the total count of contacts tagged 'Parsa User Created'. Always call out overdue tasks for Amy specifically. Use a casual tone."* The writer treats these as preferences and follows them unless they conflict with factual accuracy. Click **Send Now** at any time to fire a test digest using your current settings. Useful when you've just tweaked custom instructions and want to see how the writer interprets them. *** ## Custom Sections Custom Sections let admins surface workspace-specific data slices on top of the standard digest. They're defined at the workspace level (not per user) but you can scope each section to either individual digests, manager digests, or both. Go to **Settings → Digest → Custom Sections** to define them. Each section captures: * **Label** — the heading shown in the digest body (e.g., "New VIP contacts this week") * **Entity type** — `contact` (account support coming later) * **Tag filter** — optional, e.g. `vip` * **Field key** — a column or `data.` path * **Window** — how many days back to look (e.g. `7`) * **Item limit** — how many items to show in the digest * **Display order** — where this section appears * **Include in individual / manager** — independent toggles Custom sections are computed and inlined into the LLM prompt every morning, so the writer mentions them naturally in the narrative instead of bolting on a generic list. If your custom section is empty (zero matches), the writer will note that — it doesn't pretend results exist. *** ## Replying to the Digest Hitting **Reply** to a digest email isn't a dead end — it's a conversation with the CRM agent. When you reply with something like: > *"Reassign Amy's overdue VIP outreach tasks to Jacob, then send Amy a quick thanks for closing the Globex deal."* The reply is routed to the [CRM AI agent](/ai/chat) under your identity. The agent reads your message, calls the right tools (`update_task`, `send_email`, etc.), and either completes the request or pings you back with clarification. This is the same agent that powers the in-app chat, so anything you can ask it inside the app works in a digest reply. Digest replies execute under your user's permissions and tenant context. Don't forward a digest email to a non-team-member and expect them to reply on your behalf — replies are matched to your email account on file.