Skip to main content

Accounts View

Accounts View groups every Pod tied to a customer into a single Account, so Sales and CS can see a customer's full history in one place — plus Custom Statuses so every workspace can match its own CRM pipeline.

Written by Maddi Rose

💡 One home for every Pod tied to a customer, from first deal to renewal.


Accounts is a new layer that sits above your Pods and groups everything tied to one company into a single place. Pods are linked to each other via the parent account. Available across all plan tiers.


Alongside it, Customer Pods give Customer Success its own pod type for onboarding and BAU work, kept separate from Sales Pods which stay tied to deals. And Custom Statuses let every workspace build its own status names to match their CRM pipeline, instead of being stuck with our defaults.

Important: Every pod created before this release is treated as a Sales Pod. There's no conversion tool.

What's included

  • Accounts page - a new entry point listing every account created in trumpet, with an Owner column. Expand any account to see the pods underneath it. New pods link automatically to the right account when they share a CRM company object.

  • Account page - Pods tab - every pod under the account, with pod type, owner, status, created date, engagement score, last engagement, CRM source and stakeholder counts. A stats bar totals Total Pods, Active Pods, Total Signals and Last Engagement for the account, with a shortcut to the most recently active pod.

  • Pod Creation Wizard - creating a pod now asks for an Account and a Pod Type. Pod Type is set once at creation and inherited from the template, so it can't be changed afterwards.

  • Custom Statuses - every account is seeded with our usual four statuses (Draft, Active, Won, Lost), and workspaces can add as many custom statuses as they like to match their own CRM pipeline. Reverse mapping lets you choose which custom status trumpet or a CRM update should land a pod on. Manage these under Settings, Pods & Templates, Statuses.

  • New API endpoints and webhook - GET Custom Statuses and PATCH Pods on the public API, plus a new pod_status_changed webhook, so you can keep pod status in sync with your own CRM pipeline automatically. Full documentation at trumpetapp.dev.

  • Internal Pod page - an account's other pods now show inside the internal tab of any pod that belongs to it, so you can jump across an account without leaving the pod.

Why it's useful

A pod has always been built for one moment - the sales deal. But a customer's story doesn't end at closed won, and CS teams were stuck living in that same pod for onboarding, renewals and BAU, dragging old sales analytics along with them. There was no clean way to hand a pod from a sales owner to a CS owner, or to see the two sides separately.

↳ One home for every customer relationship

  • Stop piecing an account's history together across separate pods — see every deal, onboarding room and renewal tied to a company in one place.

↳ What this means for Sales

  • Handing a pod over to CS doesn't touch your reporting — closed won and closed lost stay exactly as they were.

  • You can still filter to your own historic pods without CS activity cluttering the view.

  • Your account now shows what happens after the deal closes too — useful context for renewal and expansion conversations.

↳ What this means for CS

  • Customer Pods finally give CS a pod that's tagged as theirs, not a repurposed sales pod still carrying old deal analytics.

  • Custom Statuses let you build lifecycle stages that reflect how you actually work — onboarding, live, renewal, whatever fits — instead of borrowing sales stages that never quite matched.

  • This is optional. If Sales and CS are already happy sharing one pod, you can keep doing that.

How to use it

  1. Create a pod as normal — the wizard now asks for an Account and a Pod Type.

  2. If the account already exists in trumpet, matching happens automatically off the CRM company object.

  3. Head to the new Accounts page to see every account and expand into its pods.

  4. Set up your custom status names and reverse mapping under Settings, Pods & Templates, Statuses.

Example use cases

CSM starting onboarding

Creates a Customer Pod straight from the wizard, linked to the account automatically.

AE checking account history

Opens the Accounts page, expands the account and sees every sales and customer pod tied to that company in one list.

Ops matching CRM pipeline

Goes into Settings and creates custom statuses that mirror their own CRM stages, mapping each one back to the internal status trumpet relies on, then uses the API and webhook to keep everything in sync automatically.

Good to know

  • Sales Pods keep their existing behaviour — Draft, Active, Won and Lost remain the defaults.

  • Every pod created before this release is treated as a Sales Pod. There's no conversion tool.

  • Account matching relies on your CRM company object only — domain matching was ruled out as unreliable (amazon.com, amazon.co.uk and amazon.ie would otherwise split into separate accounts).

  • If you're on Pipedrive, HubSpot or Salesforce, your existing pods have already been grouped into accounts based on the CRM company object. On other CRMs, this needs to be done manually — raise a request with us.

  • Without a CRM connected, you'll see a blank Accounts page and will need to add pods to accounts manually.

  • Accounts can't be deleted or archived in this release, so the account list will accumulate over time.

  • Filters on the Accounts page aren't available yet.

Did this answer your question?