Phone as Gateway: How to Estimate Monthly Operator Cost

If finance only sees the platform invoice, prepaid top-ups will look like “mystery ops spend.” Two ledgers — operator airtime and devices+volume — or you will mis-cut the wrong budget.

Estimating monthly operator cost for an android phone as sms gateway prevents the finance surprise where platform invoices look predictable but prepaid packs drain twice a week. Operator SMS airtime and gateway service fees live on two ledgers — conflating them produces wrong ROI comparisons to cloud APIs and wrong recharge schedules for ops. This spoke covers only operator cost estimation: volume math, rate discovery, worksheets, bulk vs OTP scenarios, and the HowTo sequence finance and engineering can share. Hub context: How to use an Android phone as an SMS gateway.

Service pricing is based on device count and total SMS sent through the gateway. You need a working Android phone with a SIM and SMS credit from your mobile operator. Operator message costs are yours—we do not sell carrier SMS balance. Platform pricing on device and SMS volume pricing (Priced by devices and SMS send volume. You use your own phone and operator SMS credit.): free tier 300 SMS lifetime on one device; paid from $19/month with higher caps. That is ledger B. Ledger A is whatever your operator deducts per SMS on each SIM — we do not sell it. Questions about billing vocabulary: SMS Gateway Questions.

E-commerce teams comparing notification costs often read Shopify API documentation for programmatic order messaging patterns — useful volume proxy, not a price quote. Your gateway path swaps aggregator per-message fees for operator airtime you model here.

Why estimate operator cost

Without operator estimates, teams size gateway tier from platform SMS allowance alone — then OTP stops when prepaid hits zero while dashboard quota remains. Finance approves Starter tier ($19/month) but ops never budgets $800/month operator bulk on two SIMs. Estimation aligns procurement, recharge runbooks, and tier upgrades.

Estimation also informs build vs buy. Comparing operator ledger + device ops + service tier to aggregator quotes requires both sides complete — cloud APIs hide SIM ops; Android gateway hides per-SMS operator math if you skip this worksheet.

Two ledgers: operator vs service

Never add ledger A and B into one “SMS cost” cell without labels — executives will mis-cut operator recharge budget.

Glossary

Operator SMS airtime — carrier-side credit consumed per transmitted SMS PDU.

Platform send volume — messages metered through gateway service for tier billing.

Peak day — highest 24h send count in lookback window; drives prepaid pack sizing.

Retry factor — multiplier for OTP resends and failed attempts in volume math.

Headroom — 15–25% buffer on estimates for campaigns and incidents.

Inputs you need

• 90-day send logs split OTP / transactional / bulk
• Peak day and peak hour per class
• ICCID list mapped to device_id
• Operator plan type and latest pack receipt
• Current gateway tier from Pricing
• Planned campaign calendar next quarter

Volume math

Conservative monthly SMS = peak daily sends × retry factor × days in month. Example OTP: 2,400 peak × 1.3 × 30 = 93,600 SMS. Add bulk campaigns as separate rows — do not average bulk into daily OTP peak unless they truly share the same SIM and hour.

For steady transactional traffic (no strong peak), use average daily × 30 with lower retry factor (1.1). Document which method you used — auditors ask.

Per-SIM rate discovery

Prepaid: divide pack price by bundled SMS count. Postpaid: itemized bill ÷ SMS count on line. “Unlimited” plans: derive equivalent from largest available pack or historical bill before FUP throttling. Record effective date — operators change packs silently.

HowTo: estimate monthly cost

The HowTo schema above mirrors these steps. Expand with your ICCIDs in the worksheet below.

1. Export 90-day send volume by class. Split OTP, transactional, and bulk from analytics or gateway reports. Note peak day and peak hour per class.
2. Document each SIM plan. Record operator, prepaid/postpaid, bundle size, expiry, stated per-SMS or pack price, ICCID, and device_id mapping.
3. Compute per-SMS operator rate. Derive rate from latest pack purchase or bill line. Keep conservative and note effective date.
4. Calculate monthly operator SMS spend. Monthly SMS count × rate, plus plan fixed fees. Add 15–25% headroom for retries and campaigns.
5. Add platform service tier cost. From Pricing, select tier by device count and platform SMS volume — do not merge into operator line.
6. Publish two-ledger summary. Finance slide: Operator airtime $X, Gateway service $Y, Data $Z. Review quarterly.

Monthly worksheet

Duplicate worksheet tab per ICCID, then sum operator subtotals. Add one service tier row for platform — 5 tiers available on Pricing; pick by device count and platform volume, not operator SMS.

Bulk campaign scenarios

Bulk dominates operator spend. Model each campaign: list size × segments × frequency. Link Bulk SMS use case for consent and pacing — operator cost scales with accepted sends, not with CRM audience size alone (opt-outs reduce count).

Example: 50,000 recipients × 2 campaigns/month × $0.008 = $800 operator airtime before plan fees — plus gateway tier must cover 100,000 platform-metered sends on ledger B.

OTP scenarios

OTP volume is smaller but recharge gaps are catastrophic. Model peak login day after incident news (retry factor 1.5). Separate SIM from bulk when estimating — shared SIM means shared operator balance depletion risk.

India geo note

India adds DLT template and entity costs outside simple per-SMS multiplication. Read SMS gateway India for regulatory line items; amortize annual registration into monthly operator ledger if required by finance policy.

Multi-device fleets

Each phone = one operator budget minimum. Two phones × $900 operator each + one Silver service tier is correct; do not multiply platform device fee by operator rate. Device fee is ledger B; airtime is ledger A per ICCID.

Mobile data line item

Gateway app sync over cellular consumes megabytes, not SMS packs. Budget separately on ledger C — typically small but non-zero when shelf phone has no Wi-Fi.

Contrast cloud APIs

Aggregator quotes combine transport into per-message fee. Your model splits operator A + service B + ops labor. Shopify-style notification volume from Shopify dev docs helps size message count; compare fairly by adding staff time for SIM recharge and device uptime.

Estimation failure modes

• Using monthly average on spiky bulk — under-budget recharge
• Ignoring retry factor on OTP — mid-month pack exhaustion
• Treating platform free tier as free operator SMS — sends fail at carrier
• One rate for dual-SIM with different pack types — wrong ICCID math
• Forever “unlimited” assumption — FUP throttling without cost signal

Estimation checklist

• Peak-day volume documented per traffic class
• Retry multiplier applied (typically 1.2–1.5× for OTP)
• Per-SMS operator rate sourced from receipt or bill
• Each ICCID has separate row in worksheet
• Prepaid pack expiry dates on calendar
• Platform tier matched on Pricing page
• Platform SMS volume within tier allowance (or upgrade path if near cap)
• Mobile data budget per device if no Wi-Fi
• India/other geo surcharges researched if applicable
• Bulk campaign month flagged separately from steady OTP
• Headroom line (15–25%) explicit
• Two-ledger slide reviewed by finance
• Comparison to prior month variance explained
• Recharge owner assigned for prepaid
• Quarterly review date scheduled

Common mistakes

• Single “SMS budget” line in CFO deck — hides operator recharge ownership
• Estimating from competitor blog rates in another country
• Forgetting gateway tier upgrade when device count rises
• Skipping headroom — finance treats estimate as hard cap

Worked example: mixed OTP and bulk

A logistics SaaS sends 1,800 OTP/day peak (×1.25 retry ×30 = 67,500 SMS) and one monthly 80,000-row bulk on the same postpaid SIM at $0.006/SMS. Operator: (67,500 + 80,000) × $0.006 = $885 + $20 plan fee = $905. Gateway: 147,500 platform sends → Gold tier $79. Data: $8. Total $992/mo vs underestimating operator at $400 because only OTP peak was modeled.

Prepaid recharge calendar

From monthly operator subtotal, divide by preferred pack size to get top-ups per month. Put ICCID-specific recharge dates in ops calendar before production — estimation without calendar is spreadsheet fiction.

Finance handoff slide template

• Ledger A operator: $____ / month (ICCID breakdown attached)
• Ledger B gateway service: $____ / month (tier name)
• Ledger C data: $____ / month
• Assumptions: peak day ____, retry ____, rate effective ____
• Review date: quarterly

Monthly variance review

Compare actual operator receipts to estimate. Variance >20% triggers worksheet revisit — usually new bulk campaign, retry spike, or wrong rate. Feed variance into SMS gateway FAQ and definitions FAQ updates if customers repeat same misunderstanding.

Seasonality adjustments

Retail customers: multiply November–December peak by historical analytics ratio. Tax season fintech: March OTP peak. Estimation is not flat — note seasonal multipliers in worksheet footnotes.

OTP operator cost in detail

OTP economics look cheap until retry storms. Model login attempts, password reset cascades, and SMS resend button abuse. If analytics show 1.8 sends per successful login, multiply peak logins by 1.8 before rate multiplication. Fraud spikes during credential stuffing raise operator cost without raising successful login count — watch anomaly weeks and annotate worksheet.

Separate OTP SIM from bulk SIM in worksheet tabs. Shared SIM merges peaks — finance underestimates recharge when bulk campaign week overlaps product launch OTP spike. If sharing is mandatory, add explicit overlap week row with summed peak hours.

OTP operator cost is small per message but zero tolerance for balance gaps — budget wider prepaid headroom (30%+) on OTP ICCID than bulk ICCID. Postpaid OTP lines still need spend cap headroom above modeled peak.

Bulk operator cost in detail

Bulk cost = recipients × messages × operator rate, minus hard bounces if your list hygiene is mature. For conservative finance, use gross list size. Link pacing from Bulk SMS: spreading sends across days changes peak-hour operator load but not monthly total SMS — monthly total drives airtime, peak hour drives throttle risk.

Promotional SMS rates differ from transactional on some operators — bulk worksheet should use promotional rate when applicable. Using transactional rate underestimates marketing campaign operator spend by 20–40% in some markets.

Multi-segment Unicode messages bill as multiple SMS PDUs on many operators — count segments in gateway logs when estimating. A “160 character” spreadsheet assumes GSM-7; emoji templates double PDU count and operator cost.

Matching gateway tier to volume

Ledger B tier selection uses platform-metered send count and device count from device and SMS volume pricing. Common error: picking tier from operator spend. A customer may spend $2,000 on operator bulk but fit Starter platform tier if device count is one and platform volume under allowance — or may need Gold for platform volume while operator stays flat. Two ledgers, two decisions.

Free tier 300 SMS lifetime suits proof-of-concept; operator cost still accrues per send on SIM. Finance POC budget must include small prepaid packs — platform free does not mean operator free.

India operator cost beyond per-SMS

India DLT entity registration, template registration, and scrubbing fees belong in operator/regulatory bucket per India geo guide. Amortize annual entity cost ÷ 12 into monthly operator ledger for fully loaded comparison to aggregators. Per-SMS DLT scrubbing may appear on operator invoice separately from PDU count — parse bill line items, do not assume single rate.

Promotional vs transactional route pricing in India affects bulk vs OTP worksheet rates — same billing type (prepaid/postpaid) but different PDU tariffs. Split rows when one SIM sends both classes (discouraged operationally).

Prepaid pack sizing from estimate

Once monthly operator SMS subtotal is computed, divide by pack SMS count to get packs per month. Round up. Example: 93,600 SMS/month ÷ 10,000 SMS pack = 9.36 → buy ten packs; set calendar alert mid-month for tenth pack if volume trends high. Prepaid estimation without pack calendar fails ops — finance approves monthly dollars, ops executes recharge cadence.

Pack expiry shorter than month length needs multiple smaller packs — effective rate may rise vs one large pack. Worksheet footnote: “effective rate assumes 30-day pack; 7-day promo packs increase ops touches.”

Postpaid invoice reconciliation

Postpaid estimation starts from quoted business plan: fixed fee + included SMS + overage rate. Compare actual bill monthly; variance drives worksheet update. Spend cap behaves like prepaid hard stop — model cap as maximum operator spend, not unlimited.

Finance AP needs operator invoice separate from gateway platform invoice — different vendors, different approval chains. Combined “telecom” bucket hides gateway tier upgrades needed when device count rises.

Device and shelf cost (TCO note)

Operator + service + data is not total cost of ownership. Android handset, shelf, UPS, and ops labor belong in separate TCO slide for build-vs-buy vs Shopify/Twilio paths. This spoke stays strict on operator airtime estimation — but finance comparing to Shopify API notification fees should add handset amortization (~$5–15/month per spare phone over 24 months) in another row.

Using the Questions hub in estimates

When customers repeat “I thought SMS was included in my plan,” point to SMS gateway FAQ and definitions FAQ and attach two-ledger worksheet. Support macros grounded in estimation reduce refund churn. Sales should send worksheet template during purchase evaluation — not after first recharge surprise.

Scenario: solo dev on free tier

Developer sends 400 SMS/month OTP testing on one prepaid SIM: 400 × $0.01 operator = $4/mo airtime + $0 gateway free tier + $0 Wi-Fi data. Total telecom $4 — not $0 because platform free ≠ operator free. Worksheet prevents “free gateway” expectation at finance review.

Scenario: three-phone fleet

Three postpaid SIMs each $600 operator subtotal = $1,800 ledger A. Gold platform tier $79 ledger B for three devices and 400k platform sends. Data $30. Total $1,909. Error: multiplying $600 × 3 into “SMS cost” without labeling operator vs $79 service — CFO sees $1,800 and kills project ignoring $79 platform value.

Aggregator comparison worksheet row

Add optional row: Twilio/aggregator quote for same volume (transport only). Android path: operator A + service B + ops labor. Aggregator path: per-message quote + number rental. Fair comparison includes compliance work you already do on BYO-SIM (10DLC, DLT) vs included in aggregator quote — annotate assumptions footnote.

Audit trail for estimates

Store worksheet version, rate source receipt PDF hash, analytics export date, and author. When operator raises rates mid-quarter, fork worksheet v2 — do not silently edit v1. Audit trail matters for enterprise customers with annual telecom review.

Metrics to feed estimation

Pull monthly sends from gateway dashboard export; cross-check with application analytics (successful OTP count). Discrepancy indicates failed sends still metered on platform or retries not logged in app — estimation should use gateway meter for ledger B and higher of app vs gateway for ledger A conservative case.

Recharge owner RACI

Document who recharges prepaid when estimate says $900/month operator — finance approves budget, ops executes recharge, engineering not default owner. RACI in worksheet footer prevents OTP outage while teams debate responsibility.

Review cadence

Monthly: actual vs estimate variance. Quarterly: full worksheet rebuild. Event-driven: new bulk use case, new device, carrier plan change, pricing tier upgrade on platform. Hub article cornerstone links estimation in onboarding checklist for new gateway adopters.

Transactional SMS cost row

Transactional traffic — order shipped, appointment confirmed — sits between OTP and bulk in volume and urgency. Model as average daily × 30 if no sharp peak, retry factor 1.05–1.1. If transactional shares SIM with bulk, use combined peak hour for throttle planning but separate worksheet rows for finance visibility. Link bulk use case when transactional is really marketing in disguise — consent class affects operator promo rates.

Unicode and multipart PDU costing

GSM-7 single segment is 160 characters; UCS-2 often 70 characters per segment. Gateway logs may expose segment count per message — multiply monthly message count by average segments before applying operator rate if carrier bills per PDU. Emoji-heavy templates double operator spend vs plain-text spreadsheet assumptions.

OTP templates should stay GSM-7 single segment for cost and deliverability — estimation worksheet assumes 1 PDU per OTP unless analytics prove otherwise.

Failed sends and operator billing

Some operators bill accepted PDU even when DLR shows failure; others bill only delivered. Historical DLR ratio from gateway exports adjusts effective rate: if 5% fail but bill on submit, multiply volume by 1.0; if bill on delivery, multiply by 0.95 delivered. Ask operator rep which rule applies — estimation accuracy lives in details.

Dual-SIM worksheet duplication

One phone with two active sending SIMs gets two worksheet tabs — never merge rates without merging ICCIDs. Slot A postpaid invoice ≠ slot B prepaid pack. Service tier row remains one platform line for the paired phone unless second phone added (second device_id).

Growth scenario modeling

Model 3× volume stress on operator ledger only — does prepaid pack ladder still work or postpaid overage kick in? Platform ledger stress separately: does 3× volume exceed Gold allowance? Growth slides need two sensitivity tables.Service pricing is based on device count and total SMS sent through the gateway. Growth in users does not automatically change operator rate per PDU — but volume tier might step up platform fee.

Tax and VAT on operator packs

Prepaid retail price includes VAT in many markets — use receipt total ÷ SMS count for effective rate. Postpaid invoices separate tax lines — finance may want pre-tax operator rate for international comparison; document both in worksheet footnote.

Shopify notification parallel estimate

Merchants using Shopify APIs for order events can export order count × notification templates per order as message count proxy. Compare operator worksheet total to Shopify SMS app pricing for same count — remember Shopify path is aggregator economics, Android path adds device ops but often lower PDU rate in emerging markets.

Blank worksheet template (narrative)

Row 1: ICCID and device_id. Row 2: traffic class split OTP/bulk/transactional monthly SMS. Row 3: rate source and date. Row 4: operator subtotal. Row 5: platform tier name and fee from Pricing. Row 6: data. Row 7: headroom percent. Row 8: total. Row 9: recharge owner RACI. Row 10: next review date. Duplicate per SIM; sum operator rows; single platform row per account unless multi-account enterprise.

CFO narrative script

“We pay the mobile operator for SMS airtime on our SIMs — ledger A. We pay SMS Gateway for platform device and volume metering — ledger B. They are separate contracts. Operator spend scales with messages the radio transmits; platform spend scales with paired devices and platform send allowance. Free platform tier does not include operator airtime.” Sales and support must speak this paragraph cold — estimation worksheet is the spreadsheet backing.

India bulk and promotional routes

India promotional SMS routes differ from transactional DLT routes — bulk worksheet must use promotional rate from operator tariff sheet. India geo lists template and entity costs; estimation without route type conflates OTP transactional rupee rate with marketing promo rate. Same postpaid invoice may show both line items — parse separately.

Common objections via Questions hub

Objection: “Competitor quoted all-in per SMS.” Response: ask if quote includes number rental, 10DLC, and whether Android BYO-SIM ops is in scope. Objection: “Operator gave unlimited SMS.” Response: model FUP cap from fair-use appendix; link throughput spoke. Objection: “Platform should warn before operator empty.” Response: gateway meters platform volume; operator balance is customer-operated — implement worksheet-driven recharge alerts. Point to SMS gateway FAQ and definitions for canonical answers.

Month-close reconciliation

Finance month-close: attach operator receipts/invoices sum, platform invoice, variance note vs worksheet vN. Ops month-close: confirm next month pack orders placed if prepaid. Engineering month-close: none unless meter dispute — keeps ownership clear.

Pilot to production estimate bump

Pilot used 500 SMS/month on prepaid; production forecast 40,000/month — rebuild entire worksheet, switch billing type if postpaid now cheaper, upgrade platform tier on Pricing before cutover not after overage. Pilot underestimate kills launch week — schedule estimate review gate in project plan.

Spreadsheet export tips

Export gateway send report CSV monthly; pivot by device_id and day. Peak day = MAX(daily sum). Cross-check OTP analytics export — gap between analytics successful auth and gateway send count reveals retry multiplier error in worksheet. Bulk campaigns appear as single-day spikes — do not smooth into monthly average row without footnote.

Rounding and conservative bias

Finance prefers conservative estimates — round operator SMS count up to nearest thousand, round rates up to nearest tenth cent, round headroom to 25% when launch within 30 days. Under-budget operator recharge causes outages; over-budget causes minor float waste — asymmetry favors high side on ledger A.

Multi-currency operator packs

Fleet in India + Bangladesh + US means three operator currencies on ledger A — one platform USD invoice on ledger B. Consolidated CFO view needs FX table — do not sum rupee and dollar rows without conversion. Geo guides for each market linked from worksheet tab header.

Platform allowance when operator is separate

Customer hits Gold SMS allowance on the platform while operator postpaid still has headroom — On Free and Developer, sending pauses when you use the plan SMS allowance rather than silently billing aggregator-style overage. Upgrade or request a custom allowance to continue. Radio could send more, but the control plane will not silently bill aggregator-style overage as the default. Conversely operator prepaid empty while platform tier still shows allowance remaining — sends fail at the carrier. Estimation must surface both limits side-by-side in the CFO slide; neither substitutes the other. Review device and SMS volume pricing when monthly platform sends approach the tier allowance.

Benchmark month selection

Use highest-volume month in last six for conservative operator estimate, not lowest or average — unless finance explicitly wants expected case vs worst case. Document scenario label on worksheet: “worst month Mar 2026” vs “steady state Apr–Jun average.”

Sales-to-ops handoff

Sales closes on platform tier from Pricing; ops inherits operator worksheet. Handoff packet must include estimated ledger A monthly, recharge owner, and ICCID list — not only gateway contract value. Deals that quote “cheaper than Twilio per message” without operator worksheet fail in month two when prepaid packs stack beyond proposal assumptions. Align with SMS gateway FAQ and definitions canonical billing language before customer signature.

Next steps

Run the HowTo, fill worksheet per ICCID, publish two-ledger summary. Hub: Android phone as SMS gateway. Bulk: Bulk SMS. India: India geo. Pricing: device and SMS volume pricing (Priced by devices and SMS send volume. You use your own phone and operator SMS credit.). Operator airtime and service fees stay separate — finance and ops stay aligned.