This is standard for IVRs. Why it’s in the agent scripting studio but not the IVR studio is confusing. While we can do things through Javascript to accomplish the same outcome, it really does need its own node in IVR studio so that the call flow can be more easily understood without having to open up and analyze SCRIPTING nodes.A good example would be zip code routing. The GETINPUT node is simply going to look for five digits, not whether or not it's valid. The use case here would be for a JavaScript snippet to see if it's a valid zip code and then go to a loop node. If it was valid it routes it to a queue, if not then it loops back to the GETINPUT. After a couple times through the loop finishes and the caller is disconnected. Technically we can accomplish this now through JavaScript, but this would make it simpler and more easily visible and editable to the customer.