Someone wants to know whether a film screening has wheelchair-accessible seating. Why should they have to enter a full postal address just to ask? The venue may need that address for a booking later, but it does not need it to answer this question. Move the field to the booking stage—or remove it from the inquiry form.
A cinema, festival, film club, or cultural publication may receive group screening requests, submission questions, and editorial pitches through the same page. Each conversation calls for different details. Before adding a field, ask: what does the team need to send a useful first reply? Let that answer shape the form, not the fields that happen to come with a website template.
Give each form a clear job
A general contact form can become a dumping ground for every possible request. Someone reporting a broken caption file should not have to pass fields marked “Organization,” “Event date,” and “Estimated budget.” A clear heading and a sentence beneath it can tell visitors what the form is for: “Ask about a group screening” or “Send an editorial inquiry,” for instance.
If requests really need different information, offer a short choice at the start and show the relevant fields. A group booking may need a preferred date and approximate attendance. A programming proposal may need a film title, rights-holder information if known, and a brief description. Keep an “Other question” option visible, too. People should not have to work out which department owns their problem before they can describe it.
Say what the form is not for when the distinction matters. Asking about festival submissions is different from submitting a film; a press question is not a ticket refund request. Point visitors to the right channel before they spend time writing to one that cannot help them.
Ask for what the first reply requires
Start with a name, a way to reply, and enough context to understand the request. Then examine each extra field: what happens if someone leaves it blank? If staff could answer anyway or ask a follow-up question, make it optional. If the answer determines which team responds, keep the field and explain its purpose.
For a private-screening inquiry, a short form might ask for:
- Name and email address: so the team can address the person and reply.
- Type of inquiry: group visit, private screening, or another request.
- Preferred date or date range: to check availability, with a “not decided” option.
- Approximate group size: to help identify a suitable space.
- Message: for details such as accessibility needs or a film preference.
A telephone number may be useful for a time-sensitive event, but do not require it simply because someone on the team might prefer to call. Ask when there is a clear reason, and say whether phone contact is optional. Avoid collecting sensitive details in an open message box when a safer process exists. An accessibility question usually calls for the accommodation requested, not a medical history.

Make labels answer small but important questions
“Subject” makes visitors invent a category. “What is your question about?” with plain-language choices gives them a better start. Show the expected date format, or offer a date picker that also permits typing. If plans may be flexible, “Preferred date or range” is more accurate than “Event date.” Mark required fields on their labels and explain the convention once; do not wait until submission to reveal that a field was mandatory.
Keep labels visible rather than relying on placeholder text, which disappears when someone types. Put brief help text beneath a field if it prevents a likely mistake: “An estimated number is fine,” for example. Avoid examples that look like real personal information someone might accidentally leave in place.
Make the form usable on a phone and with assistive technology
A form that looks short on a desktop can still be tiring on a phone. Try it at a narrow screen width with a real thumb. Are fields easy to tap? Do labels stay visible? Does a fixed banner cover the submit button? Use a single column where possible. An email input lets phones offer the appropriate keyboard. If visitors can give a date range, do not force them through a calendar that accepts only one exact day.
Clear visuals need sound markup behind them. Associate labels with fields, group related options under a meaningful question, and keep keyboard focus in a logical order. Identify errors in words, not color alone. Someone using a screen reader should hear that submission failed and know how to fix it. A keyboard and screen-reader test can catch barriers a visual review misses.
Give the message box room for a real inquiry. Three or four visible lines may suit a brief question; a film-rights or programming request may need more. A tiny box suggests that detail is unwelcome, even if the system technically accepts a long answer.
Handle mistakes without discarding the inquiry
Validation should catch problems that actually prevent a reply. An email address missing an “@” needs correction; a two-sentence message should not fail an arbitrary character minimum. Avoid strict rules for names, which do not follow one universal pattern. International phone numbers also vary too much for a narrow local format unless the service is explicitly local and a number is necessary.
If submission fails, keep everything the visitor entered. Put a clear explanation beside the problem field and, on a longer form, a brief notice at the top pointing to the errors. “Please enter an email address so we can reply” helps more than “Invalid input.” If the server fails or the connection drops, say whether the request was received so the visitor knows whether to try again.
Spam controls can block genuine questions. A challenge that is hard to hear, see, or complete on a phone may stop the people the form is meant to reach. Where practical, use lower-friction measures such as rate limiting and server-side detection, then check whether real messages are being rejected. A form that silently drops valid inquiries is not doing its job.
Set expectations before and after submission
Beside the submit button, explain what happens next. “Our programming team usually replies within three working days” tells visitors more than “We’ll be in touch.” Publish only a timeframe the team can meet, allowing for weekends or festival periods. If urgent ticket problems have another route, point it out before someone submits this form and waits.
After submission, show an unmistakable confirmation that the inquiry was received. If the system can display them safely, include the submitted topic and a realistic reply window. An automated email acknowledgment may help with a complex request, but it must not suggest a person has reviewed the message. The on-page confirmation should make sense on its own if email delivery fails.
Add a short privacy note explaining how the submitted details will be used for this inquiry, with the relevant privacy information easy to find in the site’s navigation. Do not quietly subscribe someone asking about a screening to a marketing newsletter. Promotional messages need a separate, optional choice, not a condition of sending a question.

Measure completion without treating every submission as success
More submissions do not necessarily mean a better form. Count how many people open it, how many submit successfully, where errors occur, and how many inquiries staff can actually answer. Compare results by device and inquiry type when there is enough traffic to make the comparison useful. Measure field-level errors and completion events without recording the personal text people type.
Staff can explain patterns that numbers cannot. If the programming team keeps having to ask, “Which city are you in?”, a location field or clearer geographic guidance might save a round trip. If accessibility requests repeatedly land under “Other,” revise the categories. And if an optional “How did you hear about us?” field yields little useful information, remove it.
Change one obstacle, then check the result
Give each revision a specific question to answer. For instance: will making the date field optional help people planning a group visit inquire earlier without increasing requests the team cannot answer? Record the current completion and useful-inquiry patterns, make the change, and compare a similar period afterward. A small site may not get enough submissions for a firm numerical result. In that case, review support conversations and run a few task-based usability tests rather than declaring a winner from a handful of clicks.
Give someone unfamiliar with the site a concrete task: ask about bringing 20 students to a subtitled screening without a confirmed date. Watch where they pause, whether they can tell which fields are required, and what they expect after pressing submit. If “Event date” stops them, try “Preferred date or range” or add “Date not decided.” Then ask another person to try the task.