| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 873 |
| Technical Name |
jjro_helpdesk |
| License | OPL-1 |
| Website | https://aski.dev |
| Versions | 16.0 17.0 18.0 19.0 |
Helpdesk & SLA Cockpit — Answer Faster, Breach Less
A real helpdesk with tickets, teams, priorities and SLA timers, plus a live cockpit of what is open, what is breaching and how fast you resolve — the support desk Community Odoo does not include. Optional AI.
Your whole queue on one screen — open tickets, SLA breaches, average resolution time, and the load on each agent.
- Issues lost in an inbox
- No SLA, no sense of what's late
- No idea who is overloaded
- Tickets with teams, priorities & a clear flow
- SLA timers — on-track / breached at a glance
- A cockpit of the whole queue and the load per agent
Stop letting tickets slip through email — give every request an owner, an SLA and a place it can't get lost.
Support, under control
Log a customer issue with team, priority and assignee — or load a sample to see the SLA flow.
Take it, set it waiting, resolve it — the SLA timer shows on-track or breached the whole way.
The cockpit shows open tickets, SLA breaches, average resolution time and the load on each agent.
Every ticket, its SLA
Each ticket with team, priority, assignee and SLA status — on-track or breached at a glance, highest priority and oldest first.
Set your SLA policy
Choose your first-response and resolution SLA in hours; every ticket gets a deadline and an on-track / breached status. Add your own AI key for a plain-language read of your queue and what to prioritize.
Features
- Tickets — subject, customer, team, priority and assignee, with a clear new → in-progress → waiting → resolved → closed flow.
- Teams & priorities — route work to the right team; urgent surfaces first.
- SLA timers — a resolution deadline per ticket, with on-track / breached at a glance and breaches highlighted.
- Worklist — open tickets first, highest priority and oldest at the top, so nothing slips.
- Live cockpit — open tickets, SLA breaches, average resolution time and tickets by agent, plus load by priority.
- Act from the cockpit — take or resolve a ticket in one click.
- AI insight (optional) — Anthropic Claude or OpenAI, your own key; reads the queue and tells you what to prioritize and whether the load is balanced, in your language.
- Secure by design — role-based access; multi-company isolation. Community and Enterprise.
- Multilingual — English, Spanish, French, German, Italian and Portuguese (BR).
Perfect for support, customer-service and operations teams on Community Odoo that handle customer issues and want a real helpdesk with SLAs — not an inbox or a list of tasks.
Keywords: helpdesk, support, ticket, SLA, service desk, customer service, ticketing, resolution time, first response, priority, support team, after-sales, breach, escalation, Claude, GPT, OpenAI, Anthropic
Permissions & data security
Built to respect Odoo's access model — audited so nothing leaks between users or companies.
- 👤 Role-based access. Dedicated User / Manager groups — recompute and configuration are manager-only. No portal, no public exposure.
- 🔑 AI key encrypted & admin-only. Your provider key is stored encrypted at rest (Fernet / AES) — the plaintext is never saved — and is readable or editable only by a system administrator.
- 🏢 Multi-company isolation. Every record and setting is tagged to its company; a user only ever sees the companies they are allowed into. Cross-company access is impossible — verified.
- ✅ Secure by design — audited across the whole suite: role-based access, key encrypted at rest and admin-only, strict multi-company isolation.
Runs on its own — no extra app required. Works with Odoo Community and Enterprise.
More from the author: Aski — ask your Odoo in natural language by chat or voice, and get real figures from your phone. https://aski.dev
Questions, or want a quick personalized demo? Email me at jhonrojas.dev@gmail.com — I am happy to answer questions or set up a short demo.
Support: jhonrojas.dev@gmail.com · License: OPL-1
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 873 |
| Technical Name |
jjro_helpdesk |
| License | OPL-1 |
| Website | https://aski.dev |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module