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
osTicket
Score 8.5 out of 10
N/A
osTicket is an open-source help desk / ticketing platform that can create inquiries online, through email, and through phone calls.
$12
per month
Pricing
Fin by Intercom
osTicket
Editions & Modules
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
No answers on this topic
Offerings
Pricing Offerings
Fin by Intercom
osTicket
Free Trial
Yes
Yes
Free/Freemium Version
No
Yes
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.
It's excellent when users often have trouble understanding certain aspects of your product, so you don't have to manually share the same information every time. It's less appropriate if your user problems are user-specific, as then you probably don't have every expected case covered in your documentation, which then requires Fin to have access to your codebase, at which point you might want to consider building your own agent.
For beginning smaller companies that are in need of partially automating their incoming requests this product is easy to set up and will assist in structuring these request[s]. These requests can come in via email/phone or web portal. For companies that are beginning to streamline their support procedures, this tool can be a first step into automating part of these processes. This is also how user[s] should see it. It is merely a tool that can assist in structuring the incoming request flow the rest still has to be fit into business processes.
osTicket is extremely user friendly for end users and support agents. It's very easy for new end users to put in a service request. This aspect of simplicity is important because we don't have to train new users on how to put in service requests.
Feature wise osTicket has everything you need without being overly complicated or cluttered. This is important for us because it allows for faster support times and happier end users.
Lightweight and very reliable, osTicket uses PHP and MySQL. Setup is easy and it can be hosted internally or externally web hosed. Also, since it relies on PHP it gives you flexibility to use Apache, Nginx , Lighttpd , IIS, etc.
Thriving community: the community behind osTicket is feature-wise. Which is very helpful if you have any questions.
Best of all, osTicket is completely free and open source. While they do offer pair tier cloud-hosting and enterprise support. The free version offers all the features of the paid tiers (minus hosing and support).
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.
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.
FIN is easy to set up and pretty quick to get everything the way you need (some things could be handled better), and you can preview how it's going to work before it's available to everyone. Since you can use FIN on multiple channels, you can save a lot of time by not having your team work on multiple chat platforms as well.
I am familiar with osTicket and this allow me to teach all the staff and support them whenever they have any concern regarding the usability and following processes.
I can get help by asking Fin questions about itself. It answers accurately, citing its own Help Center resources with visuals. It can reason and dialogue well. But when it comes to getting human support for Fin, it is not as quick. It can sometimes take a few days. They are polite and well-meaning. Some things aren't their fault (product limitations), but there was one occasion where something took a long time to resolve with lots of back and forth but it was I who found out the error in the end that they missed, so they didn't really help resolve it.
There are so many AI platforms available, and you could theoretically build a system using the available AI API's from any of the big platforms. However, I dont think it's as easy as this. Intercom is deliberately built for customer service, the features they are releasing a based on providing the best customer experience. If we were to build this ourselves or to use another platform we would be taking on the upkeep, using Fin is just much simpler as it's also our chosen ticketing platform so anything that Fin is not able to answer yet and escalated directly to our team with no extra effort required from our side.
osTicket has proven to be a very useful tool for the team to help support the business. Open-source was the right price point and self-hosting as mentioned was quite important (however I believe that osTicket does have a hosting solution available if needed). Jitbit was a close contender but didn't like how it doesn't separate people submitting tickets from users acting as agents. So all in quite happy with the choice.
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.
When we had a hosted version of osTicket, we were saving some time by having them work on our setup, but we were spending a lot. Switching to our own osTicket build from their open sourcing not only saved us money upfront but we actually spent LESS time developing because we knew our ideas and didn't have to explain them to another (unrelated) party.
Creating our own ticketing infrastructure for institutional data requests has been a game changer for us. We have been able to interface with our enterprise email client and create a level of customization that meets our existing informational technology culture.
