Show uncertainty honestly after a connection drops during sending

What to change

Ask the supplier to provide an honest pending or uncertain state and a safe way for visitors to establish the outcome.

A worked example

Illustrative example

A visitor sees that confirmation is still being checked after a connection interruption, followed by the established result or a clearly explained next step.

How to check the result

Accept when uncertain outcomes are represented accurately and the recovery interaction does not invite uncontrolled repeated submissions.

A mistake to avoid

A generic network-error message may describe the browser's experience while incorrectly implying that no request reached the practice.

Your action checklist

Use these checks to prepare a discussion with your team or supplier. Tick a check when you have recorded the decision or evidence, rather than when a feature has simply been promised.

Decisions to recordHave the supplier interrupt a test response after submission begins. Compare the visible message with what the receiving test system actually recorded.Inspect the offered actions. Ask how retry, status checking or another recovery route avoids making the visitor guess whether the first attempt succeeded.Reconnect and allow the interface to resolve the outcome. Confirm it does not show both failure and success messages for the same attempt.

Evidence, open questions and decisionsNext action and responsible role

Entries stay in this page and are not submitted to Kay & Co. Download your notes before leaving; the page does not save them.