December is an important time of year for many - all around the world, people celebrate our Birthday as a company with pine trees, carol singing and gifts.
When deploying a new PBX there's so much you need to test. So, how do you test what happens if you call emergency services?
Why does a wallboard have to go on the wall?
Early on, we realised clever code alone wasn't enough to create a great wallboard design, to do that, we needed a process.
We are now in week two of the road to launch so it’s time to go under the hood of Discover and talk about ‘The Back End’.
With your new set of wallboards, we don’t expect you to have to open your cheque book every time you want to change a 0 to a 1. That’s why we built an administration interface, so when you want to change something, you can.
As we approach the February 6th launch date we're looking, in detail, at the components that make up Discover.
Today, it's the front end and more specifically, what we can do with it.
On the run up to launch, we have 4-weeks of content planned, exploring specific parts of Discover in detail - there's some cool stuff coming so don't miss out.
Over the last 11.57 months we've laughed, we've high fived and I hit my knee off a table one time - it's been a rollercoaster.
This September, I could’ve spent a lot of my time speaking to robots or waiting in call queues but, thanks to my friends at Deezer, that wasn’t the case.
A number of weeks ago, Injixo approached us to gauge interest in authoring a blog for them on the subject of forecasting - I'm a bit of a fan of Injixo blogs and it's a great platform for us to expand the scope of our usual AVAYA focussed content so the answer was, of course, yes.
For the past few months, we’ve been working hard to develop and launch our very first product – Discover. Designed to work with AVAYA CMS, Discover extracts and processes real-time and historical data to enable us to create fully bespoke, web-based wallboards, ignoring inherent limitations of CMS.