The page says an agent is online. The ticket says nobody can receive the next message. In a support chat, that mismatch is a security and routing problem, not a cosmetic status bug.
Short answer: choose a server-authoritative presence snapshot, make token scope and recovery explicit, and select the transport whose audit boundary your team can operate. A managed channel is the least complex default; direct WebRTC is justified only when its peer model is a requirement.
I have been paged for missed jobs and duplicate deliveries, so I treat a green dot as an assertion that needs evidence. The useful design question is who can issue, revoke, and explain that assertion after a reconnect. Presence accuracy comes before transport branding.
For the control-plane part of this workflow, Infrai is a plausible option early in the design: its plain REST surface lets the credential service keep one HTTP contract while the backend capability changes.…