Running community support on Telegram doesn't scale. How are you all handling it?

We use Telegram as our main community hub, it's where users drop technical questions, feedback, and expect fast answers. Worked great when we were small. Now that we've grown it's turning into a mess.

The core problems:

Questions get swept away. Someone asks a real technical question and it's buried under general chatter within minutes. No way to know if it ever got answered.

Messages aren't threaded. Telegram groups are just one long stream, so related messages get scattered and it's impossible to follow a single issue from start to finish.

The team is jumping between tools. Support questions live in Telegram, but our internal discussions happen in Slack, and anything that needs engineering ends up in Jira. Constant context switching.

Zero accountability. No ownership, no status, no way to track what's pending. Stuff just falls through.

For those running bigger Telegram communities, how do you bring any structure to this? Are you using bots, some kind of ticketing layer, pushing issues into your internal tools?

Specifically curious if anyone's found a clean way to handle support in Telegram without making users leave Telegram, since that's the whole reason they're there.

Feels like Telegram is great for community but terrible as a support queue once you scale. Would love to hear what actually works.