What do you dislike about Commio?
UPDATE: Less than 24 hours after I made this review, Commio has been rapidly (and secretly) updating their entire KB in response to it. This reminds me exactly why I use them as opposed to someone else, thus I have adjusted my stars from 8 to 10. There isn't a perfect company out there, but there may be companies that work harder than others to do their best for you. Our company is a small fish but today Commio definitely made us feel like a big one.
_____________________
Original Review:
_____________________
1) It would have been nice to have a composer-compatible PHP API to make their API a bit faster to code for. This would also allow them to push out code and query updates for their APIs in a more strategic manner.
2) For whatever reason, they seem to have issues with their billing system all of the time which can sometimes force us to spend more time looking at our balances than is normally required with other companies and can be somewhat annoying.
3) MMS messages are limited to a single attachment per inbound message (or at least they were when we coded our endpoint for them), meaning that it's possible to lose data on inbound MMS. It hasn't generally been an issue except on those rare occasions where people attach multiple photos and send them off in a single MMS. Most modern phones these days are pretty good at separating multiple images into separate MMS messages.
4) Dual-factor authentication for account access seems like a no-brainer but they haven't added it yet which seems disappointing from a basic security standpoint.
5) Having a more MSP-focused feature-set would be nice, however not if it comes at the expense of a lost focus on fundamentals nor an increase in price.
6) Speaking now directly to thinQ (since I know they read these), It seems like the documentation for simple things often is outdated and the branding sometimes gets a bit sketchy as you used to be Siproutes, then thinQ and now Commio. Pick a branding lane please and the next time you have a board meeting where you are discussing if you should change the name and/or branding... don't, just don't. None of your customers cares about it as much as you care until we realize that we have to change settings in our switches and systems to keep up with your musical chairs of domain and branding updates.
6a) Not that it really matters to me much but while we are on the subject, thinQ was already a pretentious and contrived name and is easily confused with an LG product. Someone sold you on switching your name from Siproutes, which was a name that your potential customers in the tech community can immediately recognize as far as what products you offer, to a name that's pretentious and vague. However, you pushed that name for so long that we finally started associating our brains with it and now you've started brand-shifting to Commio which is, dare I say it, yet another vague name that you'll need to once again build recognition behind. Far be it from me to tell you what to do with your own company, but honestly, I see it all the time in the VoIP space and it's almost always self-sabotaging. Facebook and Google are dumb names but at least they didn't change them and thus continually undermine their existing brand recognition. Whenever they got the urge, they just created a parent company with a different dumb name chosen by an overpaid research group and then kept the major brand name so people wouldn't have to switch mental gears. As a customer, when I see a company that is focused on brand-switching, especially more than once in a decade, I start getting concerned as I view this as a possible red flag. The company may be unfocused on the things that originally attracted me to them, they may be trying to re-build their image without solving the underlying issues that caused their original image problems, or they may be going through leadership turnover which may mean a destabilization of their service, support, or focus. To summarize, it's a bad idea to change the name and undermine the brand recognition, it's annoying to the customer to have to re-program things and the customer may begin to view re-branding as an indicator of potential weakness or red flags within your company.
6b) On the subject of documentation, why is it so hard to get clear information on how to setup a modern version of FreePBX with your services? A lot of your documentation is either out of date, filled with low-resolution images that you can't zoom in on, or measly and incomplete. It's great that you have so much confidence in my abilities to intuit your systems but the average person coming in from the cold is going to need to open up a support ticket to get information that should be easily accessible in your KB and is already easily accessible on your competitors' KB systems.
6c) Speaking of the KB, why are there two (or is it three?) logins, one for the KB, another for the support panel, and another to manage my services? Combine these all together along with the API documentation please.
7) Changelog please. I would like to know what updates are coming to the platform and I'd like to see any bug fixes and/or improvements in an easy-to-read list. You'll often make a feature update/change and I don't even know about it until I log back into my dashboard and I notice it. Review collected by and hosted on G2.com.
