Product Decisions This Supports
- Build vs. buy for telephony: A stable 1.0.0 with click-to-call over Asterisk AMI (Asterisk Manager Interface) means the basic "agent clicks a number, call is placed, agent gets bridged" workflow is a solved commodity. This should shift the build/buy conversation away from "can we build click-to-call?" toward "what differentiates our calling experience?" — freeing engineering capacity for routing logic, CRM integration, and analytics instead of re-implementing AMI plumbing.
- Feature roadmap sequencing: The initial release bundles click-to-call, a Filament viewer with
filament-click-to-call context, and a dialplan publication tag. That trio signals a coherent vertical slice: initiate a call, display the call in an admin UI, and version/tag the telephony routing in the dialplan. Roadmap candidates now become obvious — call logs, disposition capture, agent presence, click-to-call from CRM records, and multi-tenant dialplan management.
- Admin/operations surface: Because the viewer is embedded in Filament, this package presumes a Filament-based back office. If your product already runs Filament, this is a near-zero-integration win for support and sales ops teams who need to see and act on calls in the same panel they already use.
- Dialplan change management: The dialplan publishing tag implies deployments of telephony routing are versioned artifacts. That supports a decision to treat dialplan changes like code — reviewed, tagged, and rollback-capable — rather than hand-edited on a live PBX.
- Use cases to prioritize: inbound support (agent picks up from the admin panel), outbound sales click-to-call from a record, and internal/operational calling. Each can be validated against this release without further platform investment.
When to Consider This Package
Adopt it when:
- You are on Laravel and Asterisk (AMI) and want click-to-call without writing raw AMI socket handling.
- Your back office is Filament, or you are prepared to adopt it — the shipped viewer is Filament-native.
- You need a stable, tagged baseline (1.0.0) to build on rather than chasing an evolving pre-release API.
- Your dialplan is managed as a deployable artifact and you want tags tied to releases.
- Your calling volume and agent count are modest enough that a single AMI integration is operationally sufficient.
Look elsewhere or defer when:
- Your telephony stack is not Asterisk (e.g., Twilio, FreeSWITCH, Genesys, Teams) — AMI is Asterisk-specific.
- You require high availability, call recording, or compliance features (PCI, GDPR call handling) that a first stable release does not advertise.
- You need a headless API — the shipped surface is oriented around a Filament viewer; confirm the programmatic API is sufficient before committing.
- Your admin UI is not Filament and you do not want to introduce it solely for this package.
- You need long-term vendor support, SLAs, or a commercial license — a 1.0.0 package is typically community-maintained.
Validate before committing: the 1.0.0 release notes are brief, so confirm supported PHP/Laravel/Asterisk versions, authentication model, and test coverage against your requirements.
How to Pitch It (Stakeholders)
To executives: We now have a stable, versioned foundation for click-to-call telephony inside our Laravel admin panel, built on the Asterisk platform we already run. It removes the need to build dialing infrastructure from scratch and lets our support and sales teams place and see calls from the same tool they use daily. The commercial upside is faster time-to-market on any calling feature, and the cost is lower than a bespoke integration because the hard AMI work is already done.
To engineering: This is the first stable release: AMI click-to-call, a Filament viewer wired to the click-to-call context, and tagged dialplan publication. That gives us a clean vertical slice to extend. Recommended next steps are to pin 1.0.0, verify version compatibility with our PHP/Laravel/Asterisk, and plan follow-on work (call logging, dispositions, agent presence) on top of the existing integration rather than beside it. Treat dialplan changes as tagged, reviewable deploys.
Risk note: It is a young package at its first stable release — confirm support model, licensing, and long-term maintenance expectations before making it load-bearing for critical call flows.