Skip to main content

Starting to use scheduled reports as a means of alerting Managers of CSMs to the existence of records that require their attention under certain scenarios, however when there are no records that meet the criteria, the system still sends out the report as scheduled which distracts the managers for nothing.

Really need to have a flag that gives option to suppress the send of the report if there are no records found.

 

When there are no records that meet the criteria, the system still sends out the report… really need to have a flag that gives option to suppress the send of the report if there are no records found.

 

100%.

Edited my original comment after @darkknight’s suggestion to make a separate post (here).


@dayn.johnson I would expect these sending mechanisms to be very different and encourage you to create a different idea for your use case so we don’t inadvertently conflate the two issues.


@dayn.johnson I would expect these sending mechanisms to be very different and encourage you to create a different idea for your use case so we don’t inadvertently conflate the two issues.

Done!

(edited my original response above)


This is a great idea.

We make pretty good use of scheduled reports.

However, we also have several managers with scheduled reports from all over our org flying at them. When they receive a report with the same exact data as the previous week, they can occasionally forget that they’ve taken action on the report results already and will begin a conversation anew, causing more work for all of our teams. 

 


This is a great idea.

We make pretty good use of scheduled reports.

However, we also have several managers with scheduled reports from all over our org flying at them. When they receive a report with the same exact data as the previous week, they can occasionally forget that they’ve taken action on the report results already and will begin a conversation anew, causing more work for all of our teams. 

 

100%, @dcassidy -- we’ve been taking stock of our internal enablement programs (especially as we’re looking at the emails that will need to be migrated to dynamic programs from advanced JO), and I’m planning to combine these reports or schedule them in a drip so we ensure we aren’t sending repeat information.

Thinking as we start migrating our internal programs, I’ll start sitting down with our different teams and charting out what scheduled reports they receive at what cadence, so I can start planning a better report delivery mechanism.

I’m starting to look more at team-oriented dashboards rather than single report-shares to make things easier to maintain down the road. From my perspective on the JO side of the house, updating report sharing seems easier within a JO query than through the scheduler tool in reports, especially since the schedules have to be deleted whenever they need to be modified.


@dayn.johnson I create team-oriented dashboards, currently. It’s been a tiny uphill battle to get everyone to understand filter usage, but they are being well-adopted. Something that we started in Q1 2024 is a monthly stand-up with each team we support. We meet with them, we look at their dashboard and reporting needs and continue to grow and iterate.


We need this as well.  We wanted a method to notify our CSM’s of specific Survey scores, or potentially when a new company is assigned to them or other notifications.  We have reports that show this but then that is up to them to check that report.  We wanted an email to generate to them but if the report has 0 records it still sends them the report which is pointless.  There are no filter conditions in the share report/link options where we can say “share report if count of X>0 or something like that”.


This would also be great for us. 

One of our scheduled reports is a table showing customers who churned and that are missing a post-churn analysis. A lot of the times this comes up empty but the user still has to click to know if that’s the case.