Wiki source code of 4.2. SMS mass messaging
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | The **SMS mass messaging **module allows to send SMS notifications to a group of customers. | ||
| 2 | |||
| 3 | (% class="box infomessage" %) | ||
| 4 | ((( | ||
| 5 | If your SMS provider supports the Viber option, it is possible to send Viber messages or** Viber -> SMS cascade**. | ||
| 6 | More information about using cascades can be found [[below>>doc:||anchor="01"]]. | ||
| 7 | ))) | ||
| 8 | |||
| 9 | (% class="table-bordered" %) | ||
| 10 | (% class="info" %)|(% style="width:736px" %)**SMS mailing page without Viber option**|(% style="width:719px" %)**SMS mailing page with activated Viber option** | ||
| 11 | |(% style="text-align:center; width:736px" %)[[image:SMS_without_Viber.png]]|(% style="text-align:center; width:719px" %)[[image:SMS_Viber.png]] | ||
| 12 | |||
| 13 | (% class="box infomessage" %) | ||
| 14 | ((( | ||
| 15 | No more than one link can be used in a Viber message. The link should be specified as a value for the** Link address** parameter. The link text should be specified in the **Button text** parameter. In this case, the link in the message will be displayed as a button with the specified text. | ||
| 16 | ))) | ||
| 17 | |||
| 18 | ==== SMS mailing parameters ==== | ||
| 19 | |||
| 20 | Filling out the SMS mailing parameters consists of the following steps: | ||
| 21 | |||
| 22 | 1. [[Setting up A/B testing>>doc:Main.Smart_Communications.SMC_Use.Mass_messaging.A_B_testing.WebHome]] in the mailing, if required. | ||
| 23 | 1. Filling out the **message parameters**. In case of A/B testing, it is necessary to fill out several variants of the message. | ||
| 24 | 1. Filling out the **mailing settings**. | ||
| 25 | |||
| 26 | ===== Message parameters ===== | ||
| 27 | |||
| 28 | * Specify the **Sender name**; | ||
| 29 | * Fill in the **message text**. You can use the [[Template Engine constructs>>doc:Main.Usage.Smart_Communications.Mass_messaging.Template_engine.WebHome]] in the SMS text. | ||
| 30 | * There is an option to upload the **image** (if needed). Smart Communications does not have any restrictions on the image size, except for the Nginx file upload limit — 32 MB. However, Google FCM does have file size limitations. If the payload exceeds the allowed size, Firebase may respond with the **‘Message Too Big’ error **for the entire request. To avoid such issues, we recommend following the guidelines below for image size in SMS mailings**:** | ||
| 31 | ** **Image format: **PNG or JPG. | ||
| 32 | ** **Recommended image size:** up to 300 KB. | ||
| 33 | ** **Image aspect ratio:** 2:1. | ||
| 34 | ** **Maximum image size:** 800 pixels. | ||
| 35 | ** **Maximum image width:** 1,000 pixels. | ||
| 36 | |||
| 37 | After filling out the message parameters, you can send a test message. To do this, click **Test**. In the opened window specify the phone number and click **Send**. | ||
| 38 | |||
| 39 | |(% style="border-color:white; text-align:center; width:736px" %)[[image:Test_message.png]] | ||
| 40 | |||
| 41 | (% class="box infomessage" %) | ||
| 42 | ((( | ||
| 43 | **Please note**: when you specify your phone number for a test message, the Platform generates a message for a special **test customer**. This is done due to the fact that in general case the Platform’s user may not have a customer profile in the database. | ||
| 44 | ))) | ||
| 45 | |||
| 46 | ===== Mailing settings ===== | ||
| 47 | |||
| 48 | |(% style="border-color:#ffffff; text-align:center" %)[[image:Settings.png]] | ||
| 49 | |||
| 50 | All types of settings have the same set of settings. Detailed description of mailing settings can be found in a separate [[article>>doc:Main.Smart_Communications.SMC_Use.Mass_messaging.Mailing_settings.WebHome]]. | ||
| 51 | |||
| 52 | ==== {{id name="01"/}}Cascades ==== | ||
| 53 | |||
| 54 | (% class="box infomessage" %) | ||
| 55 | ((( | ||
| 56 | **Cascades **or **cascade mailing** (chain of notifications) is the sequential sending of the same message through different communication channels. | ||
| 57 | ))) | ||
| 58 | |||
| 59 | If the SMS provider supports the Viber option, the cascade logic will be as follows: | ||
| 60 | |||
| 61 | 1. If only SMS text is provided — only the SMS will be sent. | ||
| 62 | 1. If only Viber text is provided — only the Viber message will be sent. | ||
| 63 | 1. If both SMS and Viber texts are provided, the System first attempts to deliver the Viber message. If delivery fails within 3 hours, the message is sent via SMS. | ||
| 64 | |||
| 65 | The below 3 categories of recipients do not receive Viber messages: | ||
| 66 | |||
| 67 | * customers who do not have Viber app installed; | ||
| 68 | * customers whose Viber was disabled on the day of the mailing; | ||
| 69 | * customers who at some point checked the box "Unsubscribe me from mailings of this brand" (a built-in Viber feature for branded mailings). | ||
| 70 | |||
| 71 | (% class="box infomessage" %) | ||
| 72 | ((( | ||
| 73 | **Note**: if you do not need to use the Viber option, it is recommended to fill in only the **SMS text message**. To disable the Viber messaging feature, please contact the technical support: **support@loymax.io**. | ||
| 74 | ))) |