To submit answers for each question, you must click "Vote" on each question.
Cybersecurity
DevOps Cloud
IT Operations Cloud
To submit answers for each question, you must click "Vote" on each question.
Need multi select for the second question
I tried. The platform options for polls here are very limited. I meant to include a "All of the above" option, but I must have deleted it. Anyone who would like to select more than one can leave a comment and I will review them.
We still love the product. But it needs some enhancements:
- much better mobile support for Android and iOS (just install the app from the playstore/appstore, enter the server name and credentials and then it must workt without additional settings, Push notification is a must !!
- Certificate handling
- easy Client deployment (with ZENworks, etc)
Once this is done, please have a look into
- using messenger client for multiple servers (different sites/clients)
I think you're doing a big disservice by only asking people why they don't use it. Why not ask people that do use it, what they like about it.. The simplicity? The easy quick communication between people? Ability to access on mobile phones? Archive capabilities? How light it is? Etc.. You're only focusing on the negative. It's a great product used by many organizations and you're only focusing on why people might not be using it.
The purpose of this is to get an idea as to where I could focus the product. The list above is targeting some of the top ideas that customers have suggested.
Video and voice calling missing.
Maybe if you added an option for "YES I use it. But here are some features that need improvement".. Then you'd cover the entire base. No matter what I think it is very important to connect with the actual base of customers that is using a product, not just lobbing a ball out there to find out why some people aren't using it.
The first question does exactly that. The second question is meant to ask, "if you answered no above, what might that reason be?" The list of responses could be better, but these were the top issues that I have knowledge about, so I wanted to see if one in particular was most problematic, and where I could potentially focus development resources. Polls are one of many ways to contact the customer base. Quick, short, to the point question or two is best for maximum interaction before people lose interest. Additionally, here I have the benefit of it being a discussion, giving passionate votes a place to talk about these questions, and potential issues that may not be covered in them. If you would like to discuss this topic 1-on-1, I am also happy to do so.
We use Messenger in our small company and we like to use it. When OT Teaming came along, we thought this product would replace Messenger. What was always an issue with Messenger from a security point of view was that it was never really possible to connect a WAF upstream. A messenger on 443 is a great thing.
At this point, I would like to put another thought into the round. At some point I got tired of working with Wordperfect Mail and turned to Lotos Notes. The Lotus people were way ahead of what collaboration was in the mid 90s and early 2000s. The fat Notes client was a recurring theme. Somehow they kept promising a web client. Notes had a huge advantage, in the Notes client there were tiles behind which business applications and database applications were available, everything was somehow in the client, including online messaging, shared calendars and much more.
If I go back to OT there is actually a product that has a very deep collaboration approach - Vibe - With my post I suggest to modernize Vibe and expand it to a web client collaboration platform. I.e. basically a single interface for GroupWise, Teaming, Messenger, Filr and Content Editor. Call it collaboration dashborad. At OT there are other products that can be integrated into such a web interface in everyday business. The whole thing is then really independent of any operating system platforms. George
“You can't teach a person anything, you can only help them to discover it within themselves.” Galileo Galilei
for me as an Opentext partner working with different customers and other partners and with people in my own company i need a messenger which is secure and would work with different accounts at the sane time.
Another option would be the ability of installing GWMessener app multible times for different accounts.
Most of us Opentext GroupWise partners would life to use GWMessenger for communicate with each other.
But thats simply not possible to do that beetween different GroupWise systems.
We need an multi tenant GWMessenger where each tenant can be managed by the owning company by itself.
Or allow multiple installation of GWMessenger where the company branded app is really a different app