Working with NextERP · Article 03
Support procedure
Applies to Odoo 19 · 20
The complete process through which a customer opens a support request and the NextERP team analyses it, answers it or escalates it to development through a task in the implementation project. The article covers the Helpdesk flow from opening to closing, the triage criteria, escalation, invoicing and good practices.
🎫 Helpdesk — the entry point
All support requests are handled in Odoo Helpdesk — the standard Odoo module, configured with a dedicated NextERP team. Requests are always opened through a ticket in the customer portal; the phone is strictly reserved for emergencies (production system down).
📚 Documentation migration: Odoo e-Learning → Odoo Knowledge
The NextERP documentation (procedures, user guides, support cases, per-module configurations) is moving from Odoo e-Learning to Odoo Knowledge. The reason: Knowledge offers fast full-text search, hierarchical structure on workspaces, articles linkable to each other, versioning and granular access per customer.
Access to the documentation:
- Directly in the customer portal → "NextERP Knowledge" workspace (full access to all articles published for customers).
- Directly from the ticket opening form (Submit a Ticket) — a quick "📖 Caută în documentație" (search the documentation) link that opens Knowledge in a separate tab. We recommend checking there before opening a ticket: many frequent questions (D406 configuration, e-Factura SPV, currency revaluation, month-end closing etc.) already have a documented answer.
- In each reply on the ticket, the support team includes links to the relevant Knowledge articles for further reading.
e-Learning courses (video lessons, certification quizzes) remain available for structured training modules, but the operational documentation (procedures, configurations, troubleshooting) moves exclusively to Knowledge.
⛔ Alternative channels — NO answer
The support team NO longer answers requests sent through:
- WhatsApp (personal or business account)
- SMS
- Messenger / Telegram / Signal or other chat apps
- Direct email to consultants (not through a ticket / not through the Helpdesk alias)
- LinkedIn / social networks
- Direct calls to consultants or the Project Manager about support issues (exception: system-down emergency, on the official number)
Messages sent on these channels will be neither forwarded nor taken over — they will be ignored completely, with no answer. The reason: lack of traceability, the impossibility of measuring the SLA, the risk of losing the history and the conflict with the contractual audit obligations. The only valid way to request support is to open a ticket in the customer portal. No consultant is mandated to handle support outside Helpdesk — an informal answer, if one is given anyway, does not constitute a commitment of NextERP.
1. Ticket through the customer portal (mandatory)
Log in to the NextERP customer portal → "Helpdesk" section → "Submit a Ticket" button. The form has the following fields (✻ = mandatory):
| Field | Type | Description |
|---|---|---|
| Your Name ✻ | text | Your name — used on the ticket for identification. |
| Your Email ✻ | text | Your email — receives automatic notifications on every change to the ticket. |
| Category ✻ | radio | Question / Configuration · Bug · Development — see the "Triage" section for what each means. |
| Priority ✻ | radio | Urgent · High priority · Medium priority · Low priority — corresponds to Very high / High / Medium / Low in the SLA. |
| Mediu ✻ | radio | Production · Staging · Runboat — the environment where it happened. |
| Version ✻ | radio | 19.0 · 18.0 · 17.0 · 16.0 · 14.0 · master — the Odoo version of the instance. |
| Subject ✻ | short text | The ticket title — concise, descriptive (e.g. "Cash-basis VAT — error when posting a vendor bill"). |
| Description | long text | Description of the problem + steps to reproduce (see the "Ideal content" section below). |
| Link Instanta | URL | The URL of the affected instance, so the team can access it directly (if it has an account). |
| Impact | text | How many users are affected, whether a critical flow is blocked, relevant deadline. |
| Attachment(s) | files | Screenshots, Odoo logs, tracebacks, XML/CSV files for import. |
All fields marked ✻ are mandatory. Description, Link Instanta and Impact are not technically mandatory, but without them the team will ask for clarifications — when they are filled in, the ticket is resolved faster.
2. Phone (emergencies only — system down)
For a production system that is down (critical operations impossible), call +40 770 816 455. The phone is only for reporting the emergency and activating the team immediately — it does not replace the ticket:
- Call and briefly describe the incident.
- Immediately after the call, open a ticket in the portal with the full details (description, steps to reproduce, attachments, impact). The support team starts working, but needs the ticket for audit, communication and SLA measurement.
- Any decision taken by phone is recorded on the ticket afterwards — no exceptions.
After opening, you receive an automatic confirmation with the ticket number (e.g. NXTXXX-00123, where XXX is the prefix of the team dedicated to your company).
📋 Ideal content of a ticket
The more detailed the ticket, the faster the answer (the team does not need to ask for clarifications repeatedly). Our recommendations per form field:
Subject
A concise, descriptive title: affected module/function — symptom. Good examples:
- "Cash-basis VAT — error when posting a vendor bill"
- "D406 — XML missing off-balance-sheet accounts for account 8x"
- "Currency revaluation — duplicate entries for March"
Avoid: "doesn't work", "bug", "help".
Description (description + steps to reproduce)
Structure the description in 3 parts + steps:
- What you did — the triggering action (e.g. "I tried to post a vendor bill with cash-basis VAT")
- What you expected to happen — expected behaviour (e.g. "The bill to be posted with the CABA entry generated automatically")
- What actually happened — actual behaviour (e.g. "A UserError appeared: «No CABA account configured»")
Steps to reproduce — the exact sequence the team needs to reproduce it on runboat or on the customer's database:
- Log in as user
X(role: accountant/manager/etc.) - Menu → submenu → button
- Data entered on the form (with concrete values)
- Button clicked that triggers the problem
On multi-company databases, also mention the company + user where it happened.
Mediu + Version
Select explicitly in the form: Production / Staging / Runboat and the version (19.0 / 18.0 / etc.). If there are critical modules with specific versions (NextERP, customer customisations), mention them in Description.
Link Instanta
The URL of the affected instance — direct access saves the team time if it already has an account. For staging/runboat, include the branch URL.
Impact
- How many users are affected
- Whether it blocks an operational flow (sales, invoicing, tax returns)
- Whether there is a temporary workaround and what its limitations are
- Relevant deadline (e.g. "I have to file D300 (the VAT return) by the 25th of the month")
The Impact field feeds the priority decision — without it, an Urgent/High priority may be reclassified.
Attachment(s)
- Screenshot of the error shown in the UI (with a cursor / arrow on the element)
- Odoo log — excerpt from
odoo.log(5–10 lines before and after the error) - Full traceback if there is one — copied as text, NOT a screenshot
- Test data — XML/CSV/Excel for import / configurations
- Video recording — for bugs that show up visually (animation, JS error)
🔍 Triage by the support team
After opening, the ticket is taken over by the support team within at most 4 working hours (or according to the SLA in the contract). The analysis falls into 3 categories:
Category 1: Question / configuration
Answered directly through the ticket. Typical for:
- "How do I set field X?"
- "Where do I find report Y?"
- "Why doesn't button Z appear on the partner?"
- "How do I configure feature W?"
These tickets do NOT involve development. The answer usually includes screenshots, links to the documentation in Knowledge articles or concrete steps.
Category 2: Confirmed bug
Wrong behaviour of the existing code — different from what the module documents. The support team reproduces the bug on runboat or on the customer's database and confirms that:
- It is not a wrong configuration (the user is configured correctly)
- The bug occurs consistently (it is not something sporadic related to corrupted data)
- The existing code does NOT cover that case
It needs a code fix → escalation to development.
Category 3: Development request
A new feature or a significant change to an existing flow. Typical:
- "We want to generate a custom report that does not exist"
- "We want to integrate with an external system Y"
- "We want to change the order approval flow"
It needs specification + estimate + implementation → escalation to development through a task.
🔗 Escalation to development — task in the project
For the Confirmed bug and Development request categories, the support team creates a task in the corresponding implementation project and updates the ticket with the link.
Where the task is created
- The customer's private project — for customer-specific bugs / developments (the customer's custom module, own integration). Visible only to the NextERP team and users with access to that project.
- The general NextERP project — for bugs / developments affecting common modules (l10n-romania, nexterp-base, l10n-romania-enterprise, connector etc.). The fix benefits all customers using the module.
Helpdesk ↔ task link
- The task has a
helpdesk_ticket_idfield that points back to the original ticket - The ticket has a "View Task" button that opens the related task
- When the task is closed, the ticket is updated automatically with the result (automatic message in the chatter)
- The attachments on the ticket are copied automatically to the task
Why a separate task is created
Development tasks have their own flow (specification → estimate → approval → implementation → testing), which is different from the helpdesk flow (answer + closure). The separation avoids mixing statuses and allows:
- An explicit estimate of the development time
- Separate approval by the customer (through the portal)
- Invoicing traceability (support and implementation have different rates)
- Reusing the fix for other tickets reporting the same problem
📐 Ticket stages in Helpdesk ("Suport" team)
The ticket goes through 5 stages configured on the "Suport" team:
| Stage | Folded | Who sets it | What it means |
|---|---|---|---|
| New | — | System (on opening) | New, unassigned ticket. Waiting for triage by the support team. |
| In Progress | — | Support team | Under active analysis: reproducing the bug, writing the answer, configuration etc. |
| On Hold | — | Support team | Ticket on hold. Used when: (1) we are waiting for clarifications or data from the customer, (2) the ticket has been escalated to development — task created in the project and the fix in progress, (3) we are waiting for the customer's test on runboat or staging. The SLA is stopped while in this stage. |
| Solved 📁 | ✓ folded | Support team or customer | Answer accepted or fix deployed to production. Ticket closed with a resolution. |
| Cancelled 📁 | ✓ folded | Customer or support | Ticket closed without a resolution: duplicate, withdrawn request, non-reproducible error, abandoned by the customer. |
"Folded" stages (Solved, Cancelled) — appear collapsed in the Kanban view. A ticket in these stages is considered closed and no longer appears in the active list.
🚦 Configured priorities and SLAs
On the "Suport" team there are 4 priority levels and 8 SLA policies (4 priorities × 2 target stages: In Progress and Solved):
| Priority (portal form) | Internal equivalent | Definition | To In Progress (ticket taken over) |
To Solved (resolution) |
|---|---|---|---|---|
| Urgent | Very high ⭐⭐⭐ | Production system down, critical operations impossible, tax return with an imminent deadline. | 4 hours | 16 hours |
| High priority | High ⭐⭐ | Important feature affected, but a temporary workaround exists. | 8 hours | 32 hours |
| Medium priority | Medium ⭐ | Operational problems that do not block critical flows. | 16 hours | 64 hours |
| Low priority | Low (no stars) | Questions, cosmetic issues, improvement suggestions. | 24 hours | 128 hours |
Times are in working hours (09:00–18:00, Monday–Friday, excluding Romanian public holidays). The SLA cron is stopped while the ticket is in the On Hold stage (waiting for the customer / development / testing).
SLA start time: the SLA applies to tickets opened by 13:00 (on that day). For tickets opened after 13:00, the response time is counted from 09:00 on the next working day.
To mark a ticket as Urgent, explicitly select this priority in the portal form when opening the ticket OR call +40 770 816 455 for a system-down case (then open the ticket with Urgent priority + fill in the Impact field as justification).
⚖️ Priority reclassification by NextERP
The priority declared by the customer when opening the ticket is a starting point, not a final value. At triage, the NextERP support team analyses the real impact (description, logs, environment, affected flow, deadline) and may adjust the priority up or down to reflect the criticality of the problem correctly.
The reason: the priority levels govern the contractual SLAs and the processing order for all customers. Systematically marking non-critical tickets as Urgent or High would unbalance the support queue and disadvantage customers with real high-impact problems.
Reclassification rules:
- Reclassification is done transparently: the team posts a comment on the ticket with the justification for the change and the new applicable SLA.
- Reclassification follows the contractual definitions of each level (see the table above) — it is not arbitrary.
- The customer may contest the reclassification by replying on the ticket with additional arguments (impact, deadline, evidence). The final decision rests with the support team, based on objective criteria.
- Typical cases of downward reclassification:
Urgentset on configuration questions, on staging/runboat (non-production environment), without the Impact field filled in, or on problems with an available workaround. - Typical cases of upward reclassification: a ticket marked
Lowwhich at triage turns out to block the filing of a tax return with an imminent deadline or to affect payments / invoicing in production.
⛔ Intentional abuse of the priority system (repeatedly marking non-critical tickets as Urgent to force a fast takeover) is monitored. If there is a repeated pattern, the assigned Project Manager will contact the customer for clarification; in extreme cases, tickets from those users may be triaged first by the NextERP team before the declared SLA is applied.
🏷️ Tags used at triage
The support team uses tags for quick categorisation:
question— question / configuration (Category 1)bug— confirmed bug (Category 2)development— development request (Category 3)declaration— related to tax returns (D300, D390, D394, D406, SAF-T)integration— related to external integrations (eBriza, Saga, SmartBill, ANAF)spv— related to e-Factura SPV (Spațiul Privat Virtual, the ANAF online portal)upgrade— post-upgrade module problemstraining— training request / live sessiondata-fix— data correction on the customer's database (rare, with explicit approval)
Filtering by tags in the portal lets you see only the relevant types (e.g. only active bugs).
💰 Invoicing
Category 1 — Question / configuration
Invoiced at the price agreed in the contract, under the "Odoo Support Services" service type. Amount: the actual time worked (ticket analysis + writing the answer + customer verification).
Category 2 — Confirmed bug
- With an active maintenance subscription and a bug in standard NextERP modules (l10n-romania, nexterp-base, etc.) → the fix is free. The benefit of the subscription.
- Without a subscription or a bug in a customer custom module → the fix is invoiced at the implementation price ("Odoo Implementation Services") following the standard flow with estimate + approval.
Category 3 — Development request
Always invoiced at the implementation price ("Odoo Implementation Services") following the flow in the "Project Workflow" article: estimate + approval through the customer portal + implementation + testing + documentation.
Details on rates and subscriptions — see your contract or ask your assigned Project Manager.
⏱️ How the SLAs are interpreted
To stage In Progress (takeover)
The time in which the support team takes the ticket from New and starts active analysis. Typically: confirmation of the takeover + the first clarification questions or a direct answer.
To stage Solved (resolution)
The total time until the ticket is closed in the Solved stage. For:
- Category 1 (question / configuration) — the answer closes the ticket directly.
- Category 2/3 (escalation to development) — the ticket stays in
On Holdwhile development is in progress. The SLA does not run during this interval. When it returns toIn Progress(after the fix is delivered) the cron resumes.
SLA exclusions
- Ticket in the On Hold stage — the SLA cron is stopped until it moves back to
In Progress. - Romanian public holidays and announced leave (automatic out-of-office — the SLA pauses).
- External infrastructure problems (ANAF SPV down, email providers blocked) — the SLA extension is documented on the ticket.
SLA display on the ticket
On each ticket, in the header, a visual indicator shows:
- 🟢 SLA met — comfortably within the deadline
- 🟡 SLA close to expiry — less than 25% of the time left
- 🔴 SLA expired — breach recorded (appears in management reports)
📞 Follow-up and communication
Active channels
- The customer portal (Helpdesk) — the only official communication channel for support. All messages, attachments and decisions are recorded on the ticket.
- Phone — emergencies only (+40 770 816 455) — exclusively for a production system that is down, always followed by a ticket in the portal with full details.
⛔ Channels that are NO longer accepted
To ensure traceability, SLA measurement and contractual compliance, the support team no longer answers on alternative channels:
- WhatsApp, SMS, Messenger, Telegram, Signal and other chat apps
- Direct email to consultants' personal addresses (outside the official Helpdesk alias)
- LinkedIn and other social networks
- Direct phone calls to consultants or the Project Manager about support issues — all support calls are redirected to the official number, for emergencies only
Messages received on these channels will be neither forwarded nor taken over — they will be ignored completely, with no answer or manual redirection. Requests opened outside Helpdesk do not generate an SLA, are not auditable and do not constitute a contractual obligation for NextERP. The only valid way to start a support request is to open a ticket in the customer portal.
Exception: pre-existing informal communication based on personal relationships (e.g. a consultant who has historically worked with the customer) — any technical decision or commitment discussed outside the ticket must be recorded within 24 hours on the related ticket, otherwise it has no effect.
Communication rules
- For answers to clarification questions from the support team, reply within at most 2 working days. Otherwise the ticket stays in
On Hold, blocking the SLA cron, but from a business point of view it may be considered "abandoned". - For abandoned tickets with no reaction from the customer for over 30 days, the support team may send a reminder. After 45 days without a reaction, the ticket may be closed with the note "Cancelled — no customer response".
- Use the same ticket for the same problem. If a different problem appears, open a new ticket — do not hijack another one.
🔁 Special cases
Duplicate tickets
If you accidentally open 2 tickets for the same problem, the support team merges them: it keeps one as primary and closes the other with a link to the primary. All messages and attachments are moved automatically.
Bulk tickets
To report the same problem for 10+ users or companies, open ONE SINGLE ticket with a list of those affected — not one per user. The team will handle it as a batch.
Sensitive data
For tickets that require access to the production database:
- The support team signs an NDA / confidentiality clause (from the contract)
- Access is through the customer's VPN OR through a local export of anonymised data
- Personal data (CNP — the Romanian personal identification number, emails) is anonymised on public attachments
Tickets for runboat
Problems with the test environment (runboat — see the "Runboat — the test environment" article) are reported to the internal NextERP team directly, NOT through Helpdesk. They are considered internal infrastructure problems.
📊 Reports and audit
For the customer
In the portal, the "Helpdesk" section → the "Reports" tab shows:
- Tickets opened / closed in the selected period
- Distribution by category (question / bug / development)
- Average response time vs SLA
- Top 10 users who opened the most tickets (to identify the areas where training is needed)
Audit trail
All changes to the ticket (status, assignment, messages, attachments) are recorded in the chatter. The tracking covers:
- Who made the change (user)
- When (timestamp)
- Which field changed (old value → new value)
Useful for tax audits or contract reviews.
✅ Good practices for customers
- One ticket = one problem. Do not mix several problems in the same ticket — the resolution becomes confusing.
- Check Knowledge first. Many frequent questions already have an answer in the support articles ("Cazuri de suport NextERP" workspace).
- Include context. Never "doesn't work" without details — describe what you actually did and what happened.
- Well-named attachments.
screenshot_eroare_factura_2026-04-27.pngis more useful thanimg.png. - Answer clarification questions. The support team is waiting for input — without it the ticket stalls.
- Confirm the resolution. When the team marks "Solved", check and confirm explicitly. Otherwise the ticket is not fully closed.
- Use the right priority tag. Marking non-urgent tickets as Urgent reduces credibility for real emergencies.
🏁 Closing the ticket
For Question tickets (Category 1)
- The support team answers and marks
Solved(folded stage) - We wait for the customer's confirmation (max 5 working days)
- No reaction → the ticket stays in
Solvedpermanently
For tickets escalated to a task (Category 2/3)
- While development is in progress, the ticket stays in
On Hold - The development task is completed (see "Project Workflow" — Done → production)
- The support team posts a summary of the fix on the ticket with a link to the commit / changelog
- The customer confirms in production → the ticket moves to
Solved
📞 Contact
- Customer portal: the link received at onboarding (the only channel for opening tickets)
- Phone (emergencies only — system down): +40 770 816 455 (followed by a ticket in the portal)
- "Project Workflow" article — the development flow after escalation
- "Cazuri de suport NextERP" workspace (NextERP support cases) — articles for frequent cases, with documented remedies