Loyalty And Voucher Management
(Doc ID 1267211.1)
Last updated on NOVEMBER 05, 2018
Applies to:Siebel Loyalty Engine - Version 126.96.36.199 SIA and later
Information in this document applies to any platform.
Customer was aware of the following functionality of Loyalty vouchers:
Giving Vouchers to Members
Member service representatives can give vouchers to members for a number of reasons, depending on your business model. For example, if a flight was delayed, all members on that flight might get a voucher for an upgrade on a future flight.
These are created in the application against a member and added as a voucher in the 'Voucher' child view and as part of the Loyalty program. These can also be automated upon items such as a change of tier reward.
Once the voucher has been given to the member, this can be 'spent'. This can be done by using a Voucher
Vouchers are used by associating them with a transaction. Members can use two types of vouchers:
- A specific voucher. The member presents a voucher with a unique identifier, the voucher number.
- A generic voucher type. The member does not present a specific voucher number, but instead makes Siebel Loyalty use one or more vouchers of some general voucher type. For example, an airline customer can have Siebel Loyalty use three 500 mile upgrade vouchers. When the member uses a generic voucher type, Siebel Loyalty automatically uses the vouchers that are closest to expiring.
Members can use vouchers with either an accrual transaction (for example, by using upgrade vouchers on airline flight) or a redemption transaction (for example, by using vouchers to get a free hotel stay).
A voucher can therefore be given automatically and used to redeem against a specific product.
Customer asked if the Loyalty voucher could be tracked as products are in other verticals with relation to the quantity given, the products redeemed against and the attributes of the vouchers saved.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|