Fin vs. Twilio

Fin is fantastic at answering simpler inquiries, where the range and types of questions are easier to categorize. Thereby reducing the subset of possible answers. Where it has shown great improvement - but still needs more improvement - is by becoming a true Agentic AI support engineer that is capable of answering more technically nuanced questions. Our product has a lot of variables used for troubleshooting that cannot be adequately captured in documentation. Even though we provide thousands of pages of spec docs, each issue is unique. Training and empowering Fin to be as good as a Level 1 support engineer is still very challenging.

I found Twilio to be excellent and very easy to use for a programmer in all aspects related to voice, SMS, and other features utilizing their API. I found the node client to be excellent and helpful. We previously used the Apex client for Salesforce before it was discontinued. Although we try not to use Twilio from Apex anymore, using that client was easier than implementing our own.

Incentivized

• It is very easy to train
• It does a great job of recommending answers when little context is given.
• I love the ability to create a snippet to address issues in the moment or in the long term, based on FAQs.

Incentivized

• Easy to see my team in one place, when they log in and out and what call status they are in.
• Twilio is a simple, user friendly way to log in and out of work activities.
• Excellent services and support.
• The omnichannel feature which allows agents to get request from all channels.

Incentivized

• 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.

• Segment’s email identifier is case-sensitive, which is ridiculous because emails themselves are not case-sensitive. This means that if I send a capitalized email address in an identify call, it will create a duplicate user rather than matching it with the lowercase email. I think this is a technical oversight that should be corrected.
• I’d like to see more information about the eventual transition of existing Frontline customers to Twilio Flex
• I’d like to see some integrations between Twilio Studio and OpenAI or another open source LLM to provide automated responses, if this hasn’t been done already
• I would like to be able to drag and move the actual lines connecting the steps in Twilio Studio, sometimes mine can get pretty messy
• I think a Bug Report form would be beneficial for developers

Incentivized

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.

Incentivized

Unless we can get this handled quickly -- less than 1 week -- we will likely switch to another provider who, in my opinion, we'll have to spend close to $3,000 in development time to build a new integration for texting. Our clients need texting and I feel Twilio has failed us miserably.

Incentivized

The platform is overall clear and intuitive. As with any new platform, there's a learning curve, but that wasn't an issue for our team (and it shouldn't be an issue for others). Fin options are scattered across several submenus, and I'd like them grouped together, but I also like having all those training-related tabs open at all times, so it's not much of a real issue for me.

Twilio has well documented APIs and examples. There are several tutorials, videos and Q&As regarding their services. So, usability is very good. I must say that advanced knowledge of telephony, API/Programming and error-handling is essential to make good use of Twilio. It's not just plug-and-play unless you are integrated with a system that has all of the programming built for it.

Incentivized

always there

Incentivized

works perfect

Incentivized

Twilio executes what it is designed to do: send SMS messages at scale while providing very good deliverability. I believe that Twilio is very good at what we use for adding SMS messages to our comms strategy. We can see those messages get opened and replied to, which is exactly what we are looking to achieve.

Incentivized

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.

Incentivized

I have not had to communicate with Twilio support in the last 3 years but my past experience with them has been very positive. They replied to my previous requests promptly and kept me well informed to resolve my inquiries. With their documentation that's available, I hardly imagine why anyone would need to contact support since it's all there in a concise and easy to understand format. It would probably take you longer to type out a support ticket than to just open their doc websites.

Incentivized

Easy to know the learning path

Incentivized

The implementation was surprisingly easy but we are having to adapt from our old process to work well with Intercom.

Incentivized

The developer APIs and SDKs are super easy to follow.

Incentivized

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.

Incentivized

We evaluated many fundraising-based text-to-give programs and found the subscriptions prohibitively expensive for our small scale and uncertain first few years of development. While we may be willing to invest that kind of money after discovering how things work, we're happy with Twilio now and have no desire to start over.

Incentivized

Being in South Africa, direct local currency support would be nice

Incentivized

• 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.

Incentivized

• It helps drive the adoption of multi-factor authentication by making second-factor authentication quick and easy.
• Decreases the number of times a user spends migrating to a new device from an old one.
• Enables easy access to second-factors of authentication by offering multi-device support, making multi-factor authentication painless.

Incentivized