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 1 resolution
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 1 resolution
Copilot add-on
$35
per month per user
The Early Stage program
$65
per month (6 support seats)
Proactive Support Plus add-on
$99
per month
Fin with Intercom’s Helpdesk
from $39 + $0.99 per Fin resolution
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:
Use Fin in at least 250 conversations within the first 90 days after trial. If you're not satisfied, you can request a refund of up to $1M. Refund requests must be submitted within 90 days of starting the subscription.
It's great for a web-enabled tool, so there is immediate ability to give feedback or ask questions. It isn't as easy to set up a desktop application as it would require more coding experience. Some older users are skeptical of its abilities, and that it is taking away from customer service, but in our use, it enhances it - that is a tough barrier to breach.
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.
Answering simply queries that can be gotten from information in our help articles - powering self-serve for our customers.
Helping us triage and analyse customer queries by understanding key custom attributed of a conversation and key data points to help us route customers to the right team.
Through automation, helping our teammate be more quick and efficient in resolution times and SLAs.
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).
If I can see that our Fin involvement/resolution rate has increased in one week, it would be great to see the theme of conversations it's resolving, rather than having to dig around to see why there was an increase.
Sometimes the hand-over functionality doesn't work as well as it could, and often Fin errs on the side of resolving the conversation (which I understand because we're charged per resolution), but this can be frustrating to have to sift through and dig these customers back out.
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.
The usability of Fin by Intercom is intuitive and easy to use. When I used it for the first time, it didn’t take me long to understand how the platform works and how to set things up. It also provided helpful guidance, and there is a Fin bot that you can use to learn more about the platform and ask questions.
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.
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.
Fin definitely stacks up pretty much at the same level when it comes to leveraging the input data KB to address customer queries. However reporting flexibility is something missing compared to the two mentioned platforms. The categorization of issues is much easier and accurate making it further analysis less time intensive. Why we selected Finis a difficult question for me to answer as the above platforms are from my previous company and when I moved to my current role Fin was already in place.
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.
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.
