Amazon Simple Notification Service (SNS) vs. Phone.com

Using SNS for any notification use case where available is the default and defacto solution. It directly integrates with SES to configure both incoming email and email delivery responses.

Additionally, any notifications, such as CloudWatch alarms, are a good use case for SNS topics and allow us to fan out delivery as needed (pagerduty, email, etc)

Phone.com is a no-brainer. The cost savings over a POTS or in-house PBX system are tremendous. The affordability added on top of the easy to use and deploy features make Phone.com the best choice. Phone.com is well-suited for situations where you need other-than-standard call holding, call routing, and other similar advanced call features.

Incentivized

• Built in for quicker setup within AWS ecosystem.
• Trusted as you control the users and configuration via IAM and easy access controls.
• Can be sent to S3 simple storage or for long term storage if required.
• Can be used in many regions, same configs.

Incentivized

• Provisioning phones throughout an organization
• Compartmentalization is easy with different incoming call ques, routes and rules
• Phone.com is available and generally functional from anywhere you have access to an internet connection

Incentivized

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

Incentivized

• Phone.com has been excellent with support and I can not think of any areas for improvement with regards to that
• Phone.com could provide more graphical assistance when programming call routing. A visual indication of the flow of a call should be presented and would come in handy when planning out difficult ques/call routes

Incentivized

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.

Incentivized

The AWS documentation is well maintained and has lots of information which makes it easier for developers to refer to and develop applications in a fast efficient manner. It is well documented with examples which is easy to understand and implement. You can also get help by posting into forums from like-minded developers.

Incentivized

Amazon Simple Notification Service (SNS) is well integrated in AWS and has been there since the early days of public cloud. It is a cost effective and very inexpensive solution to meet the needs of event notifications and custom messaging. Wish to share that there is considerable number of developers who can easily build solutions using AWS SNS. So, training costs are minimal. Other solutions are emerging and we are seeing a great usage especially of Firebase notifications because of its very neat integration with open source cross platform hybrid app frameworks like ionic, xamarin. SNS needs to become better and should have plugin support for the mobile application developers using low code/no code tools too.

Incentivized

• Cost of alert calls to the different stakeholders across different geographies have gone down since using Amazon SNS.
• Amazon SNS has saved a lot of time for the employees that they used to spend to call multiple stakeholders so they can now focus more on productive tasks.
• Amazon SNS usage needs prior knowledge of programming.

Incentivized

• Reduced cost and improved our efficiency - all reps love it.

Incentivized