The ability to have smart sections. IE you click yes it opens up other questions, you click no it moves onto the next section without opening up the extra question sets?
User should also have ability to navigate between the different sections.
@Mike Emery: Wonderful
We're currently completing a review of our Journeys development backlog and have decided not to do this piece of development work right now. We'll communicate more with customers soon and tell you what we're focusing on instead.
@Mike Emery: Mike, just why I think about it. It would be very helpful to find some way of attaching action triggers to the answering/answer of certain conditional questions. I’m assuming you might be able to do that now based on today’s changes to journey data using filters, but this could be quite clunky depending on how many answers could drive triggers. Thanks
@Chris Jones: It's possible you'll be able to do that after the next release but just to make sure can you give us some examples of what you're trying to achieve?
@Mike Emery: hi, yes. I would imagine the journeys to now become something like a questionnaire/needs gathering. Generally the whole journey could gather answers for say 30 fields, but of those there might be 5 fields that contain information that would trigger an action such as send this email template, place to this lead group, assign to this user, create this sms. All of these things would typically happen in workflows now, but having the actions triggered based on answers in a journey would be a simpler and more structured way of handling actions on a customer journey basis. Thanks
@Mike Emery: Is there any way to look at formulas and calculations first before conditional questions - just because the sum or input of a formula might be something that then prompts the correct navigation to the next question/section? Otherwise I suspect you might need to develop something basic for answering questions and then look at it again at a later date for when there are sums/formulas? Great to see this progressing either way.
@Chris Jones: Yes, our current thinking is most definitely to look at support for calculations within a journey before we look at conditional routing. We'll be researching conditional routing and coming up with some designs in the next couple of weeks so it's a bit early for me to tell you exactly what will be possible.
@Mike Emery: Wonderful, thanks
yes yes yes please! :-)