Knowledge is power, especially in the fast-paced world of technology where things are changing so quickly. At Bicom Systems we like to research and even test new products as they come out so that we know what we are up against.
One of our developers recently spent some time looking at the Amazon Contact Center solution and wrote a review for all of you:
Amazon Connect: A Review
The GUI is not anywhere near where it should be. The content is breaking out and overflowing. Components take up too much space that you do not needed. Everything is fixed, you cannot adjust the window size, etc.
Creating call flow logic is very easy with their graphical interface. You have components in which you add and connect with wires and then make logic. The starting position is the number which callers will dial and then enter into the system. I tried some custom, it was not too complex and it worked. But the question is how it will behave in a more complex situation. There are still some GUI problems. For example, when you move or edit a component, the connection is lost and you have to wire it again. After publishing it will show you errors and where you should fix it.
Prompts and Text-To-Speech
Prompts have the capability to use text-to-speech or recording. Text-to-speech is great for building small prompts, but of course it only works only with English.
Amazon went with customizable reports, so it allows you to choose fields from a list and then you can save and run it again. This sound nice, but as I tried making a few reports – BAM – I would run into errors or fields that showed no data. If you want to talk optimization, well we know there is none. Even with little data, it requires a couple of seconds to build every report. And if you add fields, it takes longer and longer. So handling large data may not be possible.
The most annoying thing that I ran into was that when I was expecting certain data, it would not show at all or would show lower values than expected. So data accuracy is a big issue.
Also, unlike in our statistics, you cannot filter by time, for example from 8:00 to 11:00. You cannot break the data down to see all the CDRs an agent had at that time.
So statistics gets a big thumbs down. Though it may have plenty of filters and features, everything comes down to speed and accuracy.
Amazon took the approach of making everything customizable. But even with that in mind, there are too many things missing. First of all, you cannot create any queue strategies. You could create flows, but you cannot achieve automatization. Also, there are many instances of queue configuration on our system which would require big flows or be impossible to make. Statistics covers a lot of fields, but accuracy and speed are big problems here.
They have this simple WRTC softphone that works for simple functions – dial, hangup, transfer – but real call centers agents often need to see with whom they are talking. For now, the agent is put in this “after call work” state for every call, so there are no options like wrap-up time, auto pause, etc.
In conclusion, this software does not yet provide a good solution for large call centers. And even for small call centers, there are lot of bugs and GUI problems that need to solved.
If you would like to learn about our own call center solution, please visit our website.
More posts like this one: