Leads

Leads are clients and users who interact with the project through connected channels. This section helps you find a person, inspect the lead card, import or export a base, and diagnose why a contact did not appear in the project.

The section is connected to dialogs: a message from a channel usually creates or updates a lead, and the lead card can lead you back to related conversations.

What you can do

• find a lead by name or another known detail;
• filter the list by channel, channel type, subscription, blacklist status, block status, spaces, and segments;
• refresh lead data from channels;
• import a lead list;
• export leads for analysis or transfer to another system;
• configure segments and separately create landings or get direct subscription links;
• open a lead card and check variables, channels, and related dialogs.

The lead list is displayed as a table: lead, channel, subscription/blacklist status, source, and creation date. On smaller screens, some actions are grouped into a menu, and long-running actions show a background process indicator.

Some leads can be a recipient for a project member. These records are needed when a project member should receive a message through the platform, for example "Forward to me" for an attachment or a delivery test send. It is still a channel lead, so for this sending it must be subscribed, not blacklisted, and not blocked by the platform.

Lead source

The Source column shows the first action or event through which the record appeared in the project. It is not the subscription status, so read the source together with the subscription column.

• Group join means the channel reported a user join event.
• Message means the lead first appeared after an incoming message.
• Message permission means the platform reported that the user allowed messages.
• Bot added means the bot was added to a chat and the platform provided a participant or sender.
• Comment means the lead appeared from a publication comment.
• Like means VK reported that the user added or removed a like on a tracked post or comment. This lead is created as unsubscribed: the event identifies the user, but does not by itself grant permission to message them or create a subscription. Removing the like does not delete an existing lead card because the source records how the lead first appeared, not the current reaction state.
• Manual means a project member created the record.
• Import means the record was added from an imported list.

This means a new unsubscribed VK lead without a message may be expected: check the source and creation date, then inspect the corresponding VK event.

Channel or bot as a Telegram lead

In a Telegram group, a message may be sent as a channel, as the group itself, or by another bot. When the sender is another channel or a third-party bot, Senler shows it as a Channel-type lead. The message is treated as an inbound customer message and can trigger an agent under the normal assignment rules.

A message sent as the current group itself or its linked channel belongs to space activity rather than to a separate customer, so it does not trigger an agent reply by itself. This distinction prevents the bot from replying to its own publications while still allowing messages from external channels and bots to be handled.

If an unexpected channel lead appears in the list, open the linked dialog and check which identity Telegram used for the original message. There is no need to delete the record merely because of the sender type.

Project operator

Sometimes a team member replies to customers through an external account that Senler sees as a regular lead. You can mark that account as a Project operator so the agent does not interpret the team member's messages as new customer requests.

Open the required lead card and change the Project operator switch. This requires permission to manage leads. The switch is saved immediately and affects new messages; it can also be changed through an available Senler management AI tool or the API.

Use the mark only for an account that belongs to the team. It does not add the person to the project, grant cabinet access, or replace a project member role.

After the mark is enabled, new messages and button clicks from this sender remain in the dialog and history but do not trigger or assign the agent. If the operator replies while AI is preparing a customer response, the pending response is canceled by default. Remove the mark in the same way to restore regular message processing.

Messages sent as the connected group or channel itself, or by a project member, usually do not need a separate mark: Senler already recognizes that activity as coming from the project side.

The rules for choosing between a lead and a space, the difference from a project member role, and post-change verification are collected in Project Operator and Agent Replies.

In deliveries, the cabinet counts unique recipients, not just rows in the selection. One person can have several records or sending routes, but the delivery tries not to send the same message to the same recipient more than once.

List filters

Filters narrow the list when there are many leads or the needed contact is not visible at once.

• Channel shows leads from one or several connections.
• Channel type separates Telegram, VK, Email, website, and other sources.
• Subscription shows subscribed, unsubscribed, or all leads.
• Blacklist shows leads manually added to the blacklist by the team, or regular leads.
• Blocked shows leads where the platform or channel marked a block, for example the user blocked the bot. The "No" value includes leads without an explicit block flag.
• Spaces filter by chats, groups, topics, and other channel areas and separate current members from former members.
• Segments filter by segments and separate current segment members from former members.

Active filters are synchronized with the page URL, so the list can be opened by a link with filters already selected. The cabinet removes empty and duplicate values, ignores invalid filters, and limits overly long lists.

The cabinet assistant can open the lead list with the needed filters already applied. For one lead card, it uses a separate open-card action; for a large selection, it is better to open a filtered list instead of passing a long set of IDs.

If the user cannot see a lead, first reset filters and check the selected channel.

Data refresh

Refreshing leads starts a background process. It respects the selected project and current filters, and the result can be checked in the update history: how many records were updated, skipped, or finished with an error.

During a mass refresh, the interface may not show every step immediately: data is loaded in stages, and the final status is best checked in processes and event history.

If the lead did not appear

Check in order:

1. the channel is connected and receives messages and events;
2. the lead really sent a message, joined, commented, allowed messages, or produced another supported event;
3. for a lead from a Like, the connected VK channel received the post like event;
4. the list does not have extra filters enabled;
5. the lead is not hidden by blacklist, subscription status, or block status;
6. the lead refresh finished without errors;
7. if this is a recipient for a project member, it was created in the needed channel and appears in the list;
8. event history contains an event for the needed channel or dialog.

Where this is in the interface

Main elements in this section:

• Leads item in the side menu
• lead list
• lead search
• lead list filters
• lead row in the list
• lead import
• lead export
• Project operator switch in the lead card
• Dialogs item in the project side menu
• Dialogs section