Awesome use case, @Brittney Wilson.

There are a few ways to do this, and I’ll float one here. As for assumptions, I am assuming you have user-level usage data which also has a Company identifier of some sort. Your rule setup will pull in the usage data from the MDA object it’s stored within. At minimum, you’ll want:

Show Me:

• DISTINCT COUNT of Users (ideally a User ID, or alternatively a user email or username)

Group By:

• Company GSID
• Company Name (not required, but sure will make your rule easier to follow later)
• Company → CSM GSID (you’ll need this so you have a GSID to assign the CTA to)

Then Create a CTA for those Companies where the DISTINCT COUNT of Users = 1.

To consider:

• A date filter may be helpful here, like Last 7 Days or Last 30 Days. Without that, you’ll get the number of unique users all-time, which would mask your customers where there previously where many users, but recently are far fewer.
• For the future, you could iterate further by filtering for certain actions. Maybe you have many users logging in, but there’s a key feature or action that really unlocks the value of your product. By filtering for that feature, your CS org can identify more customers who are at risk and could use some help or nudging.

There are plenty of variations you could play with too, but the above should get you started. Good luck, and let us know how it goes.

@matthew_lind Thanks for the quick and helpful reply! I’m going to play around with this and try it out. 

Something else to consider. I personally shy away from ‘notification’ type CTAs as they tend to clog up the works and lower the overall value for CTAs as a feature. Unless there’s something for the end user to actually do, you’re better off solving your business need some other way.

For example: If logins is baked into your health scores, you should modify the score for this scenario. If only one user is dominating the logins, then the score would be lower, and you can leave a scorecard comment indicating what is going on. We had something like this at a previous company where we were trying to drive multiple users to log in consistently. Can’t have that one power user leave the company and you’re left with nobody using your platform, right?

And/or, you could create a report that shows a leaderboard for logins. That way the CSM is very aware of who is logging in and when. Could do this in the C/R360 and/or on CSM dashboards.

@jason_metzler Thanks for the reply and recommendation I’m going to test this out as logins are baked into our health score so this makes a ton of sense. Thank you!