A ticket buyer whose confirmation never arrived and whose show starts tonight needs more than a “Contact us” button. They need to know where to ask, what details to send and whether anyone will reply in time. A touring artist with a booking inquiry needs a different route. Neither should have to work out the organisation’s internal structure first.
For a music publication, venue, promoter, festival or artist team, the contact page is a service point, not a directory of inboxes. It should help visitors reach someone who can act and give that person enough information to respond.
Start with the reason someone is getting in touch
Visitors arrive with a problem or a question: a lost order, an access arrangement, a performance inquiry or a booking proposal. Organise the page around those reasons before listing staff roles or email addresses.
A few clear routes are usually easier to scan than a form packed with categories. Depending on what the organisation handles, they might include:
- Tickets and orders: missing confirmations, order changes, refunds and entry problems.
- Event information: set times, age policies, accessibility arrangements and venue entry.
- Bookings and professional inquiries: artist representation, performance proposals and production matters.
- Editorial or press: corrections, interview requests and media inquiries.
Those are examples, not a checklist. A small independent night may need one address and a clear note about ticket issues. A festival with separate ticketing, access and press teams may need distinct destinations. The test is whether someone can choose a route without knowing who sits behind it.
Use labels visitors recognise. “Order problem” is clearer to a ticket buyer than “customer success”; “Accessibility inquiry” says more than “Other.” If two categories could both fit, add a few words to distinguish them. For instance, does the booking route serve artists seeking shows, venues seeking an act, or both?
Send people to the team that can act
Every route needs an owner. If a separate provider handles ticket sales, say so beside the ticket option and explain what your team can resolve. If venue staff manage step-free entry while the promoter handles event-specific access requests, spell out the difference. A form that only tells someone later they contacted the wrong organisation wastes time they may not have.
Be equally clear about event-day help. Don’t label an inbox “urgent” if nobody checks it during doors. If the team answers only during set hours, show those hours and the time zone. Someone travelling to a show shouldn’t have to guess what “Friday afternoon” means.

Make the next step visible before asking for information
After choosing a topic, a visitor should see the next step immediately: email, form, a call during staffed hours or an existing order-help process. Several identical-looking buttons leading to the same general inbox only add confusion. If you offer more than one channel, explain the difference. A phone line might handle event-day entry questions, while email lets someone attach an order confirmation.
Show an email address in full rather than hiding it behind “Send a message”; someone may need to copy it into their mail app. A form can still be the main route, but visitors should know where the message goes and whether there’s another option if the form fails. Never publish a phone number without its staffed hours, especially for an international audience.
When an answer is already on the site, place a brief pointer beside the relevant route instead of sending people off to search. “For the announced door time, check the event page; for an order-specific entry issue, contact ticket support” makes the distinction clear. A published access page can answer general questions, but people still need a way to ask about their own circumstances.
Ask only for details that help resolve the request
Each form field should earn its place. Name, reply address, topic and message may be enough for a general inquiry. Ticket support might also need an order reference and event name; a press request might need a publication name and deadline. Requiring a phone number, home address or social profile from everyone creates extra work without necessarily helping the reply.
Use conditional fields where possible. A reader reporting an article correction shouldn’t have to choose a concert date. Someone asking about lost property may need to identify the venue and show, but should be able to describe the item without sharing unnecessary personal information. Tell visitors not to send full payment-card numbers, passwords or other private details you don’t need.
Keep field labels visible after typing begins. Placeholder instructions disappear when selected and are easy to forget, particularly on a phone. Mark required fields, explain unusual formats and put error messages beside the field that needs attention. “Enter an email address so we can reply” is more useful than “Invalid input.”
Decide deliberately whether to accept attachments. They can help with an inaccessible ticket or damaged merchandise order, but uploads may fail on a slow connection or reveal more information than needed. If you accept them, state the permitted file types and size limit. If not, explain how the team will request supporting material after the first message.
Write prompts that improve the first message
A short prompt can save a round of follow-up without turning the form into an interrogation. Beneath a ticket-issue message box, ask for the event name, order reference and what happened. For an access inquiry, invite the person to describe the arrangement they need without requiring a diagnosis. Leave room for circumstances the form designer didn’t anticipate.
Keep a general “How can we help?” option, too. Some questions won’t fit a menu, and a forced category can send them to the wrong team. If you offer “Other,” make sure it reaches a monitored inbox with someone responsible for redirecting messages.

Set expectations the team can keep
An acknowledgment isn’t an answer. After submission, confirm that the message was received, ideally with a reference number or a copy of the inquiry. If an automatic email follows, say whether replies to it are monitored. Otherwise, someone may send an important correction that nobody sees.
Response-time estimates should match how the team works. “We aim to reply within two working days” helps only if the team can usually meet it and visitors understand which days count. Event teams often work outside office hours, so a stated schedule with a time zone may be more accurate. Update the estimate during a busy festival period rather than leaving an old promise in place.
For time-sensitive issues, say whether the chosen route is monitored soon enough to help. If it isn’t, point to the channel that is, if one exists. Don’t imply that every question gets an immediate answer or promise a refund through a team that cannot approve one.
Make the page workable on different devices and connections
Someone may open the page while travelling, outside a venue or on a weak mobile connection. Essential routes and contact details should load without a large graphic, animation or embedded map. Give buttons clear text and enough room to tap; a cluster of tiny email links is easy to mis-hit.
Forms must work with a keyboard and assistive technology as well as touch and mouse. Associate labels with fields, keep headings in a logical order and make errors easy to find after submission. Don’t use colour alone to mark required fields or problems. A spam check shouldn’t shut out someone who cannot complete a visual or audio challenge.
For visitors travelling across countries, name the time zone for office hours and avoid unexplained local shorthand. Use an international dialling format if calls from abroad are welcome. If support is available only in certain languages, say so rather than assuming the site’s main language makes that clear.
Plan for ordinary technical failures. Without a success message, visitors may submit the form again because they don’t know whether it worked. Test it on a phone, on a slower connection and with incorrect input. Check that messages reach the intended inbox and arrive with enough information for staff to identify the topic.
Keep routes accurate as events and teams change
Even a well-written page fails when its details expire. Shared inboxes lose owners, ticketing partners change and temporary event-day numbers linger after an event. Assign someone to review the page when a new event goes live, a sales partner changes or staff roles shift.
Look at incoming inquiries for signs of friction. Ticket questions landing in the press inbox may mean the ticket route is hard to find. Repeated questions about door times may point to an unclear event page, not a missing form field. Duplicate submissions may mean the confirmation message isn’t appearing. Don’t assume every misdirected question is the visitor’s mistake.
Review privacy practices at the same time. Explain plainly how contact details will be used to answer an inquiry, and collect only what the team needs. If messages go to a venue, ticket provider or other event partner, make that handoff clear before someone submits personal details. Remove staff addresses that no longer reach the right people.
Then try a common request yourself. On a phone, start at the public contact page and report a missing ticket confirmation without relying on inside knowledge. Send only the requested details and follow the message into the team’s inbox. If the recipient can’t tell which event or order needs attention, fix that route’s prompt before the next show goes on sale.