How to Submit a Feature Request to IZI
How to Submit a Feature Request to IZI
Section titled “How to Submit a Feature Request to IZI”Most features in IZI exist because a club described a concrete problem clearly. The submission channel is open to every club at no cost — no support tier, no minimum clubs in network. You can send a request through the in-app form (Help → Suggest an idea) or by emailing feedback@izi.is. A well-structured request reaches the product team faster and is easier to prioritise. Response time is up to 10 business days; during quarterly roadmap planning it may be longer.
How to write a request that gets heard
Section titled “How to write a request that gets heard”A vague request is hard to act on. A concrete one is easy to scope and prioritise.
Weak example: “Add tournaments.”
Strong example:
- Task: we run weekly CS2 tournaments with 20–40 registrations. Right now we track sign-ups in a spreadsheet — it costs us 2–3 hours per event.
- Current workaround: manual spreadsheet plus a third-party bracket site; we then enter winners into IZI manually to issue prize credits.
- Ideal flow: create a tournament inside IZI, players register through the client app, results are recorded automatically and converted to bonus balance.
- Scale: 3 clubs in our network, all with the same need.
The more specific the problem, the easier it is for the IZI team to understand the value and design the right solution — not a feature that looks different from what you actually needed.
Submission channels
Section titled “Submission channels”In-app form — recommended. Navigate to Help → Suggest an idea. The form guides you through the required fields so the request arrives structured and ready to triage.
Email. Send to feedback@izi.is for longer descriptions where you want to attach screenshots, flow diagrams, or spreadsheet exports. Include the same four points as above: task, current state, desired state, and number of clubs affected.
Your IZI account manager. If you have a dedicated manager, you can walk them through the request verbally. They will log it internally in the same queue.
What happens after you submit
Section titled “What happens after you submit”- Your request enters the shared idea backlog.
- The product team groups similar requests from different clubs — a pattern across 10 clubs weighs more than a single request.
- Prioritisation happens once per quarter during roadmap planning.
- You receive a reply: accepted into roadmap / not accepted with reason / existing feature that already covers the need.
Response time is up to 10 business days. During quarterly planning cycles the team is heads-down on prioritisation, so replies may arrive at the end of that window.
If your request is not accepted
Section titled “If your request is not accepted”Not accepted does not mean “never.” Common reasons:
- Existing feature covers it. IZI already has a tariff or workflow that solves the task — the team will explain how to use it.
- Too niche for the current investment threshold. If more clubs report the same need, the calculus changes. Ask your manager to flag it as a supported request from your network.
- Architectural or strategic conflict. Some requests clash with platform-level decisions. The reply will say so plainly.
In all cases you get a written reply — no request goes unanswered.
Bugs vs. feature requests
Section titled “Bugs vs. feature requests”These go through different channels and have different response SLAs.
| Type | Definition | Channel |
|---|---|---|
| Bug | Something that exists but behaves incorrectly | support@izi.is or the chat widget inside the CRM |
| Feature request | Something that does not exist yet but you want | feedback@izi.is or Help → Suggest an idea |
Routing a bug through the feature channel delays the fix. Routing a feature request through support creates confusion and slower triage. Keep them separate.
See also
Section titled “See also”Frequently asked questions
Where do I send a feature suggestion?
Use the in-app form under Help → Suggest an idea, or email feedback@izi.is directly. Describe the task you're trying to solve, how you handle it today, and what the ideal flow would look like.
How does IZI decide which requests to build first?
Priority is based on several factors: how many clubs share the same problem, the strategic fit for the platform, and implementation complexity. Requests that solve a problem across many clubs move up the queue faster.
Can I find out when my request will be shipped?
If your request is accepted into the roadmap, the status is updated in your account dashboard and on the public roadmap. If it is not accepted, you will receive a reply explaining why — or pointing to an existing feature that already solves the problem.