Event communication

(% class="lead" %)

Communications triggered by events that happen in the Loymax system are classified as event communication.

The Loymax system can monitor events and respond to them. A complete list of available events is provided in the [[dedicated article>>doc:Main.Usage.MMP.Marketing.Offers.Event_catalog.WebHome]]. For these events, marketers can configure communication channels with LP Members.

5

6

The following types of event communication are available in the System:

== Communications triggered by in-store purchases ==

11

12

Communications with customers or LP Members during an in-store purchase are considered event communication. The system can be configured to deliver messages immediately after specific events occur at the point-of-sale checkout:

13

14

* **Discount calculation** — a customer made a purchase and received a discount on the receipt, product group, or individual product.

15

* **Bonus points calculation** — an LP Member performed an action that resulted in bonus points being accrued to their bonus account.

16

* **Deduction** — an LP Member redeemed bonus points from their loyalty card within the Loyalty Program.

17

* **Balance request** — an LP Member requested their balance at a POS terminal.

18

* **Card assigned** — a customer received an LP card.

19

* **Purchase completion** — a receipt was finalized.

20

* **Purchase by friend** — an LP Member who registered as a [[referral>>doc:Main.General_information.Loymax_Loyalty.Referral_system.WebHome]] made a purchase.

21

22

{{id name="anchor1"/}}The table below lists available communication methods for in-store purchase events:

23

24

(% class="table-bordered" %)

25

(% class="info" %)|**Messaging method**|**Action**|**Description**

26

|Message to receipt|[[Message to receipt>>doc:Main.Usage.MMP.Marketing.Offers.Action_catalog.Cheque_message.WebHome]]|(((

27

A predefined message appears on the customer’s receipt.

28

)))

29

|Cashier message|[[Cashier message>>doc:Main.Usage.MMP.Marketing.Offers.Action_catalog.Cashier_message.WebHome]]|(((

30

A predefined message appears on the cashier’s screen.

31

)))

32

|SMS|(% colspan="1" rowspan="5" %)[[{{id name="01"/}}Send message>>doc:Main.Usage.MMP.Marketing.Offers.Action_catalog.Message_sending.WebHome]]|(((

33

Short text-only messages are sent to LP Members’ phone numbers.

34

Delivery can be implemented via providers [[Devino Telecom>>https://devinotele.com/ru/?client_id=16647889331001047333]], [[SmsTraffic>>https://www.smstraffic.ru/]], [[StreamTelecom>>https://stream-telecom.ru/]], or using the [[SMPP protocol>>doc:Main.Installation_and_configuration.Extra_modules.Gateaway_and_proxy.Sms_gateways.Creating_SMPP_gateway.WebHome]].

35

)))

36

|Email|(((

37

Messages are sent to LP Members via email and may include formatted text, images, and links.

38

Delivery is handled through the [[Devino Telecom>>https://devinotele.com/ru/?client_id=16647889331001047333]] provider or via the [[SMTP protocol>>doc:Main.Installation_and_configuration.Extra_modules.Gateaway_and_proxy.Email_gateways.WebHome]].

39

)))

40

|Push|(((

41

Push notifications are delivered to smartphones of LP Members who have installed the LP’s mobile application. Messages may contain text only, image only, or both.

42

Delivery is performed via the [[Microsoft Azure>>doc:Main.Installation_and_configuration.Extra_modules.Gateaway_and_proxy.Push_gateways.Configuration_push_with_azure.WebHome]] messaging platform or through providers [[Firebase Cloud Messaging and Apple Push Notification>>doc:Main.Installation_and_configuration.Extra_modules.Gateaway_and_proxy.Push_gateways_FCM.WebHome]] and [[Huawei Mobile Services>>doc:Main.Installation_and_configuration.Extra_modules.Gateaway_and_proxy.Push_gateways_HMS.WebHome]].

43

)))

44

|Viber|(((

45

Instant messages are sent via Viber to LP Members registered on this messenger. Messages may contain text only, image only, text with a URL button, or text, image, and button combined.

46

Delivery is implemented via [[providers>>doc:Main.Installation_and_configuration.Extra_modules.Gateaway_and_proxy.Viber_gateways.WebHome]] Devino Telecom and SmsTraffic.

47

)))

48

|Social media|(((

49

Messages are sent to LP Members who have accounts on social media (e.g., VKontakte, Odnoklassniki, etc.). Messages may contain text only. Message templates must undergo prior moderation by the social media platform.

50

Delivery is implemented through providers Devino Telecom and SmsTraffic.

51

)))

52

53

(% class="box warningmessage" %)

54

(((

55

When using the [[Send message>>doc:Main.Usage.MMP.Marketing.Offers.Action_catalog.Message_sending.WebHome]] action, ensure that the relevant [[gateways>>doc:Main.Installation_and_configuration.Extra_modules.Gateaway_and_proxy.WebHome]] are configured in advance and that the corresponding [[plugins>>doc:Main.Installation_and_configuration.Extra_modules.Plugins_and_adapters.Plugins_list.WebHome||anchor="05"]] are installed.

56

)))

57

58

|(% style="border-color:#ffffff" %)(((

59

When configuring the **Message to receipt**, **Cashier message**, and **Send message** actions, you can use [[filters>>doc:Main.Usage.MMP.Marketing.Offers.Filters.WebHome]] and [[counters>>doc:Main.Usage.MMP.Marketing.Counters.WebHome]].

60

61

An example of a receipt message using [[metavariables>>doc:Main.Usage.MMP.Configurations.Notification_templates_and_metavariables.Structure_of_metavariables.WebHome]] is shown on the right. For more details on message templates and metavariables, refer to the corresponding [[section>>doc:Main.Usage.MMP.Configurations.Notification_templates_and_metavariables.WebHome]].

62

63

After substituting the appropriate metavariable values, the message will appear as follows:

(% class="box" %)

(((

##Your discount amount was 8 EUR.##

68

)))

69

)))|(% style="border-color:#ffffff; width:40%" %){{lightbox image="receipt_message.png" width="500"/}}

70

71

== Communications triggered by non-purchase LP actions ==

72

73

This type of communication is linked to specific actions performed by a customer or LP Member within the Loyalty Program, associated with the following events:

74

75

* **Card activation** — a customer registered, and their issued card changed to the **Activated** [[state>>doc:Main.General_information.CRM.Member_lifecycle.Client_state.WebHome]].

76

* **Registration completion** — a customer completed registration in the System.

77

* **Application form completion** — an LP Member filled out an additional section of their [[application form>>doc:Main.Usage.MMP.CRM.Clients.Customer_profile.Info.WebHome]].

78

* **Phone/email linking** — an LP Member linked and verified a phone number or email address to their LP account.

79

* **Mobile App installation** — a customer or LP Member installed the LP’s [[Mobile application>>doc:Main.General_information.Additional_services.Mobile_application.WebHome]].

80

* **Social media linking** — an LP Member linked their social media profile.

81

* **Social media activity** — an LP Member performed an action on social media (comment, repost, like).

82

* **Social media group joined** — an LP Member joined a social network group.

83

* **Social media activity removal** — an LP Member deleted comments, likes, or reposts from their page.

84

* **Social media group exit** — an LP Member left a social network group.

85

* **Inviting friend** — a customer or LP Member acted as a [[referrer>>doc:Main.General_information.Loymax_Loyalty.Referral_system.WebHome]], and their referral entered the unique friend code during registration.

86

* **Customer status change** — an LP Member’s [[status>>doc:Main.General_information.Loymax_Loyalty.Status_system.WebHome]] changed due to an [[offer>>doc:Main.Usage.MMP.Marketing.Offers.Offers_creation_examples.Offers_for_customer.Offers_from_members_status.WebHome]], a [[recurring task>>doc:Main.Installation_and_configuration.Extra_modules.Regular_tasks_setting.Setting_regular_task_for_setting_statuses_to_users.WebHome]], or another trigger.

87

* **Status calculation** — a status was assigned to an LP Member via a [[recurring task>>doc:Main.Installation_and_configuration.Extra_modules.Regular_tasks_setting.Status_assignment_event.WebHome]] or an offer with the [[Status assignment>>doc:Main.Usage.MMP.Marketing.Offers.Action_catalog.Status_assignment.WebHome]] action.

88

89

The [[messaging method>>doc:||anchor="01"]] for the above actions is configured in the Loymax Platform by [[creating an offer>>doc:Main.Usage.MMP.Marketing.Offers.General_information.Offers_life_cycle.Creating_offers.WebHome]] and selecting the [[Send message>>doc:Main.Usage.MMP.Marketing.Offers.Action_catalog.Message_sending.WebHome]] action for a specific [[event>>doc:Main.Usage.MMP.Marketing.Offers.Event_catalog.WebHome]]. When setting up this action, you can apply [[filters>>doc:Main.Usage.MMP.Marketing.Offers.Filters.WebHome]] and [[counters>>doc:Main.Usage.MMP.Marketing.Counters.WebHome]].

90

91

|(% style="border-color:#ffffff; width:60%" %)(((

92

After inserting the appropriate [[metavariable>>doc:Main.Usage.MMP.Configurations.Notification_templates_and_metavariables.Structure_of_metavariables.WebHome]] values, the message will appear as follows:

(% class="box" %)

(((

##Dear Homer Simpson, your bonus account balances are:

97

300 bonus points, 52 stars.##

98

)))

99

100

For more information on message templates and metavariables, see the relevant [[section>>path:/xwiki/bin/view/Main/%D0%98%D1%81%D0%BF%D0%BE%D0%BB%D1%8C%D0%B7%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D0%B5/%D0%90%D0%A0%D0%9C/%D0%9F%D0%B0%D0%BD%D0%B5%D0%BB%D1%8C%20%D0%B0%D0%B4%D0%BC%D0%B8%D0%BD%D0%B8%D1%81%D1%82%D1%80%D0%B0%D1%82%D0%BE%D1%80%D0%B0/%D0%A8%D0%B0%D0%B1%D0%BB%D0%BE%D0%BD%D1%8B%20%D0%B8%20%D0%BC%D0%B5%D1%82%D0%B0%D0%BF%D0%B5%D1%80%D0%B5%D0%BC%D0%B5%D0%BD%D0%BD%D1%8B%D0%B5/]].

101

)))|(% style="border-color:#ffffff; width:40%" %){{lightbox image="send_message.png" width="500"/}}

102

103

=== Examples of event communication ===

**Example 1**

A customer registers in the System. The registration date serves as the starting point. If the LP Member makes no purchase within two weeks, they receive a message encouraging them to shop at the Partner’s store. If no purchase occurs, a second reminder is sent two weeks later.

108

109

|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="event_communication_1.png" width="700"/}}

**Example 2**

A customer registers in the System. If the LP Member makes a purchase within the first two weeks—say, on day five—the next message is scheduled for two weeks after that purchase date.

114

115

|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="event_communication_2.png" width="700"/}}

116

117

{{showhide showmessage="Show examples of event communication use cases" hidemessage="Hide examples of event communication use cases"}}

118

(% class="table-bordered" style="width:auto" %)

119

(% class="info" %)|**No.**|**Description**|**Event triggering the message**|**Event canceling the message**

120

|1|LP Member makes their first purchase but doesn’t return to the store for two weeks.|Purchase completion|Purchase completion

121

|2|Customer links their phone number but doesn’t complete the application form.|Phone linking|Application form update

122

|3|LP Member doesn’t redeem bonus points from their card.|Purchase completion|Payment using bonus card

123

|4|LP Member links a social media profile but doesn’t engage in social mechanics.|Social profile linking|Social media activity

124

|5|Customer registers but doesn’t invite any referrals.|Registration completion|Friend invitation

125

|6|Customer installs the Mobile application but doesn’t register in the LP.|Mobile app installation|Registration completion

== Automatic notification about bonus activation ==

130

131

To notify LP Members about upcoming bonus activation, configure a [[recurring task>>doc:Main.Installation_and_configuration.Extra_modules.Regular_tasks_setting.Setting_regular_tasks_when_bonuses_activation.WebHome]]. This notification is set up once in the System. If an LP Member has at least the minimum number of bonus points (specified in the recurring task settings) scheduled to activate (become available for redemption) in the defined number of days, they will receive a notification via the selected communication channel, indicating the bonus amount to be activated. All [[communication channels>>doc:Main.Usage.Communications_ways.Non-event_communication.WebHome||anchor="mailing_types"]] used for non-event communication are available for this notification type.

132

133

Example notification using a [[metavariable>>doc:Main.Usage.MMP.Configurations.Notification_templates_and_metavariables.Structure_of_metavariables.WebHome]]:

(% class="box" %)

(((

##Your $Amount bonus points will activate in 1 day.##

138

)))

139

140

== Automatic notification about bonus expiration ==

141

142

To notify LP Members about expiring bonus points, configure a [[recurring task>>doc:Main.Installation_and_configuration.Extra_modules.Regular_tasks_setting.Setting_regular_tasks_when_bonuses_expire.WebHome]]. This notification is also configured once. If an LP Member has at least the minimum number of bonus points (as defined in the recurring task) scheduled to expire in the specified number of days, they will receive a notification via the selected channel, stating the amount. All [[communication channels>>doc:Main.Usage.Communications_ways.Non-event_communication.WebHome||anchor="mailing_types"]] used for non-event communication are available for this purpose.

143

144

Example notification using a [[metavariable>>doc:Main.Usage.MMP.Configurations.Notification_templates_and_metavariables.Structure_of_metavariables.WebHome]]:

(% class="box" %)

(((

##Your $Amount bonus points will expire in 3 days.##

149

)))

150

151

== Automatic birthday notification for LP Members ==

152

153

This notification type is used to congratulate LP Members on their birthday. Optionally, bonus points of any currency and lifetime can be accrued automatically.

154

155

All [[communication channels>>doc:Main.Usage.Communications_ways.Non-event_communication.WebHome||anchor="mailing_types"]] used for non-event communication are supported. Instructions for configuring this notification can be found in the [[relevant section>>doc:Main.Installation_and_configuration.Extra_modules.Regular_tasks_setting.Birthday_setting_regular_task.WebHome]].

Navigation

Wiki source code of Event communication