Capabilities that ship today
Nothing on this page is a roadmap item.
Verdict engine /
The verdict is deterministic, not a language model guess.
Enumerated verdict set
PASS, PASS with calling-number mismatch, PASS with calling-number unavailable, distinct receive failures (busy, no answer, rejected/blocked, unallocated/disconnected, answered but not verified, DTMF not verified), originate failures, and explicitly inconclusive outcomes. The verdict is computed by fixed logic and enforced in the classifier, a database constraint, and the PDF — a language model never decides a verdict.
Per-leg detail
Every leg is timestamped and recorded separately. The report includes answering-machine detection and a carrier lookup on the leg, plus STIR/SHAKEN attestation captured where the carrier provides it.
Five timezone render
The PDF shows timestamps in UTC plus four additional timezones so the report is readable no matter where the client, the tech, or the dispatcher is located.
Proof artifacts /
Call recording
The full call recording is stored and linked from the report. A QR code on the report points to a shared results folder so the evidence is one scan away.
Cryptographic receipt
A signed receipt with a public verification URL lets a third party confirm the report is the one that was issued. A signature makes tampering detectable, not impossible.
Technician attestation
After a correct DTMF entry, the technician speaks their name — an on-site verbal attestation captured on the recording. It is a self-declaration, not independent identity verification.
When a test fails /
Isolating the failure
On a failure, the platform places a positive-control call to a known-good mobile inside the same failure window. A completed control call isolates the failure to the line under test rather than to the platform's ability to place a call. The tech answers a structured questionnaire (dial tone, ringback, reorder, intercept, demarc or inside wiring) so the evidence covers the failure, not just the verdict.