Automatic SMS failover: multi-provider routing on Mrfqy

Regional SMS gateways occasionally return 5xx errors, throttle during national holidays, or reject sender IDs mid-campaign. Mrfqy's ORDER_COD_SMS worker implements automatic failover: try primary provider credentials, log failure to order_sms_logs, retry on secondary within the same job execution.

Building your failover chain

Egypt example: VictoryLink primary (lowest cost), SMS Misr secondary (OTP-grade reliability), Twilio tertiary (global backstop). Saudi example: Unifonic primary, Infobip secondary for cross-GCC destinations.

Each tier stores separate credentials in store_sms_configs — the failover engine reads provider priority from store settings (expanding) or country-pack defaults today.

Failed attempts do not double-charge: order_sms_logs status moves from pending to sent only on first successful delivery; earlier failures stay auditable for gateway SLA conversations.

Operations visibility

Support staff can see which provider delivered each COD SMS in order detail — critical when a customer insists they never received a message but Infobip shows DELIVRD.

Platform analytics (expanding) will chart failover rate per country — if Egypt secondary triggers more than 5% of traffic, negotiate better VictoryLink SLA or add Cequens to the chain.

Failover respects isEnabled toggle — disabling SMS in admin stops all tiers immediately, useful during sender ID re-registration with NTRA or CITC.

One gateway is a single point of failure — Mrfqy's failover chain keeps COD confirmations flowing through Ramadan, White Friday, and gateway maintenance nights.