- How do I install tzsk/sms in a Laravel application?
- Install it with Composer using composer require tzsk/sms, then publish the package configuration and set your default gateway and credentials. For v10, confirm your app meets the PHP 8.4+ and Laravel 11+ requirements before installing. Check the repository README for the exact config file name and environment variables.
- Does tzsk/sms support Laravel 10 or PHP 8.2?
- No, tzsk/sms v10 requires PHP 8.4 or newer and Laravel 11 or newer. Applications still on Laravel 10 or PHP 8.2/8.3 are blocked by v10 and need to either upgrade the platform or stay on a compatible earlier major version. Confirm the maintenance and security-fix status of that earlier line before relying on it.
- Which SMS gateways does tzsk/sms support?
- tzsk/sms uses a driver-based architecture so you can send SMS through multiple gateways behind one API. The exact built-in driver list depends on the package version, so check the repository documentation for supported providers. If your provider is not included, the driver model is intended to let you add a custom gateway implementation.
- How do I send OTP verification codes with tzsk/sms?
- The package supports OTP and verification flows, so you can generate a short code, store it hashed with an expiry, and send it through the same SMS API. Verify the submitted code with rate limiting and attempt limits before granting access. Keep OTP logic in your application and use the package only for delivery.
- Can tzsk/sms queue SMS messages?
- Yes, tzsk/sms supports queued messages so SMS sending does not block web requests. Make sure your Laravel queue worker is running and that your gateway credentials are available in the worker environment. For high volume, combine queuing with rate limiting to stay within provider limits.
- How do I send bulk SMS to multiple recipients with tzsk/sms?
- Bulk sending is supported, but you should chunk large recipient lists and queue the sends to avoid timeouts and provider throttling. Respect each gateway's rate limits and consider per-recipient error handling. For very large campaigns, a dedicated job pipeline around the package is usually safer.
- How do I customize SMS message templates in tzsk/sms?
- tzsk/sms supports customizable templates, so you can centralize message text and placeholders instead of hardcoding strings. Keep templates short, test placeholder rendering, and account for gateway-specific length or encoding limits. Store templates in config or your own application layer depending on how your version exposes them.
- How can I test tzsk/sms without sending real SMS messages?
- Use a fake or log driver in your testing environment, or swap the underlying gateway client with a mock so no real requests leave your test suite. In Laravel, Queue::fake and HTTP client fakes can help assert that sending was attempted. Always run CI with test credentials or fakes, never production gateway keys.
- What are the risks of adopting tzsk/sms v10 in production?
- The main risk is platform lockout: PHP 8.4+ and Laravel 11+ exclude many currently healthy applications, and conflicting dependency floors can make Composer resolution difficult. Verify whether the 9.x line still receives security and bug fixes, and confirm whether Laravel 13 and PHP 8.5 support targets stable releases. Diff the changelog and public API before upgrading because the release notes list mostly environmental changes.
- What are alternatives to tzsk/sms for sending SMS in Laravel?
- Alternatives include Laravel notification channels for SMS, direct Twilio or Vonage SDK integrations, and other gateway-specific Composer packages. Evaluate each option's Laravel and PHP version support, maintenance activity, queue support, and driver extensibility. If you need a unified multi-gateway API, compare tzsk/sms against those packages using the same version-floor and EOL checks.