· By smsroute editorial · 8 min read

Reach all 13 million Israeli subscribers via Cellcom (37%), Partner / Orange Israel (35%), Golan / Vodafone (18%), and Rami Levi Mobile (10%). Pay with Bitcoin, USDT, Ethereum, or Solana. No KYC, no ID, no corporate docs at signup. 155 ms median latency, 98.7% delivery success. MoC sender-ID registration in 3–5 business days.

Why Hebrew SMS Segments Cut Your Israel Character Budget in Half

Hebrew text triggers UCS-2 encoding, a universal standard for non-ASCII character sets. While English SMS (GSM-7 encoding) packs 160 characters per segment, Hebrew shrinks this to just 70 characters per segment. A 150-character message in Hebrew requires two full SMS segments instead of one.

Concrete example: The Hebrew phrase "שלום, זה הודעת אימות שלך: 123456" (Hello, this is your verification code: 123456) spans 35 Hebrew characters plus punctuation and digits. In GSM-7 (English only), this fits comfortably in one segment. In UCS-2, the same message in Hebrew consumes one full segment, leaving 35 unused characters. If your campaign includes both Hebrew and English variants, budget for 2–3× the segment volume of an English-only campaign.

smsroute.cc charges per segment, so Hebrew messaging incurs higher per-campaign costs. However, our $0.0280 per-segment rate remains 60% lower than Twilio's $0.0700. Plan your messaging architecture accordingly: for customer acquisition, consider dual-language templates (English to reduce segments, Hebrew for legal compliance). For transactional messages (OTP, receipts), Hebrew is typically required by Israeli law, so budget the UCS-2 overhead.

Mobile Operators and Market Coverage

Israel's telecom market is dominated by four nationwide carriers, all integrated into smsroute.cc's network:

Cellcom Israel

37% market share — ~5.0 million subscribers

Largest operator. Direct interconnect with smsroute.cc. Supports all sender-ID types after MoC approval.

Partner (Orange Israel)

35% market share — ~4.6 million subscribers

Second-largest operator. MoC-registered sender IDs route without delay. Excellent interconnect reliability.

Golan (Vodafone Israel)

18% market share — ~2.3 million subscribers

Third-largest operator. Full A2P support via smsroute.cc. No operator-specific sender-ID pre-approval required beyond MoC registration.

Rami Levi Mobile

10% market share — ~1.3 million subscribers

Smallest carrier. Uses MVNO routing via major operators. Fully compatible with smsroute.cc A2P. Full coverage included in our price.

Combined, these four operators cover 100% of Israel's 13 million mobile subscribers. smsroute.cc maintains active interconnects with all four and monitors per-operator delivery metrics in real time. If one operator experiences temporary degradation, traffic is automatically rerouted through alternatives to maintain 98.7% success rate.

How to Send SMS to Israel in 3 Steps

Step 1: Create a free smsroute.cc account. Visit https://smsroute.cc, click Sign Up, and enter a username and password. No email verification, no phone number, no government ID required. You will receive API credentials (API key and API secret) immediately. Keep these secure.

Step 2: Top up your account with cryptocurrency. Send Bitcoin, USDT (TRC-20 preferred), Ethereum, Litecoin, Monero, or Solana to your unique smsroute.cc wallet address. Minimum deposit is $5 USD equivalent. Once the blockchain confirms your transaction (typically 1–3 confirmations), your SMS credit is live in your account. No middleman, no bank, no KYC.

Step 3: Send SMS to +972 E.164 numbers. Use the smsroute.cc REST API or Python SDK. Here are examples:

cURL example:

Python example:

The API returns a message_id and status immediately. Messages are delivered within 320 ms (95th percentile). Your dashboard logs all delivery confirmations, bounce codes, and operator-level latency metrics in real time.

Important: Always format recipient numbers in E.164 format: +972 country code, followed by the mobile prefix (5) and 8 digits. Do not include leading zeros. Example: +972541234567, not 0541234567.

Pricing Comparison: smsroute.cc vs. Competitors

smsroute.cc undercuts all major SMS platforms on per-segment pricing. Here's a real-world comparison:

Provider Price per SMS (USD) vs. smsroute
smsroute $0.0280 best price
Twilio$0.0452baseline
MessageBird$0.038427% more
Plivo$0.037125% more
Telnyx$0.033917% more

For a Hebrew-heavy campaign sending 10,000 messages (averaging 2.2 segments per message due to UCS-2 encoding = 22,000 total segments):

  • smsroute.cc: 22,000 × $0.0280 = $616
  • Twilio: 22,000 × $0.0700 = $1,540 (150% more)
  • Vonage: 22,000 × $0.0595 = $1,309 (113% more)

At scale, smsroute.cc's crypto-only model eliminates payment-processor fees (typically 2–3% on card transactions) and removes KYC delays that can add days to account setup. Combined with the lowest per-segment rate, total cost of ownership is 50–60% below traditional platforms.

Latency and Delivery Guarantees

smsroute.cc delivers to Israel with consistent, measurable performance:

  • Median latency (p50): 155 milliseconds
  • 95th-percentile latency (p95): 320 milliseconds
  • Delivery success rate: 98.7%
  • Uptime: 99.9% (monitored 24/7)
  • Tier-1 operator delivery: 99% of successful deliveries reach recipient handset within first attempt

These figures are measured across all four major Israeli operators and updated daily. The median latency of 155 ms is suitable for real-time OTP use cases and customer notifications. The p95 of 320 ms accounts for international routing, operator congestion during peak hours (20:00–23:00 IST), and seasonal load spikes (holidays, Black Friday, etc.).

The 98.7% delivery success rate reflects the combination of direct operator interconnects, intelligent routing fallback, and real-time delivery confirmation. The remaining 1.3% of failures are typically due to invalid numbers, recipient device offline, or operator-side blocks (e.g., DND lists). smsroute.cc's dashboard displays per-operator delivery breakdowns, bounce codes, and detailed logs for every message.

99.9% uptime means smsroute.cc's infrastructure experiences only ~43 minutes of downtime per month. This is backed by redundant data centers, automated failover, and real-time monitoring. If you encounter issues, our API status page (https://status.smsroute.cc) is always current.

Consent Framework and Data Protection Regulations in Israel

Israel's Ministry of Communications (MoC, https://moc.gov.il/) enforces the Data Protection Law (1981, as amended in 2021) and subsidiary SMS regulations that govern A2P messaging. The framework is strict: explicit opt-in consent is required before sending any marketing SMS.

Opt-in requirements: You must obtain documented, affirmative consent from the recipient before sending promotional content. The consent must specify the sender identity, the types of messages, and the frequency. Soft opt-in (implicit consent derived from a prior business relationship) is permitted for transactional messages (OTPs, order confirmations, account alerts), but not for marketing.

Opt-out mechanism: Every marketing SMS must include a clear, easy opt-out method—typically a reply-to-number or keyword-based unsubscribe. You must honor opt-out requests within 24 hours. The MoC tracks enforcement action against senders who fail to respect opt-out requests; fines are typically in the five- to seven-figure range for systematic violations.

SIM registration and population registry: Israeli carriers are mandated to register all SIM cards against the national population registry. This integration enables regulators to cross-reference SMS recipient identities and verify consent records. If a recipient disputes having consented, the MoC may request your consent logs. Document everything.

smsroute.cc does not store or enforce consent compliance on your behalf. You are responsible for maintaining auditable consent records and respecting opt-out requests. Use smsroute.cc's webhook API to log delivery status and implement your own opt-out list management.

Frequently Asked Questions

Why does Hebrew text use more SMS segments than English?

Hebrew text triggers UCS-2 encoding, which supports the full Unicode character set. UCS-2 limits each SMS segment to 70 characters instead of the 160 characters available in GSM-7 (ASCII-based). A message requiring 150 Hebrew characters will consume two full segments instead of one. Budget conservatively: expect 2–3× segment consumption when using Hebrew. Our pricing model charges per segment, so Hebrew campaigns incur higher volume costs. This is a technical constraint of SMS standards, not a limitation of smsroute.cc.

What consent framework applies to SMS marketing in Israel?

Israel's Ministry of Communications (MoC) enforces the Data Protection Law (1981, amended 2021) and subsidiary SMS regulations. Explicit opt-in is required before sending marketing SMS to any recipient. Transactional messages (OTP, order confirmations, account alerts) may use soft opt-in if the recipient provided a phone number in a business context, but marketing requires documented consent. All recipients must be able to opt out via reply or unsubscribe mechanism. The MoC publishes enforcement actions against major senders who violate these rules; fines are typically in the five- to seven-figure range for systematic violations.

How do I register an alphanumeric sender ID in Israel?

Alphanumeric sender IDs (e.g., 'MyBrand') require dual approval: first from the MoC and second from the recipient's mobile operator. The process takes 3–5 business days. You must provide proof of Israeli company registration and the sender ID text in both Hebrew and English (if using non-Hebrew characters, English is acceptable). Sender IDs are capped at 11 characters. smsroute.cc handles the registration workflow for you; include your company registration number and desired sender ID at account setup. Numeric-only sender IDs (short codes) involve additional operator coordination and are typically reserved for high-volume enterprise senders.

What are the quiet hours for marketing SMS in Israel?

Marketing SMS in Israel may only be sent between 08:00 and 20:00 Israel Standard Time (IST) on Sunday through Thursday. Friday quiet hours end at 16:00 IST. No marketing SMS may be sent on Saturday (Shabbat) or on Jewish holidays declared by the MoC. Transactional and time-sensitive messages (OTP, delivery alerts, security notifications) are exempt from quiet-hour restrictions. Violating quiet hours can trigger operator throttling or sender-ID suspension. Use smsroute.cc's scheduling API to enforce these windows automatically.

Which mobile operators have the largest subscriber base in Israel?

Cellcom Israel leads with approximately 37% market share (5.0 million subscribers), followed by Partner (Orange Israel) at 35% (4.6 million). Golan (Vodafone Israel) holds 18% (2.3 million), and Rami Levi Mobile accounts for 10% (1.3 million). Combined, these four operators cover all 13 million mobile subscribers. smsroute.cc maintains direct interconnects with all four, ensuring 98.7% delivery success. Each operator enforces identical MoC regulations, so sender-ID approval applies across the network.

What is the average SMS delivery latency to Israel?

smsroute.cc achieves a median (p50) latency of 155 milliseconds to Israeli numbers and a 95th-percentile (p95) latency of 320 milliseconds. These figures reflect real-world performance across all four major operators and account for network congestion, international routing, and operator processing delays. For time-sensitive OTP or alerts, this latency is suitable for real-time user experience. Latency may vary during peak hours (20:00–23:00 IST) or during holiday periods.

Do I need KYC or corporate documentation to sign up for smsroute.cc?

No. smsroute.cc requires no phone verification, no government ID, and no corporate documents at account creation. You create a username, set a password, and begin topping up immediately using cryptocurrency. However, to register a custom alphanumeric sender ID with the MoC (required for branded marketing campaigns), you must provide proof of Israeli company registration during the sender-ID application phase. Transactional senders can use numeric or shortcode-style identifiers without corporate documentation.

What cryptocurrencies does smsroute.cc accept for SMS top-ups?

smsroute.cc accepts Bitcoin, USDT (TRC-20 preferred), Ethereum, Litecoin, Monero, and Solana. Payments are processed on-chain with no intermediary or custodian. The minimum top-up is $5 USD equivalent. We do not accept credit cards, SEPA transfers, or bank wires. Once your wallet receives confirmation (typically 1–3 blockchain confirmations), your SMS credit is available immediately.

Related

Features SMS API Pricing API Docs Blog 
curl -X POST https://api.smsroute.cc/messages \
  -H "Authorization: Bearer $SMSROUTE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+9725551234567",
    "from": "smsroute",
    "text": "Your verification code is 384921"
  }'
import os, requests

resp = requests.post(
    "https://api.smsroute.cc/messages",
    headers={"Authorization": f"Bearer {os.environ['SMSROUTE_API_KEY']}"},
    json={
        "to": "+9725551234567",
        "from": "smsroute",
        "text": "Your verification code is 384921",
    },
    timeout=10,
)
resp.raise_for_status()
print(resp.json())
import fetch from "node-fetch";

const apiKey = process.env.SMSROUTE_API_KEY;

const res = await fetch("https://api.smsroute.cc/messages", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${apiKey}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    to: "+9725551234567",
    from: "smsroute",
    text: "Your verification code is 384921",
  }),
});

console.log(await res.json());
<?php
$apiKey = getenv('SMSROUTE_API_KEY');

$payload = json_encode([
    'to'   => '+9725551234567',
    'from' => 'smsroute',
    'text' => 'Your verification code is 384921',
], JSON_UNESCAPED_UNICODE);

$ch = curl_init('https://api.smsroute.cc/messages');
curl_setopt_array($ch, [
    CURLOPT_POST => true,
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER => [
        'Authorization: Bearer ' . $apiKey,
        'Content-Type: application/json',
    ],
    CURLOPT_POSTFIELDS => $payload,
]);

echo curl_exec($ch);
curl_close($ch);
package main

import (
    "bytes"
    "encoding/json"
    "fmt"
    "io"
    "net/http"
    "os"
)

func main() {
    payload, _ := json.Marshal(map[string]string{
        "to":   "+9725551234567",
        "from": "smsroute",
        "text": "Your verification code is 384921",
    })

    req, _ := http.NewRequest("POST",
        "https://api.smsroute.cc/messages",
        bytes.NewBuffer(payload))
    req.Header.Set("Authorization", "Bearer "+os.Getenv("SMSROUTE_API_KEY"))
    req.Header.Set("Content-Type", "application/json")

    resp, err := http.DefaultClient.Do(req)
    if err != nil { panic(err) }
    defer resp.Body.Close()

    body, _ := io.ReadAll(resp.Body)
    fmt.Println(string(body))
}

Pricing Comparison: smsroute.cc vs. Competitors

smsroute.cc undercuts all major SMS platforms on per-segment pricing. Here's a real-world comparison:

Provider Price per SMS (USD) vs. smsroute
smsroute $0.0280 best price
Twilio$0.0452baseline
MessageBird$0.038427% more
Plivo$0.037125% more
Telnyx$0.033917% more

For a Hebrew-heavy campaign sending 10,000 messages (averaging 2.2 segments per message due to UCS-2 encoding = 22,000 total segments):

  • smsroute.cc: 22,000 × $0.0280 = $616
  • Twilio: 22,000 × $0.0700 = $1,540 (150% more)
  • Vonage: 22,000 × $0.0595 = $1,309 (113% more)

At scale, smsroute.cc's crypto-only model eliminates payment-processor fees (typically 2–3% on card transactions) and removes KYC delays that can add days to account setup. Combined with the lowest per-segment rate, total cost of ownership is 50–60% below traditional platforms.

Latency and Delivery Guarantees

smsroute.cc delivers to Israel with consistent, measurable performance:

  • Median latency (p50): 155 milliseconds
  • 95th-percentile latency (p95): 320 milliseconds
  • Delivery success rate: 98.7%
  • Uptime: 99.9% (monitored 24/7)
  • Tier-1 operator delivery: 99% of successful deliveries reach recipient handset within first attempt

These figures are measured across all four major Israeli operators and updated daily. The median latency of 155 ms is suitable for real-time OTP use cases and customer notifications. The p95 of 320 ms accounts for international routing, operator congestion during peak hours (20:00–23:00 IST), and seasonal load spikes (holidays, Black Friday, etc.).

The 98.7% delivery success rate reflects the combination of direct operator interconnects, intelligent routing fallback, and real-time delivery confirmation. The remaining 1.3% of failures are typically due to invalid numbers, recipient device offline, or operator-side blocks (e.g., DND lists). smsroute.cc's dashboard displays per-operator delivery breakdowns, bounce codes, and detailed logs for every message.

99.9% uptime means smsroute.cc's infrastructure experiences only ~43 minutes of downtime per month. This is backed by redundant data centers, automated failover, and real-time monitoring. If you encounter issues, our API status page (https://status.smsroute.cc) is always current.

Consent Framework and Data Protection Regulations in Israel

Israel's Ministry of Communications (MoC, https://moc.gov.il/) enforces the Data Protection Law (1981, as amended in 2021) and subsidiary SMS regulations that govern A2P messaging. The framework is strict: explicit opt-in consent is required before sending any marketing SMS.

Opt-in requirements: You must obtain documented, affirmative consent from the recipient before sending promotional content. The consent must specify the sender identity, the types of messages, and the frequency. Soft opt-in (implicit consent derived from a prior business relationship) is permitted for transactional messages (OTPs, order confirmations, account alerts), but not for marketing.

Opt-out mechanism: Every marketing SMS must include a clear, easy opt-out method—typically a reply-to-number or keyword-based unsubscribe. You must honor opt-out requests within 24 hours. The MoC tracks enforcement action against senders who fail to respect opt-out requests; fines are typically in the five- to seven-figure range for systematic violations.

SIM registration and population registry: Israeli carriers are mandated to register all SIM cards against the national population registry. This integration enables regulators to cross-reference SMS recipient identities and verify consent records. If a recipient disputes having consented, the MoC may request your consent logs. Document everything.

smsroute.cc does not store or enforce consent compliance on your behalf. You are responsible for maintaining auditable consent records and respecting opt-out requests. Use smsroute.cc's webhook API to log delivery status and implement your own opt-out list management.

Frequently Asked Questions

Why does Hebrew text use more SMS segments than English?

Hebrew text triggers UCS-2 encoding, which supports the full Unicode character set. UCS-2 limits each SMS segment to 70 characters instead of the 160 characters available in GSM-7 (ASCII-based). A message requiring 150 Hebrew characters will consume two full segments instead of one. Budget conservatively: expect 2–3× segment consumption when using Hebrew. Our pricing model charges per segment, so Hebrew campaigns incur higher volume costs. This is a technical constraint of SMS standards, not a limitation of smsroute.cc.

What consent framework applies to SMS marketing in Israel?

Israel's Ministry of Communications (MoC) enforces the Data Protection Law (1981, amended 2021) and subsidiary SMS regulations. Explicit opt-in is required before sending marketing SMS to any recipient. Transactional messages (OTP, order confirmations, account alerts) may use soft opt-in if the recipient provided a phone number in a business context, but marketing requires documented consent. All recipients must be able to opt out via reply or unsubscribe mechanism. The MoC publishes enforcement actions against major senders who violate these rules; fines are typically in the five- to seven-figure range for systematic violations.

How do I register an alphanumeric sender ID in Israel?

Alphanumeric sender IDs (e.g., 'MyBrand') require dual approval: first from the MoC and second from the recipient's mobile operator. The process takes 3–5 business days. You must provide proof of Israeli company registration and the sender ID text in both Hebrew and English (if using non-Hebrew characters, English is acceptable). Sender IDs are capped at 11 characters. smsroute.cc handles the registration workflow for you; include your company registration number and desired sender ID at account setup. Numeric-only sender IDs (short codes) involve additional operator coordination and are typically reserved for high-volume enterprise senders.

What are the quiet hours for marketing SMS in Israel?

Marketing SMS in Israel may only be sent between 08:00 and 20:00 Israel Standard Time (IST) on Sunday through Thursday. Friday quiet hours end at 16:00 IST. No marketing SMS may be sent on Saturday (Shabbat) or on Jewish holidays declared by the MoC. Transactional and time-sensitive messages (OTP, delivery alerts, security notifications) are exempt from quiet-hour restrictions. Violating quiet hours can trigger operator throttling or sender-ID suspension. Use smsroute.cc's scheduling API to enforce these windows automatically.

Which mobile operators have the largest subscriber base in Israel?

Cellcom Israel leads with approximately 37% market share (5.0 million subscribers), followed by Partner (Orange Israel) at 35% (4.6 million). Golan (Vodafone Israel) holds 18% (2.3 million), and Rami Levi Mobile accounts for 10% (1.3 million). Combined, these four operators cover all 13 million mobile subscribers. smsroute.cc maintains direct interconnects with all four, ensuring 98.7% delivery success. Each operator enforces identical MoC regulations, so sender-ID approval applies across the network.

What is the average SMS delivery latency to Israel?

smsroute.cc achieves a median (p50) latency of 155 milliseconds to Israeli numbers and a 95th-percentile (p95) latency of 320 milliseconds. These figures reflect real-world performance across all four major operators and account for network congestion, international routing, and operator processing delays. For time-sensitive OTP or alerts, this latency is suitable for real-time user experience. Latency may vary during peak hours (20:00–23:00 IST) or during holiday periods.

Do I need KYC or corporate documentation to sign up for smsroute.cc?

No. smsroute.cc requires no phone verification, no government ID, and no corporate documents at account creation. You create a username, set a password, and begin topping up immediately using cryptocurrency. However, to register a custom alphanumeric sender ID with the MoC (required for branded marketing campaigns), you must provide proof of Israeli company registration during the sender-ID application phase. Transactional senders can use numeric or shortcode-style identifiers without corporate documentation.

What cryptocurrencies does smsroute.cc accept for SMS top-ups?

smsroute.cc accepts Bitcoin, USDT (TRC-20 preferred), Ethereum, Litecoin, Monero, and Solana. Payments are processed on-chain with no intermediary or custodian. The minimum top-up is $5 USD equivalent. We do not accept credit cards, SEPA transfers, or bank wires. Once your wallet receives confirmation (typically 1–3 blockchain confirmations), your SMS credit is available immediately.

Related

Features SMS API Pricing API Docs Blog