This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Product | Feature | Notes |
|---|---|---|---|
| 06 JUL 2020 | Marketing | Prevent Sending Messages During Specified Hours | Updated document. Revised feature information. |
| 25 MAR 2020 | Created initial document. |
This document outlines the features in Oracle Adaptive Intelligent Apps for Customer Experience and describes any tasks you might need to perform for this service. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.
Give Us Feedback
We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_aiapps_doc_feedback_grp@oracle.com.
Column Definitions:
Features Delivered Enabled
Report = New or modified, Oracle-delivered, ready to run reports.
UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.
| Ready for Use by End Users Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features. |
Action is Needed BEFORE Use by End Users Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing. |
|||||
|---|---|---|---|---|---|---|
| Feature |
Report |
UI or |
UI or |
|
||
Oracle Adaptive Intelligent Apps for Marketing automatically predicts the best-performing combination of send-time and path for each customer. These predictions are based on interaction history, profiles, and content metadata to optimize marketing orchestration for a defined business metric.
Prevent Sending Messages During Specified Hours
You can now set restricted hours for the time periods when you don’t want to send marketing messages. Select your preferred time zone and then select the hours when you don’t want to send email, SMS, or push notifications.
This screenshot shows the Polices page where restricted hours are set from 20:00 to 07:00 for SMS and push messages for all days of the week.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- The restricted hours are based on the selected time zone. So let’s say you select 06:00 as the restricted hour with Los Angeles – Pacific Time as the time zone. You then change the time zone to London – Greenwich Mean Time. The restricted hour remains at 06:00 for the new time zone.
- You can only select one time zone for your restricted hours. If you have customers across multiple time zones, you might want to extend your restricted times to cover the desired times in all time zones.
- Selecting a single hour, for example 11:00, restricts all send times from 11:00:000 to 11:59:999.
Key Resources