Separate presence from a status message
A custom message explains your context. A presence indicator reports availability using the platform’s rules. In Slack, for example, changing status text does not replace availability controls.
Decide what you need first. “Reachable until 18:00” may be useful as a message even when an availability routine is also running.
One person can have several sessions
Your browser, desktop app and phone can each contribute to presence. Teams explicitly combines sessions and gives some states priority over others.
That is why checking only the tool’s start button is insufficient. A successful request and a green dot visible to a colleague are separate observations.
Run a simple before-and-after check
Choose one workspace and note your starting state. Start a short session, check through a separate permitted account, then stop. Observe both the transition into your requested state and what happens at the end.
Allow for platform update delays. If the result differs, record the account, other open clients, selected status and any meeting in progress. Change one variable before testing again.
Choose local or cloud deliberately
A local browser routine needs its computer to remain on. An authorized cloud integration runs separately, but only if that specific platform connection is available and working.
OnlineHours currently offers a free experimental local extension. Cloud connections for Teams and Google Chat are being prepared; they are not a substitute for live validation today.
Common questions
Does a recent activity pulse prove I am online?
No. It confirms an action by the tool. Check the platform’s resulting presence separately.
Will one technique work in every work app?
Do not assume so. Test each platform and workspace separately; presence rules and supported connection methods differ.