Everything in one chat vs channels with rules
In a bot chat, a $79 renewal and a “user logged in” look the same. In Ahem they’re in #payments and #signups, and only #payments buzzes.
A Telegram bot is free, quick to set up and already on your phone, which is why it’s where most of us start. It stops working well once several apps and hundreds of events share one chat: everything has the same weight, you can only mute all of it, and you can’t filter or count anything. Ahem keeps every event in channels with levels and buzzes you only for the ones you chose.
| Ahem | Telegram bot | |
|---|---|---|
| Setup | Sign up, one HTTP request | Create a bot with BotFather, find the chat id, one HTTP request |
| Cost | Free plan; Maker $12/mo | Free |
| Separation | Projects → channels | One chat per group you create |
| Severity | info · success · warning · error | None (text only) |
| What buzzes | A rule per channel and per person | The whole chat, or nothing |
| Search | Full-text, plus filters by level, type, user, metadata | Text search in the chat |
| Numbers | Counters (count or sum) | None |
| Formatting | Markdown, no escaping | MarkdownV2 needs 18 characters escaped |
| Rate limits | 10 events/s per project, bursts of 100 | About 20 messages a minute to one group |
| Teammates | Invitations with per-person rules Planned | Add them to the chat (whole history, same noise) |
Checked 15 November 2026. Prices and features change; tell us if something is out of date: support@useahem.com.
Sources: Telegram Bot API, Bots FAQ.
In a bot chat, a $79 renewal and a “user logged in” look the same. In Ahem they’re in #payments and #signups, and only #payments buzzes.
A bot message is text. An Ahem event has a level, a type and metadata, so you can ask for type:payment.failed plan:pro or sum metadata.amount for this week.
Telegram’s MarkdownV2 requires escaping _*[]()~`>#+-=|{}.!. One unescaped dot in an email address and the message is rejected. Ahem takes plain Markdown.
A bot posting to a group is limited to about 20 messages a minute. Ahem accepts 10 events a second per project with bursts of 100, and keeps them all.
Replace the bot call with one request to Ahem. The project and channel are in the URL; a new channel name creates the channel.
# Every . ( ) in the text must be escaped for MarkdownV2
requests.post(
f"https://api.telegram.org/bot{TOKEN}/sendMessage",
json={
"chat_id": CHAT_ID,
"parse_mode": "MarkdownV2",
"text": "💸 New subscription from anna\\.k@mail\\.com \\(Pro\\)",
},
)# Plain text, no escaping; the level decides what buzzes
requests.post(
"https://api.useahem.com/v1/channels/my-app/payments",
headers={"Authorization": f"Bearer {AHEM_KEY}"},
json={
"title": "💸 New subscription: $12/mo",
"level": "success",
"type": "payment.received",
},
)Keep the bot running alongside Ahem for a week, then turn it off.
Forwarding chosen events to Telegram, and a drop-in endpoint that accepts Telegram Bot API calls (so switching will be a one-line change), are planned. Planned
| Ahem | Telegram bot | |
|---|---|---|
| Free | 3,000 events a month, 2 projects, 7 days of history | Free, no limit on messages beyond Telegram’s rate limits |
| Paid | $12/month or $120/year: 100,000 events a month, unlimited projects, a year of history | Nothing to buy |
Prices in USD, checked 15 November 2026. Ahem pricing in full.
Something else? Write to support@useahem.com.
Keep a Telegram bot running while you compare. Your first event takes one HTTP request.