Kbee vs. Sprinklr Service vs. Stack Overflow for Teams

Sprinklr Service has always been well-suited for all of the work we do. As it's all social media content, and most require responses or escalations, Sprinklr Service covers all of that. The only time I think we wouldn't need it is if we were working with a much smaller client who didn't need us to have eyes on so many platforms at once.

Incentivized

In my opinion, Stack Overflow for Teams is well suited for an organization that is on a hiring spree for the engineering teams. The reason for it is because instead of catering to doubts of new joinees individually, they can be asked to refer to the Stack Overflow and hence will save a lot of time for both new joiners as well as the existing employees.

Incentivized

• Automated routing to appropriate teams
• Automated notifications for certain types of content or posts from certain users
• The reporting options are fantastic.
• We've integrated a chatbot seamlessly with Sprinklr modern care so our team members can pick up a conversation if our bot isn't able to provide an answer.

Incentivized

• Sharing technical solutions to problems we encounter in our internal development environment.
• Sharing best practices we find in external resources.
• Discussions on design patterns and conventions we can use in our projects.

Incentivized

• I find it difficult to dive into analytics for each social post. The reporting tool gives me an overview of the channels but I would love to look at a breakdown of each post performance.
• You currently can't add closed caption subtitles to videos uploaded through Sprinklr so this results in having to revert to the native platform.
• I would love to be able to set up a newsfeed that includes posts from a number of our partner accounts, so I can keep up to date with what they're posting.

Incentivized

• I would recommend an increased engineering focus on the Microsoft Teams integration.
• It would be nice to make more medals.
• Easier ways to earn points.

Incentivized

The biggest reason we renewed, and kept up with Sprinklr Modern Care is because it is an active community and there is customer buy-in already. They continue to update and improve the product, but more importantly, the customers are using it. It's easy to switch products when it's not an active component in your daily structure, but switching and migrating the data or providing alternatives becomes difficult when customers have grown accustomed to a specific experience. As long as they continue to improve the available features and the community stays active, renewed use will continue.

Incentivized

I've spent year designing products so I'm a tough judge when it comes to other solutions. It's clear that Sprinklr Modern Care was designed for the average online consumer with a very user friendly interface. They have made improvements to the admin tools to make that area of the product easier to use as well.

No issues with system availability. They manage updates in off-peak hours and I usually don't notice the changes until I log into the system the next day.

Performance is great and is not negatively effecting our processes. We have to make sure it doesn't effect out load times. Not currently seeing any issues with widgets affecting page load times.

I know the Sprinklr conference calls have been helpful, but sometimes submitting a ticket can be a little daunting. In the past, we've included information in screenshots that are then asked for by a member of the support staff. The turnaround time has been between 3 days, which isn't horrible.

Incentivized

Our customer support team went through in-person training. I am not unable to rate.

Basic setup took me less than 30 minutes. This includes initial configuration, putting in the initial content, and getting the look-and-feel customized. The domain routing took the normal lag time any other website or blogging service. The really important thing was to get the user accounts setup and begin seeding the system with content before a public launch.

First, we had a social studio which was good in terms of functionalities but slow. After that, we had the chance to use Talkwalker & social bakers which were good tools yet not enough compares to Sprinklr

Incentivized

It's easier to use Stack Overflow for Teams Q&A to maintain our knowledge base over time, over the Confluence wikis that we also maintain. You don't need to bother about folders, filenames, templates - just ask a question and answer it or get it answered. It feels less formal, so developers feel more free to add content.

Incentivized

• Increased employee efficiency: Having a clear, one-stop "shop" where users can leave feedback, ask questions, and find bug fixes or workarounds has saved me (and other community managers at my company) loads of time that was once spent responding to numerous emails on an individual basis.
• Better customer service: Since everyone in the company is alerted of what's being written on our forum, it's easy to spot a high-priority issue, delegate to the person in charge, resolve it, and respond as soon as possible.

Incentivized

• It makes the search for answers more efficient, so devs can focus in more important things.
• Knowledge is not lost, even if people leave the company.

Incentivized