Accept the report through another appropriate channel, then investigate the form failure. Do not make the resident keep retrying an urgent request.

Open laptop, pens, and sticky notes on a wooden desk surrounded by houseplants.
Illustrative stock photo · Photo: RDNE Stock project / Pexels · Pexels License

Ask for the failure point

Record the time, device type, action and visible error without requesting unnecessary personal details. Check whether the submission arrived before asking for another attempt, so you do not create duplicate tickets. Tell the resident what information you received.

W3C’s form guidance connects clear labeling with instructions, validation and user feedback. [1]

A practical confirmation is: “We have recorded the kitchen leak from your call; you do not need to resubmit it.” Keep the software fault separate from the maintenance issue and track both to completion.

Sources

Editorial standards.

  1. Labeling Controls — W3C WAISource checked Sep 8, 2026.

Have a correction? See our editorial policy and correction process.