Daily Brief
Get a per-meeting rundown of your day: where each account stands, the one outcome to drive, follow-ups to close, and who is in the room.
Overview
Daily Brief gives you a per-meeting rundown of your day so you walk into each call knowing what matters. It pulls your schedule for the target day, then builds one card per meeting. Each card covers where the account stands, the single outcome to drive, the follow-ups to close from prior conversations, and who will be in the room.
The brief researches every in-scope meeting, blending account research, contact research, and conversation intelligence per meeting. Because that work costs AI credits, the skill sizes the day first. If more than a few external meetings are on the calendar, it tells you the count, notes that each one is researched with several credit-consuming calls, and offers to scope down before proceeding. That pause keeps a packed calendar from turning into a large unprompted spend.
By default the brief covers external meetings, the ones with participants outside your company, and drops internal-only blocks unless you ask for everything. You can point it at tomorrow, a named weekday, or a specific date, and you can filter to customer meetings only or a single account. Each card leads with what changes how you show up, not generic firmographics, and the brief closes with a cross-day watch-out line only when something real connects the meetings.
What It Does
- Per-meeting cards: Builds one card for each meeting in time order, carrying its state of play, focus, follow-ups, and attendee list.
- Single-outcome focus: Frames each card around the one most useful result to drive in that meeting rather than a list of talking points.
- Follow-up surfacing: Pulls open commitments from prior conversations so nothing agreed earlier slips through the day.
- Scope confirmation: Counts the external meetings and offers to narrow before researching, so a full calendar does not become an unplanned credit spend.
- Flexible targeting: Runs against today, a future day, or a specific date, and filters to a segment such as customer meetings or a named account.
- Cross-day watch-out: Adds a single closing line when a renewal clock, a slipping deal, or an executive presence ties meetings together, and stays silent when nothing does.
Use Cases
A Morning Rundown Before Back-to-Back Calls
You have six external meetings today and no time to prep each one by hand. Run Daily Brief. It confirms the count, you approve the scope, and it returns a card per meeting in time order. Each opens with where the account stands and the one outcome to push, so you move from call to call without scrambling between them.
Prepping a Filtered Slice of the Day
Your calendar mixes internal syncs, partner calls, and customer meetings, but this morning you only care about customers. Filter the brief to customer meetings only. It drops everything else, researches just the relevant calls, and hands you a focused set of cards, which also keeps the credit spend proportional to what you actually need.
Catching What Connects Across the Day
Two of today's meetings involve the same at-risk account, and one has a renewal date approaching. The brief's closing watch-out line ties them together, surfacing the renewal clock and the slipping thread so you handle the day as a connected sequence rather than a set of isolated calls.
Skill Definition
The raw markdown Claude uses when this skill is invoked.
--- name: daily-brief description: Brief the user on their day. Pull today's (or a named day's) meetings and, for each, synthesize the current state of play, a suggested focus or objective, and any follow-ups needed. Uses browse_engagements for the schedule, then account_research, contact_research, and conversation_intelligence per meeting. Use when someone says "what's on my plate today", "brief me for my meetings", "prep my day", or wants a morning rundown before back-to-back calls. Because it researches every meeting, it can consume meaningful AI credits — it confirms scope before fanning out across a full day. --- # Daily Brief Give the user a fast, per-meeting rundown of their day: where each account stands, the one thing to drive, and what to follow up on. ## Prerequisites `browse_engagements` (the schedule) requires an active calendar/meeting integration; `conversation_intelligence` requires at least one connected meeting or email source. `account_research`, `contact_research`, and `conversation_intelligence` all consume AI credits, and this skill calls them once per meeting — so a full day of meetings can be credit-heavy. Confirm scope before fanning out (see Workflow step 2). If no integration is connected, report that and point the user to their ZoomInfo admin. ## Input Provided via `$ARGUMENTS`: - **Day** (optional) — defaults to today. "Tomorrow", "Monday", or a date all work. - **Filter** (optional) — e.g. "customer meetings only", "just external", a specific account. Defaults to external meetings (ones with non-colleague participants). ## Workflow 1. **Get the schedule.** Call `browse_engagements` with a window covering the target day (`engagementType: MEETINGS`, `sort: chronological`). Drop internal-only meetings (no external participants) unless the user asked for everything. 2. **Size it and confirm.** Count the external meetings. Each one fans out three AI-credit calls (`account_research`, `contact_research`, `conversation_intelligence`), so the spend adds up quickly — even a handful of meetings is a non-trivial number of AI credits. If there are more than a few (roughly 3+), tell the user the meeting count, note that each is researched with several AI-credit calls, and offer to scope down (external customer meetings only, the most important few, or a named subset) before proceeding. This pause keeps a packed calendar from turning into a large unprompted credit spend. 3. **Research each meeting (parallel, bounded).** For the in-scope meetings, fan out per meeting: `account_research` (kept light — this is a day view, not a full brief), `contact_research` for the attendees, and `conversation_intelligence` scoped to the account or the specific engagement for recent state and open items. Parallelize across meetings, but respect the volume you confirmed in step 2. Keep each CI query scoped to one account or engagement; CI cannot search by topic, filter by call type, or count mentions, and only reasons over the last few engagements — base each card on what it returns, not on it having full history. 4. **Synthesize one card per meeting.** Frame each around the single most useful outcome for that meeting. Pull follow-ups from prior commitments surfaced by CI. Do not pad cards with generic firmographics — lead with what changes how the user shows up. ## Output Format ### Your day — [N] meetings ([date]) For each meeting, in time order: **[time] · [title] — [account]** - **State of play**: 1-2 lines on where things stand (from CI + research). - **Focus**: the one outcome to drive in this meeting. - **Follow-ups**: open commitments or items to close, from prior conversations (or "none surfaced"). - **Who's in the room**: attendees with role, one line. Close with a single **Watch-outs** line across the day if anything connects (a renewal clock, a slipping deal, an exec sitting in) — only if it is evidence-based, not generic. ### When the day is empty or data is thin If no meetings are found, say the day looks clear (for the chosen filter) rather than erroring. For any meeting with no conversation data, base its card on research only and note that no prior-conversation context was available.
Created by
Rowan Bailey
Senior Director, Product
Provided by
ZoomInfo ↗Capabilities
- One card per meeting with state of play, focus, follow-ups, and attendees
- Pulls the day's schedule and defaults to external meetings
- Follow-ups drawn from prior commitments in recent conversations
- Confirms scope before fanning out to control credit spend
- Optional cross-day watch-out line when meetings connect