An Erenköy service provider may ask for details that a visitor needs time to gather. A saved enquiry gives the visitor a way to return later, but an unclear status can make an unfinished request look as if it has already been sent. Open a test draft on two devices to check the handover.
Show whether the request is saved or sent
In a test copy, enter a fictional service and preferred date, then use the save option. Ask the visitor whether staff can act on the request yet. Show the status and remaining fields in the return message. Ask the receiving team to check that its normal queue contains only the requests the visitor has submitted.
Resume the same draft on a second device
Open the test link on a phone using the intended access steps. Review the service, date and other details that the form promised to retain. Ask the visitor to correct one answer and continue from the remaining fields. Check whether a language switch displays the same draft and explains any answer that needs review.
Try an old link after the draft changes
Open the first link again after saving an edit. Check whether it gives access to the current draft or explains how to recover it. Try an expired link in a separate test. The message should tell the visitor whether they can resume or need to start again. Keep fictional details in all tests and verify that an unrelated signed-out user cannot open the draft.
Send the request and compare the two records
Submit once and compare the final choices with what staff receive. Reopen the saved link and check the status. Record the device, language, fields kept, final reference and result in both languages.
Checklist before publishing
- Draft and sent status easy to distinguish
- Saved details visible when resuming
- Expired link gives a clear next step
- Staff receive the final submitted version