Signalbridge Laravel Sdk Laravel Package

Product Decisions This Supports

• Build vs. buy / integration strategy: This remains the lowest-effort Laravel-native path to SignalBridge. The calculus has shifted, though: richer WhatsApp message types — files/media, reply buttons, lists, and link buttons — are meaningfully expensive to hand-roll against a raw API (payload schemas, media handling, interactive message structures). That raises the cost of a custom client and strengthens the case for adopting the SDK rather than building.
• Feature and roadmap planning: v3.0.3 is a feature release, not a maintenance patch. It unlocks concrete product surfaces: sending documents/images in WhatsApp conversations, quick-reply buttons, menu-style list pickers, and link/CTA buttons. These map directly to support flows, transactional notifications, and conversational-commerce use cases, and can now be scoped as roadmap items delivered through the package instead of custom integration work.
• Use cases: Laravel applications sending conversational or transactional WhatsApp messages where the product needs multimedia and interactive UI in-chat — e.g., order updates with action buttons, support triage with list menus, document delivery, or promotions with link buttons.
• Roadmap and upgrade planning: The Guzzle 8 allowance from v3.0.1 still helps unblock framework and dependency upgrades. The v3.0.3 feature additions should now be reflected in roadmap discussions; the earlier characterization of this package as compatibility-only no longer holds.
• Risk posture: Additive, minor-level change with no breaking changes advertised. Low adoption risk if already on the package. Still validate Guzzle 8 compatibility across your dependency tree, and confirm WhatsApp template/message approval constraints before committing to delivery dates.

When to Consider This Package

• Adopt when: You use SignalBridge and need Laravel-native WhatsApp messaging — especially media sends and interactive message types (reply buttons, lists, link buttons) that are laborious to build and maintain by hand. Also adopt if Guzzle 8 compatibility is currently blocking clean dependency resolution.
• Consider cautiously when: You need multi-channel abstraction beyond WhatsApp/SignalBridge, or you require vendor-backed support contracts and a large maintainer base — this is a small-maintainer package. Also consider cautiously if interactive WhatsApp messaging isn't on your near-term roadmap; the new capabilities add no value over the prior patch line.
• Look elsewhere when: You don't use SignalBridge; native Laravel events, notifications, or queues satisfy a plain-text messaging need; you need one API across SMS, email, and push; or Guzzle 8 adoption creates conflicts across your dependency graph.

How to Pitch It (Stakeholders)

Executive summary: v3.0.3 moves this SDK beyond maintenance. It adds WhatsApp file/document sending and interactive message types — reply buttons, lists, and link buttons — which expands what the product can do inside WhatsApp without custom integration work: richer notifications, in-chat actions, and menu-style navigation. It remains a low-risk, additive release with no breaking changes advertised. If WhatsApp is a strategic channel for us, this is worth a scoping conversation; if it isn't, upgrading is optional and low-urgency.

Engineering summary: v3.0.3 adds support for sending WhatsApp files, reply buttons, lists, and link buttons (PR #9). The change is additive to the public surface, with no breaking changes advertised. Upgrading from v3.0.0–v3.0.2 should be straightforward; retain the Guzzle 8 validation step from v3.0.1 against the rest of the dependency tree. Before committing to roadmap dates, verify the new interactive-message APIs against WhatsApp Business template and approval constraints, and confirm error/retry behavior for media uploads.