ServiceNow Customer Service Management vs. Stack Overflow for Teams

It is well suited for medium to large companies that manage different teams and need to communicate constantly and track progress in a timely manner. It is less suited for small enterprises as it will overwhelm users with the features and functionalities embedded.

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

• We manage internal tickets through ServiceNow Customer Service Management. We raise tickets with IT and other team
• We manage our datapipe customers through ServiceNow Customer Service Management and it efficiently manages our customer interactions
• ServiceNow Customer Service Management helps us manage projects and tasks and keep a log of all our migration customers

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

• Adding in additional chat features would be nice
• Viewing where you stand in priority
• Having a way to automate more of the processes

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

Bottom line is that it does what you need it to do. We've been using Service Now as a ticket managing tool for a few years now. There's really not much it can't do when it comes to recording interactions. It has been nice using inventory tracking for software licenses and hardware as well.

Incentivized

Support has been very good. Any time there has been a real issue, the team has responded very quickly and identified the issue without a lot of repetitive questions that I've seen from other services. There is a great external community and internal knowledge base that covers pretty much anything you need.

Incentivized

Atlassian Jira lacks certain features and process which was delivered by ServiceNow Customer Service Management. Also, flexibility to customise was a point to select ServiceNow Customer Service Management tool. Cost which was high than Atlassian Jira compensated as it improved overall customer satisfaction and reduced resolution time by taking help of Knowledge base integration

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

• The negative impact for my team is the delay in team completing tickets but not a system issue.
• A positive impact for my team is we can easily view the status of tickets and the follow-up emails are beneficial to maintain records of tickets.
• Negative impact is that there is no user job aid or helpful tools for new users.

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