Product case study
Nexosend.
An SMS platform for scheduling campaigns and reviewing each recipient’s sending status.
01 / Context
Scheduling a campaign
A scheduled campaign can have several recipients and a different outcome for each. Users can choose a sending time, cancel an eligible scheduled message, and check individual results in their history.

My contribution
I built the Laravel backend and Vue 3 interface. For bulk sends, I create one SMS record and one queue job per recipient, so each outcome is recorded separately. A worker retries eligible processing errors and records provider rejections as failures.
In the message history, sent means the provider accepted the SMS. Confirmation that it reached the phone would require a separate delivery receipt.
API access and automated checks
I used Laravel Sanctum for API authentication. After verifying their email, users can issue and revoke tokens from the web app. The OpenAPI documentation includes example requests and responses in Swagger UI.
What runs on every pull request
GitHub Actions runs the Laravel feature tests against MySQL with PHPUnit and builds the Vue frontend.