Status and Presence Indicator
Also known as: availability indicator, presence status, online status, do not disturb mode
Status and presence indicators are visual signals in communication platforms (Slack, Microsoft Teams, Google Chat, Zoom) that communicate a user's current availability to colleagues.
Standard statuses include Available (online and ready to respond), Busy (online but in a meeting or focused), Away (idle or offline), and Do Not Disturb (active but suppressing notifications). Custom status messages allow more nuanced communication ('Working from home', 'In a client meeting until 3pm', 'On vacation until July 15'). Presence indicators reduce unnecessary interruptions and help distributed teams coordinate without constant check-ins.
Status and Presence Indicator, explained at three levels
At home
A presence indicator is the small coloured dot next to someone's name in Slack or Teams. Green means they're active (online and probably available). Yellow means they're away (idle or stepped away). Red means do not disturb (don't interrupt). These indicators let you know, at a glance, whether it's a good time to message someone -- saving you from messaging someone mid-deep-focus session or interrupting a meeting.
At work
In remote and hybrid work, you can't see your colleagues across a desk to know if they're busy. Status indicators replace that visual awareness digitally. A custom status like 'Focus until 2pm' or 'Client meeting until 3pm' tells colleagues not to expect an immediate response, setting expectations without requiring a direct message. Good status hygiene -- keeping your status current -- is a basic courtesy that reduces interruptions for yourself and helps colleagues know when to reach out.
At home
Integration between calendar and presence is a significant quality-of-life feature: Microsoft Teams automatically sets your status to 'In a meeting' when a calendar event is active, and 'Out of office' when OOO is set. Slack allows calendar connections that update status based on active meeting events. This reduces the cognitive load of manually managing status and ensures presence information is accurate without requiring deliberate updates from users throughout the day.
At work
Notification management and Do Not Disturb (DND) integration with presence indicators creates a layered attention management system: DND status signals unavailability to colleagues and simultaneously suppresses notifications on the user's device. Well-configured notification schedules (Slack's Schedule Do Not Disturb function) automatically activate DND outside working hours and on weekends, protecting personal time without requiring manual management. Platforms allow bypass for urgent messages (allowed to notify even in DND, typically restricted to specific senders).
At home
The cultural norms around presence indicators vary significantly between organizations. Some organizations treat anything other than 'active' status as a flag requiring explanation; others accept that presence status is informational rather than managerial. Remote work has surfaced 'presence anxiety' -- the pressure to appear online at all times as a proxy for productivity -- which is a management and culture problem, not a technology problem. Organizations with healthy remote work cultures use presence for coordination, not surveillance.
At work
Enterprise presence architecture in Microsoft 365 integrates presence across multiple surfaces: Teams shows presence from Teams activity; Outlook shows presence status in email when hovering over a contact; SharePoint shows presence next to document co-authors; and Viva Insights correlates presence patterns with work-life balance metrics (tracking after-hours activity and quiet days). Privacy controls allow users to control who can see their full presence versus a simplified version -- relevant for executives who want to appear available to some colleagues without broadcasting real-time availability broadly.
Real-world examples
At home
Aisha worked remotely and was in a deep focus period finishing a report. She set her Slack status to the yellow focus emoji with 'Deep work -- back at 2pm' and enabled Do Not Disturb. Her colleagues saw the status, held their questions, and she completed the report without interruption. When DND ended at 2pm, she had five Slack messages waiting -- all of which she answered in 20 minutes that afternoon.
At work
Thomas managed a distributed team across three time zones. He established team status norms: a 'Focus' status (emoji + time) for deep work blocks when immediate responses weren't expected; 'Available' for responsive periods; and a shared protocol that messages tagged @urgent could interrupt a focus block for genuinely time-sensitive matters. The norms reduced always-on expectations and the team reported more completed deep work tasks per week.
Common confusions
- Many people assume an 'Active' presence status means someone is available to respond immediately — Active status (green dot) in most platforms means the user has interacted with the platform within the last few minutes -- it doesn't mean they're ready to receive and immediately respond to messages. Someone with 'Active' status may be in a different conversation, reading a document shared in the app, or checking notifications. Active status signals they're online, not that they're waiting for you. Setting explicit custom status messages like 'Focused, checking Slack at 10 and 3' communicates actual availability more clearly than the automated active indicator.
- Some managers use presence indicators as a productivity tracking tool in remote work — Presence indicators reflect platform activity, not work quality or output. An employee who closes Slack while doing focused work appears offline; one who keeps Slack open while distracted appears active. Using presence as a proxy for productivity creates perverse incentives (leaving Slack open at all times, even when unproductive) and measures the wrong thing. Output quality, task completion, and results are the appropriate measures of remote work performance, not presence status.
For analysts
When advising remote teams on communication norms, status indicators and notification management are among the first operational agreements to establish. Teams that don't discuss expectations around presence status and response times default to anxiety-driven always-on availability that degrades both wellbeing and productivity. A simple team agreement ('focus blocks mean 4-hour response time; @urgent bypasses focus; evenings and weekends are offline by default') eliminates most presence-related miscommunication without requiring any new tools.
History & origin
Presence indicators originated in consumer instant messaging services (AIM's buddy list with online/offline status, ICQ in the late 1990s). The concept transferred to enterprise instant messaging tools: Microsoft Office Communicator (2003, later Lync, then Skype for Business) and Cisco Jabber introduced presence for business communication. Slack (launched 2013) popularized the always-visible status indicator in modern team messaging, making availability transparency a default feature. Microsoft Teams integrated presence with calendar (automatically setting 'In a meeting' status based on calendar events). Slack's expanded custom status feature (supporting emoji + text) created a new informal communication layer where team members signal context ('Heads down until 2pm', 'Focusing') without sending direct messages. The rise of remote and hybrid work increased the importance of presence indicators as a substitute for the visual awareness of in-office co-location.