Using a sprint model means that we’re able to roll out smaller batches of changes more frequently, which means there’s plenty to keep up with! In case you missed it, the first sprint in this cycle was 30.1, and you can learn more about those features here<\/a>. If you’re wondering how we jumped ahead to 30.3, it’s because our 30.2 sprint was the SoGoSurvey to Sogolytics rebrand<\/a>! Maybe you noticed? \ud83d\ude09<\/p>\n We all love automation, and Rules & Alerts<\/a> and Raise A Dialogue<\/a> are two of our favorites. But what could make them better? Making them even more automatic, of course! Two great updates in this sprint:<\/p>\n Why would you ever want to copy existing rules? Plenty of reasons! Let’s say that you’ve set up a Rules & Alerts flow so that the management group at Branch A gets an email each time a customer provides a low rating of the service at Branch A. You spend time making a clear expectation-setting email, including nice piping and a link to the full response, and it looks great! But you also have three more branches, and you want to send similar messages to each relevant management group. Ta-da! Now you can make a copy of the Branch A rule and tweak it a bit to change the condition and recipient list! Even better: If you’re triggering a follow-up Dialogue through our SogoConnect ticketing system<\/a> instead, your Raise A Dialogue rule can be copied to send the right messages to the right teams to make it even easier to close the loop.<\/p>\n This one’s a huge time-saver, too, especially in CX projects or any forms or surveys that might be live for a long time. To use the same example above: Your customer service CX project is collecting great results, but you’d like to make a few changes to the content — adding new questions, removing existing items — without impacting any existing data. Still — groan! — you don’t want to have to recreate that entire set of Rules & Alerts workflows, right? Now you don’t have to! When you make a copy of your project, all valid Rules & Alerts will be copied, too! Keep in mind, if you’re making changes to the questions the rules are based on, this will obviously affect the rules, too, so be sure to double-check the impact of any changes in the new survey. And remember: If you’ve copied a CX project, the reporting Tags<\/a> will be copied, too, so data from the newly revised survey will still show up on your CX Dashboard<\/a>! On with the flow! \ud83d\ude09<\/p>\n Okay, this one doesn’t require a lot of explanation, but it does require a visual so you can see just how big it is!<\/p>\n “What happens next?” is a key question for everyone designing a survey. What should happen when your participants click Submit? These two updates offer great options!<\/p>\n URL redirect<\/a> has been around for a while (whether or not you’ve used it!) and its purpose is to send participants to a different site after they’ve submitted your survey. Who goes where? You might use a static redirect (sending everyone to the same site) or a dynamic redirect (sending different participants to different sites). Another choice: Should they see a Thank You page<\/a> or not? You might send participants to the new link right after they click Submit, or you might show them a Thank You page first. Here’s what’s new: If you choose to display this redirect button on a Thank You page, you can now customize the text of that button\u00a0to match your brand language style, set expectations, and well, just because you can. \ud83d\ude09<\/p>\n This one’s a bit different because it happens behind the scenes. If you use HTTP Targets (Not yet? Learn more!<\/a>) to push participants’ response data to other apps or tools you use, you can now raise your game by pushing scoring variables, too! Here’s a use case: The employee onboarding team wants to monitor how new hires are doing on their training assessments. HTTP Targets let them set a rule so that when new hires submit their exams, a notification pops up on the employee onboarding team Slack group to share the person’s details and score. If the team notices any concerns, they can discuss in the same Slack channel and coordinate any follow-up. Score!<\/p>\n Can we possibly say enough about how great Omni segmentation is? Well, we can try! \ud83d\ude09 From question-level segmentation<\/a> to report-level segmentation to segmentation in Omni Scores… segmentation gives us more to love in our own data!<\/p>\n Adding a Variable in segmentation<\/a> makes it easy to see the gaps between specific data sets. For example, if you’d like to see the change in a specific metric from 2021 to 2022, you can apply segmentation using the year question and add a simple calculation (2022 – 2021, in this case) to see the difference. Your report will clearly show the difference, and whether it’s positive or negative. Sound good? Apply this calculation and display to all of the questions in your report!<\/p>\nCopy that! Doubling up on automation<\/h2>\n
\n
![\"copy](\"https:\/\/www.sogolytics.com\/blog\/wp-content\/uploads\/2022\/09\/RNAGif.gif\")
<\/p>\n\n
Logic goes big!<\/h2>\n
\n
\n
![\"big](\"https:\/\/www.sogolytics.com\/blog\/wp-content\/uploads\/2022\/09\/LogicGif.gif\")
<\/p>\nWhat’s next? Post-submission options<\/h2>\n
\n
![\"URL](\"https:\/\/www.sogolytics.com\/blog\/wp-content\/uploads\/2022\/09\/RedirectGif.gif\")
<\/p>\n\n
More segmentation, please!<\/h2>\n
\n
![\"Omni](\"https:\/\/www.sogolytics.com\/blog\/wp-content\/uploads\/2022\/09\/SegmentGif.gif\")
<\/p>\n\n
ALSO<\/h2>\n
\n