Loymax, 2026

Wiki source code of 3.3. Actions

version	line-number	content
74.1	1	Action is an activity that Smart Communications must perform on a [[customer profile>>doc:Main.Smart_Communications.SMC_Use.Customers.All_clients.WebHome\|\|anchor="Profile"]] that has entered a [[campaign>>doc:Main.Smart_Communications.SMC_Use.Campaigns.WebHome]] (e.g., send an email, wait, apply a filter, add to a target audience, etc.).
1.1	2
74.1	3	As input, the action receives an array of customer profiles. As output, it returns an array of customer profiles for whom the action was performed.
1.1	4
57.1	5	(% class="box" %)
	6	(((
54.1	7	{{toc depth="3" start="3"/}}
57.1	8	)))
54.1	9
1.1	10	=== Creating an action ===
	11
74.1	12	To create a new action in the chain:
1.1	13
74.1	14	* drag the action from the left menu onto the editing canvas;
	15	* or click the desired action, then click the canvas:
1.1	16
74.1	17	\|(% style="border-color:#ffffff; text-align:center" %)[[image:3_Actions_the_main.png]]
1.1	18
	19	\|(% style="border-color:white; width:1040px" %)(((
74.1	20	Connect the action to the previous campaign element by left-clicking. The connecting line should run from the green dot to the blue dot, as shown in the screenshot.
1.1	21
74.1	22	To delete a connection, right-click the line.
	23	)))\|(% style="border-color:white; text-align:center; width:398px" %)[[image:Connection_line.png\|\|height="130" width="285"]]
1.1	24	\|(% style="border-color:white; width:1040px" %)(((
74.1	25	=== Editing, copying, and deleting actions ===
54.1	26
74.1	27	Campaign actions can be edited, copied, or deleted. To do this, right-click the action and select the desired option from the context menu.
1.1	28
74.1	29	You can also copy actions using Ctrl+C/Ctrl+V. Select the desired action with the right mouse button and press Ctrl+C. The copied action can be pasted into the same campaign editor or into another editor opened in a new tab within the same browser.
54.1	30
74.1	31	To edit an action, double-click it with the left mouse button.
	32	)))\|(% style="border-color:white; text-align:center; width:398px" %)(((
	33
	34	[[image:actions_menu.png\|\|height="112" width="297"]]
	35	)))
54.1	36	\|(% style="border-color:white; width:1040px" %)(((
74.1	37	===== Merging multiple campaign branches =====
1.1	38
74.1	39	If a campaign includes multiple scenarios in a trigger chain that end with the same action, you can merge several branches into one action.
	40	)))\|(% style="border-color:white; text-align:center; width:398px" %)[[image:Multiple_branch_chain.png\|\|height="273" width="295"]]
57.1	41	\|(% style="border-color:white; width:1040px" %)(((
74.1	42	===== Positive and negative scenarios =====
1.1	43
74.1	44	For the Filter customers and Refresh filter actions, you can split the incoming flow into two scenarios:
57.1	45
74.1	46	(((
	47	* Positive — marked with a green plus. This branch includes all customers who meet the filter conditions;
	48	* Negative — marked with a red minus. This branch includes all customers who do not meet the filter conditions.
	49	)))
	50	)))\|(% style="border-color:white; text-align:center; width:398px" %)[[image:Scenarios.png\|\|height="238" width="287"]]
57.1	51
74.1	52	=== Full list of actions and their descriptions ===
54.1	53
1.1	54	{{toc start="6"/}}
	55
	56	(% class="table-bordered" style="width:1443px" %)
	57	(% class="info" %)\|(% style="width:417px" %)Action\|(% style="width:1021px" %)Description
	58	\|(% style="width:417px" %)(((
74.1	59	====== A/B test [[image:A_B_icon.png]] ======
1.1	60	)))\|(% style="width:1021px" %)(((
74.1	61	Allows you to conduct [[A/B testing>>doc:Main.Smart_Communications.SMC_Use.Mass_messaging.A_B_testing.WebHome]], i.e., create different continuation variants of a campaign chain. This helps identify the best-performing campaign variant to use going forward.
1.1	62
74.1	63	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="A_B_test_en.png" width="700"/}}
1.1	64
74.1	65	In the field Randomly distribute the specified number of customers, enter the number of customers on whom the test will be conducted. These customers will be evenly distributed across all branches. The most effective variant will then be selected. For example, if 500 is entered, the first 500 customers will be evenly distributed among all branches, and all subsequent customers will be directed to the winning branch.
1.1	66
74.1	67	In the field Criteria for selecting the winning variant, specify the metric used to determine the best variant. The winner will be the variant with the highest number of opens/clicks/orders.
	68
	69	\|(% style="border-color:#ffffff; text-align:center" %)[[image:Criteria_en.png]]
	70
	71	The field Results evaluation period, days allows you to delay evaluation of customer actions. For example, if 7 days is specified, opens/clicks/orders during the first 7 days will not be counted toward determining the winner.
	72
	73	The checkbox Enable test restart allows you to reset results from previous tests. If enabled, you must fill in one of the following fields:
	74
	75	* Restart period, days;
	76	* Restart period, hours.
	77
	78	To create branching variants, add child actions. You can define two or more different variants.
	79
	80	A/B test example:
	81
	82	\|(% style="border-color:#ffffff; text-align:center" %)[[image:attach:A_B_example.png\|\|height="267" width="345"]]
	83	)))
	84	\|(% style="width:417px" %)(((
	85	====== Refresh filter [[image:attach:Filter.webp]] ======
	86	)))\|(% style="width:1021px" %)(((
	87	Used when a filter (Filter customers) was already applied earlier in the action chain and now needs to be updated—avoiding duplication of the filter definition.
	88
	89	Usage example:
	90
	91	* Filter customers—for instance, include everyone who made 1 order.
	92	* Send them an email.
	93	* Wait 30 days.
	94	* Refresh the filter (new buyers may have appeared during this time).
	95	* Send them another email.
	96
57.1	97	\|(% style="border-color:#ffffff; text-align:center" %)[[image:Filter_update_en.png]]
1.1	98
74.1	99	Other actions may occur between Filter customers and Refresh filter.
1.1	100
	101	(% class="box infomessage" %)
	102	(((
74.1	103	* If multiple filters appear before Refresh filter, the nearest one will be refreshed.
	104	* For the Refresh filter action, you can define separate paths for customers who match the filter and those who do not.
1.1	105	)))
	106
74.1	107	Like Filter customers, Refresh filter splits the incoming flow into two scenarios:
1.1	108
74.1	109	* Positive — marked with a green plus. Includes all customers meeting the filter conditions;
	110	* Negative — marked with a red minus. Includes all customers not meeting the filter conditions.
1.1	111
74.1	112	For example, the filter selects all customers who will receive an SMS. All others (via the red-minus branch) receive an email.
1.1	113
74.1	114	Branches can later be merged again into a single common action if needed.
1.1	115
74.1	116	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Filter_update_example_en.png" width="700"/}}
1.1	117	)))
	118	\|(% style="width:417px" %)(((
74.1	119	====== Select customers from segment [[image:attach:Customer_selection.png]] ======
1.1	120	)))\|(% style="width:1021px" %)(((
74.1	121	Allows you to select customers belonging to a specific predefined segment.
1.1	122
	123	(% class="box infomessage" %)
	124	(((
74.1	125	You can review the list of predefined segments and their settings in Customers > [[User segments>>doc:Main.Smart_Communications.SMC_Use.Customers.User_segments.WebHome]].
1.1	126	)))
	127	)))
	128	\|(% style="width:417px" %)(((
74.1	129	====== {{id name="tags"/}}Audience actions [[image:attach:Add_to_audience.png]] ======
1.1	130	)))\|(% style="width:1021px" %)(((
74.1	131	Allows you to add to audience or exclude from audience customers during campaigns.
1.1	132
74.1	133	\|(% style="border-color:white; text-align:center; width:505px" %)[[image:Add_to_audience_example.png]]\|(% style="border-color:white; text-align:center; width:499px" %)[[image:Create_new_audience.png]]
1.1	134
74.1	135	Select the desired audience name from the dropdown list. To create a new target audience, enter a Name in the Audience actions settings window and click Create audience (see image on the right). A new target audience will be created and selected.
1.1	136
74.1	137	If needed, check the box Send audience list to Loyalty Program. If Loyalty Program integration is configured and supports audience list transfer, the list will be automatically sent to the Loyalty Program upon inclusion.
1.1	138
74.1	139	Example:
1.1	140
74.1	141	1. Create an audience named "Wants to buy iPhone 13".
	142	2. This list is automatically sent to the Loyalty Program.
	143	3. In the Loyalty Program, you can set up a rule for these customers—for example, offer a gift if they purchase an iPhone 13.
1.1	144
74.1	145	The Exclude from audience option removes a segment from the audience. Select the audience to exclude from the dropdown list. Exclusion can also be sent to the Loyalty Program.
1.1	146
74.1	147	To skip actions for control group customers, check Ignore control group customers.
1.1	148
74.1	149	(% class="box infomessage" %)
	150	(((
	151	For detailed information on working with target audiences, see the [[dedicated article>>doc:Main.Smart_Communications.SMC_Use.Customers.Target_audiences.WebHome]].
1.1	152	)))
74.1	153	)))
1.1	154	\|(% style="width:417px" %)(((
74.1	155	====== Control group [[image:attach:CG_icon.png\|\|height="38" width="40"]] ======
1.1	156	)))\|(% style="width:1021px" %)(((
74.1	157	Allows you to designate a [[control group>>doc:Main.Smart_Communications.SMC_Use.Control_groups.WebHome]] of customers during campaigns. The control group consists of potential campaign participants who are not exposed to communications or campaign mechanics. However, campaign metrics are calculated for them just as for the main group receiving communications.
1.1	158
74.1	159	(% class="table-bordered" %)
	160	\|(% style="border-color:white; text-align:center; width:511px" %)Image 1\|(% style="border-color:white; text-align:center; width:494px" %)Image 2
	161	\|(% style="border-color:white; width:511px" %)[[image:attach:Control_group.png]]\|(% style="border-color:white; width:494px" %)[[image:attach:Control_group_2.png]]
1.1	162
74.1	163	Enter an action description and select a control group determination method:
1.1	164
74.1	165	* Specify size (see Image 1). This option displays the following fields:
	166	* Control group size: specify the percentage of the campaign participants that will not receive communications.
	167	* Stratification parameters: optionally, use stratification—proportionally dividing the campaign participants into subgroups (strata) by a specific attribute (e.g., age, gender, registration date). Then, within each subgroup, assign customers to main and control groups. Add one or more stratification parameters by clicking Add parameter. A modal window with control group configuration settings will open. Read more about stratification [[here>>doc:Main.Smart_Communications.SMC_Use.Control_groups.WebHome\|\|anchor="Stratification"]].
1.1	168
74.1	169	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Start_params.png" width="700"/}}
1.1	170
74.1	171	* Use audience (see Image 2). This option displays the Audience as control group field. Select a [[target audience>>doc:Main.Smart_Communications.SMC_Use.Customers.Target_audiences.WebHome]] from the dropdown list to serve as the control group.
1.1	172
74.1	173	Example campaign:
1.1	174
74.1	175	\|(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Example_campaign_CG.png]]
1.1	176	)))
	177	\|(% style="width:417px" %)(((
74.1	178	====== Award points [[image:attach:Points.png]] ======
1.1	179	)))\|(% style="width:1021px" %)(((
74.1	180	Allows awarding internal points to customers for actions in the system.
1.1	181
74.1	182	Examples:
1.1	183
74.1	184	* Visited website — 3 points;
	185	* Made a purchase from an email — 5 points;
	186	* Bought at a store — 20 points.
1.1	187
74.1	188	Points can also be deducted. For example, if a customer hasn’t made any purchases in three months—deduct 50 points.
1.1	189
	190	(% class="box" %)
	191	(((
74.1	192	You can use point scoring to identify the most active customers and build segments.
1.1	193
74.1	194	Examples:
1.1	195
74.1	196	* Visited the site 3 times in a month — award points;
	197	* Made more than 2 purchases last quarter — award points;
1.1	198	* Opened an email — award points.
	199	)))
	200
74.1	201	In the Number of points field, enter a positive number (to award) or a negative number (to deduct). For example, you can award -10 points:
1.1	202
74.1	203	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Assess_scores_en.png" width="400"/}}
59.1	204
	205	(% class="box warningmessage" %)
	206	(((
74.1	207	Note: The Award points action is used only for internal customer evaluation. These point awards and deductions are not visible to customers.
1.1	208	)))
59.1	209	)))
1.1	210	\|(% style="width:417px" %)(((
74.1	211	====== Accrue bonus points [[image:attach:Bonus_points.png]] ======
1.1	212	)))\|(% style="width:1021px" %)(((
74.1	213	Allows accruing [[bonus points in the Loyalty Program>>doc:Main.Smart_Communications.SMC_Use.SmartCom_Bonuses_Accrual.WebHome]].
1.1	214
	215	(% class="box infomessage" %)
	216	(((
74.1	217	This action is available only if integration with [[Loymax Loyalty>>doc:Main.General_information.Loymax_Loyalty.WebHome]] is configured. Integration setup requires a request to Technical Support.
1.1	218	)))
	219
74.1	220	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Issue_bonus_en.png" width="400"/}}
1.1	221
	222	(% class="box infomessage" %)
	223	(((
74.1	224	The available parameters for Accrue bonus points depend on the capabilities of the Loyalty Program (LP) platform in use.
1.1	225	)))
	226
74.1	227	Specify the number of bonus points to accrue, expiration period (if the LP supports bonus expiration), and legal entity. Optionally, add an accrual description.
1.1	228
	229	(% class="box" %)
	230	(((
74.1	231	To notify customers about bonus accrual, create a campaign chain: Accrue bonus points > Wait > Send message. This ensures bonuses are credited before the notification is sent, avoiding cases where the customer receives a message before their bonus account is updated.
1.1	232	)))
	233	)))
	234	\|(% style="width:417px" %)(((
74.1	235	====== Limit number of participants [[image:attach:Limit_participants.png]] ======
59.1	236	)))\|(% style="width:1021px" %)(((
74.1	237	Limits the number of customers for whom actions in the chain will be performed. The limit applies to the entire campaign. Once the specified number is reached, the campaign stops.
59.1	238
	239	\|(% style="border-color:#ffffff; text-align:center" %)[[image:Customer_limit_example.png]]
	240
74.1	241	In the Period dropdown, select the timeframe for the limit:
59.1	242
74.1	243	* All time,
	244	* One campaign launch,
59.1	245	* Day,
	246	* Week,
	247	* Month,
	248	* Year.
	249	)))
1.1	250	\|(% style="width:417px" %)(((
	251	====== Limit poll [[image:attach:Poll_limitation.png]] ======
	252	)))\|(% style="width:1021px" %)(((
74.1	253	Sets the maximum number of customers who can complete a poll previously created in the [[Polls>>doc:Main.Smart_Communications.SMC_Use.Polls.WebHome]] section.
1.1	254
	255	(% class="box infomessage" %)
	256	(((
74.1	257	This action is available only if the poll functionality is enabled. Learn more in the [[Polls>>doc:Main.Smart_Communications.SMC_Use.Polls.WebHome]] section.
1.1	258	)))
	259
74.1	260	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Limit_poll.png" width="400"/}}
1.1	261
74.1	262	In the Survey field, select a survey from the dropdown list. Then choose one of the following limit types:
1.1	263
74.1	264	* Total limit: the specified number defines the total number of survey participants.
	265	* Per point of sale: the specified number applies separately to each registered point of sale.
1.1	266
74.1	267	To specify how many customers to survey at once, check the corresponding box and enter the number.
1.1	268	)))
	269	\|(% style="width:417px" %)(((
74.1	270	====== Send SMS [[image:attach:SMS.png]] ======
1.1	271	)))\|(% style="width:1021px" %)(((
74.1	272	Sends an SMS message to the customer.
1.1	273
	274	(% class="box infomessage" %)
	275	(((
74.1	276	If the SMS provider supports Viber, you can send Viber messages or a Viber > SMS cascade.
	277	Read more about cascades and Viber usage [[here>>doc:Main.Smart_Communications.SMC_Use.Mass_messaging.SMS_mass_messaging.WebHome\|\|anchor="01"]].
1.1	278	)))
	279
74.1	280	*//Viber access is restricted in the Russian Federation. Usage in other countries is subject to local laws.//
1.1	281
74.1	282	SMS message window without Viber:
1.1	283
74.1	284	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Send_SMS_en.png" width="400"/}}
1.1	285
74.1	286	Window with Viber enabled:
1.1	287
74.1	288	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Viber_message_en.png" width="400"/}}
1.1	289
74.1	290	You can use [[macros>>doc:Main.Smart_Communications.SMC_Use.Mass_messaging.Template_engine.WebHome]] in the message text.
1.1	291
74.1	292	You can also specify a [[messaging campaign category>>doc:Main.Smart_Communications.SMC_Use.Settings_SC.Mailing_categories.WebHome]] to send the message only to interested customers.
	293
1.1	294	Delivery management
	295
74.1	296	By default, SMS messages are delivered only during the system-defined allowed time window (e.g., 9:00 AM to 9:00 PM). If the recipient’s local time is outside this window, the message waits in the queue until the next valid delivery window.
1.1	297
74.1	298	The Deliver immediately checkbox bypasses this rule, sending the message instantly regardless of the recipient’s local time. This is useful when customers are in multiple time zones.
1.1	299
	300	(% class="box infomessage" %)
	301	(((
74.1	302	The Send SMS action is performed only for customers who:
1.1	303
74.1	304	* have an active SMS subscription;
	305	* have a valid phone number;
	306	* are subscribed to the selected messaging category (if specified).
1.1	307	)))
	308
	309	(% class="box warningmessage" %)
	310	(((
74.1	311	Important: Any child actions under Send SMS are executed only for customers to whom the message was sent (regardless of delivery status).
1.1	312	)))
	313	)))
	314	\|(% style="width:417px" %)(((
74.1	315	====== Send push [[image:attach:Push_icon.png]] ======
1.1	316	)))\|(% style="width:1021px" %)(((
74.1	317	Sends a push notification to the customer.
1.1	318
74.1	319	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Send_PUSH_en.png" width="500"/}}
1.1	320
	321	Fill in the required fields:
	322
74.1	323	* Message title.
	324	* Message text. You can use [[template engine macros>>doc:Main.Smart_Communications.SMC_Use.Mass_messaging.Template_engine.WebHome]].
	325	* Sections My discounts and Offer type. Loymax Smart Communications also supports In-app notifications. When using this option, you can select My discounts or Offer type in the push editor, and choose Push + Notification in the Send section.
1.1	326
	327	(% class="box infomessage" %)
	328	(((
74.1	329	Note: Sending In-app notifications requires integration with the existing mobile app’s backend, configured upon Partner request.
1.1	330	)))
	331
74.1	332	* Specify an external link or deep-link to redirect the customer to another resource or app page.
	333	* In the Send section, choose:
	334	* Push;
	335	* Notification;
	336	* Push + Notification.
	337	* Check Deliver immediately to send the push instantly, ignoring the recipient’s local time.
	338	* You can specify a [[messaging category>>doc:Main.Smart_Communications.SMC_Use.Settings_SC.Mailing_categories.WebHome]] to target interested customers.
	339	* Set the message lifetime in hours, days, or minutes.
1.1	340
	341	(% class="box infomessage" %)
	342	(((
74.1	343	The Send push action is performed only for customers who:
1.1	344
74.1	345	* have an active push subscription;
	346	* have a valid push identifier;
	347	* are subscribed to the selected messaging category (if specified).
1.1	348	)))
	349
	350	(% class="box warningmessage" %)
	351	(((
74.1	352	Important: Any child actions under Send push are executed only for customers who received the message (regardless of delivery status).
1.1	353	)))
	354	)))
	355	\|(% style="width:417px" %)(((
74.1	356	====== Send email [[image:attach:Mail.png]] ======
1.1	357	)))\|(% style="width:1021px" %)(((
74.1	358	Sends an email to the customer.
1.1	359
74.1	360	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Send_email_en.png" width="500"/}}
1.1	361
74.1	362	* Specify the sender name and email address.
	363	* Optionally, set a reply-to address by clicking the link and entering an email.
	364	* Fill in the subject and message body. You can use [[email templates>>doc:Main.Smart_Communications.SMC_Use.Mass_messaging.Email_mass_messaging.Templates.WebHome]] and [[formatting options>>doc:Main.Smart_Communications.SMC_Use.Mass_messaging.Email_mass_messaging.WebHome\|\|anchor="#HEmailbodyformatting"]].
	365	* Attach files by clicking Upload.
	366	* Add a [[UTM tag>>https://en.wikipedia.org/wiki/UTM_parameters]] to track online campaigns. If set, it will be appended to all links in the email.
	367	* Specify a [[messaging category>>doc:Main.Smart_Communications.SMC_Use.Settings_SC.Mailing_categories.WebHome]] to target interested customers.
	368	* Set the message lifetime in hours, days, or minutes.
	369	* Check Deliver immediately to send the email instantly, ignoring the recipient’s local time.
	370	* Check Use fast delivery to send via a dedicated mail server for urgent messages (e.g., promo codes). Limited to 200 fast deliveries per day.
	371	* After configuration, send a test message by clicking Send test message, entering a name and email, and clicking Send.
1.1	372
	373	(% class="box infomessage" %)
	374	(((
74.1	375	The Send email action is performed only for customers who:
1.1	376
74.1	377	* have an active email subscription;
	378	* have a valid email address;
	379	* are subscribed to the selected messaging category (if specified).
1.1	380	)))
	381
	382	(% class="box warningmessage" %)
	383	(((
74.1	384	Important: Any child actions under Send email are executed only for customers who received the message (regardless of delivery status).
1.1	385	)))
	386	)))
	387	\|(% style="width:417px" %)(((
74.1	388	====== Send notification [[image:attach:Notification_icon.png\|\|height="47" width="33"]] ======
1.1	389	)))\|(% style="width:1021px" %)(((
74.1	390	Sends an In-App notification to the customer. In-App notifications are personalized messages displayed inside the mobile app or website during use.
1.1	391
74.1	392	(% class="box infomessage" %)
	393	(((
	394	In-App notifications are an optional feature that must be enabled separately. Contact Loymax specialists to activate it.
	395	)))
1.1	396
74.1	397	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Send_InApp.png" width="500"/}}
1.1	398
74.1	399	Fill in the required fields:
1.1	400
74.1	401	* Message title.
	402	* Message text. You can use [[template engine variables and macros>>doc:Main.Smart_Communications.SMC_Use.Mass_messaging.Template_engine.WebHome]].
	403	* Specify an external link or deep-link to redirect the customer.
	404	* Optionally, upload an image.
	405	* If Communication policies are enabled, select a policy from the list.
	406	* Set a priority for the message.
	407	* Check Deliver immediately to send instantly, ignoring the recipient’s local time.
	408	* Specify a [[messaging category>>doc:Main.Smart_Communications.SMC_Use.Settings_SC.Mailing_categories.WebHome]] to target interested customers.
	409	* Set the message lifetime in hours, days, or minutes.
59.1	410
74.1	411	(% class="box infomessage" %)
	412	(((
	413	The Send notification action is performed only for customers who:
1.1	414
74.1	415	* have a non-empty Push ID;
	416	* have an active push subscription.
	417	)))
1.1	418
74.1	419	(% class="box warningmessage" %)
	420	(((
	421	Important: Any child actions under Send notification are executed only for customers who received the message (regardless of delivery status).
	422	)))
1.1	423
74.1	424	Example campaign:
	425
	426	\|(% style="border-color:#ffffff; text-align:center" %)[[image:attach:InApp_campaign_example.png]]
1.1	427	)))
	428	\|(% style="width:417px" %)(((
74.1	429	====== (% id="cke_bm_24063S" style="display:none" %) {{id name="Filter"/}}{{id name="CustomerFilter"/}}(%%)Filter customers [[image:attach:Customer_filter.png]] ======
	430	)))\|(% style="width:1021px" %)(((
	431	Defines which customers the next action will apply to. For example, you can apply the next action only to customers with both SMS and email subscriptions active.
	432
	433	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Filter_customers_en.png" width="600"/}}
	434
	435	The Filter customers action allows defining separate paths for customers who match the filter and those who do not—splitting the flow into two scenarios:
	436
	437	* Positive — marked with a green plus. Includes all customers meeting the filter conditions;
	438	* Negative — marked with a red minus. Includes all customers not meeting the filter conditions.
	439
	440	For example, the filter selects customers to receive an SMS. All others (via the red-minus branch) receive an email.
	441
	442	Branches can later be merged into a single common action.
	443
	444	For more details on filtering, see [[Creating a new segment>>doc:Main.Smart_Communications.SMC_Use.Customers.User_segments.WebHome]].
	445
	446	\|(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Filter_campaign.png]]
	447	)))
1.1	448	\|(% style="width:417px" %)(((
74.1	449	====== {{id name="Wait"/}}Wait [[image:attach:Wait.png]] ======
	450	)))\|(% style="width:1021px" %)Introduces a delay before the next action. Specify the delay duration in hours, days, or minutes.
	451	\|(% style="width:417px" %)(((
	452	====== Wait until date [[image:attach:Wait_till_date.png]] ======
1.1	453	)))\|(% style="width:1021px" %)(((
74.1	454	Delays the next action until a specified date.
1.1	455
74.1	456	The next action executes at 00:00 on the specified date (according to the time zone set in Settings > General settings > [[Contact details>>doc:Main.Smart_Communications.SMC_Use.Settings_SC.Settings.WebHome\|\|anchor="01"]] > Time zone).
1.1	457
	458	(% class="box infomessage" %)
	459	(((
74.1	460	If the next action is sending an SMS/push, messages will be delivered later during the time window defined in Settings > General settings > [[SMS>>doc:Main.Smart_Communications.SMC_Use.Settings_SC.Settings.WebHome\|\|anchor="03"]] > SMS delivery time window.
1.1	461	)))
	462	)))
	463	\|(% style="width:417px" %)(((
74.1	464	====== Show PopUp [[image:attach:PopUp.png]] ======
1.1	465	)))\|(% style="width:1021px" %)(((
74.1	466	Configures a popup message for customers who perform a specific [[trigger action>>doc:\|\|anchor="trigger"]].
1.1	467
74.1	468	(% class="box infomessage" %)
	469	(((
75.1	470	Note: The Show PopUp action requires integration with the [[Mobile App via SDK>>doc:Main.Smart_Communications.SMC_integration.MobileSDK.WebHome]].
74.1	471	)))
1.1	472
74.1	473	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Show_PopUp.png" width="400"/}}
1.1	474
74.1	475	Within this action, you can define:
1.1	476
74.1	477	* Name or title of the popup;
	478	* Subtitle;
	479	* Message text and button text;
	480	* Optionally, add an image;
	481	* {{id name="trigger"/}}Trigger action — the event that activates the popup (e.g., app/site login);
	482	* Trigger value — optional; specifies the trigger context (e.g., which catalog section was opened);
	483	* Popup action — defines what happens when the popup is interacted with (e.g., navigate to cart);
	484	* Popup action value — optional; specifies the action context (e.g., product or section);
	485	* Primary color code — matches brand guidelines;
	486	* Secondary color code — matches brand guidelines;
	487	* Promo code — if the popup includes a [[promo code>>doc:Main.Smart_Communications.SMC_Use.Promo_codes.WebHome]];
	488	* Lifetime — popup duration in hours, days, or minutes.
1.1	489
74.1	490	Campaigns with Show PopUp are created in advance using the [[Recurring date>>doc:Main.Smart_Communications.SMC_Use.Campaigns.Triggers.WebHome\|\|anchor="HRepeatdate"]] trigger, which sets the popup creation time.
1.1	491
74.1	492	The lifetime defined here controls how long the popup remains active, while the trigger action determines when it appears to the customer.
	493
	494	For example, if the start date is July 26 at 00:02 with daily recurrence, and the popup lifetime is 1 hour, the PopUp will be generated on that date and shown for one hour to customers who perform the trigger action before 01:02 on July 26.
	495
	496	An additional filter applies based on mobile app communication permissions.
	497
	498	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Customer_filter_popup.png" width="600"/}}
	499
	500	Thus, a Show PopUp campaign looks like this:
	501
	502	\|(% style="border-color:#ffffff; text-align:center" %)[[image:attach:PopUp_campaign.png]]
	503
	504	Only one popup can correspond to a single trigger action per customer. If multiple popups are scheduled for the same trigger, only one will display. However, you can create one campaign (with the same trigger) containing multiple chains with different filters.
	505	)))
	506	\|(% style="width:417px" %)(((
	507	====== Check email status [[image:attach:Status_check.png]] ======
	508	)))\|(% style="width:1021px" %)(((
	509	Used after Send email to create different follow-up paths based on customer response.
	510
	511	\|(% style="border-color:#ffffff; text-align:center" %)[[image:Check_mail_status_en.png]]
	512
	513	Possible email statuses:
	514
	515	* Not delivered;
	516	* Delivered, not opened;
	517	* Opened, no click;
	518	* Opened, clicked.
	519
	520	Action setup:
	521
	522	1. Create a Check email status action.
	523	2. Add the required number of child actions.
	524	3. Edit Check email status and assign a criterion (customer response) to each branch.
	525
1.1	526	(% class="box infomessage" %)
	527	(((
74.1	528	A Wait action must exist between Send email and Check email status to allow time for customer interaction.
1.1	529	)))
	530
74.1	531	Example:
1.1	532
74.1	533	Send email, wait 5 days, then check status:
1.1	534
74.1	535	* If opened and clicked → accrue bonus points;
	536	* If delivered but not opened → send SMS;
	537	* If not delivered → resend email.
1.1	538
74.1	539	To configure this, add three child actions to Check email status:
1.1	540
74.1	541	* [[Accrue bonus points>>doc:\|\|anchor="H41D43044743844143B43844244C43143E43D44344144BA0"]];
	542	* [[Send SMS>>doc:\|\|anchor="H41E44243F44043043243844244CSMSA0"]];
	543	* [[Send email>>doc:\|\|anchor="H41E44243F44043043243844244C43F43844144C43C43EA0"]].
1.1	544
74.1	545	Then edit Check email status and assign criteria:
1.1	546
74.1	547	\|(% style="border-color:#ffffff; text-align:center" %)[[image:Status_options_en.png\|\|height="362" width="453"]]
1.1	548
74.1	549	Resulting campaign chain:
1.1	550
74.1	551	\|(% style="border-color:#ffffff; text-align:center" %)[[image:Chain_status_check_en.png]]
1.1	552
	553	(% class="box infomessage" %)
	554	(((
74.1	555	Note: Before sending SMS, verify customer eligibility—i.e., apply filters for valid phone number and active SMS subscription.
1.1	556	)))
	557	)))
	558	\|(% style="width:417px" %)(((
74.1	559	====== Notify manager [[image:attach:Manager.png]] ======
1.1	560	)))\|(% style="width:1021px" %)(((
74.1	561	Sends an email to a Smart Communications user within your organization.
1.1	562
74.1	563	\|(% style="border-color:#ffffff; text-align:center" %){{lightbox image="Report_to_manager_en.png" width="400"/}}
1.1	564
74.1	565	Specify the subject and message body. You can use [[template engine constructs>>doc:Main.Smart_Communications.SMC_Use.Mass_messaging.Template_engine.WebHome]].
1.1	566
74.1	567	You can send to a specific employee (selected from a dropdown) or assign automatically.
1.1	568
	569	(% class="box infomessage" %)
	570	(((
74.1	571	You can manually select any employee registered in the system (Settings > Users > employee list).
1.1	572	)))
	573	)))

Created 2025/05/21 04:10
Last edited 2026/01/21 09:59

News
Updates
Tag cloud
Glossary
Site

Navigation

Wiki source code of 3.3. Actions