| Excerpt | ||
|---|---|---|
| ||
|
What does this section cover?
| Table of Contents | ||
|---|---|---|
|
Segmentation
Tags and Examples should be added after tested
Communications - Interacting with other CRM.COM entities
Communicate Rewards Participants
- Navigate to Rewards Application > Rewards > Manage Rewards Participants
- Search for the Rewards Participant you would like to communicate to your customer
- Click on the Rewards Participant Number
The Rewards Participant Detail page will be displayed - From the Top menu click on Actions > Communicate Participant
- The Communication Detail page opens in a Modal window
The Contact Information is carried over
- The Referring Participant is set automatically
- Fill out the rest of the information as described at Creating Communications
- Click on Save
Communicate Award Reward Transactions
- Navigate to Rewards Application > Rewards > Manage Award Transactions
- Search for the Award Transaction you would like to communicate to your customer
- Click on the Award Transaction Number
The Award Transaction Detail page will be displayed - From the Top menu click on Actions > Communicate Award Transaction
- The Communication Detail page opens in a Modal window
The Contact Information is carried over
- The Referring Award Transaction is set automatically
- Fill out the rest of the information as described at Creating Communications
- Click on Save
Communicate Spend Reward Transactions
- Navigate to Rewards Application > Rewards > Manage Spend Transactions
- Search for the Spend Transaction you would like to communicate to your customer
- Click on the Spend Transaction Number
The Spend Transaction Detail page will be displayed - From the Top menu click on Actions > Communicate Spend Transaction
- The Communication Detail page opens in a Modal window
The Contact Information is carried over - The Referring Award Transaction is set automatically
- Fill out the rest of the information as described at Creating Communications
- Click on Save
Communications - Using Communication Tags
| Anchor | ||||
|---|---|---|---|---|
|
Rewards participants tags can be used only if a Rewards Participant is specified in the referring to section of the communication
| Tag | Value |
|---|---|
#rewards_participant.number | The number of the related rewards participant |
#rewards_participant.sign_up_on | The date that the related rewards participant signed up |
#rewards_participant.sign_up_by_unit | The unit that signed up the related rewards participant |
| #rewards_participant.accounts_receivable | Accounts Receivable object. Any accounts receivable tag can be used as long as you do not call another object from accounts_receivable. For example #rewards_participant.accounts_receivable.name is acceptable but #rewards_participant.accounts_receivable.contact_information.name is not acceptable |
| Anchor | ||||
|---|---|---|---|---|
|
Award reward transaction tags can be used only if an award reward transaction is specified in the referring to section of the communication
| Tag | Value |
|---|---|
#award_reward_transaction.number | The number of the related award reward transaction |
#award_reward_transaction.amount | The amount of the related award reward transaction |
#award_reward_transaction.offer | The offer that was awarded by the related award reward transaction |
#award_reward_transaction.date | The date that the award reward transaction was submitted |
#award_reward_transaction.rewards_participant | Rewards participant object. Any rewards participant object tag can be used as long as you do not call another object from rewards_participants. For example #award_reward_transaction.rewards_participant.number is acceptable, but #award_reward_transaction.rewards_participant.accounts_receivable.name is not acceptable |
| Anchor | ||||
|---|---|---|---|---|
|
Spend reward transaction tags can be used only if a spend reward transaction is specified in the referring to section of the communication
| Tag | Value |
|---|---|
#spend_reward_transaction.number | The number of the related spend reward transaction |
#spend_reward_transaction.total_amount | The total amount of the related spend reward transaction |
#spend_reward_transaction.date | The date that the spend reward transaction was spend |
#spend_reward_transaction.date | The unit on which the spend reward transaction was spend |
#spend_reward_transaction.rewards_participant | Rewards participant object. Any rewards participant object tag can be used as long as you do not call another object from rewards_participants. For example #spend_reward_transaction.rewards_participant.number is acceptable, but #spend_reward_transaction.rewards_participant.accounts_receivable.number is not acceptable |
Communication Centre
Rewards
This section provides a snapshot of most important rewards information. The following information is displayed upon selection.
- Participating reward schemes - Displays all the reward schemes that the selected customer is participating to and the date and unit that signed up the customer, to each one of the reward schemes
- Award reward transactions - Displays all award reward transactions that were submitted by the selected customer along with information related with the wallet transaction that was triggered by each award reward transaction
- Spend reward transactions - Displays all spend reward transactions that were submitted by the selected customer along with information related with the wallet transaction that was triggered by each spend reward transaction
Wallets
Wallets Definition
The following causes should be added in Wallet Definitions
- Causes Debiting Wallets: The "On spend reward transactions" cause should be added. On enabling it, a debit wallet transaction of the specified type will be created each time a spend reward transaction is created
- Causes Crediting Wallets: The "On award reward transactions" cause should be added. On enabling it, a credit wallet transaction of the specified type will be created each time an award reward transaction is created
- Causes Creating Wallets: The "On using accounts receivable in rewards participant" cause should be added. On enabling it, a wallet will be created each time an accounts receivable not related with an effective wallet is associated with a rewards participant
Wallet Transactions Allotments
Wallet Transaction Allotments should be enhanced as described below:
- Each wallet transaction allotment should include the following
- Allotment amount: The amount which is allotted to the specified conditions. All conditions are optional, but at least one condition should be specified per each allotment
- Consumption Validity Date: It defines the date that the allotment can be consumed. If specified then the allotment will not be possible to be consumed before that date
- Product Conditions: The products that can consume the allotted amount. If more than one product is specified then the allotment amount can be consumed by any of those products
- Organisational Unit Conditions: The organisational units that can consume the allotted amount. Units or Groups can be specified in the conditions. If more than one organisational unit is specified then the allotment amount can be consumed by any of those organisational units
- Date Conditions: The date conditions during which the allotted amount can be consumed. If more than one date condition is specified then at least one of them should be met in order to consume the allotted amount.
- Time Conditions: The time conditions during which the allotted amount can be consumed. If more than one time condition is specified then at least one of them should be met in order to consume the allotted amount.
| Panel | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
Related Areas
|
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Popular Labels
|
| Include Page | ||||
|---|---|---|---|---|
|