Aglet

Triage notification channel fallback before adding another delivery path

When a preferred channel is muted or unavailable, an alternate path can preserve visibility or create an exhausting cascade. Triage the event’s durable state first. Map channel preference, failure, fallback, and duplicate guard so “send another alert” is not the default answer.

Establish what is happening

  1. Map one event

    Record event, channel preference, channel state, attempt, fallback, in-app record, user action, and duplicate outcome. Include a successful preferred channel and a disabled or failed path. Keep urgency and event identity visible.

  2. Compare fallback value

    Ask whether the alternate channel helps the person recover or simply repeats the same message. Compare in-app history, email, browser, mobile, and no fallback. A durable record may preserve the event without another interruption.

  3. Set a channel boundary

    State which failures trigger fallback, what remains available, how duplicates are prevented, and what copy explains uncertainty. Preserve a no-fallback control. Stop when another reviewer can predict the event path from preference and state.

What to carry forward

The triage output is a fallback matrix with event identity, preferred channel, failure, alternate path, durable state, and duplicate boundary. Stop when visibility and repetition are distinguishable. If channel state is unknown, keep the event record and route the delivery evidence.

Technical background: Android developer documentation.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow