|
Customers In-Allows you to specify that customers in a specific strategic segment can or cannot receive particular offers. For example, a financial institution might want to exclude credit offers to individuals with low credit ratings.
|
|
Interactions Where-Allows you to include or exclude specific transactions based on any attributes in the Proposed Contacts Table. For example, a retailer might want to exclude proposed transactions with a score less than or equal to zero from being delivered.
|
|
Min/Max # Offers-Offer capacity rule that allows you to specify a minimum or maximum number of offers to send over a rolling time period. For example, a telecommunications company might limit the number of free cell phone offers given in any 30-day period to 100,000.
|
|
Custom Capacity-Additional constraints you can specify based on an aggregation (sum or average) of a score field. For example, a bank giving out loan offers might specify that the average "risk score" must be below a certain threshold.
|
|
Min/Max # Offers-Offer capacity rule that allows you to specify a minimum or maximum number of offers to give to a particular segment on a channel over time. For example, a collectibles company might want to limit the dilution of multiple offers by targeting their best customers with at least 3 and at most 25 different offers in any given 30-day period.
|
|
Max # Packages-Contact-fatigue control that prevents over-communicating with customers by controlling the number of different packages (or interruptions) allowed to any recipient over a specified time period. For example, a hotel chain might want to limit the number of communications to their low value customers to a maximum of one per quarter.
|
|
Max # Duplicate Offers-Rule that controls the maximum number of times you present the same offer to the same recipient over a specified time period. For example, an online web retailer might want to present any given cross-sell offer a maximum of seven times to a web customer over a six-month period.
|
|
Never A with B-Offer-conflict resolution rule that prevents two conflicting offers (or sets of offers) from ever being given together within a specified time period. For example, a retailer might want to prevent a "$10 off a purchase of $100 on the web" offer and a "$20 off a purchase of $100 in-store" offer from going to the same individual within the same month.
|
|
Never A followed by B-Sequencing rule that prevents certain offers from following too closely after other offers. For example, a bank might want to ensure adequate spacing between sending a high-interest certificate of deposit (CD) offer to a customer after sending them a credit-limit decrease notification.
|
|
B only with A-Sequencing rule that specifies offer B might be sent only after offer A. For example, a mortgage company might specify that a call center representative might initiate a follow-up call only after the initial mortgage offer has been sent by direct mail.
|
Copyright IBM Corporation 2012. All Rights Reserved.
|