Available and Away status
Mark yourself Away so incoming calls skip you, and how Phone Clover tells who is actually reachable right now.
For everyone · Updated Sep 23, 2026
All guides
Phone Clover needs to know who is actually at their desk before it rings anyone, so incoming calls reach reps who can pick up, not someone who has stepped away. Available and Away status is how that gets tracked.
Where to find it
The Available/Away toggle sits in the top bar, on both the floating widget and the full Phone page. It is visible to every rep, not just admins.
How it works
While your Phone Clover phone is connected, it sends a presence heartbeat every 30 seconds. An incoming call only rings reps who have been seen within the last 90 seconds and who are not marked Away. If you close the tab, lose your connection, or simply have not had the app open recently enough, you drop out of who gets rung, even without touching the Away toggle yourself.
Marking yourself Away removes you from ring-all and round-robin routing immediately, on top of that heartbeat check. It is the deliberate way to say “do not ring me,” rather than relying on closing the tab.
When to use it
Turn Away on before a break, a meeting, or anytime you know you cannot answer a call. Turn it back to Available when you are ready to take calls again. Your status persists on the server, so it survives a page refresh, you do not need to reset it every time you reopen Phone Clover.
Note: Being marked Available does not guarantee you will be rung if your connection has gone stale. The heartbeat check (seen within the last 90 seconds) works alongside the Away toggle, not instead of it.
Where your team can see status
An admin can see Available/Away/offline status for the whole team from the dashboard’s “Team” card, on the full Phone page. See Team presence. This is admin-only; reps see their own status in the top bar but not a live view of everyone else’s.
How this affects routing
Both ring-all and round-robin routing only ring reps who are currently ringable by this definition: Available, and seen within the last 90 seconds. See Ring-all routing and Round-robin call routing for how each mode uses that pool of ringable reps differently.
Common reasons a rep unexpectedly stops receiving calls
- The tab was closed or the computer went to sleep. The heartbeat stops, and after 90 seconds without one, calls stop reaching that rep even if their status still shows Available from an earlier session.
- Away was left on from a previous break. It is easy to forget to switch back. Check the top bar toggle if you expect to be getting calls and are not.
- A slow or dropped internet connection. The heartbeat needs a working connection to the server; a spotty connection can cause a rep to intermittently drop out of the ringable pool without any change to their toggle.
Why this matters for routing
Both routing modes only work with whichever reps are actually ringable at the moment a call comes in. If your whole team appears to be missing calls at once, check whether something at the app or network level is preventing heartbeats from reaching the server, rather than assuming every rep individually forgot to toggle Available.