1. How to reach us
Email is, for now, the only support channel, and it is used for every type of request: questions, incidents and service requests. There is no phone line or chat.
- Write to support@i9xperformance.com from the email address of your account, so we can see your plan without asking.
- One request per email. If you have two different problems, send two emails: each one gets its own answer and neither waits for the other.
- Reply in the same thread to add information. A new email about the same problem starts a new request.
2. Response times by plan
| Plan | Channel | First response |
|---|---|---|
| Trial | No set time: answered as soon as possible, after the paid plans | |
| Starter | Within 96 hours | |
| Pro | Within 72 hours | |
| Business | Within 48 hours | |
| Enterprise | Within 24 hours, or as set in the contract |
- Calendar hours. Times are counted every day of the week, weekends and public holidays included, from the moment your email reaches us. The reference time zone is US Central Time (CT), the closest to Mexico City; any time or date we quote is in that zone.
- A first response is a real answer from a person who has read your request: the solution, an explanation, or the next step and exactly what we need from you. An automatic acknowledgement does not count.
- It is not a resolution time. Some problems are solved in the first reply; others need a fix in a new version of the application. When that happens we tell you, and we keep you informed in the same thread.
- The plan that counts is the one active on the account the email comes from. An email from an address that is not linked to an account is answered as Trial until we can identify the account.
- These are targets, not guarantees. As the plans, credits and billing agreement states, missing one does not give a right to a refund, credits or compensation. An Enterprise contract may set a service level agreement with its own terms, and that contract prevails.
3. What is answered on every plan
Some requests do not depend on the plan and are answered on every plan, the trial included, within the time limits set by law or by our own policies:
- Privacy requests: access, correction, deletion and the other rights described in the privacy notice.
- Charges, refunds and cancellation, under the refunds and cancellation page. The next section explains where each payment question goes.
- Reports of a security problem in the service, and account deletion.
4. Payment support
For assistance with charges, payments and refunds. Paddle, our reseller, is the Merchant of Record: it charges your payment method, issues the receipt and processes refunds, so the charge on your bank statement usually appears under Paddle's name rather than ours. We never see your card details.
- Receipts, invoices or a charge you do not recognise — look up the order at paddle.net with the email you paid with, or write to us. A duplicate or erroneous charge is always refunded.
- Cancelling or asking for a refund — you cancel the renewal from your account; the refund window and its exceptions are on the refunds and cancellation page.
- A charge that failed — use the link in the email about the failed payment to update your card. Your plan stays active while Paddle retries the charge.
- Anything else about a payment — write to support@i9xperformance.com from your account email, with Payment in the subject and the order number from your Paddle receipt. It is answered on every plan, the trial included.
5. Types of request
Put the type in the subject: it lets us route the request to the right answer from the start.
- Question — how to do something, or what a result or a chart means. Suggestions for new features are welcome as questions; they get a first response in the same time, but no commitment to build them.
- Incident — something does not work as described: an error, a crash, a figure that looks wrong, a licence that does not activate, or you cannot sign in.
- Request — something we have to do for you: a licence, an account change, a plan change, a receipt, or a copy or deletion of your data.
6. How to write your request
The template starts like a user story — who you are, what you wanted to do and why — and then describes what happened. With that we can usually answer in the first reply instead of asking questions back. Delete the lines that do not apply.
Subject: [Plan][Question|Incident|Request] Short summary Plan: Trial / Pro / Business / Enterprise Type: Question / Incident / Request Edition and version: desktop or online, app version Operating system: As a: (your role, e.g. QA lead) I wanted to: (what you were trying to do) So that: (what you needed to achieve) I expected: (the result you expected) What happened: (the actual result, with the exact error message) Steps to reproduce: 1. 2. 3. Attachments: (screenshots; result files only if they hold no sensitive data)
Example subject: [Enterprise][Incident] The Gantt chart is empty after loading a 2 GB JTL file. If the request does not include what we need, our first response may be to ask for it.
7. When a figure looks wrong
A figure is checked by reproducing it. We load the same data with the same filters and the same percentile estimator, and compare the result with an independent calculation — a spreadsheet or a statistics library that shares no code with the application. For that, the incident needs:
- The result file, or an anonymised excerpt of it that still gives the wrong figure.
- The filters you applied and the percentile estimator selected in the settings.
- The figure you see and where you see it (tab and chart), and the value you expected and where it comes from.
The answer is one of these:
| What we find | What it means |
|---|---|
| Our figure differs from the independent calculation by more than the rounding shown. | A defect in the application. We confirm it, tell you whether there is a way around it, and fix it in a new version. |
| Two views of the application show different values for the same metric, data and filters. | A defect in the application, handled the same way. |
| Rows were left out of the analysis without the application saying so. | A defect in the application, handled the same way. |
| The figure differs from another tool, such as JMeter's own report, because that tool uses a different estimator. | Not a defect. Both figures are correct for their method; we tell you which estimator gives the same result as the other tool. |
| The file is truncated or incomplete, your plan's row limit applies, the figure was read while the test was still running, or the result is simulated. | Not a defect. These cases are explained in the terms and conditions. |
8. What support covers
- Installing, activating and updating the application, and signing in.
- Using the features included in your plan, and understanding what a chart, an indicator or a report shows.
- Your account, your licence, your plan, your credits and your charges.
- Defects in the application: we confirm them, tell you whether there is a way around them, and fix them in a new version.
Support does not cover designing or running your load tests, performance consulting on your own systems, problems of the system you are testing, or Apache JMeter itself. How you use the dashboard and what you conclude from it remain your responsibility, as the terms and conditions explain.
9. What not to send
- Never send your password. We will never ask for it.
- Result files can contain host names, URLs, tokens or personal data. Remove or anonymise them before attaching a file, or send only the lines that show the problem.
- Sending a result file is always your choice. We use it only to reproduce your case, and we delete it once the case is closed.
- Support messages and their attachments are kept as described in the privacy notice.
10. Changes to this policy
We may update this policy, for example to add a new support channel. A change that makes the response time of your plan longer is announced by email beforehand and applies from your next renewal; a change that makes it shorter applies as soon as it is published here.