Besides the Parameter exposure and the easiness of debugging that the trigger redirect provides are there any other reasons to use this method?
Reporting. Some customers want to know what percentage of caller chose option 1 vs. 2 for example. There is no native way to accomplish this and one of the more common is to have a bunch of Triggers on the same applicatiion with Call Redirects at the various menu choices to other triggers. The beginning of the script has a Switch statement allowing the script to jump forward to where it left off (or some other way to continue on). The Application Summary report then shows how many contacts hit the various triggers.
The rule of thumb I use is this: if it's roughly a function (programming term) where I can pass in a few variables, have it do a thing, and then get a result AND it will be used across multiple scripts AND it's a fair amount of code (i.e. not three steps), then I use a subflow. ELSE I put it in the original script or do a redirect to another trigger. Subflows are a PITA to troubleshoot though. You *will* lose some hair before realizing that your subflow is why something isn't working.
Please remember to rate helpful responses and identify helpful or correct answers.
