📝 How to write a support request in JITBIT?Here are a few tips on how to write and structure your request so our team can handle it as quickly and efficiently as possible.
🎯 The goal:
Help our team spot the issue, reproduce it, and locate it precisely : so we can deliver the most effective fix.
✅ What we need from you:
- A clear, factual, and detailed description of the issue
Please describe what happened without interpreting.
❌ Avoid vague messages like “It crashed” — they don’t give us enough to work with.
💡 Instead, try something like: “When I click the 'Start' button on a hike, nothing happens. There’s no error message.” or “I’m experiencing the same issue on these two variant routes.” - A list of actions you’ve already tried
Let us know what steps you’ve taken to solve the issue.
For example: “I clicked Refresh,” “Pressed CTRL+R,” or “I exited the trip, deleted the app, and reinstalled it.” - Any error messages displayed
If there’s an error message, copy it exactly. If you can send us a screenshot, it's even better !
- Essential technical information
For the app:
- Device type (Android or iOS)
- App version (make sure it’s the latest one)
- Name of the trip and the name of the route where the issue occurred
For the web:
- Browser used (Chrome, Firefox, Safari, etc.)
✨ Tips to write the perfect demand:
- Be precise and detailed
The more detail, the better - Stick to the facts
Describe exactly what you see, not what you think is happening
- Use specific terms
Avoid words like "it" or "the window" if it's not clear what they refer to.
💡Prefer : "When I click on the 'Start' button..." rather than "When I click on it" - Test your own steps.
If you’ve listed a process to reproduce the bug, re-read it and try following it. Is everything clear? Nothing missing? - Add screenshots or a short video 🎥
Visuals often make it much easier for us to understand what’s going on.
🚀 In short:
The clearer and more complete your request, the faster we’ll be able to help you.
To understand what’s going wrong, we need to know exactly when and where things are getting stuck. An app is like a big machine with many moving parts : without clear input, we’re looking for a needle in a haystack.
A great report gives us the best chance to fix things efficiently and quickly!
🙏 A big thank you for your help and support!
Mhikes Team