Verified Purchaser badge

Verified purchaser

Member since: Jan 2013Deals bought: 544
3 stars
3 stars
Posted: Nov 14, 2020

It's a Great Start

I bought one code of MeetQuo so far, because I am constantly in meetings that didn't need to be meetings (or were very difficult to set up), but did need to be discussions. And most of those discussions need to be succinct, focused discussion, and not just team chat threads. So the need for asynchronous meetings is real.

ADMINISTRATOR CONTROLS AND DYNAMIC TEAMS ARE NEEDED
First, I wholeheartedly agree with both @willinchicago's suggestions. Better administrator control to know what is happening in the system is important. I did go into Zapier and triggered an alert for when a new meeting is setup, and that will solve part of the issue. His second suggestion that more fluid setups of teams would be much better than static team structures is spot on. All our teams are dynamic, formed according to projects, and scattered around the world. Having to set up and re-setup static teams is just not a good reflection of the way people work today.

NOTIFICATIONS ARE NEEDED
Second, there need to be some notification options. I don't want to be required to "check in" with any particular software constantly, nor do I want to keep them all open on my desktop. In Zapier, there isn't an option to trigger a new email alert when a meeting is updated or responded to, and unless I just haven't dug around enough, I don't see other settings for notifications in the system. So please add to your roadmap either notifications for

I do love the clean simplicity of this system, and I can see its potential. But it needs a little more development to be a functioning part of a productivity stack. More Zapier hooks, more flexible team setup and management would be great, and the ability to add clients to a meeting but not give them significant system permissions would be necessary before I could offer up 5 tacos.

For now, I'm keeping my one code and watching the discussion here. If some of these issues can be addressed, I would probably buy more code. Otherwise, without those changes, I think this application will become somewhat of a paper weight.

Helpful?
Share
Ratings