Monster-Lead
Inbox Router — Telegram DM routing and auto-reply
Inbox Router handles incoming private messages on your Telegram sessions: what used to be called an auto-responder is now routing plus an optional auto-reply. Every new DM lands in a manager group, in the connected bot and in a single Inbox feed inside the cabinet — and, if you want it, the client immediately gets an answer as text, a voice message or a video circle from the Media Library. Below: the chain inbound → filter → route → auto-reply → Lead CRM, which limits and pauses to set, how a session differs from Bot API, and a detailed FAQ.
Inbox Router is a public Monster-Lead Telegram module. It connects to Radar, Terminal, CRM and the rest of the platform.
How to use: open Inbox Router in the Monster-Lead cabinet after signup, connect a session in Terminal and a proxy if needed. The module ties into Lead CRM so leads and chats are not lost in DMs.
Who it is for: media buyers, agencies and sales teams that need Telegram lead gen and automation without scattered scripts. Free includes a 14-day starting path.
Start free
14 days on Free: connect a session, set Radar keys, catch intent in Telegram chats. Support channel: t.me/monsterlead.
How Inbox Router works: from an inbound DM to a CRM card
What happens after an inbound message When someone writes to the DMs of your Telegram session, Monster-Lead captures the event on the connected account. This is not Bot API and not a separate bot username — it is a live account from Terminal that already works in your lead gen: replying to Radar leads, following up after channel comments, taking inbound from ads and bio links. The event goes through a filter. If trigger keywords are set, the Router reacts only to messages containing them; an empty list means every DM. Users on the exclusion list are ignored completely — handy for teammates, partners and existing clients you do not want treated as new leads. Where the inbound goes A message that passes the filter fans out to three destinations at once. First, the manager group: you provide an ID like -100… or a @username, and a notification about the new dialog lands there. Second, the connected bot when the notify flag is on — useful for teams that live in a bot instead of a group. Third, the Inbox feed in the cabinet: a single list per session with the author name and @username, timestamp, event status, message preview and an attachment marker. Each event links to the lead card in Lead CRM. How the auto-reply works The auto-reply is optional. You can set text, pick an asset from the Media Library (voice or circle) or combine both. Before sending, the system waits a random pause inside your range — 3 to 15 seconds by default — then checks the hourly cap, the daily cap and the per-user cooldown. Cooldown 0 means “reply to every message”, a value in seconds means “no more than one reply to this person within that interval”, so a single lead never receives five greetings in a row. Media Library: voices and circles Files are not uploaded from the browser: you send a voice message or a video circle to the Monster-Lead bot, it stores the file on the server, and the record appears in the Media Library. In the cabinet you give the file a readable name, choose a funnel stage — first_touch, followup, closing or custom — and optionally mark it as the auto-reply asset. The library is shared, so AI Manager picks up the same voices and you never record the same “hi, I am here” twice. Limits and why they matter Defaults are a 3–15 second pause, up to 40 replies per hour and 300 per day per session. That is a ceiling, not a target: on a fresh account start with 10–15 replies per hour and keep the pause near the upper bound. The Router never exceeds a cap — the message still reaches the feed and the managers, just without an automated reply. Forwarding and notifications are not capped; only the outgoing auto-reply is. Why the session must be ACTIVE The module listens to events on a live account, so enable it on a session with ACTIVE status. If the session is paused, the cabinet shows a banner with a resume button and inbound messages are not processed. Before launching, assign the account a dedicated SOCKS5 proxy and warm it up so the auto-reply is not the very first activity on an empty account. How this differs from a Telegram bot A Bot API bot is a separate participant: the bot label, its own funnel, restrictions on initiating messages, and no way to reply as your account. Inbox Router runs on the user session: the client sees a normal profile with history, avatar and bio, and a voice message from a real account feels nothing like bot text. The bot still has a place in the setup — as the team notification channel and the media uploader, not as the client-facing party. The full chain Inbound DM → Terminal session → keyword and exclusion filter → manager group + bot + Inbox feed → optional auto-reply as text, voice or circle with pause and cap checks → Lead CRM card → manager continues with TG Replies scripts. Every step is visible in the interface: event statuses in the feed, “today” and “total” counters, current hourly and daily caps. Search semantics People search differently: Telegram auto-responder, auto-reply in DMs, auto-reply without a bot, forward Telegram DMs to managers, new message notifications, lead routing, distributing inbound between managers, voice auto-reply, video circle reply, inbox duty, Telegram inbox for teams. Inbox Router covers all of these — only the routing rules and the reply content change. A practical one-day launch Morning: proxy and warmup in Terminal, session switched to ACTIVE. Midday: create the manager group, paste its ID into the rules, enable bot notifications, leave keywords empty so you can see the entire flow. Record one voice in the bot — “I am here, tell me what you need” — and assign it as the auto-reply asset with the first_touch stage. Set a 5–15 second pause, 15 replies per hour, a 3600 second cooldown. Evening: open the Inbox feed and check how many DMs arrived, how many got a reply and which dialogs managers already pulled into CRM. Adjust keywords and caps the next day based on facts, not guesses.
Semantics: auto-responder, DM routing, voice reply
People search differently: Telegram auto-responder, auto-reply in private messages, auto-reply without a bot, forward inbound DMs to managers, new message notification, lead routing, distributing inbound between managers, voice auto-reply, video circle reply, inbox duty, Telegram inbox for teams. Use these phrasings naturally — one module covers both “auto-reply” and “inbound routing”.
The whole team sees inbound, not just one account
Private messages on a working session are normally visible only to whoever holds the phone. Inbox Router copies every inbound DM to a manager group and the connected bot, and keeps a cabinet feed across sessions: who wrote, when, what exactly, and whether there was an attachment.
Auto-reply is optional, not mandatory
You can run the Router as pure routing with zero automated messages to clients. When you do want a first touch, add text, a voice message or a circle and set a 3–15 second pause, an hourly cap and a per-user cooldown so the reply never reads like a bot.
Voice and circles instead of a dry template
Voices and video circles are recorded in the Monster-Lead bot and land in the Media Library. There you rename files, tag a stage (first_touch, followup, closing) and assign one as the Inbox reply. AI Manager uses the same assets — one library for the whole team.
Route to group and bot
Every inbound DM goes to a manager group by ID or @username and to the connected bot — the team reacts without opening the account.
Keywords and exclusions
An empty keyword list means every DM. The exclusion list removes teammates and partners from processing entirely.
Text and media auto-reply
Text, a voice message or a circle from the Media Library — separately or together. Each asset carries a funnel stage.
Pauses, caps, cooldown
A 3–15 second pause, up to 40 replies per hour and 300 per day, per-user cooldown so one lead never gets a series of greetings.
Inbox feed and counters
Author name and @username, timestamp, status, message preview, attachment marker, plus “today” and “total” counters per session.
Lead CRM and TG Replies
A feed event opens the lead card, and the manager continues the dialog with ready-made TG Replies scripts.
Why inbound must reach the team immediately
First-response speed in messengers directly affects dialog conversion. The bottleneck is usually not the wording but the fact that nobody learned about the message: it sits in the DMs of an account the duty staff cannot open. Routing to a group and a bot fixes that without any auto-reply, while automation only holds the client until a human joins.
FAQ
What does Inbox Router do?
The module listens to incoming private messages on a selected Telegram session and fans them out to three destinations: a manager group, the connected bot and the Inbox feed in the cabinet. It can additionally send an auto-reply — text, voice message or video circle — with a pause and caps. Every event is visible in the feed: author name and @username, timestamp, status, message preview, attachment marker and a link to the Lead CRM card. In practice it is a round-the-clock inbox duty officer that needs no access to the account itself.
Is this the same auto-responder as before?
It is its evolution. The previous module could only reply to inbound messages, which is why it was called “Auto-responder”. Inbox Router keeps the auto-reply as an option and adds the important part — routing: forwarding to a manager group and bot, a single inbox feed, keyword and exclusion filters, per-user cooldown, and voices and circles from the Media Library. In the cabinet the tab is called Inbox Router and lives in the “Session work” section.
Can I enable routing only, without any auto-reply?
Yes, that is a standard setup. Leave the text field empty and pick no asset — the Router will only forward inbound DMs to the group and bot and fill the feed. The auto-reply is one setting away whenever you decide what the first touch should be.
Where exactly do notifications go?
To the manager group you specify with an ID like -100… or a @username, and to the connected bot if the notify flag is on. Both channels work at the same time: a group suits a department, a bot suits one or two people on duty. Plus the Inbox feed in the cabinet, where events are stored with history.
How do keywords work?
One keyword per line. If the list is empty the Router processes every private message — a good way to start and see the real flow. When there is too much noise, keywords keep only relevant requests: role names, product names or words like “price”, “demo”, “exchange”.
What is the exclusion list for?
To remove people who should not be treated as leads: teammates, partners, contractors, existing clients. Listed usernames are ignored entirely — no auto-reply and no notifications for them.
What are the default limits?
A 3 to 15 second pause before sending, up to 40 auto-replies per hour and 300 per day per session, per-user cooldown 0. Treat those as boundaries, not recommendations: on a new account start with 10–15 replies per hour and set the cooldown to at least 1800–3600 seconds.
What does the per-user cooldown mean?
The minimum interval between auto-replies to the same person. Zero means replying to each of their messages, which fits a “receipt confirmation” scenario but hurts in a live dialog where the client keeps getting greetings. A value in seconds solves it.
What is Inbox Router?
Route incoming Telegram DMs: manager group, bot notification, inbox feed and auto-reply as text, voice message or video circle with limits.
How do I open Inbox Router in Monster-Lead?
Module page: /en/tools/avtootvetchik-telegram. Full catalog is /en/tools, pricing is /en/pricing, articles are /en/news.
Start free
14 days on Free: connect a session, set Radar keys, catch intent in Telegram chats. Support channel: t.me/monsterlead.