Business Problem:
  • As a business relying on agent availability for conversation routing, I want agents to remain Online when they are actually working and have respond.io open, even if they are not actively clicking in the platform
  • Currently, agents may be marked Offline when respond.io is open but inactive, minimised, or running in the background. This can cause routing to skip available agents, leading to delayed or missed assignments
  • This is especially painful for teams that keep respond.io open while working across multiple tabs, tools, or windows-
Desired Outcome:
Improve Online/Offline status detection so users generally remain Online as long as respond.io is open and connected
Users should only be marked Offline when the connection is lost and the configured inactivity timeout passes, such as when:
  • The respond.io tab or browser is closed
  • The device goes to sleep or shuts down
  • The internet connection is lost
Use Cases:
  • Agents stay available for routing while respond.io is open in another tab or background window
  • Teams avoid missed assignments caused by agents being incorrectly marked Offline
  • Managers get a more accurate view of who is actually available to handle conversations
Current Workaround:
  • Increase the workspace inactivity timeout where possible
  • Ask agents to keep respond.io active or periodically interact with the platform
  • Manually monitor agent availability during busy periods