Community Lifecycle
Once a community (a Telegram group or Discord server) is connected to your project, it passes through a small set of states depending on what's happening with the Fren One agent and your team's verified admin coverage. This page explains each state in plain terms and describes the automatic timers that keep things safe.
Community states at a glance
| State | What it means |
|---|---|
| 🟢 Active | Everything is working normally. The agent is reachable and your project has at least one team member with verified admin access to this community. |
| 🔴 Needs attention | The agent has been unreachable for a while, or it was removed from the group. Your settings are preserved and no timer has started — this state resolves as soon as the agent can confirm it's back. |
| 🔴 Recovery window | No one — anywhere on the platform — is currently verified as an admin of this community. A 14-day countdown has started. If an admin re-verifies within that window, the community returns to Active. If not, the community enters a grace period before permanent deletion. |
| 🔴 Detached | The community is no longer connected to any project. It can be claimed by a verified admin at any time. Your agent continues running with its existing configuration. |
| ⬛ Deleted | Permanently removed from the platform. This can happen if a recovery window expires without an admin re-verifying, or if the project Owner permanently deletes it. |
State diagram
The diagram below shows every valid transition and what triggers it.
The "Needs attention" state does not start any countdown. It only tracks that the agent couldn't be reached. Timers only start when there are zero verified admins for a community.
The two timers
There are two independent countdowns that can affect a community. They start for different reasons and end in different places.
Timer 1 — Recovery window (14 days)
Triggers when there are zero verified admins for this community anywhere on the platform — not just on your project. This is the safety net for completely abandoned communities.
- An email and inbox alert go to the project owner immediately.
- Any admin can stop the clock by re-verifying their access.
- If nobody acts within 14 days, the community enters a grace period with an additional 14 days to be claimed before permanent deletion.
Timer 2 — Coverage countdown (30 days)
Triggers when your project has no team member with verified admin access to the community — but verified admins exist elsewhere on the platform. This is the path for situations like a fired agency retaining a community.
- Day 0: A warning alert appears in your Inbox and the project owner gets an email. Any existing project member can re-verify to stop the clock.
- Day 23: A final warning is sent.
- Day 30: The community is automatically detached from your project. Every verified admin of that community (wherever they are on the platform) is notified that it's available to claim.
The coverage countdown is paused during agent outages. The clock only advances when the platform can definitively confirm who does (or doesn't) have admin access. An unreachable agent will never trigger an auto-detach.
What stays when a community changes state
| What | Needs Attention | Detached | Recovery window / Deleted |
|---|---|---|---|
| Agent configuration | Preserved | Preserved (agent keeps running) | Preserved until deletion |
| Member activity & analytics history | Accessible | Hidden from old project; visible to a new claiming project | Lost on deletion |
| Your project's reports & audit log | Unaffected | Stays with your project | Stays with your project |
| Premium features | Unaffected | Drops to free immediately | n/a |
See Detaching Communities for the full breakdown of what happens to data when a community leaves a project.
Next steps
- Detaching Communities — who can detach a community and what happens to the data
- Ownership & Teams — transferring ownership, leaving a project
- FAQ — edge cases like "the agent was removed — does the 30-day countdown start?"