# WhatSnap SMS Reliability

Understanding WhatSnap's reliability, infrastructure, and how we ensure consistent SMS delivery.

## How reliable is WhatSnap SMS?

**Extremely reliable** - WhatSnap leverages robust cloud infrastructure and proven SMS technology to ensure exceptional reliability for your business messaging.

***

## Infrastructure & Uptime

### AWS Cloud Platform

WhatSnap is built on **Amazon Web Services (AWS)**, one of the world's most reliable cloud platforms.

**AWS Benefits:**

* ✅ **99.99% uptime SLA** for core services
* ✅ **Redundant systems** across multiple data centers
* ✅ **Data replication** across availability zones
* ✅ **Automatic failover** mechanisms
* ✅ **DDoS protection** and security
* ✅ **Global edge locations** for fast connectivity

**What This Means for You:**

* 🟢 **Minimal downtime** - AWS infrastructure is enterprise-grade
* 🟢 **Fast message processing** - Low latency worldwide
* 🟢 **Secure connections** - Bank-level encryption
* 🟢 **Automatic recovery** - If one server has issues, traffic automatically routes to healthy servers

{% hint style="success" %}
**Enterprise Infrastructure**: WhatSnap runs on the same infrastructure used by Netflix, Airbnb, and thousands of enterprise companies. Your messages benefit from world-class reliability.
{% endhint %}

***

## How WhatSnap SMS Reliability Works

### Three-Layer Reliability Model

**Layer 1: WhatSnap Cloud Platform (AWS)**

* Handles message routing
* Manages device connections
* Processes workflows
* Stores message logs
* **Reliability: 99.99% uptime**

**Layer 2: Internet Connection**

* Your Android device's internet (WiFi or mobile data)
* Connection to WhatSnap servers
* **Reliability: Depends on your internet provider**

**Layer 3: Carrier Network**

* Your SIM card carrier (Verizon, AT\&T, Vodafone, etc.)
* SMS delivery infrastructure
* **Reliability: Typically 95-99% delivery rate**

### Overall Reliability

**Combined System Reliability:**

* **WhatSnap Platform**: 99.99% uptime
* **Device Connectivity**: 99%+ (with proper setup)
* **Carrier Delivery**: 95-99% (typical SMS delivery rates)

**Result: 95-99% end-to-end reliability** for message delivery when properly configured.

***

## Will your system crash or go down?

**Short Answer: Extremely unlikely.**

### What Makes WhatSnap Reliable

**1. AWS Infrastructure**

* **Redundancy**: Multiple servers in different data centers
* **Automatic Failover**: If one server fails, traffic routes to healthy servers
* **Monitoring**: 24/7 automated monitoring and alerts
* **Maintenance**: AWS handles all hardware and network maintenance

**2. Proven Technology**

* **Mature Protocols**: Uses standard WhatsApp Web and Android SMS protocols
* **No Experimental Tech**: Built on battle-tested messaging infrastructure
* **Millions of Messages**: Processes high volumes daily without issues

**3. Proactive Monitoring**

* **Real-time Alerts**: WhatSnap team notified immediately of any issues
* **Performance Tracking**: Continuous monitoring of system health
* **Quick Response**: Issues resolved typically within minutes

### Historical Uptime

**WhatSnap Track Record:**

* **99.9%+ uptime** since launch
* **Planned maintenance**: Announced 24+ hours in advance
* **Unplanned downtime**: Rare (< 0.1% of time)
* **Average issue resolution**: < 30 minutes

{% hint style="info" %}
**Transparency**: We publish status updates at \[status.whatsnap.ai] during any service interruptions. You can also enable notifications for real-time alerts.
{% endhint %}

***

## Factors That Affect Reliability

While WhatSnap's infrastructure is highly reliable, these factors can impact your specific setup:

### 1. Device Connectivity (Your Control)

**High Impact:**

* ⚠️ **Unstable WiFi/mobile data** → Messages delayed or queued
* ⚠️ **Device powered off** → No messages sent until device back online
* ⚠️ **Battery optimization killing app** → Gateway disconnects

**Solutions:**

* Use stable WiFi or reliable mobile data
* Keep device plugged in 24/7
* Disable battery optimization for WhatSnap Gateway app
* Monitor device status in WhatSnap dashboard

See: [Device Configuration Best Practices](/whatsnap-docs/account-management/sms/sms-installation-setup.md#device-configuration-best-practices)

### 2. Carrier Network (Carrier Control)

**Moderate Impact:**

* ⚠️ **Carrier outages** → Temporary delivery failures (rare)
* ⚠️ **Poor signal strength** → SMS delays
* ⚠️ **Fair use policy violations** → Account restrictions

**Solutions:**

* Choose reliable carriers (see [SIM Plan Recommendations](/whatsnap-docs/account-management/sms/sms-specifications.md#sim-plan-recommendations-by-country))
* Ensure strong signal where device is located
* Follow carrier fair use policies
* Have backup SIM from different carrier

### 3. Android Device (Your Control)

**Low-Moderate Impact:**

* ⚠️ **Low-end devices** → Occasional app crashes
* ⚠️ **Aggressive power management** → App killed in background
* ⚠️ **Software updates** → Temporary restarts

**Solutions:**

* Use [recommended devices](/whatsnap-docs/account-management/sms/sms-specifications.md#recommended-devices) (4 GB RAM+)
* Configure proper power management settings
* Schedule updates during off-hours
* Monitor device health regularly

***

## Reliability Features Built Into WhatSnap

### 1. Message Queuing

**How It Works:**

* Messages that can't be sent immediately are **queued**
* Queue holds messages until device reconnects
* Automatic retry when connection restored

**Example:**

* Device loses WiFi at 2:00 PM
* 5 messages attempted during outage
* Device reconnects at 2:30 PM
* All 5 messages automatically sent within minutes

### 2. Connection Monitoring

**Real-Time Status:**

* WhatSnap dashboard shows device status (Online/Offline)
* Mobile push notifications when device disconnects
* Email alerts for extended downtime (optional)

**Proactive Alerts:**

* Know immediately if device goes offline
* Address issues before customers notice
* Track device uptime history

### 3. Delivery Confirmation

**Message Tracking:**

* Real-time delivery status for every message
* "Sent", "Delivered", "Failed" indicators
* Failed message notifications (optional)

**Benefits:**

* Know if messages aren't delivering
* Quickly troubleshoot issues
* Maintain high quality standards

### 4. Multi-Device Redundancy

**Scale & Backup:**

* Connect multiple Android devices
* Distribute load across devices
* If one device fails, others continue working

**Setup:**

* Configure multiple SIMs in WhatSnap dashboard
* Use workflows to distribute contacts
* Monitor each device independently

See: [Multiple SMS Accounts Guide](/whatsnap-docs/account-management/sms/multiple-sms-accounts.md)

***

## Reliability Comparison: WhatSnap vs. Twilio

| Factor                 | WhatSnap P2P SMS                  | Twilio A2P SMS                      |
| ---------------------- | --------------------------------- | ----------------------------------- |
| **Platform Uptime**    | 99.99% (AWS)                      | 99.95% (SLA)                        |
| **SMS Delivery Rate**  | 95-99% (carrier-dependent)        | 95-99% (carrier-dependent)          |
| **Device Dependency**  | Yes (Android device must be on)   | No (cloud-based)                    |
| **Carrier Dependency** | Yes (your SIM carrier)            | Yes (Twilio's carrier partnerships) |
| **Redundancy Options** | Multi-device setup (your control) | Built-in (Twilio manages)           |
| **Recovery Time**      | Manual (restart device/app)       | Automatic (cloud failover)          |
| **Cost of Redundancy** | Low (add more devices)            | High (enterprise pricing)           |

**Summary:**

* **Twilio**: Slightly higher SLA but at premium cost
* **WhatSnap**: Excellent reliability with manual device management
* **Best Practice**: Use both - WhatSnap for conversational messaging, Twilio for critical transactional

***

## Maximizing Your Reliability

### Essential Setup

**1. Hardware:**

* [ ] Use reliable Android device (4 GB RAM+)
* [ ] Stable power source (plugged in 24/7)
* [ ] UPS backup power (optional but recommended)

**2. Connectivity:**

* [ ] Stable WiFi (primary)
* [ ] Mobile data as backup
* [ ] Signal strength: 3-4 bars minimum

**3. Configuration:**

* [ ] Battery optimization: Disabled
* [ ] App auto-start: Enabled
* [ ] Background restrictions: Disabled
* [ ] Automatic updates: Disabled (manual during off-hours)

See: [Complete Device Configuration Guide](/whatsnap-docs/account-management/sms/sms-installation-setup.md#device-configuration-best-practices)

### Monitoring & Maintenance

**Daily (30 seconds):**

* [ ] Check WhatSnap dashboard for device status
* [ ] Verify "Connected" status in Gateway app

**Weekly (5 minutes):**

* [ ] Review delivery rates (target >95%)
* [ ] Check for pending Android updates
* [ ] Verify battery optimization still disabled

**Monthly (15 minutes):**

* [ ] Full device restart
* [ ] Review message volume and performance
* [ ] Test backup devices (if applicable)
* [ ] Update WhatSnap Gateway app if available

### Backup Strategy

**Recommended Redundancy:**

* **Primary device**: Main SIM, handles bulk of messages
* **Backup device**: Second SIM, standby or handles overflow
* **Different carrier**: Reduces single-point-of-failure risk

**Implementation:**

* Configure both devices in WhatSnap dashboard
* Use workflows to split load 70/30 or 50/50
* If primary fails, manually shift all traffic to backup
* Or: Use backup only during primary maintenance

***

## Troubleshooting Reliability Issues

### Device Frequently Disconnects

**Common Causes:**

* Unstable WiFi
* Battery optimization killing app
* Low device memory
* Manufacturer restrictions (Xiaomi, Huawei)

**Solutions**: See [Troubleshooting Guide](/whatsnap-docs/account-management/sms/troubleshooting.md)

### Messages Delayed or Queued

**Common Causes:**

* Device offline temporarily
* Carrier network congestion
* High volume exceeding carrier limits

**Solutions**:

* Check device connection
* Reduce sending rate
* Add more devices for distribution

### Low Delivery Rate (<95%)

**Common Causes:**

* Spam-like content
* Sending too fast
* Carrier flagging account
* Invalid phone numbers

**Solutions**: See [Database Reactivations - Avoiding Blocks](broken://pages/1NpMBh9RXUeVt9ElFXvj#avoiding-carrier-blocks)

***

## Summary: WhatSnap Reliability

**Infrastructure:**

* ✅ 99.99% uptime (AWS cloud platform)
* ✅ Redundant systems and automatic failover
* ✅ Enterprise-grade security and monitoring

**Your Responsibility:**

* ⚙️ Keep device online with stable internet
* ⚙️ Proper device configuration
* ⚙️ Regular monitoring and maintenance

**Result:**

* 📊 **95-99% end-to-end reliability** when properly configured
* 📊 **Better than traditional SMS** in most cases
* 📊 **Comparable to Twilio** for P2P messaging use cases

{% hint style="success" %}
**Bottom Line**: WhatSnap SMS is highly reliable for business use. With proper device setup and monitoring, you can achieve 99%+ message delivery rates consistently.
{% endhint %}

***

## Related Resources

* [Device Specifications](/whatsnap-docs/account-management/sms/sms-specifications.md)
* [Installation & Configuration](/whatsnap-docs/account-management/sms/sms-installation-setup.md)
* [Troubleshooting](/whatsnap-docs/account-management/sms/troubleshooting.md)
* [Multiple Devices for Redundancy](/whatsnap-docs/account-management/sms/multiple-sms-accounts.md)

***

**Reliability concerns?** Contact support at <support@whatsnap.ai> to discuss your specific use case and setup recommendations.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://whatsnap.gitbook.io/whatsnap-docs/faq/sms/reliability.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.