A reader wants to know if a cassette is still available. A musician wants to send a recording. Someone else has spotted a wrong credit. If the contact page gives all three the same unexplained form, it has left them to work out the publication’s filing system for themselves. Show the routes before asking anyone to write.
At an independent music site, messages may come from listeners, artists, labels, venues, photographers, or readers revisiting an old post. Some need a reply; others simply need to reach the right person. Clear instructions help senders include useful context and keep the editorial inbox from turning into a heap of unlabelled files and requests.
Start with the reasons people actually write
“Get in touch” is friendly, but it doesn’t tell anyone what to do. Near the top of the page, name the kinds of messages the site actually receives: corrections, music submissions, event information, permission requests, and general questions, for instance. There’s no need to invent a category for every possible inquiry.
Give each route a little direction. “Corrections: include the article title, the passage in question, and a reliable source if you have one” is much more useful than “For corrections, contact us.” For submissions, say whether unsolicited music is welcome and what works best at first: a streaming link and a short description, perhaps, with downloads sent only if requested. Otherwise, someone may send a huge attachment to a mailbox whose limits they cannot know.
Separate routes do not require separate mailboxes. One address and suggested subject lines may be enough for a one-person publication. If you offer both email and a form, explain when to use each; an unexplained choice is just another small obstacle.
- Correction: identify the post and the specific claim or credit.
- Music submission: provide the artist or project name, a listening link, and relevant release information.
- Event notice: include the date, location, participants, and someone who can confirm the details.
- Permission request: specify the image, excerpt, or recording and its intended use.
- General question: use this when none of the other routes fits.
These are prompts, not conditions for writing. Someone reporting a broken credit should not be turned away because they lack documentary proof. The point is to make the first message useful, not to make it difficult to send.
Make the contact method easy to find and understand
Call the navigation item “Contact.” An atmospheric label may appeal to regular readers, but everyone else has to guess what it means. On the page itself, put the contact method before a long account of the publication. A sentence saying who receives messages is helpful; another site biography is not.
If email is the main route, print the address as readable text. An address embedded in an image is hard to copy and may be inaccessible to people using assistive technology. A clickable mail address is convenient, but readers using webmail or another application still need to see what they are copying. If the site uses a form instead, say which person or team receives it. A button labelled “Submit” does not answer that question.
Social messages may work for a quick exchange, but they are a poor default when the record matters. Permissions, correction evidence, files, and detailed pitches are easier to track in email or a properly configured form. If nobody monitors direct messages for editorial requests, say so. One dependable address is better than a list of unattended channels.
Use labels that survive outside the page layout
Give every form field a visible label: “Your email address,” “Subject,” “Message.” Placeholder text vanishes as soon as someone starts typing, and it can be easy to miss. Visible labels also help people using assistive technology understand what belongs in each field. Mark required fields up front rather than revealing them through failed submissions.
A general form may need only a reply address, a subject or category, and the message. A name or preferred form of address can help, but it need not be mandatory: a reader correcting a credit should not have to disclose a legal name. Ask for a phone number, postal address, or organization only when there is a real reason to collect it.
Keep music submissions workable for both sides
Submissions expose vague instructions quickly. A musician sends a folder of high-resolution audio because the page never said a listening link would do; an editor receives a bare streaming URL with no credits, context, or way to reply. A short submission note can prevent both without dictating how anyone should pitch their work.
Describe what the publication can consider. A site covering Japanese experimental and underground music can state that scope plainly without treating genres as fixed boundaries. Noise, ambient, drone, electroacoustic work, field recordings, and cassette projects often overlap. What senders need to know is whether unsolicited releases or project news are welcome—and that sending material does not guarantee coverage.
For a first message, request a listening link that works without an account, a few lines about the work, and any known credits or release details. If the release is not public, ask the sender to flag access restrictions or an embargo. A private link is not permission to publish unreleased audio, artwork, or personal correspondence. Downloads can be arranged later if an editor needs them.
Be candid about follow-ups. “One follow-up after two weeks is fine; we cannot reply individually to every submission” helps only if the site can keep to that timeframe. A volunteer-run publication may be better off saying that submissions are reviewed as time allows and that silence is not an artistic verdict. Describe the process you have, not an attentive review system you wish you had.
Tell senders what happens next
After someone presses send, the form should clearly confirm that the message arrived and say whether a reply is likely. If submission fails, the error should explain why without wiping out what they wrote. Keep an email address available as a fallback if the form goes down.
Set response expectations according to the work involved. An urgent correction to a misidentified performer may be handled sooner than a release announcement. Do not say a mailbox is checked daily unless it is; do not let a cheerful automatic acknowledgement imply that everyone will receive a personal reply. If replies are not guaranteed, say so.
An automatic receipt need not quote the entire message, which could contain private information. It can confirm the chosen category and include a reference number if the system produces one. Where there is no receipt, the confirmation on the page matters even more: people need to know the form worked.
Reduce friction without collecting too much
Every field asks for another decision. A dropdown can help sort mail, but a long menu of narrow categories makes visitors guess how the editorial desk works. Leave room for “General question” or “Other,” and let the message explain the rest. A free-text subject may suit the person reading the inbox better than a category menu.
Be especially careful with uploads. File-size limits, security risks, and slow connections can all cause trouble. A correction may need only a link to the article and a written explanation; a music submission usually needs a listening link before it needs an archive. If uploads are necessary, state the accepted file types, size limit, and whether anyone outside the receiving team will see the file. Do not request sensitive documents through a general contact form without a defined need and a secure way to handle them.
Add a short privacy note covering who reads messages, why contact details and messages are kept, and whether they are shared. “Your information is completely secure” is not a credible promise for an ordinary contact channel. If a third-party form service or spam filter handles the message, the privacy information should reflect that. People should know who will receive their words before they send them.
Check the form as a sender would
Test whether a message can be completed, not just whether the page looks tidy. Open it on a narrow screen, move through it with a keyboard, and send a test message all the way to the confirmation. Enlarge the text and check that labels, instructions, and errors remain visible. Try a long email address and several paragraphs of text. If you omit a required field, the error should point to it and say what needs fixing.
Then check the inbox. Did the full message arrive with its reply address and chosen category? Has the form placed the sender’s address in a field that causes delivery problems? Did a spam challenge block the test? A page can look effortless while silently losing mail. Test again after changes to a form plugin, email provider, or spam setting—and when someone says they wrote but never heard back.
Maintain the page as part of editorial work
Contact details go stale without much warning. An inbox is retired, a contributor leaves, or the site pauses review copies. Update the page when the practice changes. An old invitation wastes a musician’s time; an abandoned permissions address delays a legitimate request. Put someone in charge of checking the page, even if the whole publication is run by one person.
Incoming mail can reveal where the instructions fail. If several people ask whether private streaming links are acceptable, answer that on the page. If correction messages regularly lack the article URL, ask for it beside the correction route. Repeated confusion is a clue about wording or placement, not a reason to blame senders.
Before publishing an update, test every active route. Send a correction with a subject such as “Credit correction: [article title]” and a short passage in the body. Check that it reaches the right inbox with the subject and text intact, then clear it from the queue so nobody mistakes it for a real correction.