Versions Compared

Old Version 5

changes.mady.by.user Persia Xenopoulou

Saved on

compared with

New Version Current

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Back to Customer Events Main Page

Excerpt
hiddentrue

Find out how to create a new View Spend Request Customer Event

What does this section cover?

Table of Contents
minLevel2

Navigating to Spend Request Customer Event

Info

CRM > CUSTOMER EVENTS > ACCESS CUSTOMER EVENTS

Explaining Spend Request Customer Event Fields 

Name

Description

Attributes

Spend Request Customer EventsImage Added

Attributes

An * indicates a field is mandatory.

Name

Description

Main Information
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
Customer Event.
ClassificationThe classification of the customer event, which can be Customer Event which is optionally specified during the creation of the customer eventEvent. Only the customer event classifications Only Customer Event Classifications which are related with the specified customer event type, will be Customer Event Type are included in the list of available customer event classificationsCustomer Event Classifications.
Life Cycle StateThe life cycle state Life Cycle State of the customer event Customer Event which can be posted or cancelled'Posted' or 'Cancelled'.
Performed By Unit*The unit  The Unit that initiated the customer eventCustomer Event.  i.e. Represents the Merchant who initiated the Event.
Performed Date*The date that the customer event was actually performedon which the Customer Event was performed.
DescriptionA description of the customer eventCustomer Event.
Process ImmediatelyDefines if the customer event Determines whether the Customer Event should be processed immediately immediately by various business business processes, or not. By default, customer events are not processed immediately  Not processed immediately is the default.
Process Immediately will be selected (checked) and set to Read-only, if the specific Customer Event Type has been defined through the 'Active' Customer Events Definition.
Purchase Customer Event*

The

purchase customer event which is requested to be settled by the specified spend request

 

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

 

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.

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

    • MAIN INFORMATION

    Provide required information
  • Classification
  • Purchase Customer Event
  • Performed By Unit
  • Performed Date
  • Process Immediately

    • Description

    Info

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

     

    Image Removed

  • From the Action Menu click on SAVE

    • LOG INFORMATION

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

    Include PageLog Information - GlobalLog Information - Global

    Reward Related System Processing

    Once the Customer event is saved, a number of steps will be executed by the system automatically that will have a direct effect to the Rewards Module.
    If the created Customer Event is set to PROCESS IMMEDIATELY then the following steps will be executed directly. If not then the following steps will be executed but only 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:

    Info

    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 TransactionImage Removed

    InfoTo find out more regarding Reward Spend Transactions visit Viewing Spend Rewards Transactions

    Purchase Customer Event which the specified Spend Request is used to settle.

    Note

    Participants can redeem their Awards by making a purchase (Purchase Customer Event).  The amount of the purchase will be deducted from their awarded points.

    Spend Amount

    (Mandatory On Conditions)

    Status
    colourRed
    titleAVAILABLE FROM CRM.COM R9

    The amount that should be spent by the requested Customer Event.

    This information is applicable and mandatory if it is enabled through the Spend Request rules of the 'Active' Customer Events Definition. In this case, the Spend Amount defaults to the Total Purchase Customer Event Amount but can be edited by users.

    Instant Spend

    Status
    colourGreen
    titleAvailable from CRM.COM R10.0.0

    Informs whether the Spend Request Customer Event was created instantly as a result of an instant spend Reward Offer.

    Note

    Instant Spend is a Read-only field set by the System.

    External System

    AVAILABLE FROM CRM.COM R10.0.0

    		Defines the third party system that generated the Customer Event and can only be set by the WEB APIs.

    External System Reference Number

    AVAILABLE FROM CRM.COM R10.0.0

    A reference number for the Customer Event that uniquely identifies the Event in the External System and CRM.COM.

    Spend Transaction
    Spend Transaction

    A transaction that may be created by the System based on the Spend Request and related Purchase Customer Event.

    Rules that may apply to the creation of the Reward Spend Transactions are configured in the Customer Event Definition.

    Log Information
    Log Information The standard set of Log Details information available in all entities. 
    Panel
    namegrey

    Related Areas

    Filter by label (Content by label)
    excerpt
    showLabelsfalse
    spacesV4Manual
    showSpacefalsetrue
    labelscustomer-events-basics-r7,customer-events-advanced-r7,customer-events-admin-r7

    Popular Labels

    heatmap
    Panel
    namegrey
    Popular Labels
    spaceKeyV4Manual
    style

    Helpful Links

    Filter by label (Content by label)
    showLabelsfalse
    spacesV4Manual
    showSpacefalse
    labelsglobal