- How do I install mujhtech/sendchamp in a Laravel application?
- Install it with composer require mujhtech/sendchamp, then publish the package config using php artisan vendor:publish. Add your SendChamp credentials to the .env file as documented by the package. Before adopting it, confirm the Composer constraints resolve against your exact PHP and Laravel versions.
- Does this package support Laravel 11 and Laravel 12?
- Compatibility is not confirmed by the package overview. The last release was October 2022, which likely targets Laravel 8 or 9 and PHP 8.0, so Laravel 11 or 12 may fail Composer resolution. Test it in a scratch app against your full CI matrix before planning adoption.
- Does it provide a Laravel Notification channel for sending SMS?
- The overview describes a facade and fluent interface, not a Notification channel driver. Check the source for a class implementing Laravel's notification channel contract before assuming it plugs into Notifiable and via(). If it is facade-only, wrap it behind your own MessagingGateway contract rather than calling it from domain code.
- Which SendChamp endpoints does this Laravel package cover?
- The package overview names SMS, WhatsApp, voice, and email as supported channels. OTP verification, sender-ID management, delivery receipts, and webhooks are separate SendChamp surfaces that are not clearly covered. Diff the exposed methods against your required endpoint list before adopting.
- How do I send an SMS through SendChamp using this Laravel package?
- Configuration is normally token-based through the published config file and .env credentials. The overview lists SMS support but does not document exact fluent calls, so confirm method names in the README or source. In production, call it from a queued job and wrap it behind your own service contract.
- Is mujhtech/sendchamp safe to use in production?
- Treat it as high risk for revenue- or compliance-critical messaging paths. It has had no release since October 2022, five stars, zero dependents, and a single maintainer, with no visible CI or test suite. Adopt it only behind an internal contract with timeouts, retries, and your own test coverage.
- How are SendChamp webhooks and delivery receipts handled?
- Webhook signature verification and delivery-status modeling are not evident from the package overview. SendChamp callbacks are a separate surface from sending messages, so inspect the source for route or signature handling. If absent, implement a signed webhook endpoint in your Laravel app and verify payloads before updating message state.
- Can I use this package with multiple SendChamp accounts or multi-tenant apps?
- The package uses publishable config, so credentials are normally set per application environment. Multi-tenant credential sets are not evident, and runtime config swaps can collide with php artisan config:cache. Test tenant isolation and avoid environment variable naming collisions with any existing SendChamp integration.
- What are alternatives to using this Laravel SendChamp package?
- A first-party client on Laravel's Http facade is roughly two to three days of work and removes the dependency, bus factor, and version constraint. You can also use provider-agnostic notification channels if messaging is a shared, multi-provider capability. Compare both against SendChamp's current REST API documentation before deciding.
- How can I test the SendChamp integration without sending real messages?
- The package overview does not advertise a fake or sandbox mode. Prefer SendChamp sandbox credentials where available and use Laravel's Http::fake and Queue::fake around your own wrapper. Treat every package code path as untested until you add coverage for success, failure, retry, and timeout behavior.