Africastalking Laravel Laravel Package

Product Decisions This Supports

• Channel selection for last-mile reach: Informs whether SMS, USSD, voice, or airtime is the right delivery channel for target markets (Kenya, Nigeria, Uganda, Tanzania, etc.) where push/email penetration is low.
• USSD product bets: Enables USSD menu flows for feature-phone and low-connectivity users — often the difference between reaching or excluding a majority of a market.
• Mobile money vs card payments: Supports collection/disbursement decisions via M-Pesa and similar rails, rather than assuming card-first checkout.
• OTP/2FA and transactional notifications: SMS-based verification and alerts for signup, login, and transaction confirmation.
• Bulk SMS and campaign tooling: Reminders, marketing, and operational alerts; delivery reports feed into funnel and deliverability analytics.
• Voice and QA workflows: The new CallRecordingDownloaded event now carries file size — useful for storage/retention cost decisions and compliance/QA pipelines around call recordings.
• Build vs buy: Favor buying this wrapper over hand-rolling HTTP integrations: it gives Laravel-native facades, config-driven credentials, queued jobs, and events instead of custom API plumbing.
• Roadmap candidates: Airtime rewards and distribution, USSD session analytics, multi-provider SMS failover, and voice verification — all become cheaper to prototype.
• Use cases: Fintech, logistics, health, agri, e-commerce, and education products needing reliable last-mile communication.

When to Consider This Package

Consider adopting when:

• Target markets fall within Africa's Talking coverage and your backend is Laravel.
• You need SMS, USSD, voice, airtime, and mobile money in one SDK with idiomatic Laravel ergonomics (facades, config, events, queued jobs).
• You want fast prototyping of USSD or mobile-money flows without bespoke integrations.
• You can tolerate the v3.0.0-alpha stage on non-critical paths — pin the exact alpha version, validate in staging, and plan to upgrade to stable before relying on it for revenue-critical flows.

Look elsewhere when:

• You are not on Laravel (use the official Africa's Talking SDK or an HTTP client directly).
• Your markets are outside Africa's Talking coverage.
• You require vendor-backed SLAs and commercial support — this is a community package.
• You need built-in multi-provider failover (e.g., Twilio + Africa's Talking) out of the box; you'd need a routing layer on top.
• You need email/push only — this package adds little.

Release context: v3.0.0-alpha4 is an incremental alpha adding file size to the CallRecordingDownloaded event. No breaking changes versus alpha3, but it is still pre-stable — treat v3 as an evaluation track and track the changelog for breaking changes before any upgrade.

How to Pitch It (Stakeholders)

For executives: This package lets us add Africa-first capabilities — SMS, USSD menus, airtime, and mobile money — in days rather than quarters, without building and maintaining raw telecom integrations. It lowers the cost of reaching feature-phone users and opens new revenue paths (USSD services, mobile-money collections). Trade-off: it's a community package currently in alpha, so we pin versions and keep it off revenue-critical paths until stable.

For engineering: It's a thin, idiomatic Laravel wrapper over the Africa's Talking API — facades, config-driven credentials, queued jobs, and events — cutting boilerplate and error handling for SMS, USSD, voice, and payments. The latest alpha adds file size to the CallRecordingDownloaded event, which helps with storage and retention logic. Recommendation: adopt behind a config/feature flag, pin the alpha version, cover with integration tests, and budget a small upgrade once v3 reaches stable.

For product: Prioritize USSD and mobile-money flows as high-leverage experiments for African markets; SMS OTP and alerts as low-risk quick wins; voice/recording tooling as a later investment once the SDK is stable.