Mailings

Notification rules and delivery channels

A mailing is the root element that links an event in the system, the recipients, and the sending channel.

Blocks:

  • Orders (notification rules for order events)

  • WEB (notification rules for web forms and reviews)

  • HTTP Destinations (webhook URL and payload for the HTTP channel)

  • SMS Providers (SMS credentials for mailings)

  • Telegram Bots (Telegram bots for mailings)

Orders

Main block

The main block consists of:

**1. Name **
A system name for the rule that is clear to humans. It should ideally reflect the essence: who, to whom, and on which event.

Example: "Courier notification about a new assignment (Manual order)"
Example: "SMS to the customer about a change of visit date"

**2. Trigger **

Available trigger types:

  • Status change: The classic (New -> In progress -> Completed -> Canceled).

  • Assignee change: The event of assigning a responsible employee/team to an order.

  • Manager change: The event of changing the supervising manager (customer or project manager).

  • Courier change: The event of assigning or replacing a courier (relevant for logistics).

  • Execution date change: The event of rescheduling, changing the delivery interval, or changing the visit date.

**3. Recipient type: **

  • Manager: The order supervisor.

  • Assignee: The person who physically carries out the order (technician, foreman).

  • Courier: The driver or deliverer.

  • Customer: The order owner (recipient of the service).

  • Order creator: The operator who created the request (may differ from the manager).

4. Users (manual addition/override):
If the "Roles" mechanism is not enough or you need to add a recipient individually, use this field.

Execution conditions (Filters)

A set of rules that narrow down when the trigger fires. If the condition is not met, the notification is not sent. This prevents spam.

Filter types:

1. Statuses:

The order must be in the state: Specify particular statuses (for example, the rule is active only if the order was "In progress" and then canceled).

Target status: The trigger fires only on a transition to a specific status (for example, an SMS is sent only on transition to the "Ready for pickup" status, and not on any change).

2. Locales (Geo-zones / Locations):

Restriction by city, district, or branch.

Example: An SMS with a chat link is sent only to customers from Moscow and the Moscow region, and is not sent to other regions (if a different policy applies there).

3. Web source:

Where the order came from via a website. Filter by domain or site identifier.

Example: Notifications for orders from the "Retail" website are handled differently than those from the wholesale portal.

4. API source:

Where the order came from programmatically. Filter by API key or external system name.

Example: Do not send notifications to the courier if the order was created automatically (for example, by a marketplace), because it has its own logistics.

5. Conditional source:

Additional parameter / "Custom source". This is the most flexible field for custom logic.

Mailing channel

Ways of delivering the notification when the rule fires: push, SMS, Telegram, or HTTP webhook.

Screenshot name: rassylka_zakazy_novoe

The block where you can copy, edit, and delete.

Screenshot name: rassylka_zakazy_blok_kop_red_udl

Web

This block handles incoming leads and user actions that came through the web interface (landing page, website, feedback form). Unlike the "Orders" block, the triggers here are not internal status changes, but the fact that a site visitor performed an action.

**Main **

  • name

  • trigger (web form message, callback request, new order, review)

  • user

**Execution conditions **

web source

Mailing channel

Ways of delivering the notification when the rule fires: push, SMS, Telegram, or HTTP webhook.

Screenshot name: rassylka_veb_novoe

Screenshot name: rassylka_veb_kop_red_udl

HTTP Destinations

**The main block consists of: **

  • hook name

  • short description

Request block:

  1. URL
    The address the request is sent to.

  2. Method

The type of HTTP request according to REST architecture.

  • POST: The main working tool. Used to create or send data to an external system.

  • GET: Rarely used, usually for checking or triggering without a request body.

  • PUT: Used to fully update existing data.

  • DELETE: Used for deletion.

  1. Headers

  2. Request body

Screenshot name: rassylka_http_novoe

Screenshot name: rassylka_http_novoe_2

Screenshot name: rassylka_http_red_udl

SMS Provider

To configure an SMS provider, click "+" and fill in the fields.

Screenshot name: rassylka_sms_novoe

Screenshot name: rassylka_sms_red_udl

Telegram bots

To link Telegram bots, fill in all the fields.

Screenshot name: rassylka_telegram_bot_novoe

Screenshot name: rassylka_telegram_bot_red_ud

In the CRM you can integrate SMS mailings to automatically send messages to customers. To do this, you need to complete a few steps:

  1. Register with an SMS provider, such as SMS Assistant or Rocket SMS.

  2. Add the provider's data to the CRM.

  3. Configure the mailing conditions.

Step 1: Registering with an SMS provider

  1. Go to the website of your chosen provider.

  2. Register by following the instructions on the site.

  3. Obtain the API key that will be used for integration with the CRM.

Step 2: Adding the provider's data to the CRM

  1. Open your CRM settings.

  2. Find the section related to SMS integration.

  3. Enter the data you received from the provider.

Step 3: Configuring the mailing conditions

  1. Determine when and to whom to send SMS messages. For example, you can set up sending a message when an order is created, when an order is confirmed, or when an order status changes.

  2. Create the mailing rules. In the CRM this can be an automated process or manual configuration.

  3. Choose the message text. Make sure the text matches your marketing goals and does not contain confidential information.

Configuration example

Suppose you want to send SMS notifications to customers when an order is confirmed. To do this, create a rule in the CRM:

Trigger: Order creation.

Action: Send SMS.

Message text: "Your order has been successfully confirmed. Thank you for your purchase!"

Integrating SMS mailings into the CRM lets you automate sending messages to customers, which saves time and improves communication efficiency. By following the steps above, you can successfully set up SMS mailings in your CRM.

Add conditions

To add conditions in SMS, go to:

Settings − SMS − Configuration − Add "+".

Screenshot name: sms

Screenshot name: sms_dobavit_okno

Edit

To edit conditions in SMS, go to:

Settings − SMS − Configuration − Edit.

Screenshot name: sms_redaktirovat

Delete

To delete conditions in SMS, go to:

Settings − SMS − Configuration − Delete.

Screenshot name: sms_udalit

Profiles

Add

To add a profile in SMS, go to:

Settings − SMS − Configuration − Add.

Screenshot name: sms_profili_dobavit

In the "new record" window, fill in the data and click "Save".

Screenshot name: sms_profili_dobavit_okno

Edit

To edit a profile in SMS, go to:

Settings − SMS − Configuration − Edit.

Screenshot name: sms_profili_redaktirovat

Delete

To delete a profile in SMS, go to:

Settings − SMS − Configuration − Delete.

Screenshot name: sms_profili_udalit

To connect the CRM to Telegram, you need to create a bot in Telegram.

Bot

Add

To add a bot in Telegram, go to:

Settings − Telegram − Bots − Add.

Screenshot name: telegram_bot_dobavit

Screenshot name: telegram_bot_okno

Edit

To edit a bot in Telegram, go to:

Settings − Telegram − Bots − Edit.

Screenshot name: telegram_bot_redaktirovat

Bind to a domain

To bind a Telegram bot to a domain, go to:

Settings − Telegram − Bots − Bind to domain.

Screenshot name: telegram_bot_privyazat_k_domenu

Delete

To delete a bot in Telegram, go to:

Settings − Telegram − Bots − Delete.

Screenshot name: telegram_bot_udalit

Configuration

Add

To add a configuration, go to:

Settings − Telegram − Configuration − Add.

Screenshot name: telegram_dobavit

Screenshot name: telegram_okno_novoe

Edit

To edit a configuration, go to:

Settings − Telegram − Configuration − Edit.

Screenshot name: telegram_redaktirovanie

Delete

To delete a configuration, go to:

Settings − Telegram − Configuration − Delete.

Screenshot name: telegram_udalit

Add

To add a new push notification, go to:

Settings − push − bottom right, click "+" − Add push notification.

Screenshot name: push_uvedomlenie_dobavit_novoe

Fill in the information to create it.

Screenshot name: push_uvedomlenie_novoe_okno

Editing, deleting, audit log

On the right side of the block there are:

  1. Editing

  2. Deleting

  3. Audit log

Screenshot name: push_uvedomlenie_rekdaktirovat_i_udalit

Screenshot name: push_uvedomlenie_log_audit