We use SalesPad along with GP Dynamics. GP captures when a user is denied access when all seats are full. I plotted these denials and since our SalesPad & GP usage is similar this data provided a heatmap of when seats were likely to be exceeded (not just full). This information let's us know what days/times when to more carefully monitor for idle users/seat campers. If SalesPad cannot provide a usage log (revenue mitigator), perhaps a usage trending report would be an acceptable compromise. Additionally, it could send an alert when seat usage is approaching its limit and set it to alert more aggressively during maxxed out usage history. From Cavallo's POV, craft an admin report showing how purchasing additional seats would lessen blocked user events. Capture the timestamp when a user is initially blocked to when they ultimately were able to log in after another hopped out. That duration points to user inefficiency.