Clockworksms Laravel Package

Product Decisions This Supports

• Feature scoping for the SMS channel. Informs whether SMS belongs in the next release (OTP, transactional alerts, appointment reminders, order updates) by showing the integration cost is small: this is a thin MIT wrapper around one vendor API, roughly a sprint of work, not a platform build.
• Build vs. buy — decisively "buy the integration, not the infrastructure." The package gives us the vendor plumbing for free; the decision that remains is vendor selection and abstraction, not whether to write SMS transport code ourselves.
• Vendor evaluation. Lets us trial Clockwork SMS (Mediaburst, UK-centric) against Twilio, Vonage, AWS SNS, and MessageBird using real code paths rather than marketing sheets. The wrapper becomes the evaluation harness.
• Roadmap sequencing / risk register. Last release 2017, 0 dependents, 45 stars — treat adoption as interim glue or reference implementation, not a long-lived dependency. This forces an explicit "replace or reimplement" item onto the roadmap before SMS becomes business-critical.
• Supply-chain and compliance review input. A dormant transitive dependency in a payment-adjacent or auth flow (OTP) needs a security and PII-in-transit review before sign-off, plus a note that SMS content is not end-to-end encrypted.

When to Consider This Package

Consider it when:

• You already hold a Clockwork SMS / Mediaburst account and UK/EU delivery is the target region.
• You run a PHP/Laravel monolith and need a minimal, one-way transactional SMS hook (OTP, alerts) shipped fast.
• Volume is low to moderate and the messages are simple and one-directional.
• Your team is willing to own and patch a small MIT wrapper — the surface area is thin enough to fork and maintain.

Look elsewhere when:

• Greenfield or high-volume work, where a maintained official SDK (Twilio, Vonage, AWS SNS, MessageBird) is the safer default.
• You need two-way/conversational messaging, delivery webhooks with SLAs, or vendor support — this package adds no such guarantees.
• You need a maintained library: last release 2017, no dependents, modest stars — assume API drift risk and no upstream fixes.
• Your stack already has native Laravel notification channels (e.g., Vonage/Twilio) that cover the same use case with active maintenance.
• Compliance-heavy contexts (HIPAA, SOC 2, regulated notifications) where dormant dependencies fail procurement.

How to Pitch It (Stakeholders)

For executives: SMS delivery is commodity infrastructure — we should not build it. This package is a thin, MIT-licensed wrapper that lets us attach Clockwork SMS for OTP and notifications in roughly one sprint, so we can validate demand cheaply. The caveat is maintenance: it hasn't shipped a release since 2017 and has no downstream dependents, so we treat it as an interim integration or reference implementation, not a strategic dependency. Recommendation: adopt behind our own SmsGateway interface so we can swap vendors — Twilio/Vonage/AWS SNS — without touching product code. Low cost, low effort, contained lock-in risk.

For engineering: Low integration effort, small surface area, MIT — but plan to pin or fork. Wrap it in an internal interface, cover it with integration tests against the sandbox, and log a migration ticket before SMS becomes business-critical. Do not expose the vendor's client directly in domain code.

Net PM position: Approve as a time-boxed evaluation or interim integration, contingent on interface abstraction and a scheduled vendor-replacement review. Do not approve as the long-term SMS backbone.