Kavenegar Laravel Package

Product Decisions This Supports

• Build vs. Buy: Accelerates SMS integration for Iran-based projects, avoiding custom API development for Kavenegar (Iran’s leading SMS gateway). Reduces backend complexity by abstracting authentication, rate limits, and error handling.
• Feature Expansion: Enables two-factor authentication (2FA), transactional alerts (e.g., order confirmations, OTPs), and customer notifications (e.g., delivery updates) without third-party SaaS dependencies.
• Roadmap Prioritization:
  • Phase 1: Core SMS functionality (OTPs, alerts) for MVP launch.
  • Phase 2: Extend to multi-channel notifications (SMS + email) using this package as a foundation.
  • Phase 3: Integrate with customer support tools (e.g., Zendesk) for automated SMS responses.
• Use Cases:
  • E-commerce: Cart abandonment reminders, shipping notifications.
  • FinTech: Payment confirmations, fraud alerts.
  • Marketplaces: Vendor order updates, buyer inquiries.
  • Internal Tools: Password resets, system alerts for Iranian teams.

When to Consider This Package

Adopt If:

• Your primary audience is in Iran (Kavenegar is Iran-specific; alternatives like Twilio/Vonage may have higher costs or latency).
• You need low-latency SMS delivery for time-sensitive use cases (e.g., OTPs, stock alerts).
• Your team lacks SMS API expertise and prefers a Laravel-native solution.
• You require bulk SMS capabilities (e.g., sending to 100+ recipients at once via sendArray).
• Cost efficiency is critical (Kavenegar offers competitive pricing for Iranian numbers).

Look Elsewhere If:

• Your users are global (use Twilio, AWS SNS, or Plivo for broader coverage).
• You need advanced features like MMS, global number masking, or WhatsApp (Kavenegar is SMS-only).
• Your project requires high scalability (>10K SMS/day); evaluate Kavenegar’s rate limits and consider a hybrid approach (e.g., fallback to Twilio).
• You’re using non-Laravel stacks (PHP frameworks like Symfony or non-PHP backends).
• Maintenance risk is a concern: The package is stable but lacks recent updates (last release: 2021). Plan for minor customizations or forks if Kavenegar’s API changes.

How to Pitch It (Stakeholders)

For Executives:

"This package lets us integrate Kavenegar’s SMS API into our Laravel app in hours, not weeks. For Iranian users, it’s the most cost-effective and reliable way to send OTPs, alerts, and notifications—critical for features like 2FA, order confirmations, and customer support. By avoiding custom API work, we’ll reduce dev time by 70% and launch faster. The MIT license means no hidden costs, and Kavenegar’s pricing is transparent and competitive for our target market."

Key Metrics to Highlight:

• Time-to-Market: Deploy SMS features in 1–2 dev days.
• Cost Savings: Avoid SaaS fees (e.g., Twilio’s ~$0.0075/SMS vs. Kavenegar’s ~$0.003/SMS for bulk).
• User Retention: SMS open rates are 98%+, outperforming email for alerts.

For Engineering:

*"This is a lightweight, Laravel-idiomatic wrapper for Kavenegar’s API. It handles:

• Authentication: No manual API key management.
• Error Handling: Built-in status codes (e.g., 200 for success, 400 for invalid numbers).
• Bulk Operations: sendArray() for batch SMS (e.g., marketing campaigns).
• Outbox Management: Track sent/received messages via latestOutbox(), cancel().

Trade-offs:

• No active maintenance: Last update was 2021, but Kavenegar’s API is stable. We’ll monitor for breaking changes.
• Iran-only: Not suitable for global rollout.

Recommendation: Use this for core SMS needs and pair with a feature flag to switch to Twilio later if we expand globally."*

Tech Deep Dive:

• Installation: 2 commands (composer require, vendor:publish).
• Usage Example:

  $sms = new \KavenegarSMS();
  $result = $sms->send('09121234567', 'Your OTP is 12345');
  if ($result->status === 200) { /* Success */ }
  

• Extensibility: Override the service provider to add logging or retries.
• Testing: Mock KavenegarSMS in PHPUnit for CI/CD.