Laravel Sms Laravel Package

Product Decisions This Supports

• Channel expansion roadmaps: Deciding whether SMS belongs alongside email, push, and in-app notifications for transactional flows (OTP/2FA, order updates, appointment reminders, delivery exceptions). This package makes SMS a Notifiable channel, so the roadmap question shifts from "can we?" to "which events justify per-message cost?"
• Build vs. buy for notification plumbing: A PM can treat this as a thin adapter over Laravel's native notification system rather than a bespoke messaging service. That reframes the build/buy decision toward choosing an SMS gateway (Twilio, Vonage, local aggregators) while offloading channel wiring.
• Engagement and retention experiments: SMS as a re-engagement or recovery channel (abandoned cart, dormant user win-back) can be A/B tested cheaply once the channel exists, without committing to a full CPaaS integration project.
• Compliance-driven features: SMS OTP for account security, password reset, and step-up authentication — often a regulatory or enterprise-sales requirement. Cheap to enable if the channel is already wired.
• Provider portability decisions: The package abstracts the gateway behind config, so PMs gain leverage to renegotiate SMS contracts or add regional providers without re-architecting notification code. Release 6.7.0 adds a ctyun (China Telecom Cloud) gateway config — a concrete data point that regional provider expansion is a config change, and a direct input to any China-market or data-residency roadmap conversation.
• Platform upgrade planning: 6.7.0 adds support for Laravel 13, PHP 8.5, and PHPUnit 12. This package will not be a blocker on our next framework upgrade cycle, so it can be included in roadmap scoping without a carve-out for "unknown maintenance status."

When to Consider This Package

Consider it when:

• You are on Laravel and already use the framework's notification system for email/push — SMS becomes a one-line via() addition per notification class.
• Your need is narrow and transactional (OTP, alerts) rather than marketing campaigns with scheduling, segmentation, and analytics.
• You are prototyping or validating SMS as a channel before investing in a CPaaS platform contract.
• You need regional gateway coverage, including China, without maintaining per-provider integration code yourself — ctyun support in 6.7.0 makes this a config decision rather than a build.
• Your team is comfortable owning a thin dependency: adoption remains low (single-digit stars, few tracked dependents), but the 6.7.0 release shows the maintainer is actively tracking framework and runtime support, which materially lowers — though does not eliminate — the abandonment risk.

Look elsewhere when:

• You need multi-provider failover, delivery receipts, throughput management, or per-message cost analytics — that is CPaaS territory (Twilio, MessageBird, SNS), not a channel adapter.
• Compliance, audit trails, or data residency are hard requirements in a jurisdiction where you cannot self-certify the gateway contract.
• The package wraps a single gateway you don't intend to use, or you need a provider it doesn't support.
• Long-term maintenance matters and you cannot absorb a dormant dependency. Note the mixed signal: framework support is current (Laravel 13, PHP 8.5), but the project is effectively a one-maintainer effort with near-zero external adoption — assume you may be the only operator of this code in production and plan accordingly.

How to Pitch It (Stakeholders)

To executives: SMS is a proven retention and security channel, and this package lets us add it on top of our existing Laravel notification stack with minimal engineering effort and no licensing cost (MIT). It is a low-risk way to ship OTP and transactional alerts without committing to an enterprise messaging platform. The latest release keeps us current with Laravel 13 and PHP 8.5 and adds China Telecom Cloud as a supported gateway, so it does not constrain our platform upgrade path or our ability to serve regional markets. The trade-off to acknowledge up front: the library is early-stage with limited adoption, so we should treat it as an internal capability we own — budget a small maintenance buffer and keep the gateway abstraction loose so we can swap providers if commercials or reliability change.

To engineering: This package plugs SMS into Laravel's Notification contract, so feature teams keep using notify() and via() rather than learning a new messaging SDK. It keeps provider-specific code out of domain logic, which is where we want the seam. Version 6.7.0 confirms forward compatibility with Laravel 13, PHP 8.5, and PHPUnit 12, and adds a ctyun gateway config — no breaking changes. Caveats: adoption is still negligible and the dependency surface is thin, so plan to pin versions, add integration tests around the channel, and wrap it behind our own notification interface so a swap is a config change, not a refactor.