We will be marking your existing templates with all channels so that you need not have to perform an additional step to use them for LINE messaging.

Messaging users can respond to support-related queries/ new inquiries from consumers and also initiate 1-1 conversations using Converse Desk. When a messaging user is trying to send a message using the Sender ID tagged to the LINE channel, the system will by default show them the templates which are tagged against the LINE channel. They can either choose to select a template or can enter a free text/attach a media file to send it to the recipient over the LINE channel.

The attachment option in the Messaging Pane will be enabled for Sender IDs which are MMS enabled. On the selection of channel-specific Sender ID in the messaging composer, respective file type and file size support will be available as supported by the channel. You can check the details of the file type and file size by hovering on the attachment icon.

Also please note that, while sending interactive messages, if you select ‘Record Owner’s from the Sender ID selection drop-down list, you will be able to select templates that are tagged with SMS channels and messages would be sent on the SMS channel by default. Your Message Object Configuration phone fields and Sender IDs must belong to the same channel to avoid message sending failure.

Automated Messaging

Users would be able to initiate automated messages like reservation/appointment reminders with the LINE channel using existing features of the Converse apps by adding templates, creating action/message flows, and associating them with respective triggers.

Also please note that, while creating message flows if you select ‘Record Owner’s Sender ID’ from the Sender ID drop-down list, you will be able to select templates that are tagged with SMS channels and messages would be sent on the SMS channel by default. If you select ‘Auto’ from the Sender ID drop-down list, you will be able to select templates that are tagged against ‘All channels’, and messages would be sent on the same channel where the keyword is received. Your Message Object configured phone fields and Sender IDs must belong to the same channel to avoid message sending failure.

If users are trying to create an ‘Auto Reply’, ‘Automation’ and ‘Notification to User’ message flow in the Converse apps using Sender ID tagged to a LINE channel, the system will allow them to select any template tagged with LINE channel.

Bulk Messaging

A messaging user can use the Bulk messaging feature to send out messages to multiple LINE users in one go. These messages can be promotional messages or messages with a link to a survey form to collect consumers’ feedback etc. When the messaging user is trying to send bulk messages using the Sender ID tagged to the LINE channel, the system will by default show them the templates which are tagged against the LINE channel. They can either choose to select a template or can enter a free text/attach a media file to send it to the recipient over the LINE channel.

Also while sending bulk messages even if you select ‘Record Owner’s Sender ID’ from the Sender ID drop-down list, you will be able to select templates that are tagged with SMS channels and messages would be sent on the SMS channel by default. Your Message Object configured phone fields and Sender IDs must belong to the same channel to avoid message sending failure.

After completing the configuration steps, you would be able to see LINE Sender ID added into the ‘Sender ID Assignment’ table in converse settings along with the ‘Channel Type’ column showing the channel type to which the respective Sender ID belongs. While sending messages, whenever a marketing or sales user selects the value in the “From” number i.e. while selecting the Sender ID from the list, they will be able to understand Sender ID to channel tagging based on text UI identifier added in front of Sender ID as 153xenwe(LINE).

LINE Templates

When sales or marketing users are trying to send a LINE message, they will have to first select the Sender ID tagged with the LINE channel. Based upon the Sender ID selected by the user, the system will load the list of templates having respective channel tagging available in the list of templates dropdown.

LINE Outgoing and Incoming Messages

When marketing or sales users send an outgoing message using the Sender ID tagged to the LINE channel or receives an incoming message on the Sender ID tagged to the LINE channel, they will be able to see a LINE channel icon tagged with both the messages in the conversation view at the converse desk. Also, we have introduced one more column in SMS History as ‘Channel Name’ displaying the communication channel using which he will be able to identify the LINE outgoing and incoming messages in SMS History.

As per Line Messaging Guidelines, user consent is required for the LINE Official Account to be able to access user profile information, which includes display name, profile image, status message, and user ID.

Users who add your LINE Official Account as a friend or invite it to a chat automatically consent to their profile information being obtained.

SMS-Magic Compliance with LINE

Businesses capturing the recipient’s explicit LINE opt-ins as per the LINE guidelines mentioned above can use our out of box compliance configuration feature to set up and enforce compliance checks for LINE outbound messages.

Note:

1.Whenever a LINE  user will add your Business LINE Official Account as a friend or invite it to a chat, SMS-Magic captures this ‘follow’ request by the LINE user, and our out-of-box compliance feature will automatically create an opt-in consent record against the LINE user ID. You will then be able to respond to the user.

Channel Events:

• First, the Channel Events gets captured as shown in the image below. Under the ‘Message’ section, you can see whether the user has followed or unfollowed your channel.

Consent Creation:

• Then, based on the follow/unfollow status, opt-in and opt-out consent will be mapped and the Consent will get created against that channel:

Channel event in conversation UI:

• Then the same event will be seen in the conversation UI as shown below:

2. Similarly, upon receiving the un-follow request from the user, the system will automatically create/update the consent record associated with the LINE  user.
3. System will apply a compliance check for all the LINE messages sent across all UI and non-UI sources considering the multichannel compliance configurations done at the org level.

Please click here to know detailed information on setting up Multichannel Compliance.