ONE INBOX
Mail it, and it is on the board.
No portal login, no form to fill in. Your message arrives as a ticket with the body intact, and you watch the same board we do.
ONE REAL TICKET
From report to confirmed.
Every message, every step and every answer stays on the ticket, in your own Odoo. You see exactly what we see.
Your team reports it
We find the cause
We push the fix
Your team confirms
HOW IT RUNS
The lane you land in after the last sprint.
Onboarding
Helpdesk set up, your portal configured and your setup written down.
Tickets
Triage and diagnosis, root cause analysis, and the knowledge base kept up to date.
Review
Usage patterns, open issues and the roadmap priorities for the quarter ahead.
Improve
Mini releases, training refreshers and new features as Odoo ships them.
QUARTERLY REVIEW
Your system, getting stronger.
Once a quarter we go through it together in Odoo. Where the tickets came from, what caused them, and what is worth changing. You leave with a prioritised plan for the quarter ahead.
How your Odoo matures over time
Support tickets
User adoption (%)
9
Tickets this quarter
94%
User adoption
FAQ
Straight answers.
QHow fast do you reply?
AFour hours for a first response, and two hours for anything that stops production. Behind that promise sits one queue and a key account who already knows your system, so the reply is an answer and not an acknowledgement.
QCan our team raise tickets directly?
AYes. Your users get portal access to raise, follow and reply to tickets, and plain email to support@circel.com works just as well. Both land on the same board.
QWhich hosting do you support?
AOdoo.sh. Every client we take on runs there, the small ones included, because it gives us git, staging, backups and somewhere real to put your own code. We do not take on Odoo Online.
QWhat is in a quarterly review?
AWhere the tickets came from, how the system is holding up, and what you want next. You leave with a prioritised plan for the quarter ahead.