Skip to main content
Verification isn’t always clean. A customer can fail a verification — a wrong or mistyped number, a stale record, an attempt that simply doesn’t match — and normally those customers just vanish after you paid to acquire them. Authmatech Stuck and Stuck+ make that invisible drop-off visible and recoverable.
Stuck and Stuck+ are dashboard features, not a developer API. There are no endpoints to integrate — the journeys are built automatically as a side effect of every verification. You view and act on them in the Authmatech dashboard.

Matched vs. not-matched journeys

Stuck and Stuck+ are defined by the match outcome of a customer’s verification journey — not by the customer’s connection or device:
  • Stuck — a matched (recovered) journey: a customer who failed verification at first but later matched and got through. This is your friction-and-recovery view: who got stuck but found their way through.
  • Stuck+ — a not-matched journey: a customer who attempted verification, didn’t match, and is still blocked. This is your win-back list: almost-customers you can still reconnect with.
A journey is tracked automatically on each verification attempt. Repeated not-matched attempts mark the journey as stuck (Stuck+); a later successful match flips it to recovered (Stuck).

Secure Reveal — the one recoverable action

Stuck and Stuck+ store the customer’s number protected (masked and encrypted) — never in the clear. When you genuinely need to reconnect with a stuck customer, an authorized admin can use Secure Reveal in the dashboard to recover the real number. Every reveal is:
  • Admin-gated — only authorized workspace admins, scoped to your own workspace.
  • Billed — Secure Reveal consumes credits (it returns real contact information).
  • Audited — every reveal is permanently logged (who, when, why) for compliance.

Where it fits in your flow

When a verification returns validNumber: false, the journey is recorded for you — no extra work. Offer the customer Verify+ as a privacy-safe hint to correct a mistyped number, and never drop back to an SMS OTP. The not-matched journey appears in Stuck+ for win-back; once the customer eventually matches, it moves to Stuck.
Stuck and Stuck+ are included at no extra cost — they make verification stickier. Only a Secure Reveal carries a fee. Reveal availability and limits are configured per account from the dashboard; contact connect@authmatech.com to enable or adjust them.