Telegram Audience Parser in Deskgram 2

This guide explains how to use the audience parser in Deskgram 2: how to choose sources, how filters affect the result, and how to prepare an export for the next module.

What this module does

The audience parser collects users from selected Telegram sources. It does not send messages and does not invite users anywhere. Its role is to prepare a clean target base for later modules.

What to prepare before launch

• Accounts that can access the needed channels or groups.
• A source list with relevant Telegram communities.
• A clear idea of who should be collected.
• Filters that separate useful users from noisy results.

Recommended setup order

1. Add the sources

First load the channels, groups, or links where the parser should work. The source list defines the overall quality of the collected audience.

2. Configure filters

Set the rules that decide which users should be included in the result. Filters are the main tool for improving relevance.

3. Run a small test collection

Before collecting at scale, launch a smaller batch and review the first result. This makes it easier to see whether the source list and filters are correct.

4. Review logs and export

After the run, check logs and the resulting export. This is where you confirm whether the dataset is ready for outreach or invite scenarios.

Main setting groups

Source list

This setting determines where the parser searches for users. Irrelevant sources create irrelevant exports.

Filters

Filters control relevance. They are responsible for who stays in the result and who gets excluded.

Accounts

The parser depends on accounts that can access the chosen communities. If access is missing, the collection quality falls immediately.

Export logic

The export format matters because it affects how easily the next module can use the data.

What to check first if results look weak

• The source list may be too broad or too weak.
• Filters may be too loose, so the export contains noise.
• Accounts may not have enough access to the source communities.
• The first run may not have been reviewed before scaling.

Common mistakes

• Collecting from sources that do not match the later scenario.
• Running without filters.
• Ignoring logs after the first launch.
• Sending outreach immediately without checking export quality.

What to use with this module

• Direct Messaging if the next step is private outreach.
• Invite Tool if the next step is moving users into groups.
• Join Groups if accounts first need to enter the target communities.

FAQ

Can I preview the module before installation?

Yes. You can open the interactive web preview and inspect the parser interface in the browser.

Does this module contact users?

No. The audience parser only collects and prepares data. Messaging and invitations are handled by separate modules.