
Whose accounts
At the top of the summary, choose:- My accounts (the default) — the accounts you’re the CSM of, and every account inside a parent account you’re the CSM of.
- Whole organization — every account in your organization.
What you’ll see
Overview opens with the week’s numbers: the accounts that had activity, their MRR, the MRR on accounts at risk, and the meetings, messages and finished requests and tasks. Under them, the AI’s read on the week, this week’s priorities, what needs attention beside the wins, and the key meetings. Each account it names opens that account. On a wide screen, the accounts to watch sit to the right. Accounts lists every account in the summary, the ones at risk first, each with its one-line read, MRR, health score and trend, and how many meetings, messages and requests it had. Filter it by At risk, Concern, Stable or Healthy, and open Details on an account for its week, risks and blockers, what got done, and next steps.What it covers
For each account, the last seven days:- Meetings held that week. A meeting still to come isn’t counted as one that happened.
- Conversations across email, Help Scout and Slack, with the latest messages of each and whether your team or the customer wrote them
- Requests — every one still open, however long ago it was opened, plus those opened or closed that week, with any linked Linear issue and its state
- Tasks — open ones, with overdue ones marked, plus those created or completed that week
- Notes, NPS answers and status changes from that week
- Key dates within the next month, such as a renewal or trial end, with how far away they are
- Active risk and opportunity flags, leaving out any marked addressed or snoozed
- Who wrote last: how long since the customer wrote, and since your team did
- Health, and how it moved since the week before
Getting it by email
Turn on Weekly summary emails under Settings → Preferences. Delivery timing follows your organization’s setting, configured under organization settings. The email covers the last seven days. It opens with a one-line read on the week and up to three things to look at, then your active flags, open requests and open tasks, the meetings held and how long they took, how many messages customers and your team sent, and the requests and tasks opened and closed, each linked to Zudo. If you’re the CSM of any accounts, it covers those; otherwise it covers every account in your organization. Churned and ignored accounts are left out of both. If you would rather read it in the app, open Accounts, then the ⋮ menu at the top right, and choose Weekly Summary.Filtered summaries
Alongside the scheduled weekly run, you can generate a summary for a specific set of accounts — filter the Accounts list down to them, then choose Summarize Filtered from the ⋮ menu. This is the one to use before a QBR, a territory review, or a handover, where the question is about ten accounts rather than all of them. It reads the same things as the weekly summary. Every account you chose appears, and one with nothing that week says so rather than being dropped. Filtered summaries are cached per set of accounts, so asking for the same set twice in a morning does not regenerate it.Reading it over the API
The most recent weekly summary is available atGET /ai/weekly-summary, and over MCP as get_weekly_summary. Pass scope=mine or scope=organization for one in particular; without it you get the more recent of the two, and scope in the response says which.
It is read-only there: generation happens in the app and on the schedule, so an API caller reads what has already been produced. A status of none means nobody has generated one yet.
The summary is generated per person, not per organization — it reflects what you can see. Two people in the same
organization can legitimately get different summaries.
