Sendhaus
Telegram

Telegram-first · built on published limits

Telegram messaging and automation, built on the published limits

We build opt-in broadcast, channel growth and bot automation on Telegram's documented API — with the rate limits, the consent trail and the ban triggers written down before anything sends.

Get a deliverability audit Telegram — reply in 12 h

What does Sendhaus do? Sendhaus builds Telegram messaging programmes: opt-in broadcast to subscribers, audience growth through official Telegram Ads and channel strategy, and custom bots that connect Telegram to a CRM. Everything runs on Telegram's Bot API within its published rate limits, using consent you actually collected. We do not sell cold DM campaigns to scraped member lists — that is the practice that gets accounts limited and banned.

What we build

Three areas of work

Each one has its own mechanics, its own published limits, and its own honest ceiling. Most programmes use two of the three — the services overview sets out how they fit together.

  1. Broadcast & bulk messaging

    Opt-in broadcast to people who started your bot or joined your channel, queued below the documented send limits, with delivery states and opt-outs reported back.

  2. Growth & marketing

    Official Telegram Ads, channel and community strategy, cross-promotion and partnerships — plus a plain account of what bought members do to a channel afterwards.

  3. Bots & automation

    Custom bots, Mini Apps and CRM integrations built on the Bot API — including a written list of what the API structurally cannot do before you commission anything.

The numbers that govern everything

Four published limits worth knowing before you buy anything

These are Telegram's own figures, not vendor folklore. Any proposal that contradicts them — from us or anyone else — is describing something the platform will not do.

Bulk broadcast~30 / secFree ceiling before HTTP 429
Paid Broadcasts1,000 / sec0.1 Stars per message over the free tier
Per group20 / minStated as a hard cap
Cold messages a bot can send0Bots cannot start conversations

“Bots can't start conversations with users. A user must either add them to a group or send them a message first.”Telegram — Bots: An introduction for developers

That single sentence decides most Telegram briefs. If the plan is “message our list of 50,000 prospects”, a bot cannot do it, and the workaround — driving a real user account through an unofficial client — is what Telegram's API terms describe as grounds for a permanent ban. The workable version is to convert that list into subscribers first, which is slower to start and vastly cheaper to run.

How a programme is built

Audit first, sending last

The compliance gate sits before the build, not after the first wave of restrictions.

  1. Audit the existing setup

    Sender identity, current tooling, and whether a consent trail exists at all. This is also where we say if the goal is not reachable inside the rules — before anyone signs anything.

  2. Build the consent base

    Bot start links, channel joins, deep links with attribution parameters, and website capture. The base is yours and it is auditable: every subscriber has a recorded origin.

  3. Build the sending path

    Queue, retry and back-off around HTTP 429 and retry_after, per-chat throttling, opt-out handling, and CRM hooks so the message log lives somewhere you can read it.

  4. Ramp, do not blast

    Volume is raised in steps while report rate and delivery states are watched. A campaign that clears the rate limit but collects reports is still on its way to a restriction.

  5. Report on states, not sends

    Queued, sent, delivered, read, blocked, opted out — monthly, against the same definitions each time. “Messages sent” is the number vendors quote precisely because it cannot fail.

The four refusals

What we will not do

Four things get asked for regularly. All four are declined, because each one ends with the client's asset destroyed rather than ours.

Cold DM campaigns to scraped members. Scraping a group's member list and messaging strangers breaks Telegram's terms twice over — the collection and the messaging — and the accounts doing the sending are the ones that get limited. Telegram's spam FAQ is explicit that reported accounts are restricted to contacts who have saved their number, first for days and eventually for good.
Bought members, views and reactions. Telegram's API page states that faking subscriber and view counters results in a permanent ban. Beyond that, purged accounts silently vanish from your subscriber count later, and the engagement rate you are left with is worse than the one you started with.
Account farms and rotation to “beat” the limits. Rotating burner accounts to keep sending is a cost structure, not a strategy: every restricted account is a replacement to buy, and Telegram states that accounts using unofficial API clients are automatically placed under observation.
Guaranteed delivery or conversion numbers. Delivery depends on recipient privacy settings and platform-side filtering that no vendor controls. We report ranges from your own data once it exists, and we do not quote a benchmark we cannot source.

Asked before every engagement

Common questions

Can you send mass DMs to people who have not contacted us?

Not with a bot, and not safely with anything else. Telegram's own developer documentation states that bots cannot start conversations with users — a user must message the bot or add it to a group first. Reaching strangers means driving a normal user account with an unofficial client, which Telegram's API terms describe as grounds for a permanent ban. We build opt-in broadcast instead: people who started your bot or joined your channel.

How many messages per second can a Telegram bot send?

Telegram's Bots FAQ gives three published numbers: avoid more than one message per second in a single chat, no more than 20 messages per minute in a group, and roughly 30 messages per second for bulk notifications before you start receiving HTTP 429 errors. Paid Broadcasts, enabled through BotFather, raise the ceiling to up to 1,000 messages per second at 0.1 Telegram Stars per message above the free tier.

Do you work with platforms other than Telegram?

Telegram is where we do most of our work and where our published guidance is deepest. The delivery method is the same everywhere: a consent base you actually own, a queue that respects the platform's documented limits, and reporting on delivery states rather than on messages pushed. We take on work on other messaging and social platforms when that method transfers cleanly.

What does a Telegram bot cost to build and run?

The Bot API itself is free. The costs are build, hosting and maintenance: quotes across the market run from a few hundred dollars for a single-purpose bot to five figures for CRM-integrated systems, plus hosting and any model usage. We quote build and first-year running cost together, because a build price on its own tells you very little about what the system costs to own.

Start with the audit

Send your current setup — bot, channel, tooling, list origin. You get a written read on what is compliant, what will be rate-limited, and what will get the account banned. No charge, and no follow-up sequence.

Request the audit