Storyline 2 Generate Email Support

When I was using Studio I used to be able to insert an object on the master slide (usually an envelope with a question mark on it), and set it up so when the object was clicked on from any slide it would generate an email. What was uber skookum about it was the subject line would auto fill with the course/module information. Then when a user had an issue they just had to identify which slide they were on and we could get in and fix any broken functionality or other problems that were identified.

I can't seem to find any info on how to do something similar in SL2. Ideally if it would pick up the slide as well (variables maybe?), but even if it was only the course it would be a huge help in troubleshooting.

4 Replies
Allain McCallum

Thanks Matthew, I think there is an assumed higher level of technical competency then what I am able to produce at this time lol.

Let's start with the very basics...where does one type or copy and paste said code? Am I opening up something in Storyline? Am I doing something in Outlook (default mail for our internal organization)? Am I doing something deep in the bowels of my machine registry fo0r which I will require admin permission/support? Or do I just jot it down on a word doc and my machine will magically know where to put everything?


I just want it to be mystical and magical for the user so they have a problem, click on a link, it opens an email with the name of the course and sends it to the correct body to resolve the issue.

Thanks for the time and help on this.

Matthew Bibby

Hi Allain,

No worries. You can add this code to an Execute JavaScript trigger in Storyline. You don't need to make any changes in outlook or your computer, nor will your users.

I suggest you have a read of this article which explains the best practices of working with JavaScript and Storyline. 

Once it is all set up, it will be mystical and magical for your users (in most cases). There are some email clients that don't respond well to this approach, but thankfully Outlook is not one of them!

Have a read through the best practices, then work through the example in the article I linked and that should cover everything you need to know. Don't worry, it's not as scary as it looks!

Maybe try and implement the most basic example (you can even download my .story file to get a closer look at how I set it up) and then we can build on that to customise it for your needs.

Anyway, let me know if you have any other questions or if you get stuck anywhere.