How to Write a Contact Message the Organisers Can Answer Quickly
Start with the right subject line
Every message to the MS Hackathon organisers lands in the same inbox as hundreds of others. The fastest way to get a useful reply is to make your subject line self-explanatory. A subject like "Question" or "Help" tells us nothing and often gets buried. A subject like "Round 2 submission link broken for team Nova" tells us exactly what to open first.

Treat the subject line as a label, not a greeting. It should contain the round, the topic, and the action you need. If you are unsure which round you are in, say so honestly and add your team name. That single detail saves an entire back-and-forth exchange.
Name your round in the first line
The MS Hackathon runs in multiple rounds, and each round has different rules, deadlines, and support channels. If you do not name your round, the first reply you get will probably be "Which round are you in?" That wastes a day. Put the round in the first sentence of the body, even if it is already in the subject line.
Use the exact round name shown on the website, for example "Round 1" or "Final Round". Avoid vague phrases such as "the first part" or "the current stage". Clear naming helps the organisers route your message to the right volunteer.
Mention the post title you are asking about
Many questions are about a specific update, rule, or announcement. If your message refers to a post, copy its title exactly as it appears. Write the full title instead of a paraphrase. This lets the organisers find the context in seconds.
For example, instead of "the rules page", write "the post titled 'Submission Checklist for Round 2'". If the post has a date, add it. If you are replying to an email thread, keep the same subject so the history stays together.
Flag partner enquiries in the first line
Partner, sponsor, and press enquiries follow a different path than participant questions. They should not wait in the same queue. Put the words "Partner enquiry" at the very start of your first line, before any greeting. Then state your organisation and what you are proposing in one sentence.
This is not about being formal. It is about being sortable. A message that begins with "Partner enquiry: Acme Labs would like to sponsor the final round" can be forwarded immediately. A message that begins with "Hi, I have a question" cannot.
Use a simple structure
A short, structured message is easier to answer than a long paragraph. Use a numbered list for multiple questions and a table when you compare options. Keep quotations short and relevant.
"The clearer your first line, the faster we can help."
Follow this checklist before you press send:
- Subject names the round and the topic.
- First line repeats the round.
- Post titles are copied exactly.
- Partner enquiries are labelled at the start.
- One question per numbered item.
If you have several items, order them by urgency:
- The issue blocking your submission.
- The question about rules or deadlines.
- The optional request for feedback.
| Message type | First line should include |
|---|---|
| Round question | Round name and team name |
| Post question | Exact post title |
| Partner enquiry | "Partner enquiry" and organisation |
Finally, include your team name and a contact address. Do not send follow-ups within 24 hours unless the deadline is imminent. A clear, well-labelled message is the fastest route to an answer.
