Design Studio Inquiry Forms: A Practical Editing Order for Input Fields

An inquiry form should collect enough information to start the next conversation, not as much information as possible. A design studio may need to understand the kind of project, its approximate timing, and the work being requested. That does not mean visitors need to complete a lengthy creative brief before making first contact. Follow the steps below to define the purpose, edit the fields, and test the submission experience.

1. Write down what you need to decide

Before opening the form editor, note what you need to determine after receiving an inquiry. For example, a studio may need the project type, an approximate schedule, and a way to reply before recommending a service and proposing an initial meeting. Leave out information you can check internally or do not need before sending your first response.

• Describe in one sentence what you need to decide when replying to an inquiry.
• Check whether every proposed field is genuinely needed for that decision.
• Do not ask for the same information in a name field, a subject field, and a long description field.

2. Separate required fields from optional ones

Start with as few required fields as possible. A name and a reply-to email address are reasonable candidates. If you do not plan to call people, there is no reason to require a phone number. You can ask for project type using a selection list. For budget or timing, consider ranges or options rather than requiring an exact figure. If visitors may not know the answer yet, make the field optional or ask during the first conversation.

• Required: Make only the information essential for replying mandatory.
• Optional: Let prepared visitors share a project description, preferred timing, or reference site.
• Do not request sensitive information or details unrelated to the work.

**Hypothetical example:** A small brand design studio could require “Name,” “Email,” and “Inquiry type,” while making “Approximate start date” and “Project description” optional. This is only an example; adapt it to how your studio actually works.

3. Edit field labels and response formats

Write labels so visitors can understand what to enter without guessing. Instead of a vague label such as “Details,” try “What design work do you need, and what would you like to solve?” Add a short prompt to a longer description field explaining what would be useful to include. Keep selection lists to categories that actually affect how you handle the inquiry. For example, a list might include “Brand identity,” “Website,” “Packaging,” and “Other.”

• Offer options such as “Within a month,” “In 1–3 months,” and “Not sure yet” so people can respond even when they do not know an exact date.
• If you ask about budget, first decide whether a range is useful for the consultation, and phrase the question so it does not feel needlessly demanding.
• Do not rely on placeholder text as the only instruction. It disappears when someone starts typing, so keep essential guidance in the label or field description too.

4. Arrange fields in an easy-to-follow order

Move from simple contact information to the more detailed project description. One possible order is name, email, inquiry type, preferred start date, and project description. Above the form, briefly explain what kinds of inquiries you accept and what visitors can expect while waiting for a reply. Only promise a response time if you have confirmed that your team can meet it. Make the submit button describe the next action clearly, such as “Send a project inquiry” rather than simply “Submit.”

• Check that fields do not appear unexpectedly or change order while someone is filling out the form.
• Confirm that error messages identify which field needs attention.
• Make sure the confirmation message shown after submission explains what happens next.

5. Apply the edits visually and test the real page

TalkTalkMySite supports AI chat and visual editing. First decide which fields to include and which should be required; then use the visual editor to revise labels, descriptions, options, and field order. When requesting an AI revision, specify its scope—for instance, “Make the phone number optional and add an example prompt to the project description”—and review the result. Do not assume that an AI-generated change is automatically correct; it may not match your intention.

• Check that the form is readable and easy to use on desktop and mobile.
• Test both a submission with a required field left blank and one that uses only required fields.
• Before publishing, confirm that the actual submission flow fits the way your team receives and reviews inquiries.

**Limitations:** Editing a form does not guarantee that every inquiry will be a good fit or that replies will be sent quickly. Check the real submission behavior on the published page. Set any form guidance and handling steps to match your studio’s actual operating procedures.

6. Do a final check and choose the next action

After testing, remove any fields you do not need and make sure you can explain why each remaining required field is necessary. Decide internally who will review new inquiries and what information they will use to respond. After making changes, check the mobile view and submission confirmation message again.

• Is every required field genuinely needed to reply or make an initial assessment?
• Are the labels and choices clear to visitors?
• Do the confirmation message and your internal review process agree about what happens next?

**Next action:** Write down the fields in your current form and mark each one “required,” “optional,” or “remove.” Use that list to edit one field at a time in the visual editor, then send a test inquiry to check the complete flow.