Service

Telegram Automation

Bots and agents that live inside Telegram — answering questions, routing requests, scraping group data, and running full conversation flows. Built on the official Bot API and MTProto. Deployed on Fly.io so they never go down.

Get a quote See the work

What it is

Telegram as an ops layer, not just a chat app

Most teams already run on Telegram. We extend it — a bot that responds to customer messages, a group agent that monitors and tags conversations, an auto-responder that collects leads before a human picks up the thread.

For more sophisticated use cases we reach into MTProto directly: group membership scraping, channel monitoring, and large-scale message ingestion that the public Bot API rate-limits don't permit.

Everything ships with inline keyboards and structured conversation flows — not open-ended chat that breaks on unexpected input.

Ops bot

online · MTProto

What's included

Every Telegram build ships with these

Bot API + MTProto

Standard webhooks for bots. MTProto for user-level access — group scraping, channel monitoring, bulk ingestion.

Inline keyboards

Structured reply buttons that constrain the conversation to defined paths — no free-text ambiguity, no broken flows.

Group & conference bots

Bots that operate in group chats — tagging messages, answering questions, routing to subgroups, enforcing rules.

Auto-responders

Instant replies to inbound messages matched by keyword, intent, or pattern — before a human sees it.

Group scraping

Extract member lists, message history, and engagement data from public or authorised groups via MTProto. Structured output to your database or sheet.

Persistent deployment

Hosted on Fly.io with health checks and automatic restarts. Session state persisted to Supabase — no token drops, no manual babysitting.

How it works

From brief to deployed bot

1

Audit the use case

We map the conversation flows, identify edge cases, and confirm whether Bot API is sufficient or MTProto access is needed.

2

Build the bot

TypeScript implementation. Webhook or polling. Inline keyboards, state machine for conversation flows, integrations to your backend or CRM.

3

Test end-to-end

Every flow tested with real Telegram messages before handoff. We run the failure paths, not just the happy path.

4

Deploy and hand over

Live on Fly.io with monitoring alerts. You get access to logs, the ability to update copy, and docs on how to extend it.

Self-healing behavior

Bots log every unhandled message type and every failed API call. When a pattern of failures accumulates, the system drafts a fix and surfaces it for review — it doesn't just crash silently.

Fly.io health checks restart crashed processes in under 30 seconds. Session tokens are persisted to Supabase — a restart doesn't lose conversation state.

Security and keys

Bot tokens and MTProto session strings are stored encrypted at rest in Supabase (EU region). They are never written to source code or config files — unlike some other automation shops.

GDPR compliant Encrypted at rest EU data residency

BYOK available — bring your own Telegram bot token and MTProto credentials; we never hold credentials you don't want us to hold.

Common questions

Telegram Automation FAQ

Bot API is Telegram's official public interface — it covers message sending, keyboards, webhooks, and most automation needs. MTProto is the lower-level protocol that regular Telegram clients use. MTProto access lets you operate as a user account: read group history, scrape members, monitor channels at scale, and bypass some Bot API rate limits. We use whichever is appropriate for your use case.
MTProto scraping works on public groups and on private groups where the authenticated account is a member. We don't build tools to access groups without authorisation — scraping non-public groups you're not a member of violates Telegram's terms and we won't do it.
A straightforward auto-responder or FAQ bot: 3–5 business days. A multi-flow bot with CRM integration or group scraping pipeline: 1–2 weeks. We scope it before committing to a date — the audit call is where we size it.
No. A standard Telegram account and a bot token (created via @BotFather — free) are sufficient for most builds. MTProto builds require a registered phone number for the session account, which we handle during setup.
Fly.io restarts crashed machines automatically, typically within 30 seconds. Session state is persisted to Supabase so conversations resume where they left off. You receive an alert on crash; the bot recovers without manual intervention.

Ready to build?

Tell us what you need the bot to do

Describe the use case. We'll confirm whether it needs Bot API or MTProto, scope it, and send a quote within one business day.

Get a quote