Notifications

SMS vs Push Notification

Key differences between SMS and push notifications: 

1. Delivery Requirements: 

• SMS can be sent to any mobile phone number and works without internet connection or app installation 

• Push notifications require users to have installed your app and be logged in 

2. Content Capabilities: 

• SMS is limited to 160 characters of text only 

• Push notifications support rich media like images, videos, GIFs and interactive elements 

3. User Experience: 

• SMS is more intrusive but has a 90% read rate within 3 minutes of delivery 

• Push notifications are less intrusive as users can easily swipe to dismiss them 

4. Cost Considerations: 

• SMS is significantly more expensive due to carrier fees 

• Push notifications only have infrastructure costs, making them more cost-effective (First 1 million SNS API requests per month are free, $0.50 per million thereafter)

5. Functionality: 

• Push notifications offer one-click access to specific app features and deeper integration 

• SMS requires users to manually click links and navigate to content 

Sender ID

Sender IDs are alphanumeric identifiers that telecom carriers support and regulate in countries where they are permitted.  The process involves multiple parties working together - AWS provides the infrastructure and handles initial processing, while telecom carriers validate and manage the final delivery aspects.

A Sender ID is a more flexible and faster alternative to short codes for sending SMS messages to the UK. 

• An alphanumeric string (up to 11 characters) that appears as the sender name on recipient devices 

• Helps with brand recognition and allows companies to use their brand name as the sender 

• Typically used for one-way messaging only - recipients cannot reply back 

• Suitable for lower volume messaging (less than 100 messages per second) 

• No lengthy registration process required in most countries, though some require pre-registration 

• Regulated by telecom carriers in supported countries 

Security & Importance 

• Helps establish brand authenticity 

• Some countries require pre-registration to prevent misuse 

• Traffic is monitored to prevent spam 

 1. Sender ID Benefits: 

• Faster setup compared to short codes (which take 12-16 weeks) 

• Allows you to identify yourself to recipients using an alphanumeric string instead of a phone number 

• Maximum length of 11 characters 

2. Sender ID Characteristics: 

• Can be alphanumeric 

• Must be registered in countries where required 

• Designed for SMS messaging where supported by telecom carriers 

3. Implementation Considerations: 

• No lengthy registration process like short codes 

• More cost-effective solution 

• Suitable for both transactional and promotional messages when properly registered 

Short Codes 

• 5-6 digit phone numbers specifically designed for commercial SMS 

• Supports two-way messaging - customers can reply back 

• Designed for high-volume messaging (100+ messages per second) 

• Requires extensive registration and approval process (12-16 weeks for UK) 

Long registration time due to: 

• Must be reviewed by all wireless carriers 

• Requires approval of use cases and content 

• Involves multiple carrier dependencies 

Security : 

• More secure due to rigorous vetting process 

• Better deliverability rates for high-volume messaging 

• Allows customer interaction through two-way messaging 

Role of AWS and telecom providers in SMS messaging: 

Both Sender IDs and short codes are managed through a collaboration between AWS and telecom providers: 

AWS's Role: 

• •  Provides the API and software infrastructure for sending SMS messages 

  • Works with SMS aggregators to push messages through 

  • Handles the initial message processing and routing 

  • Manages customer accounts and configurations 

  • Provides monitoring and delivery status tracking 

Telecom Providers' Role: 

• Carriers (like Verizon, T-Mobile, etc.) are responsible for actual message delivery to subscribers 

• Set limits on messaging rates (e.g., 1 SMS/second for long codes vs higher limits for short codes) 

• Validate and process sender IDs and short codes 

• Manage the final delivery to end-user devices 

 Message Flow: 

Client → AWS SNS → Aggregators → Mobile Carriers → Mobile Phone 

 The process involves multiple parties: 

• AWS handles the initial processing and routing 

• Aggregators negotiate with carriers for message delivery 

• Carriers are responsible for the final delivery to phones 

A comparison between Amazon SNS and Amazon Pinpoint: 

If you only need basic push notifications triggered by alerts Use Amazon SNS for simpler implementation

• More cost-effective for basic push notification needs

• Direct integration with mobile push notification services

If you need advanced features Use Amazon Pinpoint if you want:

• User analytics and engagement tracking

• Scheduled campaigns

• A/B testing

• Segmentation based on user attributes

• Campaign performance metrics

Key Differences 

 Amazon SNS 

 Primary Purpose : Simple pub/sub messaging service for application-to-application (A2A) and application-to-person (A2P) communication 

Messaging Capabilities:  Basic push notification delivery without advanced targeting or scheduling 

Analytics & Targeting : No built-in analytics or audience segmentation 

Throughput : Limited throughput with throttling restrictions 

Use Case Fit :  Simple push notification delivery without need for targeting or analytics  

 Amazon Pinpoint 

 Primary Purpose : Digital user engagement service focused on targeted messaging and analytics 

Messaging Capabilities:  Advanced campaign management, segmentation, and scheduled delivery 

Analytics & Targeting : Rich analytics, user segmentation, and campaign performance tracking 

Throughput : Higher throughput (up to 100,000 messages/minute) 

Use Case Fit :  Full-featured customer engagement with analytics and campaign management