Skip to main content

Posting this on behalf of a customer:

It would be great to have the ability to set the default time for the skippable step in the engagements. This could be an option to setup per product or subscription. For example: set the value to 100 milliseconds if there isn't a value greater than 0 set in the editor.

@srinivas myakala You were too fast! 🙂 Thank you for creating this.

 

The default value of 0 milliseconds cause unexpected consequences.

The only place that I could even find a screenshot of skippable value being set was the 2021 launch details.

 

Additional Context:

As our product changes we want to safe guard the engagement performance.

There are scenarios where a mapped element in an engagement won’t be available within the users UI. This could be due to customer account level licensing, enabled feature sets or because their activity didn’t present attributes to trigger UI elements. Honestly, the scenarios are endless.

By clicking “Enable Skippable” we can prevent the engagement from failing.

We also found another beneficial usage. We have a feature launching in a few weeks, we can setup the engagement to announce the new feature - and feel confident that the engagement will present the new step when the feature is launched.

 

 

 

 


The request should be to have the engagements have a default value for milliseconds greater than 0.

From support:

Search Time does need to be set to a value greater than 0. If it is not, it will default to waiting 30 seconds before skipping the step.


Honestly, or please just enhance the documentation to cover a better default value.


Reply