When something isn’t working the way these docs describe, or you have feedback on the product, there’s one place to write: hi@dijji.ai. The same address handles support questions, bug reports, and feature requests.
Before you write
Most of what goes wrong has a known cause and a fix you can apply yourself. If you haven’t already, check the Help section first — there’s a page for each of the common stuck states:
- A run that’s paused — waiting for a gate, waiting for payment, waiting for an answer, paused at a checkpoint, or with a rejected plan.
- A task that won’t start — the balance is too low, or another run is already active.
- An issue that didn’t sync into a task, or an integration that isn’t healthy.
- A control you expected that’s missing — usually a role difference, not a fault.
Each of those pages ends with a “still stuck” note. If you’ve worked through it and the problem holds, that’s the point to write in.
Reaching support
Email hi@dijji.ai. There’s no in-app support window or chat — email is the channel.
A clear report gets a faster answer. Include:
- What you were doing — the exact action, in product terms. “I selected Run on a task and it stopped with an error” beats “it’s broken.”
- What you expected, and what happened instead.
- The names that locate it — your organization name, the project name, the task, and the run number if a run is involved. The run number is on the run detail page.
- The exact on-screen text — if there’s an error message or a status badge, quote it word for word, including anything after a colon. If a message appears in a language that isn’t yours, say so and describe what you were doing — that’s a known display issue and the report still helps.
- When it happened — roughly the time, so it can be matched against activity.
You don’t need to attach anything technical. Describe what you saw on screen; that’s what’s useful.
Sending feedback
Feedback goes to the same address — hi@dijji.ai. That covers anything that isn’t a fault:
- A feature you want, or a workflow that’s more friction than it should be.
- A doc page — including these — that’s wrong, unclear, or missing something.
- A label or message that confused you.
For feedback, the most useful thing you can add is the why: what you were trying to get done, and where the product got in the way. A concrete example of the situation is worth more than a general request.
What to expect
Every message gets a reply by email — there’s no public ticket tracker or status page to follow. Writing from the email address on your DIJJI.ai account helps connect your message to your organization quickly.