Release Date: Feb 12, 2019

New Features

  • Tier Downgrade on points earned: In addition to downgrade tier on number of visits and purchases, now tier can be downgraded on points earned. This validation is useful for brands that use points earned during a period as a measure of engagement or retention.

  • Tier Downgrade on return: In Tier Downgrade, a new option 'Enable downgrade check on return' is introduced. If this option is enabled, when a customer returns a transaction for which his/her tier is upgraded,  the tier will be downgraded automatically.

When a customer returns a bill, Loyalty first identifies if the customer is eligible for downgrade.  If yes, the tier downgrade condition is evaluated at the end of the day.

If for a customer, tier downgrade condition is satisfied, irrespective of the tier downgrade criteria set - Any lower tier or Lowest tier - tier will be downgraded only to one lower tier.
  • Eligibility for downgrade check:
    • The loyalty program has a tier upgrade strategy on the basis of either lifetime purchases, lifetime points, or current points and the customer's tier is upgraded only on this condition. 
    • The customer's lifetime purchases, lifetime points, or current points computed after return should be less than the tier upgrade threshold set for the current tier.
    • The original transaction date is in between the last two tier change dates. For example, if the current tier is Tier 4, the bill date should be between the Tier 3 and Tier 4. If the customer is in any other tier, the downgrade check will not be performed.
    • The bill on which the tier is upgraded
  • Downgrade check:
    • The condition or values are evaluated for the period between last tier change date and tier expiry period. For example, assume a tier expiry period is set for 12 months. If a customer returned a bill on Jan 25, 2018, the tier expiry condition is calculated for 12 months until the return date -  Jan 25, 2017 - Jan 25, 2018.
  • Rules on bill-level Tender Modes: Until this release, tender mode expressions were supported only with tender unroller and could not be possible to include or exclude an entire bill. 

Loyalty now supports rule expressions on bill level tender modes. These expressions could be used to include or exclude a bill from being processed, and calculate the amount paid through a specific tender at the bill level.

Some sample use cases on where you can use this feature: 

  • No points allocation on bills that have credit note as one of the tenders.
  • Additional points allocation on bills for payments through a particular bank's credit card.
  • Points allocations on bills that have bill value, excluding credit note amount, more than 1000.

New expressions based on tender  modes (TransactionAdd event):

  • currentTxn.tenderCombinationIncludes - Usage currentTxn.tenderCombinationIncludes("points")
  • currentTxn.tenderCombinationExcludes - Usage currentTxn.tenderCombinationExcludes("credit")
  • currentTxn.tenderCombinationRegexSum - Usage currentTxn.tenderCombinationRegexSum("credit.*")>100
These expressions cannot be used on bill level rules, that is, before item unroller or tender unroller.
  • Domain and Sender ID Selection in Emails: All Domains and sender IDs configured for the org (in InTouch Settings > Communications & Gateways > Domains > Configure Domains) will appear in the drop-down box while configuring email templates. A user can directly select from the available options instead of entering manually.

 Domain and Sender ID Configuration Screen

Option to select domain and Sender ID while configuring email templates

Also emails are sent including the details Sender ID and Sender Name