The Telegram Desk

005

Lead Systems · Agency sales inbox · Telegram

LIVE

Deployed

2026 · userbot on the founder’s account

Base

2,225 community members parsed, 906 active

Protocol

drafts only — a human hits send

For a services business in Eastern Europe, Telegram is the CRM whether you like it or not. Deals start, stall and die in one endless inbox.

The Desk connects to the founder’s account and imposes order: every dialogue is classified into pipeline folders — clients, leads, sleeping, partners — rebuilt from actual message history, not memory. A community of 2,225 members was parsed into a structured base: 906 active, segmented by niche.

Follow-ups to dormant leads are drafted by an agent in the founder’s voice and placed as Telegram drafts. Nothing sends itself: the human reads, edits if needed, and hits send. Volume of a sales team, judgment of the owner.

EXHIBIT A

Inbox as pipeline

Every chat auto-filed into pipeline folders, rebuilt from real correspondence.

desk-sort — nightly

▸ scanned 312 dialogues

▸ clients: 41 · leads: 67

▸ sleeping: 128 · partners: 22

▸ moved 9 chats → 🔥 push

▸ drafted 6 follow-ups

an inbox that files itself

EXHIBIT B

Community X-ray

A 2,225-member community parsed into a working base, segmented by business niche.

2,225

members parsed

906

active, segmented by niche

a member list became a market map

EXHIBIT C

Draft, don’t send

Outreach lands as editable drafts in the owner’s own account. Human approval is the protocol, not an option.

Draft for M. (construction, quiet 3 months): "Saw your new object on…"

Softer opener. Mention the spring project.

Redrafted ✓ — waiting in your drafts.

scale without the spam smell

Keep going — next file in the archive The LinkedIn Engine