What to Include in a Tech Request Email to Gamers Beat Cancer
Start With a Clear Subject Line
Your subject line is the first thing the Gamers Beat Cancer team sees, so make it count. A vague subject like "Help" or "Question" slows everything down because it does not tell anyone what the request is about or how urgent it is.
Use a format such as "Tech Request: [Your Name] – [Short Summary]" so the team can sort and prioritise your message at a glance. If your request relates to a live event, a streaming setup, or a fundraising page, say so in the subject line itself.
Introduce Yourself and Your Connection
Explain who you are and how you are connected to Gamers Beat Cancer. Are you a fundraiser, a streamer, a volunteer, or a partner? This context helps the team understand the scope of your request without needing to ask follow-up questions.
Include your preferred contact details, such as an email address or Discord handle, and mention the best times to reach you. If you are representing a group or a studio, name the organisation and your role within it.
Describe the Request in Detail
State exactly what you need. Whether it is technical support for a charity stream, access to a fundraising tool, or advice on integrating donation alerts, be specific about the outcome you want.
Break the request into bullet points so nothing gets lost in a long paragraph. For example:
- What platform or software you are using
- What you have already tried
- What error message or blocker you are seeing
- What deadline you are working towards
If your request involves multiple steps, number them in the order you need them completed. This makes it easier for the team to assign the right person to each part.
Include Relevant Screenshots and Links
A screenshot or a link can save several back-and-forth emails. If you are reporting a bug, capture the error message and the steps that led to it. If you are asking about a page on gamersbeatcancer.co.uk, paste the exact URL.
Use a simple table to organise supporting details such as device, browser, and account type:
| Item | Details |
|---|---|
| Device | Windows PC |
| Browser | Chrome 124 |
| Platform | Twitch |
Attach files only when they are safe to share, and avoid sending sensitive personal data unless the team has asked for it through a secure channel.
Set a Timeline and Say What Happens Next
Tell the team when you need a response and what will happen if the request is delayed. A realistic deadline helps them plan, while an unrealistic one can create unnecessary pressure.
"The clearer your request, the faster we can help you get back to gaming for good."
Finish by confirming what you will do next, such as testing a fix or sending more information. A short closing line like "I am happy to jump on a call if that is easier" keeps the conversation moving.
Finally, review your email before sending. Check that every question is answered, every link works, and every attachment is included. A complete request means fewer delays and more time spent supporting the cause.