ERP Ticketing
π οΈ VCM TicketSP β Internal Ticket Management System
VCM TicketSP is designed to handle internal service and support requests efficiently. It helps track issues, assign responsibility, set priorities, and ensure timely resolution β with full visibility.
π¦ **
Ticket Status Workflow
Each ticket moves through the following statuses:
π’ Open β Ticket is created and awaits processing
π Pending β Waiting for further info or external input
π οΈ Working β Assigned staff is resolving the issue
β
Resolved β Solution provided, awaiting closure
π Close β Ticket marked as completed
π Re-Open β Re-activated after closure due to recurring issue
π© Automatic Email Alerts are triggered on every status change for:
Ticket creator
Assigned user
All CCβd emails (max 3)
π¨ *Priority Levels *
The following priorities determine the expected resolution time:
Urgent β Must be resolved within 5 hours
High β Must be resolved within 3 days
Medium β Within 5 days
Low β Within 15 days
Invalid β No action required; ticket is closeds
ποΈ* Main Categories:*
ERPNext
Farvision
π Subcategories Include (but not limited to):
Purchase (PO etc.)
Store (MRN / PR / Gate-IN)
Finance
POS
Sales Order / Sales Invoice
Item & Supplier Creation
Print / Format
Rights / Workflow / Permissions / Users
Masters / Opening
Reports / Dashboard
ERPNext Bug
Hall Booking
Support (Login etc.)
New Feature / Application
Budget Related
HR
Training Requirement
Dhananjaya
π¨βπΌ Assigned To β Agent Allocation Feature
When a user creates a ticket, it can be assigned to a specific support agent through the βAssigned Toβ field.
π― This ensures clear ownership of the issue.
π οΈ The assigned agent becomes responsible for resolving the ticket within the SLA timeframe.
π The agent receives an email notification upon assignment.
π§Ύ All ticket updates and solutions are tracked under the assigned agent's actions.
β
Note: Tickets can be reassigned to a different agent if required by the support manager.
π§ CC Email Feature β Keep Managers in the Loop
You can add up to 3 additional email addresses in the CC field to keep relevant stakeholders β such as your manager, team lead, or department head β in the email loop.
All CCβd users will automatically receive email notifications when the following actions occur:
π Ticket is created
π Ticket status is updated (e.g., from Open to Working)
β
Ticket is closed
β
Best Practice: Always CC your manager or concerned authority to ensure visibility and faster resolution.
β Feedback
After ticket is Closed, the requester can give feedback using a 1 to 5 star rating.
βοΈ Auto-Generated Fields
π Creation Date β Auto-set when ticket is submitted (Read-only)
π Closing Date β Auto-set when ticket is marked Closed (Read-only)
π For best results, ensure each ticket is categorized properly and the correct priority is selected. This ensures the right team handles your issue within the expected timeframe.