AlphaCloud v1.8.1: Who on Your Team Is Actually Active

v1.8.1 is an update for everyone who runs a team. Two of the three big additions came straight from suggestions on our ideas board, and both answer the same question: who on my team is actually active?

Voice Support Activity

Many servers handle support in voice. Until now there were no numbers for that, only a feeling. The new module counts who helped how much.

A conversation is a team member and a member without the team role together in one of your support channels. Every valid conversation gives one point, plus one point per ten active minutes. The points of the last 7 days turn into a status: Inactive, Normal, Active or Most active.

With /voiceactivity stats every team member sees their own points, and team leads see the whole team with /voiceactivity list. Everyone with the team role is on that list, also with zero points. Those are exactly the people a team lead wants to see.

Counting without rewarding what is not help

A points list is worthless if it can be inflated with little effort. So the rules are strict:

• Only active time counts. While the team member is muted or deafened, no time passes. The same applies when the member is deafened
• Short hellos do not count. A conversation needs at least two active minutes, and at least half of it has to be active
• No farming through repetition. The same pair counts at most once every 30 minutes, and there is a daily cap
• Only real members. Bots and team members talking to each other never count, and neither does the AFK channel

What the bot does not do: listen. It does not know whether someone actually speaks, it only sees whether someone is muted or deafened. Conversation content is never recorded, and stored conversations are deleted after 90 days.

With Premium, rank one gets a role of your choice automatically every Monday, and inactive members can get another one. A weekly report with the change against the previous week lands in a channel, and a chart in the panel shows the last eight weeks per person.

All settings are in the Voice Support Activity documentation.

The daily check-in

The second suggestion was simpler: a message with a button that every team member presses every day. Whoever misses it too many days in a row loses their team roles automatically.

This is now part of the Activity Check. You pick the channel, the time, how many missed days in a row are allowed and what happens then: remove the team roles or give a warning. One day before, a reminder arrives by DM.

An automatic consequence has to be fair, otherwise it hits the wrong people. Four rules make sure of that:

• A day only counts if the message was actually posted that day. If the bot was briefly offline, the day counts for nobody
• New team members start at zero
• Absent members are not counted, and the count starts over when they return
• After a warning the count starts over, so one missed stretch is punished only once

You design the message like any other in the Message Builder. With Premium you pick the weekdays yourself, for example only Monday to Friday, and see the check-in rate per person. Details are in the Activity Check.

A role for former team members

Small, but asked for often: in Team Updates you can now set a role that /teamkick gives automatically after the team roles are removed. Bring someone back with /teamjoin and the bot takes it away again. More in Team Updates.

Also new

• Welcome gift: every server gets three days of Premium once, the first time AlphaCloud is added
• Prepaid Premium: our team can send you a personal payment link for one server and a fixed number of months. One payment, no subscription, nothing to cancel
• Integrations: Game Integrations became Integrations, with a full VPC (ucp.li) integration
• Promotion application: if you want to advertise with us, you now fill in a guided form right inside your ticket
• Tickets: roles that may delete tickets, and a configurable retention for closed tickets from 1 to 365 days
• Absences can give a role while someone is away

The bugs you only notice once something is missing

The most important fix in this version was invisible. On single shards, welcome messages stopped arriving until the bot restarted. The cause was a request to our own API that never got an answer during a restart and held up the entire handling of new members. Every outgoing request now has a time limit.

Also fixed: tickets that disappeared seconds after being created, a verify button that sometimes did nothing, and redemption codes that were used up on servers with Lifetime Premium without doing anything.

The full list is in the changelog on our Discord server.