Entire Automation System for Libraries
E-Mail: info@easylibsoft.com
Website: http://www.easylibsoft.com
Service Desk Module
Table of Contents
- Overview
- Accessing the Service Desk Module
- Listing
- 3.1 Tickets List
- 3.2 Customer Tickets
- 3.3 Support
- 3.4 Easylib Support Meet
- Setup
- 4.1 Ticket Types
- 4.2 Ticket SubTypes
- 4.3 Ticket Status
- 4.4 Ticket Forms
- 4.5 Products
- 4.6 Modules
- 4.7 Ticket Efforts
- Import Tickets
- SMTP Credentials
- Mass Updates
- 7.1 Ticket Mass Update
- 7.2 Bulk Update
- 7.3 Ticket Bulk Update
- CRM Screens
- 8.1 Customized Org List
- 8.2 Opportunity List
- 8.3 Opportunity Statistics
- SQL Reports
- Help Module
- 10.1 Help Modules Setup
- 10.2 Help Screen Setup
- 10.3 Help Function Setup
- 10.4 Internal Documentation
- 10.5 Help (Internal)
1. Overview
The Service Desk Module in Easylib ERP is used to manage customer support requests, internal service tickets, CRM-related activities, and help documentation. It enables efficient tracking, resolution, and reporting of tickets while providing tools for configuration, bulk updates, and internal help management.
This module is commonly used for:
- Customer and internal support ticket management
- Tracking issues, requests, and resolutions
- CRM opportunity tracking
- Managing internal help and documentation
2. Accessing the Service Desk Module
- Login to Easylib ERP with valid credentials.
- Navigate to Menu ? Service Desk.
- Select the required screen from the Listing, Setup, CRM, or Help sections.
3. Listing
The Listing section provides access to all ticket-related operational screens.
3.1 Tickets List
Displays all tickets raised in the system and Create New Tickets if required,
Key columns include:
- Ticket ID
- Customer / Organization
- Ticket Type & SubType
- Priority
- Assigned To
- Status
- Created Date
Users can search, filter, modify, or view ticket details.
3.2 Customer Tickets
The Customer Tickets Dashboard provides a consolidated view of all customer support tickets across organizations, categorized by Ticket Type and Status.
It helps support teams and management to:
- Monitor overall ticket volume
- Track ticket progress by status
- Identify pending, in-progress, and delayed tickets
Key Features:
- View ticket counts for statuses such as New, Open, Responded, Resolved, Scheduled, Closed, Awaiting Deployment, To Be Tested, and On Hold
- Use Filter Type and Filter By options to refine ticket data
- Click on ticket counts to view detailed ticket lists
- Use Search and Show entries for quick navigation
3.3 Easylib Support Meet
This screen is used to manage and track:
- Scheduled support meetings
- Online or offline support sessions
- Follow-up actions after meetings
4. Setup
The Setup section is used to configure master data required for ticket management.
4.1 Ticket Types
The Ticket Types screen is used to define and manage high-level categories under which support tickets are created (e.g., Production Issues, Software Changes).
Key Functions:
- View the list of existing ticket types
- Add new ticket types using + Add New CRM Tickets Type
- Modify or delete existing ticket types
Usage:
Ticket Types help organize tickets, improve classification, and enable better tracking and reporting in the Service Desk module.
4.2 Ticket SubTypes
The Ticket SubTypes screen is used to define detailed classifications under each Ticket Type, helping route and manage tickets more precisely.
Key Functions:
- Create subcategories for existing ticket types (e.g., Bug Fix under Software Changes)
- Specify whether a form is required using Form Needed (Yes/No)
- Add, modify, or delete ticket subtypes
Usage:
Ticket SubTypes improve ticket categorization, enable form-based data capture, and help support teams handle issues efficiently.
4.3 Ticket Status
The Ticket Status screen is used to define and manage the different stages of a ticket’s lifecycle.
Key Functions:
- Create statuses such as New, Open, Responded, In Progress, Resolved, Closed
- Modify or delete existing statuses
Usage:
Ticket Status helps track progress, manage SLAs, and clearly indicate the current state of each ticket.
4.4 Ticket Forms
The Ticket Forms screen is used to create custom forms that capture additional details when specific ticket subtypes are selected.
Key Functions:
- Design forms with required fields
- Map forms to ticket subtypes
- Modify or delete forms
Usage:
Ticket Forms ensure structured data collection for specific issues or requests.
4.5 Products
The Products screen allows for configuration of products or services for which support tickets can be raised.
Key Functions:
- Add and manage product names
- Modify or delete products
Usage:
Products help categorize tickets based on supported systems or offerings.
4.6 Modules
The Modules screen is used to define and manage functional modules related to products or systems for which support tickets can be raised.
Key Functions:
- Create modules such as Circulation, Cataloguing, Service Desk, Sales Desk CRM
- Modify or delete existing modules
- Associate tickets with specific application areas
Usage:
Modules help categorize tickets accurately, making issue tracking, assignment, and resolution more efficient.
4.7 Ticket Efforts
The Ticket Efforts screen tracks time and effort spent on resolving tickets.
Key Functions:
- Log work hours against tickets
- Update or modify effort entries
Usage:
Ticket Efforts help in workload tracking, billing, and performance analysis.
5. Import Tickets
The Import Tickets screen allows bulk creation of tickets using Excel to upload.
Key Functions:
- Upload ticket data in predefined format
- Validate and import records
Usage:
Useful for migrating tickets or creating multiple tickets at once.
6. SMTP Credentials
Used to configure email settings for the Service Desk.
Enables:
- Ticket creation via email
- Email notifications
- Status update alerts
Ensure correct SMTP details are configured for uninterrupted communication.
7. Mass Updates
The Mass Updates section allows for updating multiple tickets at once.
7.1 Ticket Mass Update
The Ticket Mass Update screen allows updating multiple tickets at once.
Key Functions:
- Update status, assigned user, or priority in bulk
Usage:
Saves time when handling large volumes of similar tickets.
7.2 Bulk Update
Allows large-scale updates across tickets based on criteria.
7.3 Ticket Bulk Update
The Ticket Bulk Update screen provides Excel-based bulk ticket updates.
Key Functions:
- Upload Excel file with ticket updates
- Apply changes to multiple tickets simultaneously
Usage:
Efficient for large-scale ticket corrections or status changes.
8. CRM Screens
The Service Desk integrates CRM-related screens for opportunity tracking.
9. SQL Reports
Allows generation of custom SQL-based reports.
Used by administrators for:
- Advanced reporting
- Data analysis
- Custom dashboards
10. Help Module
The Help Module is used to manage system help and internal documentation.
10.1 Help Modules Setup
The Help Modules Setup screen is used to define and manage ERP modules for which help and documentation will be maintained.
Key Functions:
- View the list of available ERP modules
- Add new help modules using Add New Module
- View module descriptions
- Edit existing module details
Usage:
Help Modules Setup organizes system documentation module-wise, enabling structured help content and easy navigation across the ERP.
10.2 Help Screen Setup
The Help Screen Setup screen is used to configure help content for individual ERP screens or menu items.
Key Functions:
- Select the Subsystem / Module
- Define a unique Screen Code (6 characters)
- Enter Screen Name
- Add detailed help content using the rich text editor
- Save, edit, or delete help screen entries
Usage:
Help Screen Setup enables screen-level documentation so users can access contextual help directly from specific ERP screens.
10.3 Help Function Setup
Maps help content to specallows forunctions or actions.
Help (Internal) – Help (Short)
The Help (Internal) screen is used to maintain internal documentation for Easylib support, implementation, and development teams.
Key Functions:
- Create and manage internal-only help content
- Document workflows, troubleshooting steps, and internal processes
- Edit or update internal documentation as needed
Usage:
Internal Help ensures consistent knowledge sharing within teams and serves as a reference for support and implementation activities.
10.4 Internal Documentation
Stores internal process documentation.
Used for:
- Support team reference
- Training
10.5 Help (Internal)
The Help (Internal) screen is used to create and maintain internal documentation meant only for Easylib support, implementation, and development teams.
Key Functions:
- Add internal notes, SOPs, and troubleshooting steps
- Document known issues, fixes, and workflows
- Update or modify internal help content as processes evolve
Usage:
This section acts as an internal knowledge base to ensure consistent support, faster issue resolution, and better team coordination.