Skip to end of banner
Go to start of banner

Creating Spend Request Customer Event

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

What does this section cover?

Navigating to Spend Request Customer Event

CRM > CUSTOMER EVENTS > ACCESS CUSTOMER EVENTS

Explaining Spend Request Customer Event Fields 

Name

Description

NumberAn auto generated number that uniquely identifies the customer event
Type*Determines the business behavior of the customer event, it is set automatically by each process which is creating the customer event, and it can be one of the following:

  • Purchase

  • Referral

  • Web

  • Social Media

  • Achievement

  • Spend Request
ClassificationThe classification of the customer event, which can be optionally specified during the creation of the customer event.

Only the customer event classifications which are related with the specified customer event type, will be included in the list of available customer event classifications.

Life Cycle StateThe life cycle state of the customer event which can be posted or cancelled
Performed By Unit*The unit that initiated the customer event
Performed Date*The date that the customer event was actually performed
DescriptionA description of the customer event
Process Immediately

Defines if the customer event should be processed immediately by various business processes or not. By default, customer events are not processed immediately

Process Immediately will be checked (selected) and set to Read Only if the specific Customer Event type has been defined as to be Processed Immediately through the active Customer Events Definition

Purchase Customer Event*The purchase customer event which is requested to be settled by the specified spend request

Spend Amount

(Mandatory On Conditions)

AVAILABLE FROM CRM.COM R9

The amount that should be spend by the requested customer event.

This information is applicable and mandatory only if it is enabled through the active Customer Events Definition, through the spend request rules. In that case the spend amount defaults to the total purchase customer event amount, although it can be edited by users.

 

Creating & Saving, Validations & Restrictions

ActionValidations
Create

 Not Applicable

Save
  • The specified customer event classification is related to a customer event type that is the same type as the customer event's type
  • Mandatory Fields:
    • Type
    • Performed By Unit
    • Performed Date
  • All the rules which include the classification of the created spend request in their list of applicable classifications are retrieved
    • For each applicable rule
      • If the "Allow creating spend requests for specific amount is enabled" then
        • The spend amount on the spend request customer event is enabled
        • The spend amount defaults to the total purchase customer event amount, although users can modify it (through the UI or Web API)
        • The spend amount specified falls between the "Minimum Spend Request Amount" and "Maximum Spend Request Amount", if specified
      • If the "Reject Spend Requests if the Requested Spend Amount is not Covered" is enabled then
        • The system retrieves the wallet amount that can be spend based on the attributes of the spend request to be created
        • If a spend amount is specified on the spend request then
          • The spend amount should not be more than the wallet available amount.
        • If a spend amount is not specified on the spend request then
          • The purchase customer event amount (which is the amount that will be spend) should not be more than the wallet available amount.

 

Creating a Spend Request Customer Event

Spend request customer events are created whenever a customer requests to pay for a specific purchase customer event using his wallet. Spend request customer events can only be submitted against specific purchase customer events.

  1. Search using the criteria available in the summary page
  2. From the top menu click on the NEW and select Spend Request Customer Event 

  3. MAIN INFORMATION

    1. Provide required information
      1. Classification
      2. Purchase Customer Event
      3. Performed By Unit
      4. Performed Date
      5. Process Immediately
      6. Classification

      7. Spend Amount

        Spend Amount is allowed to be specified through the active Customer Events Definition, through the spend request rules

      8. Description

        The Total Spend Amount is automatically updated once the Spend Request Customer Event is Processed

         

        SPEND CUSTOMER EVENT

  4. From the Action Menu click on SAVE

  5. LOG INFORMATION

    The following information is automatically set by the system on saving the Spend Request Customer Event

    Log information section keeps all the logging information related to the specific record

    • Basic set of information available in all entities
      • Created By User: The user that created the entity
      • Created By Unit: The unit of the user that created the entity
      • Updated By User: The user that last updated the entity
      • Updated by Unit: The unit of the user that last updated the entity
      • Date Created: The date the account was entity
      • Date Updated: The date the account was last entity
        LOG DETAILS

Reward Related System Processing

 

Customer events can be directly linked to Rewards. 

If the created Customer Event is set to PROCESS IMMEDIATELY then the following steps will be executed immediately. If not, then the following steps will be executed during the Rewards Run 

Spend Requests are used to redeem awarded points and they must always be related to a specific Purchase Customer event. Rewards are awarded by adding money to the customer's wallet. 

This process is used to evaluate spend request customer events in order to decide if the specified amount can be spent or not. This process is applied before spending an awarded amount. The evaluation is applied based on the following steps: 

  • The reward participant's wallet is identified

  • The amount which is available to be spent is calculated based on the wallet allotments using the following information:

Visit Understanding Wallets to find more information regarding Wallets

    • The products that are specified in the spend request
    • The amount of money per each product
    • The date and time that the spend request was performed
    • The Unit that initiated the spend request
  • If there is an amount of money available then:

    • If the amount of money which is available per product is more than the requested amount then:

      • The requested amount per product is returned
    • Else
      • The amount of money which is available per product is returned

REWARD SPEND TRANSACTION 

Based on the Spend Request Customer Event and the related Purchase Customer Event the system may create a Reward Spend Transaction. This information will be available under REWARD SPEND TRANSACTION.

Spend Request Customer Event - Reward Spend Transaction

To find out more regarding Reward Spend Transactions visit Viewing & Cancelling Spend Rewards Transactions

Related Areas

Popular Labels

  • No labels