Versions Compared

Key

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

Business Feature / Process

Description

Customer events

  • Support for

purchase
  • Purchase,

achievement,
  • Achievement and

referral eventsCustomer identification based on contact id
  • Referral events.

  • Contacts identified using a dynamically generated CRM.COM Wallet code (secure creation on contact request) or an OTP.

  • Optionally, other identification methods supported are contact identifier, contact code, CIM, gift card number

, OTP
  • .

Purchase Events

  • Captures the purchase basket in full, total amounts and SKUs. If SKUs do not exist in CRM.COM, then they are created.

  • Captures the organisation that submitted the event by matching to the organisation id or transaction acquire points

  • Support for multi-currency, if purchase in another currency, then purchase event converted to business currency.

  • Purchase event classification. If submitted and does not exist, then classification is created.

  • Net, total and tax amount handling. Support to input or be calculated

Two spend models. Payout-driven and POS driven
  • One-click to securely identify the contact at the POS via a QR- or barcode, OR One-click to identify and spend.

  • Optional spend request. Ability to specify that the spend is successful only if enough funds to cover the purchase.

  • Validate whether the OTP spend amount is the same with the explicit spend amount on purchase customer events

Transaction

processor

Processor purchase events

  • Transaction processors submitting events and routed to all businesses with the same transaction access points (terminals)

  • Transaction matching mode where the purchase is matched to one submitted by the POS

  • Transaction claim mode, where a customer claims the already submitted purchase via a self-service API

Purchase estimates

  • Estimates what if a purchase was submitted and provides the response

  • Ability to block wallet funds during purchase estimation and up until the purchase is eventually created

  • Ability to consumers to approve a purchase during estimation. Once the consumer accepts the purchase’s charges, then the same estimation id is used to create the purchase and is considered as approved by the consumer.

Achievement event

An event designating a customer achievement

Referral event

An event designating a referral by a contact for another contact. Max 2 per day allowed

Event utilities

  • Ability to void and list events

  • Ad hoc returns, where products are returned and reversed

Automations

Automations for Customers can be created based on the following trigger events:

  • Refer a Friend where a CRM.COM Communication is triggered to notify the person receiving the referral

In addition Automations can be utilised in order to create Purchase events on issuing an Invoice so as to map the invoiced items to purchased items.

Analytics

  • Dashboards: View summarised Customer Events numbers from the following dashboards:

    • Home

    • CRM Overview

    • Rewards Overview

  • Reports: View summarised and aggregated information for Customer Events performance in:

    • Customer Events Analysis

    • Organisations Purchase Events Analysis

    • Organisations Purchases Statement

    • B2B Spend Analysis

  • Insights: In-depth analytics of Customer Events:

    • Purchases

    • Achievements