Telegrapp Release: Multi-Account Support

🚀 Overview
Type: Major Feature Release — Architecture Update
Telegrapp now supports multiple Telegram accounts (bots and personal accounts) inside the same GoHighLevel subaccount. This is a major upgrade that enables teams to centralize conversations, scale operations, and manage multiple identities without creating extra subaccounts.

This update introduces a new data structure, a new way conversations sync, and a one-time migration required for all existing users. Follow these links for more info:

✨ What’s New?

✔ Multi-Account Support (Bots + Personal Accounts)

Connect multiple Telegram identities under one GHL subaccount — perfect for teams, brands with multiple stores, or agencies managing several profiles.

✔ New “Accounts” Layer in Telegrapp

Each connected Telegram bot or personal account is now treated as an independent account object with its own:

Message sync
Webhook handling
Contact routing
Conversation mapping
Preferences & settings

✔ Isolated Conversations per Telegram Account

Messages are now segmented by the specific Telegram account they originate from. No more mixing or overwriting conversations.

✔ New UI on Telegrapp Dashboard

Clear list of connected accounts
Per-account status indicators
Ability to enable/disable sync per account
Group, channels and chat filters

✔ Improved Reliability & Performance

Under the hood, Telegrapp now uses:

A new messaging pipeline
More consistent message handling and error handling
More resilient connection handling for simultaneous accounts

🔄 Migration Required for Existing Users

To enjoy this new features, existing users must complete a one-time migration because previous Telegrapp versions supported only one Telegram identity per subaccount.

What’s Changing

Your current setup will be converted into the new multi-account structure. This requires users to follow this migration guide.

https://telegrapp.gitbook.io/telegrapp-documentation/getting-started/migration-guidelines

The migration takes ~2 minutes and avoids message delivery issues.

What Happens If You Don’t Migrate?

Legacy connections are still recognized, but:

New messages may not sync properly
Conversations may not route correctly
Automations could fail
You will be shown a persistent warning banner

We recommend all users migrate immediately to ensure continuity.

🧑‍💻 Who Is This For?

✔ All Telegrapp users
✔ Agencies managing multiple Telegram bots
✔ Businesses with multiple storefronts or regional Telegram accounts
✔ Teams needing multiple personal accounts inside the same pipeline

💡 Why This Matters

This upgrade unlocks entirely new use cases:

Multi-agent support under one subaccount
One business → multiple Telegram identities
Testing and production bots in the same GHL instance
Seamless scaling without cluttering your CRM