How to Write a Contact Page for a Music Publication or Events Site

An editor sorts incoming music event messages

A festival visitor with an accessibility question should not have to guess which inbox to use. Neither should an artist pitching a show have to wonder whether the general address also takes editorial submissions. A good contact page tells people where to write, what to include and what sort of reply they can expect.

For a music publication or events platform, messages may come from readers, performers, promoters, photographers and venues, as well as people reporting errors in listings. You do not need a separate process for every sender. You need clear routes for the common requests, without asking anyone to disclose more than necessary.

Give each type of message a clear route

Look at recent messages and group them by the work they create. A publication might need routes for editorial tips, event listings, factual corrections, rights requests and general questions. A venue might put booking, ticketing, accessibility and lost property first. Choose categories someone actually handles. One reliable address is better than a menu of departments that do not exist.

Describe each route in ordinary language. “Send an event for coverage” is clearer than “Partnerships.” If one inbox covers several topics, say so: “For listing submissions and corrections, email our editorial team. Put ‘Correction’ or ‘Event submission’ in the subject line.” Staff can sort those messages without asking visitors to decipher an organization chart.

Keep time-sensitive corrections easy to find. A wrong door time or outdated venue address may need attention sooner than a release sent for consideration. If corrections have their own route, place it near the top and ask for the affected page, the detail that appears wrong and a source or firsthand explanation. Do not suggest the inbox is monitored around the clock unless it is.

An editor sorts incoming music event messages

Put essential answers before the form

Before inviting a message, explain what the organization can answer. An independent music magazine may not sell tickets, set entry policies or manage artist bookings. A short note can point people to the ticket seller, organizer or venue named on the relevant event page, without implying the magazine can resolve the issue itself.

Put answers to recurring questions beside the relevant contact route. Are event submissions considered? Is unsolicited music accepted? Can anyone guarantee coverage? “Submissions are considered but may not receive an individual reply” is more useful to an artist than “Get in touch!” If submissions are not reviewed, say so rather than collecting them.

Separate corrections from change requests, too. A reader saying a published date is wrong is flagging a possible editorial error. An organizer asking to replace a description or promotional image is requesting an update that may need verification or an editorial decision. Clear labels help both messages reach the right person without giving up editorial checks.

Tell senders what makes a message actionable

A few prompts can make messages easier to act on without turning the page into an application form. Ask for details that fit the request:

  • Event submission: the event name, city, venue, date, lineup or program, and a place where those details can be independently confirmed.
  • Correction: the page title or URL, the disputed text, the proposed correction and supporting information.
  • Editorial pitch: the story angle, why it matters to readers and whether the material is exclusive or under embargo.
  • Rights inquiry: the work in question, where it appears and the sender’s relationship to it.

Treat these as guides, not entry requirements. Someone should be able to report a wrong address without knowing the exact page URL. A rights holder should not have to upload identity documents through a general form. Collect only what is needed to route or assess the message.

Choose a form that works on a phone

A form is useful if it feeds into a managed workflow. Otherwise, it may fail without warning, hide a more convenient email address or demand details the sender does not have. If the form is the main contact method, keep required fields to a minimum: a reply address, a topic and a message are often enough. Ask for an event date or article URL only when the chosen topic calls for it.

Use labels that remain visible after someone starts typing, rather than placeholders that disappear. Give the button a specific label, such as “Send message,” and show a confirmation after submission. Confirm receipt, not a guaranteed answer. If something goes wrong, explain the error and preserve the typed message where possible.

Try the form with a keyboard and on a narrow screen. Check the focus order, make sure errors identify the field that needs attention, and do not rely on color alone to convey information. Captchas can shut out legitimate senders when they are difficult to see or hear. If spam protection is needed, choose the least obstructive option available and test it with real users.

An email address is a useful alternative, particularly for attachments or people who prefer to use assistive technology with their email client. If you accept attachments, say which kinds are appropriate and whether a size limit applies. If you do not, ask people to describe the material in their first message. Do not request large audio files or private download access by default; a short description may be enough to identify the right reviewer.

Set honest expectations for replies

“We’ll get back to you soon” tells a sender little. A firm deadline is worse if the team cannot meet it. If you have a dependable response window, give it with the relevant time zone and say whether weekends and holidays count. Otherwise, explain which messages receive replies: corrections might be acknowledged, for example, while unsolicited pitches might not be.

Time zones matter to an international music audience. A submission sent from Tokyo to an editorial team elsewhere may arrive outside working hours. Naming the team’s working time zone helps explain a delay without implying that a change to tomorrow’s event will be checked in time. If you accept messages in multiple languages, list only those staff can reliably read and answer; do not promise translation support you do not have.

Keep automatic replies short. They can confirm receipt, repeat the selected topic and provide a reference number if one exists. Avoid echoing sensitive details into an email that could be forwarded or viewed on a shared device. For an imminent event, the reply can also say that real-time verification of changes is not guaranteed.

Make the destination trustworthy

People should know who receives their message. Name the publication, venue or organization, and identify the inbox by function if no individual staff member is a stable contact. Listing a person can help a small team, but only with that person’s agreement and a plan to update the page when responsibilities change.

If the site publishes event guides but does not organize the events, distinguish editorial inquiries from operational ones. Admission, refunds, age restrictions and access arrangements are often matters for the venue, organizer or ticket provider. Explain that boundary without leaving readers to hunt for a contact: when an event page names the responsible party, direct them to those published details rather than suggesting one universal address.

Messages about access needs, harassment concerns or disputes may contain personal information. Add a brief note, consistent with the site’s actual privacy practices, explaining why contact details are collected, who can see submissions and how long they are kept. Do not ask for medical details just to route an accessibility question. Make clear that a publication inbox is not an emergency channel for immediate safety concerns at an event.

A visitor writes a question from their phone

Keep contact details aligned with the rest of the site

A contact page cannot make up for an event listing that omits the organizer or a booking page that leaves basic terms unexplained. Repeated questions can reveal those gaps. Check the page where people first needed the answer. The guide to writing music service pages that answer booking questions deals with that earlier step; the contact page should handle questions that need a conversation.

Review the page when staff roles, submission policies or event operations change. Send a test message through every form route, check that it reaches the intended inbox and read the automatic reply. Check the page on a phone and a desktop, including whether the email address is easy to copy. Remove old addresses instead of leaving them alongside new ones without explanation.

For a final check, take a real, anonymized message that landed in the wrong inbox and try routing it using only the published page. If a request to correct a festival listing still looks like an editorial pitch, rename the options before adding more instructions.

Related posts