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 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.