Watch this Ask the Expert session to learn how you can use scheduled journeys to optimize your marketing campaigns.    Watch the Webinar   You will learn more about: Typical use cases that can best be achieved through scheduled journeys. How to turn existing segments into target audiences. Mapping out a typical multi-wave campaign as a SAS Customer Intelligence 360 scheduled journey.   The questions from the Q&A segment held at the end of the webinar are listed below and the slides from the webinar are attached.   Q&A How should audience attributes that have changed since creation of the audience be handled (e.g., consent revoked, mobile number changed, etc.)? // How to handle changing customer attributes during the journey? For example, customer was in segment on the 20th, opts out on day 3. Or customer changes "value" (high/medium). There are two types of attribute changes that have been touched on here. One is opting out or revoking consent. For example, as a customer, if I opt out, it means I want to be removed from those communications and therefore it is no longer appropriate for me to be in that journey because I have decided I do not want to subscribe to your emails. This would typically be handled through drop conditions. You can set up key events as drop conditions that indicate it is no longer appropriate for the customer to remain in the journey. Opting out is a classic example.   The second type of change is when the customer updates their value or other attributes, and you want the journey to reflect those changes. Currently, this is not possible—the attributes are static for the duration of the journey. Whatever the attributes were when the journey started on day 5, they remain the same regardless of any changes in the customer’s real-world status. However, this will change and the ability to refresh your audience’s attributes within the journey is on the roadmap and expected sometime during 2026.   What if tasks in the journey should be suppressed from sending messages during a certain period, e.g., over night? You would handle this via a combination of the journey scheduling and Wait Node options. The journey scheduling controls when the journey starts each occurrence – for example, 12:00 UTC (or whichever timezone your tenant is using). This controls when the first task is sent. Subsequent tasks’ timing is controlled by the Wait nodes. These allow you to control how long you give the customer to receive, read and act upon your communication before you take the next action. Typically, you will want to use the “Relative amount of time” or “Relative days of the week” options. If the relative time is more than 24hours, then both settings allow you to specify the time the Wait node should release customers – again allowing you to control when customers receive your messages. Where users may need to consider timing is using hour wait periods for the “Relative amount of time” option. In this scenario, it is possible for the settings for Wait Nodes over the course of the journey to result in releasing tasks during desired ‘quiet time’ and users should draw out the proposed journey and work through the likely task release timings as part of their overall Scheduled Journey design and build work.   If we don't have migrated channels within SAS CI360, how we can extract data to .xls files? I'm not sure I fully understand your question but let me answer it this way to see if it addresses it. If you are using direct marketing tasks, and I'm guessing at the intent here—so apologies if I've misunderstood—they are on the roadmap and expected sometime during 2026. In the meantime, you can use a custom task. We have a custom bulk task that you can use to integrate with any channel, so whatever export file you would use for a direct marketing task, you can use the custom bulk task to send it to the same integration point, as I did for telemarketing in my journey. I used a custom bulk task to integrate with the telemarketing system.   If your question is about the other scenario—where you are not using segments, but rather external targeting with a list of customers, such as a CSV file, that is external to 360—you can use the audience API to bring that list in and create an audience from it. Just as I did with audiences created from a segment and a segment map, you can use an API to upload your external customer list or CSV file and load it into 360 as an audience. Hopefully, this answers your question from one end or the other.   In your demo, on the first split, you had clicked, opened but not clicked or not opened, and remainder. What would the remainder be for that one?  Whether you include a remainder or not is an interesting topic. The remainder is, in my opinion, a safety option for whatever is left at the end. Typically, you want customers to follow different paths based on their actions, so each of those paths is defined in the split node—such as clicked, opened, didn’t open, etc. The remainder is essentially a catch-all for anyone not covered by the other paths. Obviously in that split no customers should end up in the remainder, but it allows for the unexpected case when, either due to data issues or an unusual customer action, a customer ends up there.   That’s usually how I build a customer journey: I design it so that every expected customer action I want to address is accounted for. Looking back at my example, the remainder was simply a catch-all for anyone who reached that point without taking the expected actions. I ended the journey for anyone in the remainder, making it a safety net.   Alternatively, you can rename the Remainder to be a specific path. So, in my example, path 1 might be email clicked & remainder could be, by default "Did not click".   Both approaches are equally valid.   What is the difference between a CI 360 scheduled journey and real-time journey? A real-time journey is designed for situations where you need to respond to the customer in the moment. It involves interacting with customers on an individual level; for example, if a customer clicks on the website, you can instantly respond and provide information related to their actions. Another example is when a customer abandons their cart—you may want to follow up within the hour to ask why they didn’t complete their purchase or send a polite reminder. Real-time journeys focus on immediate, one-to-one reactions to customer interactions.   Scheduled journeys, on the other hand, are when immediate timing doesn’t matter. These involve scheduled communication flows such as onboarding or reactivation campaigns.   The key difference is that real-time journeys provide individual responses to customer actions, while scheduled journeys deliver group communications according to a set timetable.   How do I avoid a customer getting multiple journeys all at the same time? For that you would use entry criteria which you’ll find in Journey Conditions as per this slide:     In my explanation of entry limits, I mentioned that you can prevent someone from re-entering the journey within three months or restrict them to entering a particular journey only once. Additionally, you can specify that a person is allowed into this journey only if they are not already participating in another journey. This allows you to manage it so that customers are only in one journey at a time. That is how you achieve this—by setting entry limits.     Recommended Resources SAS Learning Subscription for CI SAS Communities Library for CI SAS Support Community for CI Please see additional resources in the attached slide deck.   Want more tips? Be sure to subscribe to the Ask the Expert board to receive follow up Q&A, slides and recordings from other SAS Ask the Expert webinars. ... View more