Tarjeeh
Start a project

What should a quotation form say when a customer cannot submit it?

Test the words, field links and confirmation shown to someone who encounters an error while requesting a quotation.

Website Development2 min read

Tell the customer which part of the quotation request needs attention, how to correct it and whether the request has reached your team. Keep the details they already entered wherever practical. A form that simply turns a border red leaves someone on a small screen hunting for a problem they may never see.

Write the correction beside the field

Take a form that asks for an email address so the estimator can reply. Enter a value with the domain missing and press send. A useful message names the email field and shows the expected shape of an address, with a clearly fictional example. Compare that with a message that says only that the details are invalid. W3C's forms tutorial recommends identifying the affected control and providing guidance on correcting the mistake. Check that the example agrees with what the form actually accepts before translating it.

Give several errors a sensible reading order

Imagine that both the email address and project category need attention. The customer has scrolled past these fields to write a long description of the job. Place a short summary where the customer encounters it after submitting and link each item to the relevant field. Keep a local explanation beside that field so the correction still makes sense after the jump. Try following the links using only a keyboard. On the Arabic page, use the exact field names visible in that version and test the same route again.

Distinguish a field error from a delivery problem

If the connection drops after someone presses send, editing the address may accomplish nothing. Have the implementation team describe which outcomes the server can confirm. When the outcome is unknown, the page should say so and explain how the customer can check before sending a second copy. If your team offers a separate contact route, show what reference or details to provide there. Reserve a receipt message for a request the system has actually accepted and avoid inventing an expected reply time.

Run one test from the customer's chair

Prepare a fictional enquiry with a long project description and an incorrect address. Submit it, correct the address and check whether the description survives. Then send it once and have the receiving team locate that same enquiry. Compare the receipt on the customer's screen with the record the team finds. Save the exact failed step, field label and language when they differ. That evidence gives the developer a reproducible task and gives the business owner a simple acceptance test for the next release.

Sources and further reading

Prepared with AI assistance and checked against the sources listed above. Planning examples are illustrative; your project scope is agreed separately.