Support

What support covers

Most help requests fall into a few practical buckets: progress or stats not updating, a lesson feeling too hard or too easy, keyboard layout confusion, mobile scrolling or focus issues, accessibility problems, broken navigation, or a question about which lesson should come next.

Because TypeForge is local-storage based and browser-personalized, the strongest support questions are usually about user context rather than server-side failure. The useful answer often depends on which page the learner visited, which device they used, and which practice mode they were running.

The fastest triage path

1. Confirm the route you were on — lessons, practice, stats, academy, games, or blog.
2. Check whether the problem is mobile-only, desktop-only, or affects both.
3. Note the exact lesson or mode, such as home row, finger placement, numbers, or speed.
4. Describe the expected behavior and the actual symptom in one short message.

If the request is about learning rather than a technical bug, the support page should lead the user to the relevant learning path instead of sending them in circles. That distinction is important for trust and for building a real educational product.

Recommended resources

• FAQ for short self-service answers about privacy, use cases, and practice habits.
• Contact for direct questions and detailed bug reports.
• Academy hub to find the right learning path for a learner’s current stage.
• Editorial Policy for content quality expectations and learning-value standards.

What a strong support response should include

Good support answers do more than confirm receipt. They should explain what likely caused the issue, whether the user needs to retry on a different route or browser, and which educational resource can help them continue practicing without losing confidence.

That model matters because the website is not just a utility app. It is a learning system. When a learner gets stuck, they need a practical next step, not a generic “sorry.”