🛑 Bad OTP — Verification Failures
Onboarding OTP gate (SIGNUP + VERIFY). A "bad OTP" = a session that received a code but never reaches a verified state.
📅 2026-02-09 → 2026-06-10 · daily
Verify Fail Rate
–
Drop-off (No Verify)
–
Wrong Code Rate
–
Wasted Cost
–
⚠️
Anomaly detected
–
Failure composition rate
Share of sessions, by failure mode · % of all SIGNUP+VERIFY sends
Why sessions fail
Failure reasons · % of total sends (one denominator)
Fail rate — SIGNUP vs VERIFY
New user gate vs returning verification
Fail rate by vendor
SMS provider (ptype) · verify failure %
Daily volume & wasted cost
Total sends vs $ spent on sends that never verified
Fail rate by country
Top corridors by volume · excludes un-attributed drop-off
Vendor performance
Verify fail rate is user-side; carrier success is delivery-side
| Vendor | Sends | Verify Fail | Carrier OK | Wasted $ | Total $ |
|---|
Source:
ex_algento.botim_pd.dwd_botim_logs_server_otp_session_di via Grafana datasource fevnxapb1i0hsf. purpose 1=SIGNUP, 2=VERIFY. A failure = is_verify_success=0; NO_VERIFY_ATTEMPT = user never submitted a code. Observation + data only — root cause lives in the analysis doc. Rebuild: python analysis/build.py.