Absent Status
An idle agent can be marked as absent after a configurable period and returns to online when they start interacting again.
See who is online, absent, on break, or blocked and take action without leaving the monitoring screen. Configurable rules help prevent distribution and transfer when an agent should not receive new contacts.
Agent management differentiates inactivity, break, and blocking so that supervision sees the team's real state. Monitoring is no longer just observation and now offers controlled actions.
An idle agent can be marked as absent after a configurable period and returns to online when they start interacting again.
Monitoring highlights the agent's state and shows the number of absent agents to support the supervisor's reading.
The supervisor can block or unblock an agent directly on the screen, respecting the operation hierarchy.
Rules can consider break or absence overruns, with time limits, occurrences, and profiles reached.
Blocked agents stop receiving chats and calls and do not appear as a valid transfer destination.
Absence and blocking reports record period, team, user, reason, and responsible party according to the available view.
Absence is a management signal; blocking is an operational action. The company decides when to just observe and when to prevent new contacts.
Set the time without interaction used to identify an available agent as absent.
Observe presence, breaks, absence, and blocking directly in monitoring.
Choose whether breaks or absences can trigger blocking and which limits apply.
Prevent new chats, calls, and transfers while blocking is active.
Analyze patterns by period, team, and user to guide process, scaling, and follow-up.
Supervision works best when presence, absence, pause, and blocking represent different and actionable states.
The supervisor distinguishes active connection from prolonged idleness and a registered pause.
Blocking and unblocking happen within monitoring, with a persistent effect.
Chats and calls are no longer sent to those who should not receive new interactions.
Reports help separate isolated episodes from recurring behaviors by team or user.
When they remain for the configured time without interacting with the screen and are not on pause, in an interaction, or on a call. When they interact again, they automatically return to online.
The status can work only as information. To prevent distribution due to absence, the operation needs to configure the corresponding blocking rule.
Yes. Blocking can be applied through monitoring and persists even after page refresh or new login, until it is removed.
They stop receiving new chats and calls, cannot be a transfer destination, and see the blocking indication on the platform.
The operation can configure rules for pause timeout and absence, defining time, number of occurrences, and affected profiles.
Show how presence, pauses, and distribution work today to evaluate the states, rules, and reports suitable for your operation.
Tell us the basics about your scenario.