Leadgram
Product

Telegram Outreach Automation That Automates the Finding, Not the Sending

Telegram outreach automation in Leadgram automates the finding, not the sending: a campaign is a saved brief plus a watchlist of public Telegram channels that Leadgram re-searches on a cadence you pick — every hour to once a week — and every new person it catches is filed with an intent score of 0-100 and a plain-language reason for the match. There is no send step anywhere in a campaign: no auto-DM, no sequence, no scheduled follow-up. You write the first message yourself.

Caught by a sweepIllustrative example
  • TW

    Tom W.

    @tom_pageturners

    Hot
    88intent score

    Indie booksellers UK· public group · found 25 min ago

    We run a small new-and-secondhand bookshop in Leeds and our till can't handle used stock at all. Looking for a POS with inventory that copes with one-off secondhand books, ideally switched over before Christmas. What do you all use?

    Why · Wants to replace a till system before a set date; matches “independent bookshops that need a new POS”.

The kind of message a sweep catches in a watched chat; the campaign files the person with a 0-100 intent score and the reason they matched.

What a campaign automates — and what it deliberately doesn't

Between sweeps you do nothing. Each sweep re-runs the same semantic search you would run by hand, keeps only the hits from channels on your watchlist, and files everyone the campaign has not seen before with an intent score and a match reason. It never sends a message.

  • Automated: searching, re-checking, scoring, de-duplicating, and logging every sweep.

  • Always manual: the message you write and the moment you send it.

  • Not built at all: auto-DMs, bulk sequences, unattended follow-up chains.

Building one: Brief, Watchlist, Launch

Brief is a name and a description of your ideal customer in ordinary words — every message is scored against this text. Sharpen with AI offers a tighter version beside your own; you press Use this or Keep mine. Your wording is never silently overwritten, and if the model is unavailable your own text comes back unchanged.

Watchlist says where to look: public channels and groups added by @handle, a t.me link, or the room's title. Links are normalised to the handle, a string that cannot be a Telegram username is rejected as you type, and a channel already listed says so instead of appearing twice. Each arrives with keyword chips seeded from your brief.

Launch picks the frequency, replays the campaign back to you, and starts it — created active with its first sweep already due, so it begins on its own within minutes. The draft survives a refresh, and cancelling a half-written campaign asks first.

Campaign setup

  1. Step 1: Brief

    Name the campaign and describe your buyer in plain words.

    step 1

  2. Step 2: Watchlist

    Add public channels by @handle, t.me link or title, each with keyword chips.

    step 2

  3. Step 3: Launch

    Choose hourly to weekly, review, go live. The first sweep is due at once.

    step 3
Three steps to a campaign: say who you want, say where to look, pick how often.

  • Brief: the campaign name and who you want, in plain language.

  • Watchlist: public channels or groups, each with its own keyword chips.

  • Launch: choose the cadence, review, and go live.

See also: How the semantic search behind it works

What one sweep actually does

For each channel the campaign runs one search per keyword — a channel with no keywords of its own falls back to the brief, so nothing goes unsearched. Every hit is then checked back against that channel, forgivingly in both directions, so @rustlang still lines up with a room titled Rust Developers while a hit from elsewhere is dropped.

Then the part that keeps a campaign readable over weeks: de-duplication by person. Anyone already found is skipped, so each lead appears exactly once, on the sweep that first caught them.

Finally it schedules the next sweep by its own cadence and logs this one. A due campaign is picked up by a background scanner on its next pass, so sweeps land within a few minutes of their scheduled time rather than to the second — and Run now skips the wait.

Illustrative example
Independent bookshops · North of Englandpublic group · on the watchlist

  1. Maggie

    Sold a signed first edition today to a man who thought it was a cookbook

  2. Owen

    Our stock still lives in an Excel file and a notebook. Can anyone recommend inventory software that syncs the shop with our website?

    Buying intentHot · 86

  3. Ruth

    Honestly, the notebook has never crashed on me

In a chat on the watchlist, small talk never becomes a lead; the person asking for help is what a sweep files, with a score and reason.

  • Search each watchlist channel, keyword by keyword — or by the brief when it has none.

  • Each keyword pulls a bounded batch of top matches, so two or three specific keywords beat one broad one.

  • Keep only the hits whose channel matches that source.

  • Skip everyone the campaign has already found.

  • Store the new people with score, reason and time found, then reschedule and log the sweep.

See also: How the 0-100 intent score is built

Automation should decide who deserves a message. It should never decide to send one.

Cadence, pause, resume, edit

The frequency is a straight choice: every hour, every 3, 6 or 12 hours, daily, or weekly — six hours is the default. Fast cadences suit noisy rooms where a question is buried by the afternoon; weekly is plenty for a quiet, high-value community.

Pausing stops the sweeps and keeps everything else — brief, watchlist, keyword chips, every lead found. Resuming schedules a sweep immediately instead of waiting out the interval. Editing reopens the same three steps, and the watchlist you submit replaces the old one wholesale.

Campaign controls
Sweep cadence
1h – 1wk
Hourly, every 3, 6 or 12 hours, daily or weekly
Default cadence
6h
Any state
Run now
Skip the wait, even when paused
Messages sent for you
0
No auto-DM, no sequence
What you control on a campaign's clock, and what it will never do on its own.

  • Run now works in any state, so you never wait on the schedule.

  • Pause keeps the configuration and everything found; resume sweeps straight away.

  • Delete removes the campaign with its watchlist, leads and run history — permanently.

Two ledgers: the leads and the runs

Latest leads lists the people the sweeps caught, newest first: an intent score bar, the person's name and @handle once their identity resolves, the match reason in plain language, and how long ago they were found.

Run history holds the recent sweeps, each tagged manual or auto with how many new people it produced and when. That is the honest answer to "is this campaign working?" — a column of zeroes means the brief or the watchlist is wrong, not that Telegram went quiet.

  • Per lead: intent score, person, match reason, when it was found.

  • Per sweep: manual or auto, how many new leads, when it ran.

  • Per campaign card: status, next-sweep countdown, watchlist, total leads found.

  • The overview sorts active campaigns first, then whichever sweeps soonest; a name filter appears past six.

See also: Analytics across your searches and leads

What a campaign is not: saved search, keyword monitoring, drip, mass DM

Four things get confused with a campaign. Only a campaign has a clock, and none of them makes Leadgram send a message.

Mass DM / drip tooltypical outreach bot
  • Messages a scraped member list
  • Fixed sequence on a timer
  • Sends whether or not anyone asked
  • Risks spam reports on your account
Leadgram campaignLeadgram
  • Re-runs a brief against your watchlist
  • Files only people it has not seen
  • 0-100 score and a reason for each
  • You write and send the first message
A mass-DM or drip tool sends on a timer; a Leadgram campaign only finds and scores people.

  • Saved search: a bookmark on a search you already ran — the query, its source, and the scored people it returned, reopened in one click. It does not re-run itself. See saved searches.

  • Keyword monitoring: matching on meaning rather than exact words, so a buyer who phrases the need their own way still surfaces. That is how matching works, not a schedule. See keyword monitoring.

  • Drip campaign: a fixed sequence of messages on a timer, sent whether or not the person asked for anything. There is no sequence step in a Leadgram campaign.

  • Mass DM tool: you supply a scraped member list and it messages everyone on it. Leadgram does not do this.

  • Leadgram campaign: a standing brief that re-runs itself on a cadence against a fixed watchlist and accumulates scored, explained, sourced people over time.

Why nothing sends itself

Everything a campaign reads is a message somebody chose to post in a public room. That is a signal, not a mailing list: you are answering a specific question, not turning up uninvited.

Because campaigns have no send step, there is no way to blast a channel from one. When someone is worth contacting you open the conversation in the inbox and write it yourself, from an account you connected, one person at a time. The campaign itself needs no connected account — sweeps search the same index of public conversations the manual search uses.

  • Public messages only — nothing private, nothing behind an invite link.

  • Answer the message that matched: the reason sits right there in the ledger.

See also: Telegram data, scraping, and GDPR

Teams, and where campaigns sit in the workflow

A campaign belongs to a workspace, not to a person. In a Teams workspace every active member sees the same campaigns, runs and edits them, and reads the same two ledgers — one rep's sweep fills the whole team's ledger. A campaign from a workspace you are not in reads as not found.

Search is where you find out that a brief works. A campaign is what you do with it next: freeze it and point it at the channels that produced.

  • Search — find the brief that actually works.

  • Campaign — keep it running against the channels that produce.

  • Inbox — write the first message yourself.

  • Pipeline — track what happens after they reply.

See also: How a shared team workspace worksThe unified Telegram inboxThe built-in pipeline board

Frequently asked questions

Does Leadgram send Telegram messages automatically?

No. A campaign only finds, scores, and files people — there is no automated DM, no message sequence, and no scheduled follow-up in it. Every message is written by you, from a Telegram account you connect yourself.

How often does a Telegram campaign run?

You choose the cadence at launch: every hour, every 3, 6, or 12 hours, daily, or weekly. A background scanner picks up due campaigns, so a sweep lands within a few minutes of its scheduled time. A changed cadence takes effect from the next completed sweep, and Run now never waits.

Do I need to connect a Telegram account to run a campaign?

No. A campaign searches Leadgram's index of public Telegram conversations, so it runs with no account of yours attached. You connect your own Telegram account only when you decide to message someone, because that message is sent from you, by you.

Is this a Telegram drip campaign tool?

Not in the usual sense. A drip campaign fires a fixed sequence of messages at a list on a timer. A Leadgram campaign keeps rebuilding the list instead — people publicly showing intent in the channels you picked — and leaves every message for you to write.

What stops the same person showing up sweep after sweep?

Each sweep de-duplicates against everyone the campaign has already found. A person is filed exactly once, on the sweep that first caught them, with the intent score and match reason from that moment. Later sweeps add only people the campaign has never seen.

What happens when I pause or delete a campaign?

Pausing stops the sweeps and keeps everything else — brief, watchlist, keywords, and the leads already found; resuming schedules a sweep straight away. Deleting removes the campaign with its watchlist, found leads and run history, and cannot be undone.

Find your next leads in Telegram

Run a search, review scored matches with the reason they fit and the source group, and export a clean list — all from public signal, no Telegram login.

Try LeadgramExplore Leadgram