Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.
$2
per GB (first 2GB free)
Fin by Intercom
Score 8.8 out of 10
N/A
Fin is Intercom’s AI Agent for customer service, designed to deliver high-quality answers, even for complex queries. It works with any helpdesk, or it can be paired with Intercom’s next-generation Helpdesk to get the full Intercom Customer Service Suite.
$0.99
one-time fee per outcome
Pricing
Azure DevOps
Fin by Intercom
Editions & Modules
Azure Artifacts
$2
per GB (first 2GB free)
Basic Plan
$6
per user per month (first 5 users free)
Azure Pipelines - Self-Hosted
$15
per extra parallel job (1 free parallel job with unlimited minutes)
Azure Pipelines - Microsoft Hosted
$40
per parallel job (1,800 minutes free with 1 free parallel job)
Basic + Test Plan
$52
per user per month
Fin with your current helpdesk
$0.99
one-time fee per outcome
Copilot add-on
$35
per month per user
Pro
$99
per month For analysis of 1,000 conversations
Fin with Intercom’s Helpdesk
from $39 + $0.99 per Fin outcome
per month per seat
Offerings
Pricing Offerings
Azure DevOps
Fin by Intercom
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
Fin comes with a 90-day money-back guarantee. Here's how it works:
Intercom states that users who sign up for the Fin Guarantee Success Program and do not achieve at least a resolution rate of 65% will be paid $1M. This program is designed for high volume customers.
Eligibility criteria:
High volume customers (over 250k monthly conversions) in North America and Europe. Intercom states that phase one of this program will admit customers on Intercom Helpdesk or Zendesk.
Azure DevOps works well when you’ve got larger delivery efforts with multiple teams and a lot of moving parts, and you need one place to plan work, track it properly, and see how everything links together. It’s especially useful when delivery and development are closely tied and you want backlog items, code and releases connected rather than spread across tools. Where it’s less of a fit is for small teams or simple pieces of work, as it can feel like more setup and process than you really need, and non-technical users often struggle with the interface. It also isn’t great if you want instant, easy programme-level views or a very visual planning experience without putting time into configuration.
Fin is great for using for first line support. We use Fin for conversations where customers have a standard question, and Fin is able to pull from our content to answer this accurately and go above and beyond to include some basic problem solving. This really helps us free up our Support Team's time for more complex queries. Fin isn't appropriate for us on technical issues or conversations which require human support. We've had to remove Fin from interacting on these conversations as customers were becoming frustrated with speaking to AI, or having Fin be unable to problem solve. However, this was easy to set up through Intercom, and now customers with complex questions/situations or bugs/technical issues do not engage with Fin and Fin only handles suitable conversations.
I did mention it has good visibility in terms of linking, but sometimes items do get lost, so if there was a better way to manage that, that would be great.
The wiki is not the prettiest thing to look at, so it could have refinements there.
It seems some users really struggle to figure out how to escalate to a human (especially through email).
Not excited about how "soft" resolutions still count as resolutions and are paid for. Though some abandoned cases appear to be able to be concluded as "the user got the answer they needed", there are others where they clearly didn't, because they just open up another chat (or even more), trying to get more info. This pads the resolution stats and makes it seem more effective than it actually is.
Cost -- Fin is quite expensive. It helps us with scaling coverage, but we're not really saving money.
I don't think our organization will stray from using VSTS/TFS as we are now looking to upgrade to the 2012 version. Since our business is software development and we want to meet the requirements of CMMI to deliver consistent and high quality software, this SDLC management tool is here to stay. In addition, our company uses a lot of Microsoft products, such as Office 365, Asp.net, etc, and since VSTS/TFS has proved itself invaluable to our own processes and is within the Microsoft family of products, we will continue to use VSTS/TFS for a long, long time.
We have been and will be continuing our journey with Intercom and nothing too concerning has happened that I have experienced or heard of that has us on the edge yet. If it ever happens it will be something along the lines of "Outgrowing" the use of need of the platform.
It's a great help to get more information about new feature release and stay updated on what the dev team is working on. I like how easy it is to just login and read through the work items. Each work item has basic details: Title, Description, Assigned to, State, Area (what it belongs to), and iteration (when it’s worked on). See image above.They move through different states (New → Discovery → Ready for Prod → etc.).
From an administration standpoint, Fin is very easy to set up, train, and test. Having the ability to impersonate a user in our system to see how Fin responds is huge. It lets you test several situations and throw curveballs at it (as customers will) without the risk of setting Fin live and wondering what will happen. It's also easy to fine-tune. Some chatbots you can never quite get right without spending hours on, but Fin usually takes a few minutes to dial it in. From a customer standpoint, Fin couldn't be easier to engage with. We tell customers up front it's an AI bot and they're wow'd with the experience
When we've had issues, both Microsoft support and the user community have been very responsive. DevOps has an active developer community and frankly, you can find most of your questions already asked and answered there. Microsoft also does a better job than most software vendors I've worked with creating detailed and frequently updated documentation.
Intercom is the premier customer support/engagement model and it definitely has one of the top tier customer support teams as well. I don't think I have ever waited more than 5 minutes to get the information I need or get help with an issue. They are incredible and I aim to model our customer service department after them.
Microsoft Planner is used by project managers and IT service managers across our organization for task tracking and running their team meetings. Azure DevOps works better than Planner for software development teams but might possibly be too complex for non-software teams or more business-focused projects. We also use ServiceNow for IT service management and this tool provides better analysis and tracking of IT incidents, as Azure DevOps is more suited to development and project work for dev teams.
We only used the free live chat version from HubSpot, so Intercom is yards better! If I were just comparing an actual live chat between the two tools, HubSpot was often clunky and delayed, and it was hard to find past conversation information
We have saved a ton of time not calculating metrics by hand.
We no longer spend time writing out cards during planning, it goes straight to the board.
We no longer track separate documents to track overall department goals. We were able to create customized icons at the department level that lets us track each team's progress against our dept goals.
New role opportunities — Using the “Fin-first” approach has reduced the workload for our Tier 1 team, giving them more time to focus on their own career growth. It’s also opened the door to a dedicated, AI-focused role, where a team member regularly reviews Fin’s answers and makes updates to help it perform even better.
Enabling Fin has also reduced our response time and allowed us to meet SLA's.
