Offer Notification Profiles

Notification profiles are reusable pricing components that define when expiration and recurring processing failure notifications are sent and the frequency with which those notifications are sent. Notification profiles can be assigned to each status in status life cycles. For a complete list of possible notifications, see the discussion about notifications in MATRIXX Integration.

For time-based offer status transitions, an advance notification advising of an upcoming transition is generated. The status definition's defined notification profile indicates when the advance notification should be generated.
Note: The notification profile should contain relative before entries in order for advance notifications to be generated.
The kinds of notification profiles are:
  • Expiration Notification Profiles — In My MATRIXX, expiration notification profiles can be assigned to balance, product offer, and bundle definitions for expiration notifications.

    Each expiration notification profile can be configured to send a notification on expiration and multiple notifications (minutes, hours, days, weeks, months, or years) before and after expiration. If the balance instance is periodic, a notification is triggered when the instance expires and when each period in the instance expires.

  • Recurring Processing Notification Profiles — Specifies how long before recurring processing a notification should be delivered. The notification is only delivered before recurring process is executed. Each recurring processing notification profile can be configured to multiple notifications (minutes, hours, days, weeks, months, or years) relative to the time that recurring processing begins.
  • Recurring Processing Failure Notification Profiles — In My MATRIXX, recurring processing failure notification profiles can be assigned to balance cycle templates and billing cycle templates.
    Each recurring processing failure notification profile can be configured to send a notification on failure and multiple notifications (minutes, hours, days, weeks, months, or years) relative to the time of the initial recurring failure for the period in which the failure occurred.
    Note: If recurring processing succeeds (for example, due to a product offer purchase) after a failure and before the time to generate the notification, then the notification is not generated.
  • Offer and Status Life Cycle State Change Notification Profiles — Status changes that occur in an offer or bundle can trigger status change notifications. Notifications can be generated for object status changes for devices, users, subscriptions, and groups on or before a status change as defined in the notification profile for the status life cycle. Notification profiles can be assigned to each status in status life cycles.
For more information about status life cycles, see the discussion about object status life cycles in MATRIXX Subscriber Management API.
You can create multiple notification profiles for use in different circumstances. The following are two examples of expiration notification profiles:
  • Offer Expiration (Multiple Prior)
    • Prior to Event 1 Month
    • Prior to Event 1 Week
    • Prior to Event 1 Day
    • On Event.

    This notification profile generates four notifications (three before expiration and one on expiration).

  • Balance Expiration (Multiple All)
    • Prior to Event 1 Week
    • Prior to Event 1 Day
    • Prior to Event 30 Minutes
    • On Event
    • After Event 1 Day

    This notification profile generates five notifications (three before expiration, one on expiration, and one after expiration).