Not so much worried about the connectivity or hardware to operate the system on, we have that pretty well covered. I am more concerned about support and end-user adoption of feature functionality. The customer is very interested in the collaboration aspects of the platform. In the smaller deployments, ad-hoc conference calls and voice mail to email are the dominate "Unified Messaging" features. The desktop sharing, presentation sharing with or without video are the main collaboration points that keep coming up as the driving points behind implementing a new platform. They are currently on an old Avaya legacy system, so there is a huge potential bump the collaboration side of the house.
Having deployed and supported Skype for Business, in large enterprise networks I know what this entails before and after the sale. Comparatively my experiences deploying and supporting 3CX in less than (200) seats has been pretty straight forward and significantly less stressful than S4B on all fronts. Ultimately I am trying to gauge or get a feel for the scaling of features and support to larger enterprises; has your support or client interaction for the 2,000 endpoint client increase exponentially or have you found it to be more linear?
I know this is a broad open ended question and depends on many factors which is why I am looking for things we may have missed or not taken into account. To scale S4B and support it across many sites is resource intensive. Regular updates to the desktop, quarterly updates to server, SQL updates and maintenance keeps people pretty busy.
