Changes for page Event communication

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.zanina
	1	+XWiki.arylov

Content

...	...	@@ -1,7 +1,7 @@
1	1	(% class="lead" %)
2		-Communications triggered by events that happen in the Retail Engine system are classified as event communication.
	2	+Communications triggered by events that happen in the Loymax system are classified as event communication.
3	3
4		-The Retail Engine 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.
	4	+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	5
6	6	The following types of event communication are available in the System:
7	7
...	...	@@ -17,7 +17,7 @@
17	17	* **Balance request** — an LP Member requested their balance at a POS terminal.
18	18	* **Card assigned** — a customer received an LP card.
19	19	* **Purchase completion** — a receipt was finalized.
20		-* **Purchase by friend** — an LP Member who registered as a [[referral>>doc:Main.General_information.Retailengine_Loyalty.Referral_system.WebHome]] made a purchase.
	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	21
22	22	{{id name="anchor1"/}}The table below lists available communication methods for in-store purchase events:
23	23
...	...	@@ -82,11 +82,11 @@
82	82	* **Social media group joined** — an LP Member joined a social network group.
83	83	* **Social media activity removal** — an LP Member deleted comments, likes, or reposts from their page.
84	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.Retailengine_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.Retailengine_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.
	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	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	88
89		-The [[messaging method>>doc:||anchor="01"]] for the above actions is configured in the Retail Engine 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]].
	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	90
91	91	|(% style="border-color:#ffffff; width:60%" %)(((
92	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:
...	...	@@ -93,7 +93,7 @@
93	93
94	94	(% class="box" %)
95	95	(((
96		-##Dear Homer Simpson, your bonus account balances are:
	96	+##Dear participant Homer Simpson, your bonus account balances are:
97	97	300 bonus points, 52 stars.##
98	98	)))
99	99
...	...	@@ -104,21 +104,21 @@
104	104
105	105	**Example 1**
106	106
107		-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.
	107	+A customer registered 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	108
109		-|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="event_communication_1.png" width="700"/}}
	109	+|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Group 2_1.png" width="700"/}}
110	110
111	111	**Example 2**
112	112
113		-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.
	113	+A customer registered 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	114
115		-|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="event_communication_2.png" width="700"/}}
	115	+|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Group 1_1.png" width="700"/}}
116	116
117	117	{{showhide showmessage="Show examples of event communication use cases" hidemessage="Hide examples of event communication use cases"}}
118	118	(% class="table-bordered" style="width:auto" %)
119	119	(% class="info" %)|**No.**|**Description**|**Event triggering the message**|**Event canceling the message**
120	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
	121	+|2|Customer binds their phone number but doesn’t complete the application form.|Phone binding|Application form update
122	122	|3|LP Member doesn’t redeem bonus points from their card.|Purchase completion|Payment using bonus card
123	123	|4|LP Member links a social media profile but doesn’t engage in social mechanics.|Social profile linking|Social media activity
124	124	|5|Customer registers but doesn’t invite any referrals.|Registration completion|Friend invitation