Support Request & Technical Ticketing
Support Request & Technical Ticketing - User Guide
1. Introduction đđ
Clear and tracked communication is essential for maintaining a high-performance ERP environment. The Support Request module is an integrated ticketing system that allows you to communicate directly with your technical support team (erpcrew). Instead of relying on disconnected emails or phone calls, you can document issues, request new features, or ask for operational help directly within the software, ensuring that your requests are never lost and always tracked for resolution.
âšī¸
Purpose of this Utility:
- Issue Tracking: Log system bugs or data discrepancies and monitor their progress toward resolution.
- Feature Advocacy: Formally request new reports or functional improvements for your department.
- Knowledge Collaboration: Ask for help with complex transactions and receive documented guidance.
This module is essential for Department Heads, System Users, and IT Administrators.
2. Key Reporting Metrics & Creation Fields đ
A. Dedicated Ticketing
The system assigns a unique Request No to every entry.
- Type: Categorize your request as a Bug (system error), Feature (new request), or Query (how-to assistance).
- Subject: A concise title describing the issue.
- Description: Comprehensive notes detailing error messages, steps to reproduce, or requested operational features.
- User Mobile No: Direct phone contact for urgent clarifications from the support team.
- Attachment Upload: Attach diagnostic files directly to the ticket. Supported file formats include
.pdf, .xlsx, .png, .docx. - Status: Monitor progress as the request transitions across lifecycle states: Open, In-Progress, Waiting for Input, and Closed / Resolved.
- Suggested Solution: When the technical desk investigates or resolves the ticket, technical diagnosis and operational solutions are documented in the Suggested Solution notes.
B. Account & Project Isolation
- Privacy for Units: Standard users only see support requests logged by personnel within their designated business unit or branch.
- Consolidated Support: The support engineering team (
erpcrew) maintains centralized administrative oversight across tickets and retains exclusive permission to export tickets to Excel for development sprints and project scheduling.
3. The Resolution Workflow đ ī¸
- Creation: Use Create New to log a ticket. Select the request type, enter a clear subject and description, provide your mobile number, and attach any relevant error screenshots or spreadsheets (
.pdf, .xlsx, .png, .docx). - Assignment & Investigation: The support team reviews the ticket and moves its status to In-Progress.
- Reviewing Solutions: Once investigated, review the Suggested Solution field on the ticket details screen for instructions, patches, or resolution guidance.
- Closure: Once resolved, the ticket is marked as Closed, and a resolution confirmation email can be dispatched.
4. Understanding Global Indicators đ
- Request No: Unique auto-generated tracking identifier.
- Type Name: Operational classification (Bug, Feature, Query, Issue).
- Date: Submission timestamp (
dd-MMM-yy HH:mm). - Status Name: Real-time lifecycle stage (Open, In-Progress, Resolved).
- Download File: Interactive link on the ticket details view to download and inspect attached files.
5. System Interactivity & Communication đ
The ticketing engine integrates with:
- User Directory: Links tickets directly to the reporting user’s profile, email address, and mobile number.
- Enterprise Projects: Maps requests to specific implementation phases, manufacturing plants, or operational branches.
- Real-Time Alerts: Dispatches automated notifications to support desk engineers upon ticket creation or status transitions.
6. Best Practices / Tips đĄ
- The “Clear Subject” Rule: Always use a descriptive subject line. Instead of saying “It’s not working,” use “Duplicate entry error in Purchase Invoice.” This helps the technical team prioritize your request much faster.
- Attach Screenshots or Samples: Always attach error screenshots (
.png) or problematic spreadsheets (.xlsx) during ticket creation to speed up technical reproduction. - Provide Mobile Contact: Keep your mobile number accurate so support engineers can reach you quickly if immediate diagnostic clarifications are needed.
- Review Suggested Solutions: Before reopening a ticket, verify whether the guidance posted under Suggested Solution resolves the issue.