Pypestream vs. Zoom Contact Center

Pypestream is suited for standard chatbot and conversational flows versus more multi-departmental scenarios. They do very well with guided flow bot services which are great for agent bots within a contact center, but less so for those implementations that have a large document management implementation for FAQs. They do well with service integrations; however, at times troubleshooting edge cases that are impacting performance and adoption can take a while to remedy. I want to believe that better monitoring tools on the platform side would alleviate this for them.

Incentivized

Perfect for companies that have agents all over the place, e.g., different offices or WFH. Also good for companies that aren't big enough to have a "phone guy" as this platform allows IT to do the phone work as it doesn't require esoteric knowledge like other phone systems.

• Native live agent platform
• Managed services for service creation and maintenance
• Custom analytics

Incentivized

• Customer service - Whether for sales, setup, or technical assistant, their team is always patient, informed, and helpful.
• Cutting Edge - Every month there are a plethora of new or enhanced features that are well thought, tested, and ready for implementing.
• Stability - Our uptime is important to our clients. As a 24/7 365 day/year contact center, having confidence that Zoom's systems are up and running means our clients have trust in our abilities to service their calls.

Incentivized

• Generative AI - Large Language Model Support
• Standardized Reporting
• Custom UI Support
• Developer Tools

Incentivized

• The Teams dashboard for monitoring agents needs some customization options.
• Friendly names, I would like to be able to name a number and when it rings you can see the name of the number.
• Point flows at flows would be nice, instead of flows to queues only.

Incentivized

First and foremost for our results, the omnichannel approach and ease of use on the internal side (agents, supervisors and administrators) have made adoption very simple, we have managed to reduce response times (SLA) and internal communication has become very fluid. We get good feedback from our clients for having implemented ZCC in the company to serve them.

Incentivized

In comparison to Microsoft Bot Framework or now Azure AI service structure, where Pypestream is better suited is in those organizations who want to truly have a partner in development. Pypestream allows the flexibility for your Dev teams to do it themselves, or to be in a managed service where you provide requirements and information and they build and allow you to test and give approvals. They are more willing to work directly with you versus a Microsoft where you will eventually get pushed off to a 3rd party partner to help with advanced implementations.

Incentivized

Microsoft Teams was very difficult. Many third-party providers didn't understand the integration and capabilities of the systems. The Teams app is very clunky, and you can get very different capabilities and compatibility when using it between Mac and PC environments. Zoom had a local team that could help with the transition directly, which is very valuable

Incentivized

• Enabled the contact center business lane to grow a chat agent support channel that has a 2 to 1 (customer to agent) support ratio
• Provides an alternate channel for training, marketing information, and data services which help grow our business and support different value streams

Incentivized

• Intuitive, Easier and almost effortless to maintain.
• Lesser Operational Expenses that the alternative we also have
• We wish it has a better integration with Zoom Phone, in terms of channels integration (Voice and Chat) to quick identify callers.
• It is missing "modular" programming to "reuse" Existing Flows and call them from other flows then return to the main flow.
• It is missing the capability to compartmentalizing different teams/groups related to reporting, admin, and global parameters.