When availability changes, suggest the alternative path

What it is

When modality availability changes, the system should point to the alternative. Users generally do not know their current modality has stopped working; they assume the action was not recognized. A notice tells them the modality is unavailable and names the usable alternative.

Why it happens

The need follows from the user's limited vantage point: rising noise, a busy microphone, an occluded camera are outside direct perception, while the system can detect them. Silent failure leads users to retry the same route and blame their own phrasing or the system's recognition, eroding trust. A notice also shortens recovery, since users need not search for the alternative themselves. Keep it light, because availability can fluctuate often and a prominent notice creates its own interference.

Studying it

Measure the effect of notice on recovery: create unavailable-modality conditions and compare, with and without notice, the time to switch to the alternative, retry count, and trust ratings. Variables include the type of unavailability, notice form, and familiarity with the modality. Include retry count, since it directly reflects whether users understand the cause of failure.

Where it stops holding

When unavailability is brief and self-recovering—momentary noise—an immediate notice can make the interface flicker, so delay or silent retry may be better. When users already know and have chosen the alternative, no notice is needed. If the alternative is also unavailable, say that no route currently works rather than naming an invalid one.

Applying it

• Give a light notice when the default modality is unavailable, naming the usable alternative.
• Delay or retry for brief fluctuations to avoid interface churn.
• If the alternative is also unavailable, state that no route works rather than pointing at an invalid option.
• Verification: under unavailable conditions, measure time to switch and retry count against a no-notice condition.

Related

• Within the group: D5.04.1 Ambient noise, lighting, and social setting determine modality availability · D5.04.2 Every function needs at least one non-primary modality path
• Adjacent: D5.10.2 Failed detection should suggest an alternative modality rather than fail silently · D2.05.1 Critical information must move to another channel when sound is muted
• Search terms: availability notice · reroute · recovery time