Handle escalations from your phone

Install the console to your home screen, enable push in Settings → Security, and an escalation arrives with enough to decide from the lock screen.

8.4 USDC held · 27m left
api.exampledata.io — stale evidence

That is the whole notification: amount, time remaining, payee, and which clause failed. Four facts, chosen so the decision does not require opening anything.

1. Install

Open console.gowarrant.xyz on the phone and add it to the home screen. It is a PWA — standalone display, opening on the queue rather than in a tab full of other tabs.

The icon and badge carry queue state: a count appears when something is waiting on you. Held warrants are deliberately not counted. Forty held warrants that need no decision is noise, and noise trains people to ignore badges.

2. Enable push

Settings → Security → Devices → Enable on this device.

Subscriptions are per user per device, so enrol each phone you actually carry. Each is listed with when it was added and last reached, and any of them can be revoked from the same screen.

A device that stops accepting pushes is shown as not delivering rather than quietly dropped — that state is usually the answer to "why did nobody tell me". A failed push is logged, and after three consecutive failures the subscription is disabled rather than retried forever.

3. Register a passkey

Settings → Security → Register a passkey, on the phone you will approve from.

Do this before you need it. Above your organisation's threshold, an approval with no passkey enrolled is blocked, not waved through — correct, and unhelpful at the moment you are trying to pay somebody.

4. Approve

Tap the notification. It opens the queue with that escalation already open and its evidence expanded.

The card reads top to bottom in the order the decision is made: amount, clock, payee, which clause failed, the evidence, then the two buttons. The desktop console renders the identical component — it is one card, not a mobile variant, so nothing can change on one screen and skip the other.

Above the threshold, approving prompts for WebAuthn: on a phone, the fingerprint sensor. Then the balance moves.

Telegram, if you would rather not install anything

Settings → Security → Telegram → Link Telegram. You get a code; send it to the bot as /start <code>. It expires in fifteen minutes and works once.

Escalations then arrive as messages carrying the same four facts.

The bot cannot release funds

It carries the notification and hands off, and that is all it can do. Tapping through opens the console, where your passkey signs the decision.

The approval link resolves only for the person it was minted for — a forwarded message opened by a colleague is worth nothing — and it burns on first use, so a message sitting in a chat history is not a standing key to the queue. There is a test asserting no Telegram-scoped route can settle a warrant.

Email

Always on, and always the fallback. It carries a link to the escalation rather than the decision itself, and arrives only when no device and no chat took the notification first.

Nothing waits forever

An escalation nobody resolves is not left hanging. The expiry sweep takes the warrant held → expired → refunded and the money is back in available. Missing a notification costs you the payment, never the funds.