A publisher following up on a licensing conversation and a player reporting a crash should not have to guess which option in an unlabelled inbox will reach the right person. Both need to contact the studio, but their messages call for different information and different handling. The contact page should make that clear before either person starts typing.
For a game studio, publisher or industry event organiser, the page may be the first stop after a conference introduction. It is also where applicants, journalists, accessibility researchers and potential partners turn when an earlier email thread goes quiet. It does not need to display every department. It needs to show visitors where to write and what to expect next.
Start with the routes people actually need
Say briefly who the page serves, then list the main types of enquiry. Base those categories on the messages that come in, rather than the organisation chart. A small studio can use one address and suggest subject lines; a larger company can offer separate routes without publishing every employee’s details.
- Business development and publishing: partnership proposals, licensing, distribution and introductions after industry events.
- Press and creators: interview requests, fact-checking questions, review-key enquiries and approved asset requests.
- Player support: account, purchase, technical and accessibility issues, preferably sent to a support system rather than an executive inbox.
- Careers: applications and recruitment questions, with a route to current openings if one exists.
- Event enquiries: meeting requests, speaking opportunities, sponsorship discussions and attendee assistance where relevant.
Do not add categories just to make the company look bigger. If two labels lead to the same team and ask for the same information, one may be clearer. On the other hand, a single “general enquiries” option can leave time-sensitive partner messages buried under support reports. Look through a sample of recent mail before settling on the labels.
Give each route enough context to work
Business and publishing enquiries
A partner does not need a full pitch template on the contact page. A few prompts can save an exchange of emails: company name, role, project title, proposed relationship, relevant platforms or territories, and a brief reason for getting in touch. Unless a deck or build is needed to assess a proposal, leave it optional at first contact. Large unsolicited attachments can be difficult to handle securely.
For introductions made at a networking event, ask senders to mention the event and whom they met. “We spoke about localisation after the publisher session” gives a shared-mailbox team more to work with than “Following up.” It lets a colleague find the intended conversation without guessing.
Be explicit about the scope of each route. A studio looking for publishing partners should not appear to invite developer submissions if it does not review them. An event organiser should separate partnership proposals from registration questions. Clear boundaries are more considerate than a form that accepts everything and answers little.
Press, player support and careers
Press enquiries should reach someone authorised to answer them. If the site has a press kit or a list of approved spokespeople, label it clearly so journalists do not have to request basic assets one by one. Say whether the team considers review-key requests, without promising keys or expecting coverage in return.
Support instructions should explain what helps with a report without prompting players to post sensitive data publicly. Useful details may include the game title, platform, version, region, steps to reproduce and an error message. Account and payment problems belong in the designated private support process. If the company publishes games with different age ratings, show the correct rating on each relevant game or support page rather than guessing at a single rating for the contact page.
For careers, point applicants to current vacancies and say whether speculative applications are reviewed. If portfolios are welcome, explain how to share them. Do not request sensitive personal information that is unnecessary at this stage. Where studios share a parent company, identify the hiring team that will receive the message.
Choose between an email address and a form deliberately
Email is easy to copy and forward, and people can use it with accessibility tools they already know. Making an address public can attract spam, though. A form can direct messages to different teams and collect consistent details, but it can also fail silently, reject legitimate enquiries or ask for too much. Neither format is automatically more professional.
If you use a form, require only what the team needs to reply and route the message. For many business enquiries, a name, email address, enquiry type and message will do; company and project fields can be optional. Mark required fields in text, not just by colour. Give fields clear labels, make errors readable and confirm when a submission has been received. Do not say a person has reviewed it when only the system has accepted it.
Set an attachment policy. If uploads are allowed, put accepted formats and size limits beside the control. A pitch document may be safer and easier to review through an agreed follow-up than through an unrestricted public upload. Never ask for passwords, account credentials or confidential deal terms in a first message.
Test the route end to end, not just the page’s appearance. Send a message from a phone and in a keyboard-only session. Check that errors make sense, the message reaches the intended mailbox and a reply can reach the sender. If a spam filter or consent tool blocks submission, the visitor needs to know why.
Set realistic expectations after submission
“We reply as soon as possible” tells visitors little. A narrower statement helps if the team can stand behind it: business enquiries might be reviewed on local working days, while player support has its own queue. Avoid a precise response-time promise without the staffing and process to meet it. Conference weeks, holidays and launches can change capacity.
Say whether an automatic acknowledgement will arrive, especially when a form gives senders no record in their outbox. If the team cannot reply individually to every proposal, say that too. Established partners still deserve a response, but first-time senders need a basis for deciding when to follow up. Define what counts as urgent and provide a suitable channel; simply labelling an ordinary mailbox “urgent” does not help. Security vulnerability reports, for example, should not go to a public comment thread.
For global deals, an operating time zone helps with meeting requests. Let people suggest more than one meeting window, without publishing staff calendars or implying that every request will be accepted.
Show who is receiving the message
A legal company name, a city or country, and a brief description of the team behind the page help visitors check that they have found the right organisation. This matters when a studio name resembles a game title or an event has multiple editions. Keep the details consistent with other public materials; unexplained differences make even a legitimate contact route harder to trust.
Named contacts can help in public-facing roles such as press or partnerships, provided someone keeps the details current. A name belonging to someone who left six months ago is less useful than a well-managed shared inbox. Publish direct staff details with permission, and consider whether a role-based address will survive team changes.
For an annual networking event, make clear whether the visitor is writing to the event team, its host company or a participating studio. A publisher arranging a meeting and an attendee asking about an invitation need different recipients. Claims on the page should match how the organisation actually works, a principle that also underpins how game studios build a trustworthy online reputation.
Handle privacy and access as part of the page
Explain briefly who receives submitted information, what they use it for and where visitors can find the applicable privacy information. Do not use a vague consent checkbox as permission for unrelated marketing. If there is a newsletter invitation near the form, keep it separate from sending an enquiry.
Ask only for information the recipient needs. A potential partner may volunteer a company website; a player seeking support should not have to provide an employer. Recruitment messages may contain personal data, so access should be limited to those involved in hiring. Check retention practices and any mandatory notices against the organisation’s real operations and applicable requirements, rather than copying another site’s wording.
Accessibility has an immediate purpose here: visitors need to identify fields, understand errors and submit the form with a keyboard or assistive technology. Offer another contact method if the form is unavailable or cannot accommodate a request. Make the page readable on a narrow screen, too. A conversation started on a conference floor may continue from a phone minutes later.
Keep the details current
Contact pages age quietly. Staff move roles, support providers change, and an event inbox can stop being monitored. Give someone ownership of regular checks and review the page after organisational changes. Check the visible copy, form delivery, automatic replies and mailbox access. A shared inbox with no assigned reviewer is not a working contact route.
Incoming mail can reveal what the page fails to explain. Repeated requests for approved press assets may mean those resources are hard to find. Players writing to partnerships may mean support is hidden. Broad enquiry categories and misroutes are enough to guide changes; the team need not retain every message’s contents for analysis.
Before the next industry event, send a test message through the partnership route and trace it to the person responsible for replying. Check the confirmation, mailbox subject line and reply address. Fix any break in that chain before putting the page on a business card or event profile.
