Dynamic JO needs the ability to auto-archive one-time programs

As an update, something like this (Eloqua has had it since AT LEAST 2017) where we can configure the the End Date is what I have in mind... There’s even a DEFAULT end date if one is not selected (3 months after the program launches). This is so participants are not brought in when they shouldn’t be.

Once the end date is reached, the campaign is switched to read-only.

As someone currently combing through hundreds of old one-time Programs which are still Active, I can personally attest to how much time this would save. It is NOT quick to review Programs one by one and identify the “dead” ones, and stop them. If these could be set to auto-stop after launch (esp in the case of csv sourced Programs, which are 99% one-time deals that can be stopped immediately after sending) it would make for a much cleaner experience for me and whoever replaces me one day.

Bringing this back up again, since it’s almost time for spring cleaning. Is this on the roadmap for dynamic JO? Being able to schedule a 1x program to automatically switch to “stopped” (and being able to configure the default number of days/weeks/months) after sending would be a big QoL update.

I would add that I want the option to flag as truly a one-time program vs something that I want to trigger now manually and potentially again sometime in the future. 

Oh man, this would be fantastic. Very similar to ​@kstim’s idea to have a column for shared reports (linked below). What would be amazing would be allowing admins to add columns with boolean fields and tags across the entirety of the Gainsight system, so we can filter for what is most valuable to us.

Like ​@gunjanm always says… don’t tell us how to do our business. 😂

Hey ​@revathimenon – could we get some eyes on this? Related to this other post – JO program cleanup is painful right now. Anything that could help would be welcomed!

Support and PS both clearly stated to us that deleting a program deletes it from AO Advanced Programs and orphans a bunch of data points, and that it’s essentially bad practice (unless it was UAT or similar) so it is quite a strange endeavor to want to delete a program.

And considering stopping a program impacts the ability to later clean-up objects it’s referencing, I’d be reticent to this becoming a thing. 

I heard an idea where you create a report of JOs/Programs that haven’t had any actions in the last X days (for example 90 days) and target those for review and Stoppage. Still very manual.

I’d be curious to hear how program admins currently manage the growing number of one-offs. (maybe even ​@dan_wiegert could chime in?)

My two cents: This would 100% be a great feature! It comes up frequently, and would save a bunch of time.

Best,

Ben Wanless

On it ​@dayn.johnson 

Fair points, ​@alizee – most of the programs I’ve been stopping are one-time sends, and I’m not deleting JOs (with the exception of test programs). The note about object cleanup is interesting – curious how that plays out, I haven’t seen that come up before in our instance.

My biggest pain point is the fact that we leverage JOs more heavily for one-time customer emails (enablement, product updates, newsletters, monthly CSM check-ins, etc.) – and the process of stopping those is pure busywork.

​@dayn.johnson and others - Thanks for sharing this. I wanted to acknowledge the feedback and let you know that we are considering introducing a completed status for one-time programs, as well as plans for archiving completed programs. Since this isn't in the near-term roadmap, I wouldn’t provide a specific timeline, but I will update the thread once development is confirmed.

Thank you ​@vmallya!

Fantastic news – having a similar function to how shared reports are set to expire after a set period of time would be a huge QoL update for those of us sending 10s of one-time programs every month (or quarter) so we would no longer have to go back and manually stop each one after engagement metrics were gathered.

This is a great idea, especially in light of information that there is a limit to the number of live programs we can have.