Microsoft Dynamics 365 Customer Service is designed to create positive experiences through any channel and on any device to exceed customer expectations.
$50
per month per user
Pypestream
Score7 out of 10
N/A
Founded in 2015, Pypestream created the Customer Engagement Center (CEC), a conversational AI solution where the core product, the Customer Engagement Center (CEC), is an all-in-one, cloud-based suite of 12 components designed to transform any business into a fully automated digital brand. With headquarters in New York, Pypestream has a customer base that includes Shell, Chase, Procter & Gamble, Google, Sling, and HBO Max. Pypestream provides customer engagement in several key industries,…
N/A
Pricing
Microsoft Dynamics 365 Customer Service
Pypestream
Editions & Modules
Dynamics 365 Customer Service Professional
$50
per month per user
Add-In - Chat
$60
per month per user
Dynamics 365 Customer Service Enterprise
$105
per month per user
Dynamics 365 Customer Service Premium
$195
per month per user
No answers on this topic
Offerings
Pricing Offerings
Microsoft Dynamics 365 Customer Service
Pypestream
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Features
Microsoft Dynamics 365 Customer Service
Pypestream
Incident and problem management
Comparison of Incident and problem management features of Microsoft Dynamics 365 Customer Service and Pypestream
Feature
Microsoft Dynamics 365 Customer Service
7.4
3 Ratings
10% below category average
Pypestream
-
Ratings
Organize and prioritize service tickets
9.03 Ratings
00 Ratings
Expert directory
1.33 Ratings
00 Ratings
Subscription-based notifications
7.02 Ratings
00 Ratings
ITSM collaboration and documentation
6.83 Ratings
00 Ratings
Ticket creation and submission
10.03 Ratings
00 Ratings
Ticket response
10.03 Ratings
00 Ratings
Self Help Community
Comparison of Self Help Community features of Microsoft Dynamics 365 Customer Service and Pypestream
Feature
Microsoft Dynamics 365 Customer Service
4.5
3 Ratings
56% below category average
Pypestream
-
Ratings
External knowledge base
4.93 Ratings
00 Ratings
Internal knowledge base
4.23 Ratings
00 Ratings
Multi-Channel Help
Comparison of Multi-Channel Help features of Microsoft Dynamics 365 Customer Service and Pypestream
Suitable for ticketing that might also require routing to 'queues' and capturing communication timelines. Not as suitable for heavily credentials-management-type organizations or organizations that are not on the Microsoft stack. Also, not as suitable for organizations that have very high needs for knowledge base management or organizations that do not have resources or a partner to help extend the capabilities.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
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.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
It's not as simple as some of the other offerings, but it is fairly intuitive. The design philosophy is a little more bloated, but it can be streamlined by customizing views and forms (pages) to be organized for end users. Once it is set up, though, assuming your UI choices and design are intuitive, it is simple for end users to use.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
I have worked with Oracle CRM On Demand earlier, mainly for case management and basic customer support workflows. Oracle CRM was stable and worked fine for standard use cases, but customization was limited and changes usually required more effort and time. Integrations with other systems were also not very flexible. Microsoft Dynamics 365 Customer Service is much stronger in terms of flexibility and scalability. The biggest advantage is tight integration with the Microsoft ecosystem like Outlook, Teams, Power Automate, and Power Apps, which makes automation and productivity much better. Case management, SLAs, queues, and omnichannel features are more advanced and easier to configure.
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.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info