Recipients
Choose who should receive the message, such as leads from a particular channel or members of a segment. Before starting, the list shows recipients matching the current criteria.
Selecting The Audience
In the Recipients block on the delivery page:
- Select specific leads through search if the delivery is only for them.
- Choose one or more channels, or a channel type.
- To filter by space or segment, open additional filters and set the condition.
- Check the recipient list and count.
The channel selection is saved with the delivery. All channels, including future channels includes new eligible channels at sending time. Specific channels keeps only the checked channels, even if every current channel is checked. See channel selection.
See Lead filters for details. Regardless of your criteria, deliveries include only subscribed leads of the "User" type who are not blocked or blacklisted. Project members' accounts connected for test sends are excluded from mass sending.
Supported Channels
Deliveries support Telegram, VK, Discord, Widget, and Email. MAX, Avito, and StreamVi do not support mass sending.
The channel selector shows project channels available for deliveries. Leads from deleted channels are excluded from the audience, including when all channels are selected. If a saved filter contains an unavailable channel, change the selection before starting.
Why There Are Fewer Recipients Than Leads
One user of a platform can have several lead records, for example by subscribing to two Telegram bots in the project. If both records match the filters, the delivery sends that user one message.
Recipients are counted separately for each platform. The same person's VK and Telegram accounts are two recipients. Matching names do not merge them.
Each recipient row shows the channel selected for sending. Select or hover over the channel list to see other matching options. More recipients load as you scroll.
When The Audience Is Determined
Before starting, the list changes as leads, subscriptions, and segment memberships change. Starting fixes the audience for that run. A scheduled delivery's final count can therefore differ from the preview you saw when setting it up.
If you configure a delivery through an integration, check its recipients through the API. Previewing different filters does not save them to the delivery.
Continuing after a quota pause uses the same audience and does not add new leads.
If the list is empty, check the selected channels, filters, and lead subscription status. Once configured, proceed to a test or start.
Sending Without Audience Restrictions
With no recipient filters, a delivery targets the entire eligible project audience; selecting only channels targets the entire eligible audience of those channels. Mandatory subscription, blocklist, and project-member exclusions still apply. Sending to the whole audience without further selection is not recommended.
If an agent configures this delivery, it must show the current recipient count and channel scope and obtain separate, explicit confirmation before starting or scheduling it. Approval of the message or of sending to two named groups does not approve the entire audience. Confirmation need not be repeated if the user already approved this exact scope and count.
Group names from Senler.ru are not Senler.io filters. When a user names a group, find the corresponding segment and check its members. If the mapping is unknown, clarify the audience; do not replace the group with an empty filter.