Skip to main content
A customer is often more than one account. One publisher might have an account per product or per platform, each with its own IDs, billing and usage. A parent account groups them so you can work with the customer as a whole. The accounts inside a parent keep everything they have. Their IDs, MRR, contacts, health scores and activity stay on them, and integrations keep syncing to them as before. The parent account adds a view on top.

​
Create a parent account

  1. Open one of the customer’s accounts.
  2. In the actions menu (⋯), choose Create parent account.
  3. Name it. The name starts as the account’s name.
The account you started from becomes the parent’s first account.

​
Add an account to a parent account

  1. Open the account.
  2. In the actions menu, choose Add to parent account.
  3. Search for the parent account and select it.
An account belongs to one parent account at a time. If it’s already in one, the menu item reads Move to another parent account, and Zudo shows which parent it will leave before you confirm. To take an account out, choose Remove from parent name in its actions menu, or Remove next to it in the parent account’s list of accounts. If your organization has CSM auto-assignment rules, a new parent account gets a CSM from them, judged on its accounts’ combined MRR.

​
Find a parent account

Parent accounts show up in the command palette (⌘/ or Ctrl+/) and wherever you pick an account, such as when adding a request, meeting or task. When an account inside a parent matches your search, it’s listed indented under its parent. When a parent account matches, its accounts are listed under it.

​
Add records to a parent account

Requests, meetings, tasks, emails, notes and files can be added to a parent account itself, for things that concern the whole customer. They appear on the parent’s timeline alongside its accounts’ activity. A request linked to a parent account counts the parent’s accounts in its impact score. If a request is linked to both a parent account and one of its accounts, that account’s MRR is counted once.

​
What a parent account shows

  • Accounts in the parent: each account’s status, MRR and health score, with a link to it.
  • MRR: the total MRR of its active accounts. Churned and inactive accounts stay in the parent but don’t count toward its MRR. The total updates when an account’s MRR or status changes, or when an account is added, removed or deleted. If you edit MRR on the parent account, your figure is used instead until you clear it.
  • Timeline: meetings, emails, tasks, requests, notes and files from every account in the parent, plus anything logged on the parent itself. Items from an account in the parent are labeled with that account’s name.
  • Contacts: the contacts of every account in the parent.
Each account’s page shows Part of parent name under its name, linking to the parent.

​
Accounts list

The Accounts page has two views: Total MRR is correct in both views. Parent account rows show how many accounts they contain. In the Customers view, filtering by a segment keeps a parent account when any of its accounts is in the segment. A filtered summary run from the Customers view summarises each parent account using its accounts’ meetings, emails, requests, tasks and notes, and counts each customer’s MRR once.

​
Current limits

Parent accounts are new, and some parts of Zudo still work only with individual accounts:
  • Health scores, indicators, product events and traits are calculated for each account, not for the parent account. Setting a CSM Pulse on a parent account saves the pulse but doesn’t calculate a health score from it.
  • Trait and indicator filters on the Accounts page judge a parent account on its own values, which are usually empty.
  • Meeting Prep, Account Summary, AI Pulse and account search on a parent account use only what’s logged on the parent itself, not its accounts’ activity.
  • Segments, the renewal pipeline, dashboards and reporting count individual accounts. A parent account isn’t counted separately, so totals don’t double.
  • Alerts go to each account’s own CSM, not the parent account’s CSM.
  • The API and MCP tools return only a parent account’s own records, not its accounts’.
Deleting a parent account doesn’t delete its accounts. They become standalone accounts again.

​
Daily and weekly emails

If you’re the CSM of a parent account, your daily follow-up digest and daily and weekly summary emails include every account in it, even ones assigned to someone else.

​
API

The REST API and MCP tools support parent accounts:
  • Accounts include isRollup (true for a parent account) and parentAccountId. GET /accounts/{accountId} also returns memberAccounts.
  • GET /accounts takes level: accounts (the default, every account except parent accounts), customers or parents. Filter to one parent’s accounts with parentAccountId.
  • POST /accounts with isRollup: true creates a parent account, optionally with memberAccountIds.
  • PATCH /accounts/{accountId} with parentAccountId adds the account to a parent, or removes it with null. Set moveFromCurrentParent: true to move an account that’s already in another parent.