Who can use this feature?
- All roles with access level "high"
- Available on all plans
Common CS team structures
Here are three ways to structure your CSM teams to support high-touch, low-touch, and hybrid engagement models:
- Traditional: Individual customer success managers (CSMs) are assigned specific accounts to manage and build personal relationships (1:1).
- Scaled: Relies on both human and digital touches to engage with customers, allowing individual CSMs to effectively manage a large number of customer accounts while still providing personalized service (1:M).
- Pooled: Instead of dedicated CSMs, you have a pool of CSMs working together to serve a larger segment of customers. There's no single point of contact for each client; any CSM in the pool can be assigned to help a customer at a given time.
Both scaled and pooled team structures aim to manage customer success efficiently, but they approach it in different ways:
Scaled: Personalized CSMEach scaled CSM has their own (large) book of business, which is typically segmented by region, vertical or other commonalities. This approach offers a personalized experience but workload balancing and PTO coverage can be difficult. |
Pooled: Full coverageMultiple CSMs support a large pool of customers using a FIFO (first in, first out) queue. This approach ensures consistent coverage, but customers may not interact with the same CSM each time. A well-defined process and productivity monitoring are crucial for a consistent customer experience. |
Configure scaled / pooled structures in Catalyst
If you want to implement a low-touch engagement model, consider setting up the following team structures for a scaled or pooled approach.
1. Set up a shared "team user"
Within Catalyst, create a shared "team user." This is a user that's associated with a separate email, such as digitalsuccess@xyz.com
, for the purpose of managing scaled accounts.
Every Catalyst user must be able to log into your organization's email provider(Google/Microsoft). If you don't already have a "shared" email address set up within your email workspace, you'll need to create one before adding a Catalyst "team user.'
- Create a unique user profile for each team member.
- Create an additional user profile to represent the "team user."
2. Create a shared "team user" layout
Create a team dashboard to manage the shared book. Recommendations include:
- Display aggregates on health for pool team to target at-risk accounts and nurse them back to health
- Include a module to showcase the highest paying pooled accounts
- Add insight into recently-won renewals to understand what led to the win; create repeatable playbooks to keep momentum
- Add insights into ticket topics to understand the most common support case drivers; find patterns in the topics based on customer lifecycle / milestones to help create proactive communications.
3. Task management
In a pooled model (full coverage), consider using the following approach to task assignment:
- Leverage playbooks to create tasks for the "team user," such as activities related to renewals, at-risk indicators, or survey feedback.
- The task appears within a module on the scaled team dashboard. As scaled CSMs review the dashboard, they can open the task, and assign it to themselves for completion.
The process of taking ownership of tasks must be monitored closely, and we would recommend a task completion aggregate on the dashboard, to ensure there isn’t a large disparity between scaled CSM productivity.
4. Nurtured communications
Both scaled and pooled structures typically have an element of customer nurturing via proactive email messaging. Aligning a nurtured email campaign with the customer journey is a fantastic way to make a customer feel all the warm fuzzies with very little CSM lift. Considerations for a nurture campaigns include:
Lifecycle stages and milestones
- Welcome email once the customer has signed
- Proactive value email x months into the contract using timely best practices and enablement resources. (If possible, map support ticket data to customer tenure to help determine what resources to send and when.)
- Anniversary email for auto-renewal customers
- Adoption and productivity metrics
Seasonal communication
- Tax/payroll software emailing in November/December to offer educational piece on preparing for year end
- Best practices on how to scale efficiencies during economic downturn
- Preparing support ramp up for industry busy season
Communication on upcoming items
- New product releases, and what value they can offer
Webinar invites