Hi Darryn,
Are you referring to capturing the Inbound Flow journey ?
I had some request for debug statements to be added, and used the set participant data to 'write' debug statements at different steps in the call flow. The information is retrievable from the conversation "attributes", using GET /api/v2/conversations/{conversationId}
If you are actually referring to menu options and the default menu choice, I had similar issue where we needed to capture the menu option entered by the caller.
Say there is a 3 options menu (1, 2, 3) and the default menu choice is "2". You can 'set participant data' the menu choice taken. However you cannot tell if the option '2' was actively selected by the caller or the default option. One possibility considered was to have the default option as '0' and build the task to then jump to the same task defined with option '2'. This allows you to capture the user journey and distinguish a menu choice from a default choice.
Hope this helps
Jean-Christophe
------------------------------
Jean-Christophe Poyelle
Foehn Ltd.
------------------------------