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
Magnolia
Score 9.8 out of 10
Mid-Size Companies (51-1,000 employees)
Founded in Switzerland in 1997, Magnolia is a CMS used to build composable digital experiences. Magnolia helps create fully integrated customer experiences and speeds up digital delivery of content. Magnolia boasts 480 enterprise customers, thousands of Community Edition deployments, and more than 200 certified Magnolia Partners around the world. They further state that their enterprise customers include Sanofi, Generali, the Atlassian, The New York Times, Harley Davidson, and Union…
$3,500
per month
Pricing
Fin by Intercom
Magnolia
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
DX Core
$3500
per month
DX Cloud
$6000
per month
Offerings
Pricing Offerings
Fin by Intercom
Magnolia
Free Trial
Yes
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
Yes
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.
FIN is great if you need someone to direct the customers based on their problems. You also have the option to use multiple languages if you have a worldwide customer base, so that's great. If you provide enough documentation to feed it, FIN can also solve tickets on its own, which enables your team to focus on other tasks. You can also have him handle conversations in other applications, such as Discord or Slack, and have them create ticket issues in JIRA if your team uses it.
Magnolia is a very capable DXP, that provides client with lots of flexibility in composing its own stack. While the core of the platform is a content management system, the open architecture of Magnolia DXP allows it to connect to any platform, allowing client to extend the capabilities. One scenario would be a centralized content hub - where through a single platform, content authors can choose which channel to distribute what content. For example, long form content for consumers viewing on a laptop, short form content for those using a mobile browser. This allow the client to personalized the experience based on channels. Another scenarios would be leveraging on GenAI - using Magnolia's built-in connector to ChatGPT. If that is not the service that one desire, you can always connect to another AI service such as Google Gemini. With GenAI, connected, content author can use AI as co-pilot to help them scale up their content production.
Speed of development - time to delivery from zero to MVP was excellent
Ease of use - the authoring experience is very easy to build and train
PAAS/SAAS - the managed service platform removed the traditional overhead of running in-house technologies, meaning we could focus on value add, with less time spent keeping the lights on.
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.
The documentation provides samples that are often out of context, and difficult to know where the provided example code should be implemented. More tutorials providing the full project or step-by-step instructions on how to implement subject material would help greatly. Baeldung is a resource I would consider the gold standard in how this is done in other spaces.
The use of JCR and Nodes makes object serialization/deserialization painful. Jackson compatibility or similar would be a welcome enhancement to the developer experience. Maybe leveraging code-gen from light modules to build model classes when possible could help accomplish this.
Modifying the home layout from light modules is frustrating. It seems that any configuration overrides made merge with the default rather than overwriting, which makes for a difficult combination of guess-and-check while referencing the documentation to see what should be in each row/column when making changes.
Including "mark all as read" or "delete all" in the notifications app would be a great quality of life improvement. It seems that by default, users have to individually select messages and operate them.
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 core experience is solid but the key friction across our team is that there are so many new features for improving Fin are being launched. Content improvements, guidance settings, recommendations, trends, and monitors are each useful in isolation, but they sit across separate areas of the platform with no clear starting point. The recurring feedback from my team is that it is hard to know where to focus. A consolidated "Improve Fin" section could really improve the experience, the ideal option would be a training page where our team could improve Fin in one place, ideally by answering questions and Fin would then be able to add those details in the right place, where it's creating new guidance or building procedures. I feel that would make uptake a lot quicker.
We've shown it to a number of users both clients and our own team and despite initial apprehensions, they "get it" very quickly. It's intuitive and friendly and quick to perform daily tasks. We once had a client tell us "Using Magnolia makes me smile" which says it all for us.
I gave [it] 7/10 only because of the loading time of pages. Otherwise, I think it deserves an 8. Normally this is not an issue per [se] but considering the rating matrix and as I have been asked to honestly write about it. Yes, the page loading times could be improved.
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.
You always get an answer based on your SLA. But you always get a solution. That's the successfactor in this case. To often i was frustrated about people in a company without even a clue what there product is about or how to solve a problem. Magnolia's Support Team does a very good job and try to help you in most of the cases
Although we have not utilised a specific chat box like Fin before in other websites, we have used ChatGPT and Claude within our general work. Our Product and Engineering team make use of Devin within Azure Dev Ops to support with their work. However, Fin is the most suitable for what our Support Team requires as this can be integrated into our chat with customers.
I've used several CMSs like AEM and EpiServer, and comparatively, they all excel at different things. Magnolia is the best to develop for/against. Episerver has the best/most fluid UI in terms of content editing, and the overall admin experience AEM is just all around sucks.
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.
Magnolia has brought about positive impacts. For instance, we need not outsource web design and marketing services because thanks to this software, we can handle most work inhouse
The software is affordable with no compromises on capabilities and therefore it is gives us value for money.
