A long request can be lost when validation fails or the connection ends. We review the form's fields, feedback and confirmation steps to identify where a customer becomes unsure about what happened.
Keep the task proportionate
The first version can reduce unnecessary fields, retain appropriate entered information after an error and provide accessible status messages. Any browser-side storage of customer details needs a deliberate information-handling decision; saving everything automatically is not assumed.
A successful button press should not become a false thank-you. The interface should distinguish a confirmed receipt from a failed or still-uncertain attempt and offer a useful alternative contact route.
Acceptance
Try invalid input, a slow response and a repeated action using fictional details in a private environment. Check keyboard operation and phone layouts, including the on-screen keyboard and longer Spanish labels.