chat
The chat function should not be dependent on the remote user activating it.
Walter Velez
shared this idea
Nice! The feature you requested is being considered for development. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!
-
Stuart Hill
commented
I've worked with someone in higher-tier support to create scripts to activate this, currently w.i.p. though so not ready for public release.
-
Chris Rawlings
commented
I have international techs that would benefit from this immensely since the current Chat Feature is basically useless
-
Ben Solomon
commented
This has been huge pain point for us, phasing out of our Splashtop Enterprise. The Atera agent chat is just clunky in my experience, it seems sometimes the requests do not pop up on the remote side? It would be REALLY nice to have the same chat functionality you get once ALREADY in a Splashtop session, or definitely at least to model the Atera chat around it (simple pop-up/takes focus, no need for any users to be tied to it or accept any prompts, just good ol' chat -- even if it means losing out on other chat features). Perhaps a separate 'QuickChat' option vs full the featured chat?
Simple effective chatting BEFORE remoting in is a massive and critical part of our workflow. This is a nightmare on kiosk and shared workstations.. we do not always know the user on the PC and they may not even have email :(
-
Michael Fahey
commented
I would like agent and chat funcitonality to be tied to a policy for all workstations PLS! Also, tie logged in user to their account in Atera. TY