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
ServiceNow IT Service Management
Score 8.4 out of 10
N/A
Built on the ServiceNow Now Platform, the IT Service Management bundle provides an agent workspace with knowledge management, and modules supporting issue tracking and problem resolution, change, release and configuration management.
$10,000
per year
Pricing
Fin by Intercom
ServiceNow IT Service Management
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
Starting Price
$10,000.00
per year
Offerings
Pricing Offerings
Fin by Intercom
ServiceNow IT Service Management
Free Trial
Yes
No
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:
Use Fin in at least 250 conversations within the first 90 days after trial. If you're not satisfied, you can request a refund. Refund requests must be submitted within 90 days of starting the subscription.
We started using Intercom five years ago, and it is probably the best decision we made. It is without a doubt the best investment in our startup journey. It is rock solid, with constant innovation and product improvements. We are a fully remote team, and it helps keep all the customer conversations and interactions in one place. So, we can seamlessly collaborate and ensure that nothing drops.
In our organization, we are using ServiceNow extensively. Change Management, Incident Management, Problem Management, Time tracking are few modules which we use extensively. This sort of model will work for any product or service based companies as the product is built on ITIL framework. So this product will be suited for small or large scale companies to better organize and add controls and track SLA's for technology or business process.
Great UI - everyone has their own inbox but can still see all incoming messages.
Fin AI - we love the AI functionality, it saves tons of time of the team.
Automated emails - we configured Intercom in a way that it uses a lot of information we have about our users (e.g. their subscription, date of upgrade, etc.) so that we can use it to automate communication.
When I have a number of requests to make, for example a request to add a dozen or so user accounts to more than one group account in Active Directory , I can put all the needed information into the initial form, add it to my "shopping cart" and all of that information remains on the screen for the next item for which I only need to edit a few items (like the AD group name in this example), and keep adding them to the shopping cart until I have them all. When I "Check Out" each of those items is generated as a separate task under the one request. It simplifies and expedites the creation and tracking of these kinds of requests.
I can easily and quickly see what tickets are currently assigned to me in order to prioritize them and remain aware of my workload.
Numerous fields for CIs can be used when trying to find the entry for a particular item. For example, IP Address, server name, raw text, classification, and so on.
To help with making sense out of related tasks, when a task is assigned to me and I need to open another task for a different team to work in order to complete my task, I can open a sub-task from my ticket so that the relationship between the two can be pulled up later into reports. For example, I may have a task to build a new vm, and need to open tasks for networking, security accounts, software installation and so on. By opening sub-tasks from my assignment, the time spent by all parties concerned is tied together for more meaningful cost accounting.
There was a report of active chats per hour that helped us a lot to organize the team schedule, understand hours of greatest flow, nowadays there is only this report for new chats, but if we have chats that started at other times but were not closed, it ends up giving a false impression that the service was empty at a certain time.
Not being able to group users by platform, only by API, we have a small team and having to send a developer to do this all the time is unthinkable.
Unable to determine what is a lead and a user based on our criteria, today Intercom assumes that just because a user exists on our platform then they are a customer, but this is not true for us, as our platform allows free trials, so this function of separating leads and users is completely useless for us.
When we create a user manually, I either have to provide an email or manually provide an ID, since nowadays you have integration with WhatsApp, so I often register a user with just a name and phone number. So the tool should allow me to consider the phone number as an ID as well, or at least generate an ID automatically for me, as it does when we receive a conversation via WhatsApp started by a customer who was not previously registered in the tool.
The attendant can record audio directly through the Intercom, it has been integrated with WhatsApp for some time, and until today we need to use other platforms to record a simple audio that is so common when using WhatsApp.
Sometimes the attendant is busy and the customer sends an audio message on WhatsApp. It would be nice to be able to transcribe the customer's audio message as an internal note to help the attendant be more agile.
The AI marks many calls as resolved even though the agent has taken over the conversation, just because the customer hasn't clicked on anything, but that doesn't make sense, most customers don't bother to respond to the AI, sometimes they don't even remember to respond to us, I understand that if there are more than 2 messages sent by our agent after the AI's response, it should already be considered that the AI didn't resolve the service.
In cases of users with many companies, it should be possible to send via API the information about which company the customer is logged into at the time of the conversation. Nowadays, we have to ask the customer which company they are talking to because all of them appear on the Intercom and we cannot know which one they want support from.
Being able to place hierarchy in tags, today we use tags to categorize conversations and there is a hierarchical level in this classification, for example: Usability > Fiscal > Rejection, but as there is no way to define hierarchy, we cannot do analysis by tags through the platform, we have to do the part in Excel
Being able to make calls to other countries like Brazil
Report of customers and users who call the most by period, today I can even get a list of customers who haven't called for a long time, but customers who call support a lot is also very relevant information and I don't have it on the platform.
Tinha um relatório de chats ativos por hora que nos ajudava muito a organizar escala de time, entender horas de maior fluxo, hoje em dia só tem esse relatório para novos chats, mas se temos chats que começaram em outros horários mas não foram encerrados, acaba dando uma falsa impressaão que o atendimento estava vazio em determinado momento
Não poder agrupar usuários pela plataforma, somente por API, temos uma equipe pequena e ter que toda hora passar um desenvolvedor pra fazer isso é impensável
Não poder determinar o que é lead e usuário mediante nossos critérios, hoje o Intercom assume que só porque um usuário existe na nossa plataforma então é um cliente, mas isso não é verdade pra nós, pois nossa plataforma permite testes gratuitos, sendo assim essa função de separação de lead e usuário pra gente é completamente inútil
Quando criamos um usuário manualmente ou tenho que informar e-mail ou informar manualmente um ID, sendo que hoje em dia vocês tem integração com o whatsapp então muitas vezes vou cadastrar um usuário só com nome e número de telefone, então a ferramenta deveria me permitir considerar o telefone como ID também ou no mínimo gerar um ID automaticamente pra mim como faz quando recebemos uma conversa pelo whatsapp começada por um cliente que não estava previamente cadastrado na ferramenta
O atendente poder gravar áudio diretamente pelo Intercom, já tem integração com o whatsapp a tempos, e até hoje precisamos usar outras plataformas pra gravar um simples áudio que é tão corriqueiro no uso do whatsapp
As vezes o atendente está ocupado e o cliente manda um áudio no whatsapp seria bacana poder transcrever o audio do cliente como uma nota interna pra ajudar o atendente a ter mais agilidade
A IA marca muitos chamados como resolvidos mesmo o atendente tendo assumido a conversa, só pelo cliente não ter clicado em nada, só que isso não faz sentido, a maior parte dos clientes não se preocupa em responder a IA, as vezes não lembra nem de responder a gente, entendo que se tiver mais de 2 mensagens enviadas pelo nosso agente após o atendimento da IA, já deveria contar que a mesma não resolveu o atendimento.
Em casos de usuários com muitas empresas, deveria ser possível enviarmos por API a informação de em qual empresa o cliente está logado na hora da conversa, hoje em dia temos que perguntar para o cliente de qual empresa ele está falando pois no Intercom aparecem todas e não conseguimos saber pra qual ele quer atendimento
Ter como colocar hierarquia nas tags, hoje usamos tegs para categorizar conversas e tem um nivel hierarquico nessa classificação, exemplo: Usabilidade > Fiscal > Rejeição, mas como não tem como definir hierarquia, não temos como fazer analises por tags pela plataforma, temos que fazer a parte no excel
Ter como fazer ligações por outros países como o Brasil
Relatório de clientes e usuários que mais chamam por período, hoje até consigo pegar uyma lista de clientes que não chamam a muito tempo, mas clientes que acionam demais o suporte também é uma informação muito relevante e não tenho pela plataforma
It is hard to find areas for improvement, the tool is very powerful. That said, building the CMDB still involves some manual interaction which was not how it was presented in demos.
The CMDB data is almost too deep and detailed. When you build the relationship map it can be so large that it is overwhelming. You can limit this, but the default maps are massive if you are discovering lots of device classes.
The product is expensive. Since they are the leader in the industry and the product has tons of features, they definitely charge for it!
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.
To be completely honest setting up a new ticketing system can be a pain in the ass. Once you have it setup and customized the way you want it, you don't want to switch unless you're unhappy with the product. Unless future releases and updates really muck the system up, I wouldn't change.
I'm giving it an eight since certain items are self-explanatory and intuitive, depending on where you are in the suite. In contrast, other features, such as copying/duplicating workflows, are not prominent (nor available). I have worked with different platforms, such as Sprinklr, Engagor, and Zendesk, and given my experience, I know my way around these quite well. I love Intercom, but there is room for improvement.
The dashboard is so confusing, [there are] many clicks to open a task and search by a ticket. The Enterprise customisation [we did] has finished to kill the software and creates a really bad experience on a daily basis. [It is] So slow, and so many clicks to process a ticket. Works only on IE so, that [should] make you realize that [it] is a bad idea.
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.
I would give it this rating because we have had no major issues with the support for ServiceNow after we implemented it at our organization. They seem to respond promptly and efficiently if we ever do need to open a support case with them about an issue we are having.
To type in what should be a text box, you have to click an empty cell, a tiny text box pop up opens with a check box and an X. You the. Type in the text box and have to click the check mark. If you have a bunch of fields to fill out, doing this is very annoying. Absolutely know thought went in to this. I'm sure somebody in marketing thought it was a good idea. It wasn't.
Without exception, every client I have worked with has been very happy with their resulting product. While this is partly due to my work, I must point out that the platform is the winning decision, not the implementer.
Odoo was, in my opinion, terrible - a jack of all trades and master of none, which is why all teams in the business moved away to bespoke software. Freshdesk - an easier and more organisable way of creating and managing tickets. Although Intercom now has tickets, we're still using Freshdesk due to ease of use after 5 years, and our development team is also using it, so more cross-team collaboration happens there.
We used to use Jira to handle service tickets but it's way too robust for something this straightforward. Due to the nature of Jira, you needed to already have a lot of documentation and knowledge about who should be assigned the ticket, so the lift of creating a ticket was time consuming.
Intercom has allowed Frayt to improve customer satisfaction by ensuring any active issues are addressed immediately to ensure effective service for their needs.
Has decreased the time for response when addressing contractors due to the ability to reach out through various means to individuals.
Has increased visibility for specific issues to multiple team members for things to be addressed appropriately.
Overall ServiceNow has a positive impact on getting the SLA of tickets down in supporting our customers.
One negative impact has been the amount of time to get the product to produce an ROI, it's almost too big to fail and too big to replace. You almost become committed to the product. Good or bad.
Another negative impact would be if you track metrics of employees and time tracking, there is a lot of scenarios where engineers will track time on tickets but not get credit for closing them as the assignee function of tickets can only be tied to one user and credits only the engineer who closes the ticket.
Another positive impact would be the level of security for permissions and scaling the workloads is robust and you will get out of the system what your team is willing to put in.
