3.3. Actions - Loymax

1

**Action **is an activity that the Smart Communications module should perform with respect to the [[Customer Profile>>doc:Main.Using.Smart_Communications.Customers.All_clients.WebHome||anchor="Profile"]] that was included in the [[campaign>>doc:Main.Usage.Smart_Communications.Campaigns.WebHome]] (e.g. send an email, wait, apply a filter, tag, etc.).

2

3

As the **action** input, the campaign receives an array of customer profiles. As the **action **output, the campaign receives an array of customer profiles for which the **action** was performed.

(% class="box" %)

(((

)))

=== Creating an action ===

11

12

To create a new **action** in a chain, perform the following steps:

13

14

* drag an **action** from the left-side menu to the editor field;

15

* or click on the **action**, and then click on the editor field:

16

17

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

18

19

|(% style="border-color:white; width:1040px" %)(((

20

Connect the action with the previous element of the campaign using the left mouse button. The connection line should go from the green point to the blue one, as shown on the image.

21

22

To remove the link, right-click on the line.

23

)))|(% style="border-color:white; text-align:center; width:398px" %)[[image:Connection_line.png]]

24

|(% style="border-color:white; width:1040px" %)(((

25

=== Action editing, copying and deleting ===

26

27

The action in the campaign can be **edited**, **copied**, or **deleted**. Right-click on the action and select the desired option in the context menu that opens.

28

29

There is an option to copy the campaign actions through Ctrl+C/Ctrl+V. Highlight the desired action with the right mouth button and press Ctrl+C. The copied action can be pasted into the same campaign editor or into an editor opened in a new window within the same browser.

30

31

To proceed to action editing, double-click on it with the left mouse button.

32

)))|(% style="border-color:white; text-align:center; width:398px" %)[[image:actions_menu.png||height="117" width="314"]]

33

|(% style="border-color:white; width:1040px" %)(((

34

==== Combining multiple campaign branches ====

35

36

If a campaign has several scenarios for a trigger chain that end with the same action, there is an option to combine several campaign branches into a single action.

37

)))|(% style="border-color:white; text-align:center; width:398px" %)[[image:Multiple_branch_chain.png||height="258" width="306"]]

38

|(% style="border-color:white; width:1040px" %)(((

39

==== Positive and negative scenarios ====

40

41

There is an option to split the incoming flow into two scenarios for the **Filter customers** and **Actualize filter** actions:

42

43

* **Positive** — marked as green plus. All customers that satisfy the filter conditions will be filtered into this branch of the campaign chain;

44

* **Negative** — marked as red minus. All customers that do not satisfy the filter conditions will be filtered into this branch of the chain.

45

)))|(% style="border-color:white; text-align:center; width:398px" %)[[image:Scenarios.png||height="236" width="310"]]

46

47

=== List of available actions and their description ===

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

52

(% class="info" %)|(% style="width:417px" %)**Action**|(% style="width:1021px" %)**Description**

53

|(% style="width:417px" %)(((

54

====== Actualize filter [[image:attach:Filter.webp]] ======

55

)))|(% style="width:1021px" %)(((

56

This action is used when the filter (**Filter customers**) has previously been set in the action chain, and now there is a need to update it. This is done to avoid duplicating the filter description.

57

58

**Example of filter application**:

59

60

* Filter customers. For example, add all customers who placed 1 order.

61

* Send a text message.

62

* Wait for 30 days.

63

* Actualize filter (new customers appeared during this time).

64

* Send them a test message.

65

66

|(% style="border-color:#ffffff; text-align:center" %)[[image:Filter_update_en.png]]

67

68

There may be other actions between the **Filter customers** and the **Actualize filter **actions.

69

70

(% class="box infomessage" %)

71

(((

72

If there are several filters in the chain prior to the **Аctualize filter **action,** **only the nearest filter will be updated.

73

)))

74

75

Similar to the **Filter customers **action, the **Actualize filter** action allows to split the incoming flow into two scenarios:

76

77

* **Positive scenario** — marked as green plus. All customers who satisfy the filter conditions will be filtered into this branch of the chain;

78

* **Negative scenario** — marked as red minus. All customers who do not satisfy the filter conditions will be filtered into this branch.

79

80

For example, the filter selects everyone to whom an SMS message will be sent. All others (the red minus branch) will receive an email.

81

82

Then both branches of the chain can be combined again with one common action (if required).

83

84

|(% style="border-color:#ffffff; text-align:center" %)[[image:Filter_update_example_en.png||height="200" width="587"]]

85

)))

86

|(% style="width:417px" %)(((

87

====== Use customers from segment [[image:attach:Customer_selection.png]] ======

88

)))|(% style="width:1021px" %)(((

89

The action allows to select customers who are included in a certain preset segment.

90

91

(% class="box infomessage" %)

92

(((

93

The list of preset segments and their settings can be found in the **Customers > **[[User segments>>doc:Main.Usage.Smart_Communications.Customers.User_segments.WebHome]] section.

94

)))

95

)))

96

|(% style="width:417px" %)(((

97

====== А/В test [[image:A_B_icon.png]] ======

98

)))|(% style="width:1021px" %)(((

99

This action allows to run the [[А/В testing>>doc:Main.Using.Smart_Communications.Mass_mailings.A_B_testing.WebHome]], i.e. to create different variants for continuing the chain in the campaign. This helps to choose the best variant and further apply only this variant.

100

101

|(% style="border-color:#ffffff; text-align:center" %)[[image:attach:A_B_test_en.png||height="313" width="592"]]

102

103

In the field — **Distribute the number of customers randomly **—** **randomly specify the number of customers that will be used for A/B testing. These customers will be evenly distributed across all branches. Then the most effective variant will be given preference. For example, if 500 is specified in the field, the first 500 customers will be evenly distributed across all branches, and all subsequent customers will be directed to the winning branch.

104

105

In the field — **Criteria for selection of the winning options **—** **specify the criterion for selecting the best option. The winning option will be the one with the maximum number of openings/clicks/orders.

106

107

|(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Criteria_en.png]]

108

109

The field — **Result waiting period, days** — allows to make a pause and not immediately take into account the actions of customers. For example, if the field is set to 7 days, openings/clicks/orders will not be taken into account for the first 7 days for calculation of the winning option.

110

111

To create branches, add the child actions. It is possible to add 2 or more different variants.

112

113

**А/В test example:**

114

115

|(% style="border-color:#ffffff; text-align:center" %)[[image:A_B_example.png||height="278" width="385"]]

116

)))

117

|(% style="width:417px" %)(((

118

====== Add to audience [[image:attach:Add_to_audience.png]] ======

119

)))|(% style="width:1021px" %)(((

120

This action allows to **include customers in audience** or **exclude from audience** as part of campaigns.

121

122

|(% style="width:498px" %)[[image:Add_to_audience_example.png]]|(% style="width:506px" %)[[image:Create_new_audience.png]]

123

124

(% style="background-color:transparent" %)Select the required **audience name** from the drop-down list. To **create a new audience**, enter the **Audience name** in the field and then choose **Create an audience **(%%)(see image on the right). A new audience will be created and chosen for the action.

125

126

If you need to **transfer** the list of customers from the audience to the **Loyalty Program**, check the corresponding box. If integration with the Loyalty Program is configured and it supports transfer of customer lists, the list will be automatically transferred to the Loyalty Program when it is added to the audience.

**For example:**

1. An audience with the customer list "Wants to buy iPhone 13" is created.

131

1. This list is automatically sent to the Loyalty Program.

132

1. A rule for customers from this audience can be set up in the Loyalty Program. For example, offer a gift if they buy an iPhone 13.

133

134

The option **Exclude from audience **allows to exclude a customer segment from the audience. Select an audience that should be excluded from the drop-down list. Lists for **excluding from audience **can also be transferred to the Loyalty Program.

135

136

If there is a need not to perform any actions for customers from a control group, check the **Ignore clients in control group** box.

137

)))

138

|(% style="width:417px" %)(((

139

====== Assess scores [[image:attach:Points.png]] ======

140

)))|(% style="width:1021px" %)(((

141

This action allows to accrue points/scores to customers for their actions in the System.

**For example:**

* Visited the website — 3 points;

146

* Made a purchase from the mailing — 5 points;

147

* Made a purchase in the store — 20 points.

148

149

Points can be both accrued and deducted. For example, if the customer has not purchased anything for three months — deduct 50 points.

(% class="box" %)

(((

Using this action, you can pick the most active customers and build segments using scoring.

**Example: **

* Visited the website 3 times in a month — award points.

158

* Made more than 2 purchases in the last quarter — award points.

159

* Opened an email — award points.

160

)))

161

162

In the **Amount of scores **field,** **you can specify both a positive number (to accrue points) and a negative number (to deduct points). For example, it is possible to accrue -10 points:

163

164

|(% style="border-color:#ffffff; text-align:center" %)[[image:Assess_scores_en.png]]

165

166

(% class="box warningmessage" %)

167

(((

168

**Note**: the **Assess scores** action is used for internal customer assessment only. Accruals and deductions of scores are not displayed for customers.

169

)))

170

)))

171

|(% style="width:417px" %)(((

172

====== Issue bonus [[image:attach:Bonus_points.png]] ======

173

)))|(% style="width:1021px" %)(((

174

This action allows to[[ accrue bonus points to customers in the Loyalty Program>>accrue bonus points to customers in the Loyalty Program]].

175

176

(% class="box infomessage" %)

177

(((

178

This action is available if the module is integrated with the [[Loyalty Program>>doc:Main.General_information.Loymax_Loyalty.WebHome]]. Integration can be configured via request to the technical support service.

179

)))

180

181

|(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Issue_bonus_en.png||height="367" width="415"]]

182

183

(% class="box infomessage" %)

184

(((

185

A set of parameters of the **Issue bonus** action** **depends on the capabilities of each specific Loyalty Program platform.

186

)))

187

188

Specify the **quantity **of bonus points to be accrued, **validity **period (if the Loyalty Program supports expiration of bonus points), and a **legal entity**. If required, add the **description **for bonus points accrual.

(% class="box" %)

(((

If there is a need to accrue bonus points and send notification to customers, create a chain of actions in the campaign: **Issue bonus** **> Wait > Send e-mail**. In this case customers will get bonus points first, and then they will receive a message about accrual of bonus points. This will allow to avoid situations when the customer has already received a notification, but their bonus account has not been updated yet.

193

)))

194

)))

195

|(% style="width:417px" %)(((

196

====== Limit the number of clients [[image:attach:Limit_participants.png]] ======

197

)))|(% style="width:1021px" %)(((

198

The action allows to limit the number of customers for whom subsequent actions in the chain will be performed. This limit is applied to the entire campaign. Once the specified number of customers is reached, the campaign stops.

199

200

|(% style="border-color:#ffffff; text-align:center" %)[[image:Customer_limit_example.png]]

201

202

Choose the **period** from a dropdown list within which the specified **limit** (number of customers) will be in effect:

203

204

* Lifetime — all the time,

205

* Single run of campaign,

* Day,

* Week,

* Month,

* Year.

)))

|(% style="width:417px" %)(((

212

====== Limit poll [[image:attach:Poll_limitation.png]] ======

213

)))|(% style="width:1021px" %)(((

214

The action allows to set the maximum number of customers who will be able to participate in a poll previously created in the [[Polls >>doc:Main.Using.Smart_Communications.Survey.WebHome]]section.

215

216

(% class="box infomessage" %)

217

(((

218

This action is available only if the polls functionality is enabled. For more details, please refer to the [[Polls>>doc:Main.Using.Smart_Communications.Survey.WebHome]] section.

219

)))

220

221

|(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Limit_poll.png||height="342" width="383"]]

222

223

In the **Poll** field, select a poll for which you want to limit the number of participants. Then select one of the options for setting a limit:

224

225

* **Total limit**.** **In this case, the specified number will determine how many customers in total can participate in the poll.

226

* **Trade object limit**. The specified number of customers who can participate in the poll will be set for each point of sale registered in the System.

227

228

If there is a need to specify how many customers to **ask at a time**, check the respective box and specify the number of customers.

229

)))

230

|(% style="width:417px" %)(((

231

====== Send SMS [[image:attach:SMS.png]] ======

232

)))|(% style="width:1021px" %)(((

233

The action allows to send a text message to customers.

234

235

(% class="box infomessage" %)

236

(((

237

If the SMS provider supports the Viber option, it is possible to send Viber messages or Viber > SMS cascade.

238

More information about cascades and Viber messages can be found [[here>>here]].

239

)))

240

241

**Example of window for sending SMS without Viber option:**

242

243

|(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Send_SMS_en.png||height="509" width="396"]]

244

245

**Example of window with active Viber option:**

246

247

|(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Viber_message_en.png||height="481" width="374"]]

248

249

There is an option to use [[macros>>doc:Main.Using.Smart_Communications.Mass_mailings.Template_builder.WebHome]] in the text of the message.

250

251

There is also an option to specify the [[mailing category>>doc:Main.Using.Smart_Communications.Settings_SC.Mailing_categories.WebHome]] so that to send the message only to interested customers.

252

253

**Delivery management**

254

255

By default, SMS messages are delivered to recipients only within the time interval allowed in the module settings, for example from 9:00 a.m. to 9:00 p.m. If the recipient's location time is outside the allowable interval, the message will wait in the queue for the next day until the allowable delivery interval.

256

257

The **Deliver immediately** checkbox allows to ignore this rule and send the message immediately at the moment when a campaign is triggered, ignoring the time at the location of the message recipient. This functionality is relevant if the customers are located in several different time zones.

258

259

(% class="box infomessage" %)

260

(((

261

The action of sending SMS messages is performed only for customers who simultaneously have the following:

262

263

* active subscription to the SMS communication channel;

264

* the phone number is valid;

265

* active subscription to a selected mailing category (if specified).

266

)))

267

268

(% class="box warningmessage" %)

269

(((

270

**Important: **any actions in the chain that are child actions to the **Send SMS** action are performed **only **for customers to whom the message was sent (ignoring the delivery status).

271

)))

272

)))

273

|(% style="width:417px" %)(((

274

====== Send PUSH [[image:attach:Push_icon.png]] ======

275

)))|(% style="width:1021px" %)(((

276

The action allows to send a push message to customers.

277

278

|(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Send_PUSH_en.png||height="572" width="432"]]

279

280

Fill in the required fields:

281

282

* **Title **for the mailing.

283

* **Push text**. You can use [[macros from Template Engine >>doc:Main.Using.Smart_Communications.Mass_mailings.Template_builder.WebHome]]in the text of the message.

284

* The Loymax Smart Communications module provides an option of sending In-app notifications. In case of using this option, the window for editing a push notification will contain sections **My discounts **or **Promo type** that should be selected.

285

286

(% class="box infomessage" %)

287

(((

288

**Note**: to be able to send In-app notifications, the backend of the existing Mobile App should be integrated with the module at the Partner's request.

289

)))

290

291

* Fill in the **external link **or **deep-link**, if there is a need to re-direct the customer to a different website or page in the Mobile App.

292

* Check the **Deliver immediately **box, if there is a need to send push notification immediately at the moment of campaign triggering, ignoring time at the location of message recipient.

293

* There is an option to select the [[mailing category>>doc:Main.Using.Smart_Communications.Settings_SC.Mailing_categories.WebHome]] so that to send message to the interested customers only.

294

* Specify the **message lifetime **in hours, days or minutes.

295

296

(% class="box infomessage" %)

297

(((

298

The action for sending push notifications is performed only for customers who simultaneously have the following:

299

300

* active subscription to PUSH channel;

301

* push identifier is filled in;

302

* active subscription to the selected mailing category (if specified).

303

)))

304

305

(% class="box warningmessage" %)

306

(((

307

**Important: **any actions in the chain that are child nodes to the **Send push** action are performed **only **for customers to whom the message was sent (ignoring the delivery status).

308

)))

309

)))

310

|(% style="width:417px" %)(((

311

====== Send e-mail [[image:attach:Mail.png]] ======

312

)))|(% style="width:1021px" %)(((

313

The action allows to send an email to customers.

314

315

|(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Send_email_en.png||height="557" width="461"]]

316

317

* Fill in **Sender name **and **Sender e-mail**.

318

* Specify the **return e-mail address**, if required. To do this, click the link and type the e-mail address.

319

* Fill in the **Subject** and **Mail body**. There is an option to use [[email templates>>doc:Main.Using.Smart_Communications.Mass_mailings.Emails.Templates.WebHome]]. It is also possible to [[format >>doc:Main.Using.Smart_Communications.Mass_mailings.Emails.WebHome||anchor="H42443E44043C43044243844043E43243043D43843544243543A44144243043F43844144C43C430"]]the text of the email.

320

* If necessary, you can attach files to the text by clicking the **Upload **button.

321

* It is also possible to add the [[UTM-tag>>https://ru.m.wikipedia.org/wiki/UTM-%D0%BC%D0%B5%D1%82%D0%BA%D0%B8]] to track online advertising campaigns. If the UTM-tag is set, it will be added to all links in the email.

322

* There is an option to specify a [[mailing category>>doc:Main.Using.Smart_Communications.Settings_SC.Mailing_categories.WebHome]] to send an e-mail only to interested customers.

323

* Specify the **Message lifetime **in hours, days, or minutes.

324

* Check the box **Deliver immediately**, if there is a need to send e-mail immediately at the moment of campaign triggering, ignoring time at the location of message recipient.

325

* Once you have filled in all parameters of the e-mail, it is possible send a test message. To do this, click **Send test message **button. Fill in the name and e-mail address, and click **Send**.

326

327

(% class="box infomessage" %)

328

(((

329

The action for sending e-mail is performed only for customers who simultaneously have the following:

330

331

* active subscription to e-mail channel;

332

* E-mail address is valid;

333

* (((

334

active subscription to the selected mailing category (if specified).

)))

)))

(% class="box warningmessage" %)

339

(((

340

**Important: **any actions in the chain that are child nodes to the **Send e-mail **actions are performed **only** for customers to whom the message was sent (ignoring the delivery status).

341

)))

342

)))

343

|(% style="width:417px" %)(((

344

====== Filter customers [[image:attach:Customer_filter.png]] ======

345

)))|(% style="width:1021px" %)(((

346

This action allows to determine for which customers the next action will be performed. For example, you can perform the following action only with those customers who have active SMS and email subscriptions.

347

348

|(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Filter_customers_en.png]]

349

350

The filter allows to split the incoming flow into two scenarios:

351

352

* **Positive scenario** — marked as green plus. All customers who satisfy the filter conditions will be filtered into this branch of the chain;

353

* **Negative scenario** — marked as red minus. All customers who do not satisfy the filter conditions will be filtered into this branch.

354

355

For example, the filter selects everyone to whom an SMS message will be sent. All others (the red minus branch) will receive an email.

356

357

For example, the filter selects everyone to whom an SMS message will be sent. All others (the black point branch) will receive an email.

358

359

Then both branches of the chain can be combined again with one common action (if required).

360

361

More information about setting up filtering can be found in the section [[Creating a new segment>>doc:Main.Using.Smart_Communications.Customers.User_segments.WebHome]].

362

363

|(% style="border-color:#ffffff; text-align:center" %)

364

)))

365

|(% style="width:417px" %)(((

366

====== {{id name="Wait"/}}Wait [[image:attach:Wait.png]] ======

367

)))|(% style="width:1021px" %)This action allows to delay the next action. Specify by how many hours/days/minutes you want to delay the next action.

368

|(% style="width:417px" %)(((

369

====== Wait till specific date [[image:attach:Wait_till_date.png]] ======

370

)))|(% style="width:1021px" %)(((

371

This action allows to delay the next action till a specified date.

372

373

The next action in a campaign will be performed on the specified date at 00:00 (according to the time zone set in the section **Settings > General settings > **[[Contact details>>doc:Main.Using.Smart_Communications.Settings_SC.Settings.WebHome||anchor="01"]]** > Time zone**).

374

375

(% class="box infomessage" %)

376

(((

377

If the next action in a campaign is sending SMS/push notifications, the messages will be delivered later (at the time specified in the **Settings > General settings > **[[SMS>>doc:Main.Using.Smart_Communications.Settings_SC.Settings.WebHome||anchor="03"]]** > Time interval for SMS delivery**).

378

)))

379

)))

380

|(% style="width:417px" %)(((

381

====== Сheck mail status [[image:attach:Status_check.png]] ======

382

)))|(% style="width:1021px" %)(((

383

This action is applied after the **Send e-mail **action. It allows to implement different chains for customers depending on their reaction to the e-mail.

384

385

|(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Check_mail_status_en.png||height="224" width="429"]]

386

387

Possible e-mail statuses:

388

389

* Not delivered;

390

* Delivered, not opened;

391

* Opened, no click;

392

* Opened, clicked the link.

**Action settings:**

1. Create the **Check mail status **action.

397

1. Create the required number of child actions (descendants).

398

1. Edit the **Check mail status **action and specify the criteria for each variant. The criteria are the customers' reaction to the e-mail.

399

400

(% class="box infomessage" %)

401

(((

402

The **Wait** action is required in a chain between the **Send e-mail **and **Check mail status**. This is necessary to maximize the chain efficiency and to give a customer an opportunity to react to the e-mail.

)))

**Example:**

Send an e-mail, wait for 5 days. Then check the e-mail status:

408

409

* If the e-mail was opened and read, and a customer clicked the link in the e-mail, award bonus points to the customer.

410

* If the e-mail was delivered but it was not opened, send an SMS message to the customer.

411

* If the e-mail was not delivered, send it once again.

412

413

To set up such branching, add 3 child actions to the **Check mail status **action:

414

415

* Issue bonus points;

* Send SMS;

* Send e-mail.

Then edit the **Check mail status** and specify a criterion for each option:

420

421

|(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Status_options_en.png||height="278" width="344"]]

422

423

This is how the campaign chain will look like:

424

425

|(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Chain_status_check_en.png||height="245" width="425"]]

426

427

(% class="box infomessage" %)

428

(((

429

**Note**: before sending SMS messages it is necessary to check customers for availability of the communication channel, i. e. a combination of filters should be applied:** E-mail is valid **and **Active SMS subscription**.

430

)))

431

)))

432

|(% style="width:417px" %)(((

433

====== Report to Manager [[image:attach:Manager.png]] ======

434

)))|(% style="width:1021px" %)(((

435

This action allows to send an email to the company's employee who is using the Smart Communications module.

436

437

|(% style="border-color:#ffffff; text-align:center" %)[[image:attach:Report_to_manager_en.png||height="306" width="378"]]

438

439

Specify the **subject** and add the text of the **mail message**. It is possible to use [[Template Engine patterns >>doc:Main.Using.Smart_Communications.Mass_mailings.Template_builder.WebHome]]in the **mail message** field.

440

441

You can send an e-mail to a specific employee by selecting his name in the drop-down list or make the selection of an employee automatic.

442

443

(% class="box infomessage" %)

444

(((

445

You can manually select any employee registered in the System (**Settings > Employees**).

446

)))