Description of the capabilities of the BSG module. World for 1C-Bitrix

Module installation link: http://marketplace.1c-bitrix.ru/solutions/bsg.world/

Introduction:

The module is intended for sms -, viber -, as well as omnichannel notifications for administrators and users of the online store created on the platform 1C-Bitrix.

The BSG-1SBitrix module allows you to expand the functionality of the site, under the control of the “1C-Bitrix: Site Management” system and the “1C-Bitrix: Corporate Portal” program, and is also suitable for other programs created on the 1C-Bitrix platform (bitrix).

The SMS sending module will be useful for online stores, corporate portals, content projects, social networks and other web projects created using 1C-Bitrix: Site Management and 1C-Bitrix: Corporate Portal.

The use of the SMS module helps site owners to quickly transfer information to subscribers, customers, employees and automatically create SMS messages based on any events that occur on the site.

For online stores and other web projects based on the 1C-Bitrix system (bitrix), the SMS module allows:

• notify online store buyers about the change in order status;
• intercept email events and send messages generated by the email template via SMS;
• to send bulk SMS messages using the standard Subscription and Distribution module;
• Subscribe to SMS campaigns like regular mail, using the improved subscription component;
• process incoming SMS messages;
• manage the date and time of the beginning and end of SMS distribution;
• set the night time interval during which SMS should not be sent.

The module can also be used to perform individual tasks, for example:

• informing the technical support staff about a new request;
• creating any custom components for working with the SMS service (there is a detailed API description and open source codes).

For a corporate portal on the 1C-Bitrix system (bitrix), the SMS module allows:

• use the capabilities of the SMS module described above for online stores and other web projects under the control of the 1C-Bitrix: Site Management system;
• send SMS from 1C-Bitrix: Corporate Portal to employees and departments (groups of employees) using a convenient interface for filling in and selecting numbers:
  • according to the list of employees,
  • by divisional structure.

Main features of the module:

• Sending issues via SMS + Viber etc based on the standard distribution mechanism;
• Multi-site support. The ability to enter unique settings for each site;
• Support for backup service if the main one is not available;
• Notifying the site administrator about the impossibility of contacting the BSG service;
• Notifying customers by SMS, Viber about various events in the online store:
• New order
• Order status change
• Delete order
• Order payment
• Delivery
• Duplicate SMS, Viber to the site administrator’s phone.
• Sending SMS, Viber from the admin panel.
• SMS, Viber notification of support requests.
• Working with the corporate portal:
• Sending SMS, Veiber from the public part to company employees
• Configure task notifications (new, edit, delete)

Installing the BSG-1CBitrix module:

Installation of the BSG-1CBitrix module for the 1C-Bitrix system (bitrix) is simple – by clicking on the “Install module” button in the Marketplace.

The module distribution kit on SiteUpdate includes a single installer for 1C-Bitrix programs “Site Management” and “Corporate Portal” with the ability to install a demo section and a registration wizard for the BSG.WORLD SMS service.

First visit:

Immediately after installing the module, the user immediately gets into the module settings:

To get started, you need to specify API_KEY. You can get it in your account on the BSG.WORLD website.

Module settings sections:

• General settings
• Site settings
• Configuring SMS Events
• Help
• Technical support
• Access
• Debug mode
• General Settings Tab:

Refresh button allows you to update your balance at any time.

Time zone. Ability to specify the time zone in which the site is located. Necessary for correct SMS sending.

Notification of the administrator about the unavailability of the service. If the module cannot contact the BSG service, then the site administrator will receive a notification by e-mail (the email is taken from the settings of the main module).

Available SMS senders: indicate here the senders that you will receive in your BSG account after; testsms is available by default. After adding senders to this field, you can select them in the settings for the site.

Available Senders Viber : indicate here the senders you will receive in your BSG account after; AdvInform is available by default. After adding senders to this field, you can select them in the settings for the site.

Tab Site Settings “ :

Default sender SMS . For 1C-Bitrix module clients, the testsms sender is available by default. You can order a symbolic name in your personal account. After receiving the personal sender, indicate them according to the above instructions and then you can select him from this field.

Default sender Viber . For 1C-Bitrix module clients, AdvInform sender is available by default. You can order a symbolic name in your personal account. After receiving the personal sender, indicate them according to the above instructions and then you can select him from this field.

Autotranslated mailings. The length of the SMS for the Cyrillic alphabet is 70 characters, for the Latin alphabet – 128. To reduce the number of SMS, you can use this function.

Where the customer number is stored. Select the field where the mobile phone is stored.

Allowed sending time. The option allows you to allow sending notifications at a specified time interval, which will prevent sending notifications at night, for example. Match this option with the time zone.

Administrator numbers. Messages to users will be duplicated to these numbers.

Selecting a notification delivery option: By selecting SMS, the module will send notifications via SMS. By choosing Viber, the module will send notifications via Viber. By choosing Omni, the module will send in a mixed way: the system first sends messages to Viber, and which were not delivered to Viber are automatically delivered to SMS.

Subsection description < Store<

In this subsection, the client can find the default conditions for sending notifications.

Send messages to the client on events:

• Order
  • New order
  • Order paid
  • Order delivery allowed
  • Cancellation of order
• Order status change
  • Completed
  • Accepted, payment pending
  • Paid, generated for shipment
• Change shipment status
  • Order picking
  • Shipped
  • Waiting for the arrival of goods
  • Pending Processing
  • Submitted to delivery service
  • We are waiting for pick up by the transport company

Send to administrator on events:

• Заказ
  • New order
  • Order paid
  • Order delivery allowed
  • Cancellation of order
• Order status change
  • Completed
  • Accepted, payment pending
  • Paid, generated for shipment

Setting up custom templates for the orders page:

• Custom templates
  • Sample Custom Template

For each condition, create a message template with the ability to edit it. For instance,

For each condition when installing the module, create templates according to the example above.

Parameters for each template:

Send messages to the client on events:

• Order
  • New order
    • Your order N # ORDER_ID # accepted
    • Cost: # PRICE #
  • Order paid
    • Order N # ORDER_ID # paid
  • Order delivery allowed
    • Order delivery N # ORDER_ID # allowed
  • Cancellation of order
    • Order N # ORDER_ID # canceled
    • # ORDER_CANCEL_DESCRIPTION #
• Order status change
  • Completed
    • New order status N # ORDER_ID #: # ORDER_DESCRIPTION # Completed
  • Accepted, payment pending
    • New order status N # ORDER_ID #: # ORDER_DESCRIPTION # Accepted, payment awaiting
  • Paid, generated for shipment
    • New order status N # ORDER_ID #: # ORDER_DESCRIPTION # Paid, generated for shipment
• Change shipment status
  • Order picking
    • New status of order shipment N # ORDER_ID #: # STATUS_NAME # Order picking
  • Shipped
    • New status of order shipment N # ORDER_ID #: # STATUS_NAME # Shipped
  • We are waiting for the arrival of the goods
    • New status of order shipment N # ORDER_ID #: # STATUS_NAME # Waiting for goods to arrive
  • Pending processing
    • New order shipment status N # ORDER_ID #: # STATUS_NAME # Pending processing
  • Submitted to delivery service
    • New status of order shipment N # ORDER_ID #: # STATUS_NAME # Submitted to delivery service
  • We are waiting for pickup by a transport company
    • New status of order shipment N # ORDER_ID #: # STATUS_NAME # Waiting for pickup by the transport company

Send to administrator on events:

• Order
  • New order
    • Your order N # ORDER_ID # accepted
    • Cost: # PRICE #
  • Order paid
    • Order N # ORDER_ID # paid
  • Order delivery allowed
    • Order delivery N # ORDER_ID # allowed
  • Cancellation of order
    • Order N # ORDER_ID # canceled
    • # ORDER_CANCEL_DESCRIPTION #
• Order status change
  • Completed
    • New order status N # ORDER_ID #: # ORDER_DESCRIPTION # Completed
  • Accepted, payment pending
    • New order status N # ORDER_ID #: # ORDER_DESCRIPTION # Accepted, payment awaiting
  • Paid, generated for shipment
    • New order status N # ORDER_ID #: # ORDER_DESCRIPTION # Paid, generated for shipment

Setting up custom templates for the orders page:

• Custom templates
  • Sample custom template
    • Message text based on a new custom template

For the field From whom » set: #

For the field set: # PHONE_TO #

The following fields should be available for the message body:

• # ORDER_ID # – order code
• # ORDER_DATE # – order date
• # CONTACT_PERSON # – customer
• # PRICE # – order amount
• # PHONE_TO # – customer’s phone number
• # ORDER_LIST # – order contents
• # DEFAULT_EMAIL_FROM # – E-Mail address by default (set in the settings)
• # SITE_NAME # – Site name (set in the settings)
• # SERVER_NAME # – Server URL (set in the settings)

Also in this subsection the client can add his own template on his own.

The list of all templates is in the corresponding section:

Subsection description < Standard events “

In this subsection, you can find the default conditions for sending notifications for other conditions (not the store).

Send SMS to the client on events:

• Standard
  • Subscription confirmation
  • Technical support call events

Send SMS to administrator in case of events

• Standard:
  • Subscription confirmation
  • Technical support call events

Setting up custom templates for the users page

• Custom templates
  • New custom template

For each condition when installing the module, create templates according to the example above.

Parameters for each template:

Send SMS to the client on events:

• Standard
  • Subscription confirmation
    • Subscription Information:
    • Phone # PHONE #
    • Date added / modified # DATE_SUBSCR #
    • Confirmation code: # CONFIRM_CODE #
  • Technical support call events
    • Ticket Info:
    • Number # ID #
    • Date added # DATE_TICKET #
    • Critical: # CRITICAL #
    • Changes: # WHAT_CHANGE #

Send SMS to administrator in case of events

• Standard:
  • Subscription confirmation
    • Subscription Information:
    • Phone # PHONE #
    • Date added / modified # DATE_SUBSCR #
    • Confirmation code: # CONFIRM_CODE #
  • Technical support call events
    • Ticket Info:
    • Number # ID #
    • Date added # DATE_TICKET #
    • Critical: # CRITICAL #
    • Changes: # WHAT_CHANGE #

Setting up custom templates for the users page

• Custom templates
  • New custom template

Make it possible to choose for which site each template will be applied (if more than one).

For the field From whom » set: # DEFAULT_PHONE_FROM #

For the field set: # PHONE_TO #

The following fields should be available for the message body:

# ID # – reference number

# PHONE_TO # – support phone

# CRITICAL # – criticality

# DATE_TICKET # – date added

# DEFAULT_EMAIL_FROM # – E-Mail address by default (set in the settings)

# SITE_NAME # – Site name (set in the settings)

# SERVER_NAME # – server URL (set in the settings)

Also in this subsection the client can add his own template on his own.

Tab on Creating an event “:

The module allows you to create an event based on any mail event in the system.

Working with events is exactly the same as working with standard mail events.

List of available events by default:

ADD_IDEA New idea added

ADD_IDEA_COMMENT Added new comment to idea

ADV_BANNER_STATUS_CHANGE Banner status has changed

ADV_CONTRACT_INFO Advertising contract parameters

BIZPROC_MAIL_TEMPLATE Mail Send Action Message

BLOG_BLOG_TO_YOU A blog has been added to your friend

BLOG_POST_BROADCAST New message added

BLOG_SONET_NEW_COMMENT New comment added

BLOG_SONET_NEW_POST Added new message

BLOG_SONET_POST_SHARE Added new message recipient

BLOG_USER_TO_YOUR_BLOG A friend has been added to your blog

BLOG_YOU_TO_BLOG You have been added as a blog friend

BLOG_YOUR_BLOG_TO_USER Your blog has been added as a friend

CALENDAR_INVITATION Meeting Invitation

CATALOG_PRODUCT_SUBSCRIBE_LIST_CONFIRM Confirmation Code

CATALOG_PRODUCT_SUBSCRIBE_NOTIFY Notification of goods receipt

CATALOG_PRODUCT_SUBSCRIBE_NOTIFY_REPEATED In-store product notification

EDIT_FORUM_MESSAGE Changing forum post

FEEDBACK_FORM Sending a message via the feedback form

FORUM_NEW_MESSAGE_MAIL New message on the forum in the chat mode by E-Mail

IM_NEW_MESSAGE New message

IM_NEW_MESSAGE_GROUP New message (group)

IM_NEW_NOTIFY New notification

IM_NEW_NOTIFY_GROUP New Notification (Group)

LDAP_USER_CONFIRM Registration confirmation

NEW_BLOG_COMMENT New blog comment

NEW_BLOG_COMMENT2COMMENT New comment on your blog comment

NEW_BLOG_COMMENT2COMMENT_WITHOUT_TITLE New comment on your blog comment (no topic)

NEW_BLOG_COMMENT_WITHOUT_TITLE New blog comment (no topic)

NEW_BLOG_MESSAGE New blog post

NEW_FORUM_MESSAGE New forum post

NEW_FORUM_PRIV Private letter to forum visitor

NEW_FORUM_PRIVATE_MESSAGE Private message

NEW_LEARNING_TEXT_ANSWER New text response

NEW_USER New user registered

NEW_USER_CONFIRM New user registration confirmation

SALE_ORDER_REMIND_PAYMENT Order payment reminder

SALE_ORDER_TRACKING_NUMBER Notification of change of item ID

SALE_RECURRING_CANCEL Subscription canceled

SALE_SUBSCRIBE_PRODUCT Item Receipt Notification

SMSBiz_EVENT_ADMIN_SALE_ORDER_REMIND_PAYMENT

SMSBiz_EVENT_SALE_ORDER_REMIND_PAYMENT

SONET_AGREE_FRIEND Consent to become a friend

SONET_BAN_FRIEND Blacklisting

SONET_INVITE_FRIEND Invite to join friends list

SONET_INVITE_GROUP Invite to join a group

SONET_LOG_NEW_COMMENT New comment added

SONET_LOG_NEW_ENTRY New message added

SONET_NEW_EVENT New Event

SONET_NEW_EVENT_GROUP New Group Event

SONET_NEW_EVENT_USER New User Event

SONET_NEW_MESSAGE You have a new message

SONET_REQUEST_GROUP Request to join a group

STATISTIC_ACTIVITY_EXCEEDING Activity limit exceeded

STATISTIC_DAILY_REPORT Daily site statistics

TICKET_CHANGE_BY_AUTHOR_FOR_AUTHOR Title modified by author (for author)

TICKET_CHANGE_BY_SUPPORT_FOR_AUTHOR The appeal was changed by a technical support employee (for the author)

TICKET_GENERATE_SUPERCOUPON Coupon used

TICKET_NEW_FOR_AUTHOR New ticket (for author)

TICKET_OVERDUE_REMINDER Reminder to answer (for technical support)

USER_INFO User Information

USER_INVITE Invite new user to the site

USER_PASS_CHANGED Password change confirmation

USER_PASS_REQUEST Request to change password

VIRUS_DETECTED Virus detected

VOTE_FOR New voice

WF_IBLOCK_STATUS_CHANGE Status of infoblock element changed

WF_NEW_DOCUMENT New Document Created

WF_NEW_IBLOCK_ELEMENT New infoblock element created

WF_STATUS_CHANGE Document Status Changed

Event creation form:

Available macros. List of fields that can be used when creating an event:

# FULL_PATH # – Path to the idea comment

# IDEA_TITLE # – Idea title

# AUTHOR # – Name of the author of the idea comment

# IDEA_COMMENT_TEXT # – Idea comment text

# DATE_CREATE # – Date and time when the comment to the idea was created

# EMAIL_TO # – Subscriber Email

Phone (macro or number). In this field, you can specify either a phone number or a macro (from the available macros) in which it is stored.

You can also specify a macro with a user ID or EMAIL (example below). In this case, the search for a mobile phone will be carried out in the following order:

Phone (PERSONAL_PHONE)

Mobile (PERSONAL_MOBILE)

Worker (WORK_PHONE)

Enter the text of the message to be sent to the user. Enter the message template. You can use “Available Macros”. This message will be sent to the number specified in the “Phone” field.

Enter the text of the message to be sent to the site administrator (s). Enter the message template. You can use “Available Macros”.

The phone (s) of the administrator (s) must be set in the module settings on the “Site settings” tab

Example

Let’s create an event that will be triggered when a new user is registered.

Task. When registering a user, send a message to the user, send a message to the site administrator about a new user.

On the “Configure SMS event” tab, we find the type of mail event “NEW_USER”.

Double click – open the SMS event settings form.

Phone field. We enter the # USER_ID # macro.

Field “Enter the text of the SMS that will be sent to the user” – Good afternoon # NAME #! You have registered on our site. Your login is # LOGIN #.

“Enter the text of the SMS that will be sent to the site administrator (s)” – A new user has registered. ID – # USER_ID #, login – # LOGIN #.

If you don’t need to send an SMS, just leave the field with the message text empty.

Email templates

During operation, the module intercepts the message sending event and sends a message according to its template.

Upon installation, the module automatically installs the required mail templates. You can find them by the prefix BW_ “and change at your discretion using the markers indicated in them.

Tab on Help “:

Tab on Technical support “:

In this tab you can send a message to BSG technical support.

Tab Access Access :

In this tab, you can configure access to the module.

Tab o < Debugging :

Serves to track the work of the module.

Sending messages:

In addition to automatic messages, you can send messages in “manual” mode.

At the first stage of sending notifications, you can choose the sending option: Viber, SMS or Omni. By choosing Viber, you will be taken to sending bulk emails to Viber. Having selected SMS, you will proceed to sending bulk SMS. By selecting Omni, you will proceed to sending bulk mailings in a mixed way (first, it will be sent to Viber, and not delivered to Viber will be redirected to SMS).

Account Balance Tab:

Here you can check the balance of your account, as well as top up.

Sent Items Tab :

Here you can see a full report on messages sent from your store.

You can send messages directly from orders.