Android SMS Gateway Scenario 376: Edtech multi-device failover in practice

Summary

Scenario 376 is late-bus failover. Notices leave Android SIMs you host when a route slips past the 15:40 pickup. 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.

If both phones live in a closet that locked at 15:00, the late run is not HA. It is parents waiting at an empty stop.

Not a CodeCanyon “school SMS” pack. Device meters apply — Twilio vs Android SMS gateway.

Key takeaways

• Scenario 376 is 15:40 late-bus pickup failover — not exam dawn, homework 19:00, enrollment, snow-day 05:40, PTC night, or results 08:00.
• A spare that IT racks at lunch and unplugs at 15:00 is not dismissal HA.
• Priced by devices and SMS send volume. You use your own phone and operator SMS credit. Free is 300 SMS lifetime, 1 device. Developer is 25,000 SMS per year.
• Starter is 2 devices; the spare still counts.
• Hold PTA and lunch-balance lists until the late-run drain ends.
• Canary both radios at 15:10, not at the noon health check.

Related reading

multi-device and dual SIM routing, OTP and 2FA SMS, how an Android SMS gateway works, GOV.UK school attendance.

Context

Traffic and a broken lift turn one route late. Parents need the stop and a new time, not a district-wide blast. PTA wants the same hour. One radio and a sleeping OEM policy will lose Tuesday dismissal.

Free (300 SMS lifetime) is a rehearsal house. Developer is 25,000 SMS per year.

Core scenario guidance

Keep primary + spare paired through dismissal. Health is last submit after 15:10, not a noon screenshot.

Hold PTA and lunch-balance until the last late route. Locale per family if you span regions.

Late-bus roles

Cost and ownership

Priced by devices and SMS send volume. You use your own phone and operator SMS credit. The spare is a billed device. Resends burn airtime.

Name a 14:45–17:00 on-call for dismissal, not only exam week.

Operations

15:10 canary both radios. After OEM updates, re-pair before the first bell.

Abort: hold PTA, keep late-run notices, rate-limit resend. Do not “resend all routes.”

Security and compliance

Minors: short bodies. No full student lists in SMS. Authenticate transport-app hooks.

PTA is promotional. A late-bus notice is ops — still honour STOP with a human follow-up.

Decision guide

Ship when 15:10 canary is green and the spare is reachable after office lock. Delay if phones live in a closet that closes at 15:00. If handsets are forbidden, CPaaS for parent OTP.

Checklist

• Primary + spare paired through dismissal.
• 15:10 canary.
• PTA held.
• Per-route, not district blast.
• Portal OTP isolated.
• Airtime before 15:00.
• Battery exemptions both OEMs.
• Locale per family.
• Dismissal on-call named.
• Device cap includes spare.

Next steps

Review device and SMS volume pricing, device setup, SMS API documentation.

Deep dive: production hardening

Cleaners pulling USB at 15:00 is an outage. One brick per radio, labelled.

Dual-SIM remap after patches. Late-run SMS stays on the documented slot.

No auto-reply on ops numbers. Watch DLR, not SIS 200s.

Deep dive: scaling and failure modes

Districts add devices before a multi-campus delay week. Do not invent a hidden unlimited-handset SKU.

Several 15:40s across timezones. One UTC cron complains.

Raise OEM ceilings; fair-use remains. Not unlimited carrier SMS.

Deep dive: integration discipline

Idempotency on route_id + delay_event_id.

If an agent files bus SMS, MCP is a REST wrapper — live fields in Developer Center.

Priced by devices and SMS send volume. You use your own phone and operator SMS credit.

15:10 late-run canary

Unplug primary. Confirm spare takes a staff route notice within SLA.

Hold a dummy PTA list; confirm it does not transmit during the spike.

Abort: hold PTA, keep notices, page if both dark.