| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Website (website)
• Discuss (mail) |
| Lines of code | 2281 |
| Technical Name |
eg_all_in_one_helpdesk |
| License | OPL-1 |
| Website | https://www.inkerp.com |
| Versions | 16.0 17.0 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Website (website)
• Discuss (mail) |
| Lines of code | 2281 |
| Technical Name |
eg_all_in_one_helpdesk |
| License | OPL-1 |
| Website | https://www.inkerp.com |
| Versions | 16.0 17.0 18.0 19.0 |
Our Most Suggested Products
All-in-One Helpdesk
The All-in-One Helpdesk app provides a robust solution for managing help desk operations efficiently. It supports ticket creation, management, and resolution while enabling collaboration among help desk teams. Customers can track and manage their tickets through a user-friendly portal, improving communication and support quality.
Features
Access Rights Management
The module provides flexible access control to grant or restrict helpdesk functionality based on user roles. Administrators can define who can view, create, edit, or resolve tickets, ensuring sensitive data remains secure.
Helpdesk Ticket Management
Managers can create, assign, monitor, and resolve support tickets from a centralized workspace. Advanced search and filtering options make it easy to locate tickets by status, priority, customer, or assigned team member.
Helpdesk Team Management
Support teams can be organized based on departments, expertise, or service levels to streamline ticket handling. Tickets can be automatically or manually assigned to the appropriate team, improving workload distribution and collaboration.
Ticket Types and Categories
The module allows administrators to define ticket types and categories to classify customer issues accurately. Categorization helps in prioritizing requests, routing tickets to the right team, and analyzing recurring problems.
Customer Portal Integration
Customers gain access to a dedicated portal where they can create, track, and communicate on support tickets with ease.
Configurable Ticket Lifecycle Stages
Ticket stages can be customized to match the organizationâs support workflow, from initial request to final closure. Automated notifications keep both customers and support teams informed as tickets progress through each stage.
Screenshot
1.) Access Rights Configuration
Control helpdesk permissions by assigning specific rights to users based on their roles.
Navigation : Settings â Users & Companies â Users
2.) Helpdesk Tickets Dashboard
A centralized view for managing all helpdesk tickets efficiently. Managers can monitor requests, update details, and ensure smooth ticket resolution from one place.
3.) Advanced Ticket Search Options
Search and filter tickets using multiple criteria such as ticket ID, customer, team, status, or priority. This helps locate issues quickly and improves response time.
4.) Helpdesk Team Management
Create and manage helpdesk teams to organize support operations effectively. Teams can be structured based on departments, expertise, or service requirements.
5.) Assign Customer Contact to Ticket
Link customer contacts directly to tickets to maintain accurate communication and ensure proper tracking of customer issues.
6.) Ticket Type Configuration
Define different ticket types to classify support requests and service issues. This helps in routing tickets correctly and improving support efficiency.
7.) Subject Type Management
Organize ticket subjects to standardize issue descriptions and streamline issue handling across the support team.
8.) Ticket Tags Management
Use tags to label and organize tickets for easier filtering, grouping, and reporting of related issues.
9.) Ticket Stages Setup
Configure ticket stages to represent each step in the support workflow, helping teams track progress from creation to closure.
10.) Email Templates for Ticket Stages
Set up automated email notifications for different ticket stages. Notifications can be sent to customers and team members whenever a ticket status changes.
11.) Ticket Categories Management
Group tickets under predefined categories to classify issues clearly and support better reporting and analysis.
12.) Ticket Sub-Categories
Add sub-categories under main categories for more detailed classification of support requests and improved issue organization.
13.) Ticket Priority Levels
Define priority levels to ensure urgent issues receive immediate attention while maintaining an organized support queue.
14.) Customer Tickets in Portal
Allow customers to access and manage their helpdesk tickets directly from the portal, improving transparency and self-service.
15.) Customer Ticket List View
Customers can view all their submitted tickets in a single list, along with status updates and relevant details.
16.) Create Ticket from Customer Portal
Customers can submit new helpdesk tickets directly through the portal, making issue reporting quick and convenient.
17.) Track Ticket Status and Messages
Customers can follow ticket progress and exchange messages with the assigned support user, ensuring clear and continuous communication.
18.) Close Ticket from Portal
Customers can close their tickets once issues are resolved and provide a closing message or confirmation.
19.) Assign Team Head to Ticket
Helpdesk managers can assign a team head to a ticket to oversee resolution and ensure proper coordination.
20.) Team Head Approval and Notifications
Team heads can approve or cancel tickets and trigger automated email notifications when ticket stages are updated.
21.) Assigned User Ticket Management
Support users can view their assigned tickets and team details, helping them focus on relevant tasks and manage workloads effectively.
22.) Chat with Customer in Ticket
Built-in ticket communication enables direct messaging between support users and customers for faster issue resolution.
23.) Mark Ticket as Done
Support users can mark tickets as completed once the issue is resolved, signaling readiness for closure.
24.) Automatic Email on Ticket Completion
Email notifications are sent automatically to both customers and assigned users when a ticket is marked as done.
25.) Close Ticket After Resolution
Tickets can be formally closed once all actions are completed, keeping the helpdesk system clean and up to date.
26.) Add Closing Message to Ticket
Support users can add a closing note with resolution details or feedback to provide a professional conclusion.
27.) Additional Ticket Workflow View
An extended view of the ticket workflow highlighting smooth transitions between stages and assigned roles.
28.) Helpdesk Configuration Overview
A consolidated configuration view covering teams, categories, priorities, and workflows for complete helpdesk setup control.
User Guide
Teams
team@inkerp.com
Suggested Products
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