The form on the website is a transfer of business between the customer and the business. The user submits the information; The business must receive this request, forward it to the right person, and respond. Designing only the first screen of this chain can produce applications that look good but cannot be followed.
Select questions based on decision need
The type of service, approximate scope and contact information can provide a starting point for a freelance graphic design offer. Asking for a lengthy company survey before the interview has even taken place can create unnecessary burden. Write why each field is needed; Reserve details that can be learned in the second interview.
Time zone, duration and meeting type in the appointment form; product need in demo form; The delivery expectation stands out in the proposal form. Don't try to solve them with one immutable template. Specify required fields clearly, don't leave field labels just for temporary placeholder text.
Design success and error screens together
“Your message has been sent” should not appear until the data is actually saved. Identify slow connections, reclicks, invalid files, and server errors with the developer. The user should not have to re-enter everything he wrote after an error.
If adding a file, show the allowed format and size from the beginning. On mobile, opening the keyboard in accordance with the relevant area, reaching the error area and not closing the button are also part of the control.
Clarify responsibility in CRM transfer
Which field in the CRM will the “service” selection on the form go to? What happens if the same person writes twice? Which team member will the request be assigned to? The technical team should test this pairing; The business must take responsibility for the response flow. The designer organizes the side of this that is visible to the user.
Do not submit names, emails, or free message content to analytics events. In measurement, it may be sufficient to separate phases such as form initiation and verified completion. The scope of an actual installation must be determined separately.
With Selçuk Aker, we can prepare all the states of the form in the UI UX design work. For the texts, you can look at UX writing guide.
Frequently asked questions
Is multi-step form always better?
No. The number of fields, complexity of the decision and device usage are decisive. Don't break a short form into unnecessary steps.
Does clicking the button count as a referral?
It doesn't count alone. After clicking, the operation may fail; Successful registration must be verified separately.
What should be included in the design submission?
Field list, requirements, validation messages, loading and result statuses, and explanations for the developer should be added.
