The JetXBit Information System technical support email address is support@jetxbit.com.

To help us resolve your issue as quickly as possible, please follow these technical support guidelines.

1. Before contacting technical support, make sure you have reviewed the documentation available at https://wiki.jetxbit.com.

2. Verify that you are using the latest version of the application. In the Help → About program menu, the version numbers of the Information System and the database must match.
If your issue concerns the web application, ensure that your web browser is up to date.

3. Technical support specialists can rely only on the information provided in your request. Please describe the issue in as much detail as possible. A general description is usually insufficient.

4. The technical support specialist will continue communicating with you until all information required to resolve the issue has been collected. Please answer all follow-up questions. If any question is unclear or you are unsure what information is being requested, let the specialist know.

5. Do not include multiple issues in a single request. One issue — one request.

6. Include your company's ICAO code in the subject line.

7. Make the subject line as informative as possible.

Good: RSY. Error 3501 when opening the Airports directory.

Poor: Directory error.

8. Every request must include the minimum required information.

9. Describe the issue step by step and include screenshots. Do not omit any steps.
Screenshots should include all relevant information. Make sure that fields, Card File/directory/register names, and any other elements related to the issue are fully visible.

10. When describing the issue, try to answer the following questions:
- What result did you expect?
- What steps did you perform?
- What actually happened?

11. Attach any files that can be used to reproduce or verify the issue described in your request.

12. Specify what steps you have already taken to resolve the issue yourself and where you looked for a possible solution.

13. Describe the issue unambiguously to avoid misunderstandings. If an action can be performed in more than one way, specify the exact procedure that leads to the reported result.

14. Repeat the steps described in your request and verify that the issue can be reproduced.

15. Before sending your email, read your request again and make sure the description is clear, complete, and unambiguous.