Amazon Web Services offers the Amazon Simple Notification Service (SNS) which provides pub/sub messaging and push notifications to iOS and Android devices. It is meant to operate in a microservices architecture and which can support event-driven contingencies and support the decoupling of applications.
$0.01
per 1 million
Fin
Score 8.8 out of 10
N/A
Fin is an AI Agent for customer service. It automates complex queries, improves resolution times, and delivers consistently high-quality support at scale.
$0.99
one-time fee per outcome
Pricing
Amazon Simple Notification Service (SNS)
Fin
Editions & Modules
API Requests & Payload Data
$0.01
per 1 million
API Requests
$0.50
per 1 million requests
Notification Deliveries
$0.50
per million notifications
Fin with your current helpdesk
$0.99
one-time fee per outcome
Copilot add-on
$35
per month per user
Pro add-on
$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
Offerings
Pricing Offerings
Amazon SNS
Fin
Free Trial
No
Yes
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:
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.
The Amazon SNS service is well suited to support event notifications, monitoring applications, workflow systems, time-sensitive information updates, and mobile applications that generates or consumes notifications. It can be used to relay time-critical events to mobile applications and devices. It provides significant advantages to developers who build mobile applications that rely on real-time events. It is not well suited for hybrid cross platform mobile application frameworks at this juncture. An optimal version to meet the needs of a cross platform mobile developer is needed as generally the frameworks are not meant to manage real-time events. It is also not suited for cases where the queue management needs improvement or requires special workflows/tooling.
Fin is well-suited to most use cases as long as it is trained accordingly. With a robust, well-designed knowledge base, Fin can extrapolate information from help articles and provide detailed instructions to an end user without simply sending a link to the article without context. In my experience, Fin is best suited to standard support requests. As the product becomes more complex and product types change, Fin seems less successful at accurately supporting those requests. It is best to maintain Fin's knowledge sources continuously.
At times you receive access denied errors which are annoying.
Rarely do you receive internal failure errors where you can't access the information. It is rare but it does happen.
You are required to add an MWS Authentication Token every so often. I wish it would pull that information automatically for you so you don't have to go searching for it.
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.
It is useful for applications developed using event driven architecture. It helps in tracking and logging the events in a very timely and efficient manner. The dashboards are a little difficult to implement. But overall it is very easy to integrate with other AWS services like Lambda, API GW, S3 and DynamoDB. The permissions to access should be resolved before using it.
Much improved and improving feature set, but overall navigation of the interface and platform is cumbersome. While it's worthwhile to continue building out new functionality and features, there should be some effort to make overall usage more intuitive. Becoming an admin requires either months of daily usage or more complex training.
Amazon Simple Notification Sevices (SNS) support depends on your usage pattern and definitely on your support plan as an enterprise with AWS. Before reaching out to support you should read their documentation, as they have mentioned almost all the common issues and their solutions there. However, for specific issues, they generally respond in 1-2 business days.
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.
Amazon’s SNS is incredibly easy to set up compared to the more powerful, but complex, Kafka flavours.
SNS’s core advantages are –
· no setup/no maintenance
· either a queue (SQS) or a topic (SNS)
· various limitations (on size, how long a message lives, etc)
· limited throughput: you can do batch and concurrent requests, but still achieving high throughputs would be expensive
· SNS has notifications for email, SMS, SQS, HTTP built-in.
· no "message stream" concept Overall, it would be the best choice to get into the concepts of Pub/Sub concepts as although it has limitations it can provide significant capabilities and solutions
Our previous support platform didn't offer an AI agent (they used it internally for their own tickets, but there were delays with shipping it to their users, i.e., us, so we migrated to Intercom). Our colleagues from different brands within our own company demoed a different chat-only tool, but it looked much less impressive than what Fin offered, so we haven't considered it either.
Amazon Simple Notification Service (SNS) saved us a lot of extra coding time by providing straightforward functionality we needed in our ad campaign automation tool.
Amazon Simple Notification Service (SNS) allows us to maintain a consistent, serverless model within our applications.
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.
