Users who need help can quickly contact us hearthstats.net for support. The page lists email, a web form, and social handles. The guide explains which method to pick and what details to include. The guide shows simple steps to speed a reply. The guide avoids jargon and gives clear actions.
Key Takeaways
- Contact HearthStats.net support via email, web form, or social channels depending on your issue type for efficient assistance.
- Use the official web form for account or match log issues, including clear problem descriptions, relevant screenshots, and proper categorization.
- Send direct emails for privacy requests or when attaching multiple files, ensuring concise, focused messages with clear subject lines.
- Include detailed information like account ID, app version, timestamps, and reproduction steps to accelerate problem resolution.
- Perform basic troubleshooting like restarting the app or clearing cache before contacting support to potentially resolve issues faster.
- Expect responses within two business days during support hours, and follow escalation procedures if no reply is received after three days.
Primary Contact Methods — Email, Web Form, And Social Channels
HearthStats lists three main ways to contact support. Users can send a message through the official web form. Users can send a direct email to the support inbox. Users can reach out on the site’s supported social channels. The web form suits account issues and match logs. Email suits file attachments and privacy requests. Social channels suit quick questions and outage reports. When a user wants a record, they should use email or the form. When a user needs a fast status update, they should try social messages. The site recommends one clear contact method per issue to avoid confusion.
How To Use The Official Contact Form Effectively
The form asks for name, account ID, and a short description. Users should state the problem in one clear sentence. Users should attach screenshots when relevant. Users should choose the right category from the dropdown. Users should set priority only if the issue blocks play. Users should include timestamps or match IDs for data errors. Users should avoid sending long logs in the message field. Users should use email for large attachments and keep the form concise. A clear form entry speeds diagnosis and leads to a faster reply.
Direct Email And When To Use It
Users should email support for privacy requests and file uploads. Email allows multiple attachments and extended logs. Users should add subject lines that summarize the issue. Users should paste short reproduction steps in the message body. Users should reference any form submission ID if they already used the form. Users should avoid vague phrases and list exact error messages. Users should keep each email focused on one problem. Clear emails help staff assign the right engineer and fix issues faster. Staff respond faster to focused, well-documented emails.
What Information To Include For Faster Resolution
Users should include the account ID and platform. Users should list the app version or browser and exact timestamps. Users should state the expected result and the actual result. Users should include match IDs or log excerpts for game data errors. Users should attach screenshots or short videos for UI bugs. Users should name the steps to reproduce the issue in order. Users should add the ticket or form ID if they already contacted support. Users should note recent changes like updates or reinstalls. Clear and specific facts reduce follow-up questions and shorten resolution time.
Expected Response Times, Support Hours, And Escalation Path
Support aims to reply within two business days for standard requests. Critical outages get priority and faster replies. Support operates Monday through Friday on normal hours. Users should tag messages as urgent only for true outages. If a user does not get a reply in three business days, the user should send a follow-up. If the follow-up fails, the user should request escalation and include the original ticket ID. The escalation path moves a ticket to a senior agent. The site logs each escalation to track progress. Users who provide clear initial details see faster escalations.
Troubleshooting Steps To Try Before Contacting Support
Users should restart the app or reload the browser first. Users should clear cache and cookies when they see display errors. Users should update the app to the latest version before reporting bugs. Users should test the same action on another device to confirm the issue. Users should export match logs when the stat data looks wrong. Users should check the status page or social feed for known outages. Users should gather screenshots and timestamps before contacting support. These steps often fix simple problems and speed support when a report still needs escalation.
Privacy, Data Handling, And What Happens After You Send A Message
Support logs each incoming message and links it to the account. Staff use the provided details to reproduce and fix issues. Staff redact sensitive fields when they store screenshots. Users can request account data or deletion through email. The site follows standard terms and legal notices similar to public service pages and terms documents. For example, the MLB site lists its [terms of use] (https://www.mlb.com/official-information/terms-of-use) that show how a large sports site handles web terms. After a user sends a message, staff confirm receipt and provide a ticket ID. Staff update the ticket with progress notes until closure.
