Key Takeaways
- laravel sms gateway how to train support staff is a first-line script: last-seen, airtime, Horizon, then escalate — not a second engineering team.
- Most “Laravel OTP is down” tickets are Doze, empty SIM, or unpaired phones.
- Support must not paste API keys or OTP bodies into tickets or Slack.
- Horizon failed jobs ≠ radio failure. Teach the split.
- Priced by devices and SMS send volume. You use your own phone and operator SMS credit. Support cannot refund operator airtime.
- Docs for fields; this page for people.
A script, not tribal knowledge
Search intent for laravel sms gateway how to train support staff is a first-line runbook so OTP tickets do not skip the phone. Service pricing is based on device count and total SMS sent through the gateway. Hub: Laravel SMS gateway. Pairing: device setup.
If the laminated card starts with “retry the Horizon job,” you trained people to duplicate OTP before they check whether the SIM is empty.
First five questions
Last-seen, airtime, which lane (OTP vs promo), Horizon error class, then escalate. Reboot and recovery.
| Ask | Looks like | Then |
|---|---|---|
| Last-seen? | Stale hours | Power, Doze, pairing — not artisan queue:retry |
| Airtime? | Stock Messages also fail | Top up the operator; we do not sell credit |
| Horizon? | Jobs failed with 401 | Key rotated; env — escalate, do not paste the secret |
| Which lane? | Login vs sale SMS | OTP device vs promo device; do not mix retries |
Horizon vs the phone
Failed jobs with 5xx across all devices may be control plane. One device Pending is radio. API incident response. Docs: docs.sms-gateway.app.
What support must never paste
Bearer keys, OTP digits, full MSISDNs in public channels. Keys in env. Laravel OTP.
When to page on-call
OTP lane down, last-seen fresh, jobs 401/5xx, or a soak that was not supposed to run. Load-test carefully. Priced by devices and SMS send volume. You use your own phone and operator SMS credit.
Training checklist
- Shadow three tickets with the laminated order.
- No secrets in the ticket body.
- Canary number documented for staff tests.
- OTP vs promo device map posted.
- Quarterly reboot drill with support watching.
Next steps
Print the card, then drill. Pricing. FAQ.
Related product pages
Jump to the live product docs for this topic—not another long-form article.
- SMS API documentationLive endpoint reference
- PHP REST send samplesPHP code examples
- device and SMS volume pricingPlans and allowances
- Android SMS gateway product guideDefinition, product, and how to buy
