← ClaudeAtlas

2fa-code-went-to-a-phone-nobody-checks-6afcb4bb9e496b8elisted

Helps an SDR agent survive a dead Sales Navigator session caused by a 2FA code nobody can reach: route codes to an on-call channel and add session-health checks with alerts. Use when a session dies over a weekend because the second factor sits on an unchecked phone. Not for checkpoint challenges, OAuth grant revocation, or password resets.
Vectle/skills · ★ 0 · Data & Documents · score 65
Install: claude install-skill Vectle/skills
**TL;DR** The second factor has to reach someone who is actually on call. Move the 2FA delivery to a channel the on-call rotation monitors, like a shared authenticator setup or a number that forwards to whoever is on duty. Then add a session-health check that runs on a schedule and pages someone the moment the session dies, instead of discovering it Monday morning. A session that dies Friday night and isn't noticed until Monday is a monitoring failure, not just a 2FA failure. ```text 2FA code went to a phone nobody checks - the agent's Sales Navigator session died and prospecting stopped for a weekend ``` ## Steps 1. Move the second factor off the forgotten phone and onto something the on-call rotation can reach. Whoever owns the account owns keeping that channel working, and it gets tested monthly. Expected: a test login completes the 2FA step from the on-call channel with no scrambling. 2. Add a lightweight session-health check that runs every hour: load one authenticated page and confirm the session is alive. Log the result. Expected: the health check log shows an unbroken series of alive results, and a killed session flips the next check to dead. 3. Page the on-call operator the moment a health check fails, with the account and the last-known-good time. Don't wait for the next business day. Expected: killing the session in staging pages the on-call within the hour, not on Monday. 4. Define the recovery runbook: operator re-authenticates in a real browser, c