CommunityOne Analytics Overview: Engagement, Forecasting, and Chat Retention

Summary

CommunityOne Analytics focuses on what members actually do in chat—messages, people chatting, time spent, and retention. Learn how its Growth and channel insights help improve community health.

CommunityOne Analytics is built to help community managers understand community health using engagement and retention—based on real member activity in chat, not impression-based tracking. Its dashboard highlights what’s happening now, what’s likely to happen next, and which actions may improve retention.

In this overview, we’ll walk through the core concepts discussed in the video: what’s in the Growth tab, how engagement is measured, how activity is forecast by hour/day, how retention is benchmarked (with a strong emphasis on five-minute and 7-day retention), and how channel and support analytics add operational clarity.

What CommunityOne Analytics is and why the Growth tab matters

The Growth tab is described as the most popular view because it gives community managers an instant overview of what’s happening inside the community.

Rather than relying on impressions or reach, the dashboard emphasizes real engagement signals—tracking actual participation such as people chatting and time spent in chat. This makes it easier to interpret community performance in terms of member behavior.

Engagement metrics: messages, people chatting, and time in chat

CommunityOne Analytics includes engagement metrics designed to answer practical questions like:

  • Are messages being sent?
  • Are people actually chatting about the community?
  • How much time do members spend in chat?

These signals form the foundation of the dashboard’s engagement view. The approach is specifically framed around tracking what members do (engagement and retention metrics) rather than what is merely shown to them (impression-based tracking).

Forecasting peaks: activity by hour and day

Beyond current engagement, the dashboard supports operational forecasting by showing activity patterns by hour and by day.

This helps community managers identify when message activity peaks, so they can plan moderation and engagement efforts around the times when members are most active.

Retention benchmarks: weekly retention and 5-minute vs 7-day correlation

Retention is a major focus of CommunityOne Analytics.

The platform compares retention performance against benchmarks by category. The overview specifically references weekly retention around 25% as an average indicator, used as a comparative benchmark.

Why five-minute chat retention is emphasized

CommunityOne Analytics highlights a strong relationship between:

  • five-minute chat retention
  • 7-day chat retention

The transcript describes this as a “huge correlation.” The reasoning is that if a member begins chatting, the probability that they continue chatting in the next 5 minutes is strongly linked to whether they will return later—captured by 7-day chat retention.

This framing matters because it positions five-minute retention as an early, actionable indicator. Instead of only reacting to whether retention is high or low on longer windows, community managers can look at near-term engagement behavior to drive improvement.

Conversation quality: words per message and new-member vs old-member share

CommunityOne Analytics also goes beyond counts to help interpret conversation quality and community composition.

Words per message

The dashboard tracks words per message and presents it as the best indicator of the quality of a conversation. The goal is to understand whether conversations are producing meaningful discussion rather than only minimal activity.

New members vs old members

The analytics also measure what portion of conversations involve new members versus old members.

The overview notes that the number representing new-member conversation percentage correlates with five-minute retention. This is presented as a reason community managers and moderators should pay attention when new members arrive.

A practical suggestion mentioned is for moderators to notice new members and “say hi” when they appear in the community.

Channel usefulness and support analytics: words per message, message per member, and tickets

CommunityOne Analytics includes channel-level insights that help determine which parts of the community are working well and how to prioritize support.

Channel engagement basics

For each channel, the dashboard tracks:

  • total messages
  • how many people chat in that channel

Two usefulness indicators

To judge how useful a channel is, the dashboard uses two indicators:

  • words per message (used as an indicator of conversation quality)
  • message per member (how actively individuals participate within the channel)

The video references the type of differences you might expect across channels—for example, a change-log style channel having higher words per message, and a food-related channel showing stronger message-per-member behavior. (These are described as examples of how the metrics can look across different channel purposes.)

How channel metrics guide action

The channel analytics are presented as decision support for community management, including:

  • promoting or boosting channels
  • supporting channels with ambassadors
  • removing channels that are not serving the community well

Support activity: tickets responded to and response within 10 minutes

The platform also supports tracking community operations through support analytics.

Specifically, it can track:

  • tickets responded to
  • responses within 10 minutes

This ties community management to responsiveness and service quality in addition to chat-based engagement.

Conclusion

CommunityOne Analytics is focused on measuring real member engagement and translating it into retention insights. The Growth tab centers on messages, people chatting, and time in chat, while also providing forecasting by hour and day.

For retention, the platform highlights weekly benchmarks and, importantly, the correlation between five-minute chat retention and 7-day chat retention to support earlier, more actionable engagement improvements. Channel analytics add depth through words per message and message per member, and support analytics add operational context via ticket response metrics.

If you manage a community, these analytics help you understand what’s happening, when it’s happening, and which behaviors are most likely to drive members to return.