Use Case - Testing the engagement policies
2 Tasks
45 mins
Scenario
The Decisioning Architect imported the subscription, account, and product holding data that is required for unit testing through data jobs and manual import. The business team shared the following matrix for unit testing of the engagement policies. This matrix shows which actions are eligible for specific subscriptions.
|
Actions/Engagement Policy Matrix |
|||||
|
Selling/CrossSell |
Retention/ Mobile |
Selling/Up Sell |
|||
SubscriptionID |
ProtectYourDevice |
SamsunGalaxyBuds |
DownloadMobileApp |
AppleAirPodsPro |
EarlyUpgradeSpecial |
FreePremiumHandset |
1111111111 |
x |
x |
x |
|
|
|
2222222222 |
x |
|
|
x |
x |
|
2222222223 |
|
|
x |
x |
|
|
3333333333 |
x |
|
|
|
|
x |
4444444444 |
|
x |
x |
|
x |
|
5555555555 |
x |
x |
x |
|
|
|
5555555556 |
|
|
x |
x |
|
|
5555555557 |
|
x |
x |
|
|
x |
Detailed Tasks
1 Other details
- Use Customer Profile Viewer to verify that each subscription is able to receive the corresponding actions. If the subscription is not eligible for the specified actions, use the "Explain filtering by feature" view to identify the reason, and then manually update the data as necessary to ensure that the subscription becomes eligible for the action.
- Once the subscriptions meet the requirements and are eligible to receive the listed actions, create a new persona for the subscriptions by using Customer Profile Viewer. To create the test persona, use the following details:
- Direction: Inbound
- Channel: Web
- Real-Time container: Next best action
2 Acceptance criteria
- Each action is eligible for the corresponding subscriptions based on the table provided in the scenario.
- A persona is created for each subscription.
Available in the following mission:
Want to help us improve this content?