Mara Vogel

Areas of work

• Broadcast queue design on the Bot API — throttling, back-off around HTTP 429 and retry_after, and retry policy that does not compound a throttle.
• Consent architecture: deep-link attribution, opt-in capture and opt-out handling that actually removes people from the base.
• Deliverability reporting — defining delivered, read, blocked and opted out so the numbers mean the same thing month to month.
• Compliance review of inherited setups, including the awkward finding that an existing list cannot lawfully or technically be messaged.

Editorial responsibilities

Every guide published here is checked by a named person before it goes out; Mara holds that responsibility for the messaging and automation topics. In practice that means three checks:

1. Every platform figure is traced to Telegram's own documentation, and quoted with its original wording where the wording matters — advice and hard caps are not the same thing.
2. Where Telegram publishes nothing, the guide says so, instead of repeating a number found on a vendor page.
3. Every method is published with its limit in the same section, and articles are updated substantively or retired.

Published guides

Each entry is dated, signed, and checked against the three rules above before it appears. The standard a guide has to clear is published alongside them.

• Telegram Ads Cost: What Telegram Actually Publishes — 17 August 2026. The one advertising price Telegram publishes and the absence of any minimum deposit, every circulating entry figure set against the documentation, the commission and currency lines above the CPM, the destination-quality clauses by section number, and the categories the guidelines close off.
• Telegram Ads Agency: What You Are Actually Buying — 17 August 2026. What an agency retainer actually bundles, the Ad Platform terms on who may bid from an account and what happens to an unspent balance, the parameters Telegram publishes against the figures the market states, and where forex and real estate really sit in the guidelines.
• Telegram Member Add Bot: What Your Code Can Call — 7 August 2026. Why the Bot API exposes no method that adds a user to a chat, which Telegram libraries do carry the call and on whose credential it runs, the update Telegram withholds unless a bot asks for it, and the approval-gated flow that replaces the add.
• Telegram Shill Bot: What It Actually Runs On — 7 August 2026. Why no bot can join a group on its own, what the tooling runs on instead, the published error tables for posting and joining, Telegram's own native antispam system, and the paid-promotion disclosure rules that sit above the platform's terms.
• Telegram Invite Member Bot: What It Can Add — 4 August 2026. Why the Bot API has no method that adds a user to a chat, the documented invite-link parameters and their limits, the errors the client API returns instead, and the daily figures Telegram never published.
• Telegram Scraper: What It Can and Cannot Collect — 3 August 2026. Why the Bot API cannot list members at all, the errors Telegram publishes for the method that can, the terms clause covering scraping, and the figures the market states that Telegram never printed.
• Telegram Mass Report Bot: Does It Actually Work? — 31 July 2026. Why no bot can file a Telegram report, what the panels and scripts actually sell, Telegram's own moderation counters, and what to do if a channel is the target.
• Telegram Mass DM: What Telegram Actually Documents — 30 July 2026. Every published send limit with its original wording, the four things Telegram documents nowhere, and the contradictory daily limits the vendor market states as fact.

Contact

Project enquiries go through the contact page so they arrive with the setup attached. For a correction to a published guide, email [email protected] with the article URL and the specific claim — corrections that identify a wrong figure get priority over everything else in the inbox.