If something is unclear in this manual, broken in the platform, or feels wrong, the path to a human is short. This page lists the channels.
The primary support channel: hello@jadiroon.sa.
Useful information to include in any message:
- Your workspace slug (the
/{slug}/part of your URL). - The page URL where the issue occurred, if applicable.
- A description of what you expected and what actually happened.
- A screenshot if the issue is visual.
- The time (with time zone) the issue occurred, for log correlation.
We respond within one business day for non-urgent issues. Urgent issues affecting platform availability or data integrity are routed immediately.
Status
Platform status — outages, scheduled maintenance, performance incidents — is published when applicable. The status surface is at status.jadiroon.sa (when applicable to your release).
In v0.5, the status page is informally maintained; a formally hosted status page with subscription notifications is on the v0.6 roadmap. Until then, hello@jadiroon.sa is the channel for status questions.
Reporting a security issue
If you believe you have found a security vulnerability, write to security@jadiroon.sa rather than the general support address. Describe the issue with enough detail to reproduce; include the steps and the expected versus actual behaviour.
We follow responsible-disclosure norms: we will acknowledge the report within two business days, work with you on a fix, and credit you in the release notes if you wish to be credited.
Do not publicly disclose the issue before we have had a reasonable time to fix it.
Reporting an AI-generated mistake
AI-generated content (JDs, narratives, recommendations) is occasionally wrong in ways that are not just stylistic. If you find an output that is materially incorrect — claims a candidate has competencies they do not, mentions information from outside the prompt, or recommends something obviously inappropriate — write to hello@jadiroon.sa with the report ID and a description.
These reports drive iterations on prompts and guardrails. They are taken seriously.
Documentation issues
If a page in this manual is wrong, unclear, or missing a topic, write to hello@jadiroon.sa with:
- The page URL.
- What you found unclear or incorrect.
- What you would have expected to read.
Documentation gaps are tracked. Common requests become updates in the next release.
Feature requests
If something the platform does not do would meaningfully help you, write to hello@jadiroon.sa with:
- The use case.
- The current workaround (if any).
- Why this matters for your organisation.
Feature requests are tracked alongside the v0.6+ roadmap. We do not commit to every request, but we read every one.
Things that are not in v0.5
To save you the trip:
- A help chat or live chat widget in-product.
- A community forum or user group.
- A self-service ticket portal.
- Account managers for non-enterprise accounts.
The deliberate channel is email. It is slower than a chat widget but allows considered responses and creates a written record both parties can refer back to.