Webex Contact Center vs. eZ Platform

- Well suited in managing a large staff base in a call centre environment. The real time data is incredibly insightful and useful - Gathering statistics for both customers and staff habits has large benefits towards creating an efficient workplace for all involved - Allows us to help staff grow in areas they might lack in with the was we can see and understand their habits

For a new site: 1. Are there any hosting requirements? eZ Publish works best on a traditional LAMP stack. 2. What is the expertise of the development and systems administrations individuals? There should be some PHP development experience and a solid level of Apache and MySQL hosting. 3. Who will be managing the content of the site? What is their bandwidth for training? For ongoing content changes?

Incentivized

• Things that it does particularly well include a really good UX or UI so that our agents as well as our administrators, can easily provide remote access from agents, new agents, and old agents, manage interactions with customers, and have a good call experience from start to finish.

Incentivized

• Content Taxonomy: Content is managed in a tree. Though taxonomy vs folksonomy is a near-religious debate among professionals, clients seeing the system for the first time just seem to "get it" more often.
• Content Flexibility: Common content types such as blog posts and articles are available out of the box. However, customizing these and creating new content types is very easy.
• Developer Friendly: Developers need only a little PHP experience to get started. Of course being an expert doesn't hurt and opens the door for the development of custom modules.

Incentivized

• Better integration with Webex Calling.
• More on premise features integrated into the cloud solution.
• Better documentation for pebble templates.
• Better information for changes and when new features are available. Instead of having to look on the what’s coming webpage alerts or a pop-up inside Webex control hub would be nice.

Incentivized

• The template language: Outputting content or doing something special with it requires use of the templating language. Myself along with other developers I have trained, found this to be one of the biggest hurdles.
• Layout of physical files: The system decides what settings files and templates to use based on a hierarchy of modules. The same file can exist in multiple modules and you can find yourself deep within very similar looking folder structures, causing confusion during debugging.
• Community: eZ has a solid set of community contributors but the gap between it and Drupal or Wordpress is pretty large.

Incentivized

They all have the niche, but I feel Webex is the most well rounded complete suite. It provides exactly what a business would need, from an onboarding, training, security, updates, road mapping all the way to great user experience and beyond.

Incentivized

eZ Publish isn't as large in community size and number of installations as other content management systems. However, it's just as capable and met our needs:

• Developers, system administrators, and project manager can all speak the same language during the development and maintenance cycles of a site.
• End-user training is very straight-forward.
• Vendor support is available.
• Client IT departments can access if need (developers/designers/sysadmins).
• The community is there (forums) and there are solid contributions (extensions) from both the vendor and the community.

Incentivized

• Increasing the number of channels agent can reach out to customers, especially text has shaved off a lot of hours from calling , leaving voicemail and waiting for customers to call back.
• Less Downtime. No Upgrades or certificate Renewal, so fewer overtime hours.
• Adoption of new features is now so quick, I don't have to worry about upgrading the Software or even hardware to get new features deployed.

Incentivized

• Common knowledge: By making eZ a core offering, developers, system administrators, and project managers were able to communicate with each other effectively.
• Training: Due to its content taxonomy, end-user training often went well.
• Support: In our case, we had Gold support from eZ Publish which saved time and helped with customizations.

Incentivized