Pay Only for What You Use: Introducing the Credits and Addons Ecosystem

Telegram bot pricing is usually all-or-nothing: you pick a plan, you get a bundle of features, and you hope that bundle matches your real workflow. On January 28, 2026, we announced a different model for Auto Forward Messages: a Credits and Addons ecosystem designed around flexibility — pay only for what you use, activate specific capabilities when you need them, and keep your workflow uninterrupted with clear renewal options.

This post expands the official announcement into a practical guide: how credits work, how addons unlock extension features for a defined duration, what gifting and auto-renew enable for teams, and how the new UI supports both mobile and web users.

If you’re evaluating the bot itself, the best starting point is /products/telegram-forward and the setup guide /blog/automating-telegram-message-forwarding-complete-setup-guide.

Table of Contents

• Why pricing models matter in automation
• Credits: an in-app currency that doesn’t expire
• Addons: unlock individual features (30-day duration)
• Gift addons & gift plans
• Auto-renew: avoid interruptions
• Modern gradient UI for mobile and web
• Use cases: pay-per-feature in the real world
• FAQ
• Conclusion

Telegram bot pricing that matches automation reality

Automation tools are infrastructure. When you rely on a Telegram forwarding pipeline for operations, pricing affects behavior:

• Teams want predictability: no surprise lockouts during critical periods.
• Workflows vary: some users need multi-target fan-out, others only need simple forwarding.
• Features are unevenly valued: OCR might be essential for one user and useless for another.

A credits + addons approach aims to match this reality. Instead of forcing everyone into one bundle, it lets you activate the features that map to your actual pipeline — whether that’s multi-target distribution, AI rewriting, or high-throughput bot delivery.

Credits: an in-app currency that never expires

The Jan 28 announcement introduced Credits as a currency within the app. The key properties:

• Never expire: credits stay available until you use them.
• Purchase options: via in-app purchase (IAP) or crypto.
• Referral conversion: convert referral rewards into credits.
• Transparent tracking: see transactions clearly.

“Never expire” is a deceptively important detail: it means you can stock up when convenient, then activate features when you’re ready — without fighting a timer.

Transparent tracking: treat credits like a ledger

Credits only work when they’re legible. Transparent transaction tracking makes it possible to answer basic operational questions quickly: what did we buy, what did we spend, and what’s currently active?

Two practical habits that keep teams out of trouble:

• Calendar renewals: note which addons are required for business-critical routes, and renew ahead of time.
• Start with one route: enable addons on a single forwarding workflow, evaluate impact, then expand.

Purchase paths: IAP and crypto

The announcement highlighted two purchase paths: in-app purchases (IAP) and crypto. The important operational point is optionality: teams in different regions and payment situations can still fund a workflow without blocking on a single payment rail.

If you’re running forwarding as part of a business process, choose the purchase path that best fits your accounting and renewal habits, then standardize it across the team.

Referral rewards: convert and reinvest

The announcement also mentioned converting referral rewards into credits. Practically, this encourages the healthiest kind of growth loop: users recommend the tool because it’s useful, and rewards become budget for the same workflows that created value in the first place.

For teams, the simplest way to treat referrals is as a small “innovation budget” for trying new addons (AI Mode for a month, bot delivery for a launch window) without touching your primary spend.

Credits as operational control

When credits are tied to addons and renewals, they become a control surface for teams. Instead of asking “which plan should we buy,” you ask “which capabilities do we need for the next 30 days?” That aligns spend with operational phases: migrations, launches, seasonal volume spikes, or multi-language expansions.

Addons: unlock individual features for 30 days

Addons (extension features) are the heart of the new ecosystem. The announcement described them as:

• Feature unlocks instead of full plan upgrades.
• Simple toggles or configurable options.
• 30-day duration (renewable).

This is useful because forwarding pipelines evolve. You might start with basic forwarding, then add multi-target fan-out when your distribution grows, then add AI Mode when you need translation and OCR, then add Bot Sender mode when delivery volume demands it.

Addon budgeting: match features to the month’s goals

Because addons are time-bounded, you can plan them around goals: a month of translation while launching regional channels, a month of high-throughput delivery during an event, or a month of AI summarization during a news cycle. This makes spend easier to justify because it’s tied to outcomes.

To understand what those capability layers look like, these posts map the feature progression:

• /blog/multi-target-forwarding-revolution
• /blog/introducing-ai-mode-autoforward
• /blog/bot-sender-ghost-mode-v1034

My Addons: management and renewal

The announcement also introduced My Addons for easy management and renewal. This is a UX feature with real operational impact: teams can see what’s active, what’s expiring, and renew before workflows fail.

Addons as 30-day experiments

Many automation upgrades start as questions: “Will OCR reduce manual work?” “Do we need bot-based delivery for peak months?” Addons create a bounded experiment window where you can decide based on outcomes, not guesswork.

Gift addons & gift plans

Gifting is more important than it sounds. In communities, one admin often pays for tools used by multiple operators. Gift addons and gift plans enable:

• Team onboarding: an owner can provision a new operator quickly.
• Community rewards: moderators can be rewarded with time-based feature access.
• Frictionless trials: gift a feature to validate ROI before committing broadly.

Auto-renew: avoid interruptions

Auto-renew exists for one reason: forwarding pipelines can’t afford downtime. When a feature is critical (like high-throughput delivery or AI translation for regional posts), expiration becomes a risk.

Auto-renew reduces that risk by keeping addons active unless you intentionally disable them. Combined with transparent transaction tracking, auto-renew is a “set it and forget it” option for teams running the bot as infrastructure.

Modern gradient UI (optimized for mobile & web)

The announcement called out a modern gradient UI optimized for mobile and web. UI work is part of pricing clarity: users need to understand what they’re paying for, what is active, and what happens next.

Pricing UX is a product in itself: if renewal is confusing, workflows break. If activation is complex, users never try features that could help them. The goal of the UI refresh is to make the credits/addons model understandable in seconds.

Use cases: pay-per-feature in the real world

Seasonal volume spikes

Some channels run quiet most of the year, then surge during events. Addons let you scale features up for 30 days, then scale back without changing your entire plan strategy.

Migrations and large clones

When you do a one-time migration, you might need advanced cloning and high throughput for a limited window. Pairing credits with addons matches this reality.

Multilingual expansion

Translation workflows often start as an experiment: “will a Spanish channel grow our audience?” Addons let you activate AI-driven translation for a month and measure results.

Cost control for small teams

Small teams often need one or two “power features” but don’t want to pay for a full bundle. Credits + addons let you unlock exactly what matters (multi-target fan-out, AI Mode, or Bot Sender delivery) and keep everything else simple.

Agencies and multi-client workflows

If you manage multiple communities or clients, needs vary wildly: one client needs Discord → Telegram bridging, another needs AI translation, another needs high-throughput delivery for multi-target distribution. Addons let you tailor capability per workflow instead of forcing every client into the same bundle.

Cross-platform bridges

If you’re bridging from Discord, the “activate what you need” model applies there too. Start with /products/discord-to-telegram and read /blog/discord-to-telegram-launch for the launch overview.

For a broader view of how we build products and invest in sustainability, see /blog/our-open-source-journey-building-tools-for-the-developer-community.

FAQ

Do credits expire?

No — credits are designed to never expire, so you can purchase them and use them when you’re ready.

How long do addons last?

Addons have a 30-day duration and can be renewed. This keeps activation simple and predictable.

Can I gift addons or plans to someone else?

Yes — gifting supports both addons and plans, making it easier for teams and communities to share access.

What happens if an addon expires?

If an addon is required for a workflow, expiration can interrupt that feature. Auto-renew is designed to reduce this risk for critical setups.

Where should I start if I’m new?

Start with /products/telegram-forward and follow /blog/automating-telegram-message-forwarding-complete-setup-guide to set up your first pipeline. Then add features (multi-target, AI Mode, Bot Sender) as your needs grow.

Conclusion: pricing that matches real workflows

The credits and addons ecosystem is designed to make telegram bot pricing feel fair and flexible: pay for the capabilities you use, activate features when you need them, and keep workflows stable with renewals and auto-renew. If you’re building a forwarding pipeline as infrastructure, that flexibility matters as much as performance.

Explore the product at /products/telegram-forward, and use /blog/automating-telegram-message-forwarding-complete-setup-guide to set up a workflow that’s ready for multi-target delivery, AI rewriting, and high-speed bot sending.