The role of community managers in modern customer support

Customer support is changing. Traditionally, when customers encountered a problem, they opened a support ticket and waited for a response from a customer support manager. But today, many of the most helpful support conversations happen somewhere else entirely: inside customer communities.

I saw this shift firsthand a few years ago while working in customer support at Lucidental, a finance house. More and more customers were turning to our Telegram community instead of submitting support tickets. They would post questions to see if anyone else had already faced the same issue or discovered a solution.

Customers began posting questions to see if someone else had already faced the same issue or discovered a solution. At first, I didn’t think much of it. But one moment completely changed how I saw the role of community in customer support.

A customer posted a question in our Telegram channel saying they were trying to log into their account dashboard but kept receiving an “incorrect login information” message.

Before my team even had time to respond, another customer stepped in and explained that they had experienced the same issue before. They shared what had confused them initially and explained the steps that eventually helped them resolve it.

Within minutes, the problem was solved.

What stood out was that the explanation came from someone who had recently faced the same problem. That made the answer clearer and easier to understand than a typical support response.

That moment made me realize something important: sometimes the most helpful support doesn’t come directly from the company; it comes from the community surrounding the product.

But those conversations don’t happen by accident. Behind the scenes, someone is helping guide discussions, highlight useful answers, and ensure the space remains welcoming and helpful. That person is the community manager.

What surprised me about customer communities

When I first began noticing more discussions happening in the community, I assumed the main benefit would simply be reducing support tickets. And to some extent, that was true.

However, what surprised me most was how communities improved the quality of customer support conversations.

In traditional support channels, the interaction is usually simple: a customer asks a question and a support agent provides an answer.

In community spaces, conversations often develop into discussions where multiple users share different perspectives, solutions and experience. I saw that our customers didn’t only ask how to fix a problem, but they also enquired how others are using the product. I found that customers would ask questions like:

• How are other customers using the account dashboard to track their investments?
• Has anyone found a better way to monitor transaction updates?
• What mistakes should I avoid when setting this up for the first time?

These types of discussions went beyond simple troubleshooting and became something organic: they were sharing experiences with one another. These conversations often produced explanations that were more practical and relatable because they came from people actively using the product.

When community made a real difference

One situation I remember clearly involved a recurring issue customers were facing with the account dashboard.

Our support team frequently received tickets from customers who had submitted liquidation requests, but could not see the update reflected in their account. Even after the issue was fixed internally, customers continued to ask questions about the process.

One day, a customer posted the same concern in Lucidental's Telegram community, asking why their liquidation request was not appearing on the dashboard.

What happened next was interesting. Several experienced customers joined the discussion and each contributed something different:

• One explained how to correctly submit the liquidation request.
• Another shared a quicker way to track the request status through the transaction history.
• Someone else pointed out a common mistake: submitting the request but forgetting to complete the final confirmation step.

By the end of the conversation, the thread had become far more helpful than a single support response. It provided multiple perspectives, tips and explanations that made the process much clearer for new users. And the best part? It was all organic.

From that point forward, whenever similar questions appeared, we could guide customers to that thread. It became apparent that a well-managed community can become one of the most valuable knowledge resources a company has.

How support and community teams worked together at Lucidental

At Lucidental, our customer support team and community manager worked closely together to help customers find answers more efficiently. One of the ways this collaboration worked was through recurring support tickets.

Whenever my team noticed the same issue appearing repeatedly in customer tickets, we would share those patterns with our community manager. This helped identify topics that customers were struggling with.

This collaboration helped surface common challenges much earlier, allowing the community manager to proactively start discussions around those topics. Our community manager would then raise those topics on the Telegram group, encouraging customers to share their experiences and solutions.

These discussions often led to helpful peer-to-peer explanations from customers who had already faced the same challenges.

Instead of each person waiting for an individual response from the support team, they could learn from a broader conversation.

How community marketing and customer success teams can work together

When you think about the goals of community marketing and customer success teams, it can be difficult to pick apart exactly how they differ. After all, they’re both trying to make the customer as happy as possible, right?

Customer Success CollectiveJade Warne

Using community discussions to support customers

Another helpful process involved linking community discussions to support responses.

When a conversation in the Telegram group provided a particularly clear explanation, the community manager would highlight or pin that discussion so other customers could easily find it.

Support agents could then refer customers to those threads when responding to tickets.

Instead of receiving a short answer from a support agent, customers could explore a full discussion where several users had shared their experiences and solutions.

Over time, these discussions gradually turned the community into a growing knowledge resource for Lucidental customers.

The role of our Telegram community

Our Telegram community also helped customers receive answers quickly. Because the group allowed real-time conversations, experienced members often responded within minutes when someone posted a question. Customers who had previously solved a particular issue frequently shared their experiences and suggestions.

Our community manager played an important role in guiding these discussions, ensuring responses remained helpful, accurate, and respectful. This allowed the support team to focus more on complex issues, while simpler questions were often resolved directly within the community.

The impact on customer support

Within five months, the collaboration between the support team and the community manager began to make a noticeable difference.

As more conversations happened in the Lucidental forum and Telegram community, customers were able to find answers to common questions much faster. In many cases, experienced community members responded before a support agent even needed to step in.

This also helped reduce the number of recurring support tickets, since customers could search existing discussions and find solutions that had already been explained.

For our support team, this meant we could focus more on complex customer issues, while simpler questions were often resolved through community discussions.

Final thoughts

Looking back, one of the biggest lessons my experience in customer support taught me is that great support doesn’t always come from the company alone. While working closely with our community manager, I saw firsthand how often customers helped one another by sharing solutions to challenges they had already faced.

There were many times when someone in the community would respond with a helpful tip or workaround, even before the support team stepped in. Watching those conversations unfold changed the way I think about support. It showed me that sometimes the most valuable support comes from shared experiences between customers.

Working alongside our community manager also helped me see how important their role is. They guide conversations, organize helpful information, and make sure valuable discussions don’t get lost. For the support team, these community insights often reveal recurring customer questions and real pain points we might not see right away.

In many ways, community managers become a bridge between customers and support teams. They help turn everyday conversations into knowledge that benefits everyone. And when that happens, customer support becomes more than just solving problems; it becomes a shared experience where customers learn from one another.