What Are Tickets?
Tickets in Zeltask are a centralized channel for registering, managing, and tracking incidents, requests, or reports that arise during daily operations. Any user can report a problem or need, and the responsible teams can coordinate resolution from start to finish.
[Screenshot: Tickets module showing a list of tickets with different statuses and priorities]
Internal vs. External Tickets
Tickets are classified by their origin:
| Type | Origin | Example |
|---|---|---|
| Internal | Created by users within Zeltask — from the module, a location/asset QR code, or an inspection | Equipment failure reported during a routine round |
| External | Submitted through a configured ticket channel | Customer complaint received via a public form |
For internal tickets, the Origin field shows the associated asset or location name. For external tickets, it shows the channel name.
What the Tickets Module Helps You Do
- Register incidents, requests, and reports quickly and clearly
- Classify and prioritize each ticket by urgency and importance
- Assign responsible parties and track the status of each case
- Link corrective actions and inspections directly to the ticket
- Maintain a complete history of activity and communication
- Share tickets via public links when needed
How Tickets Connect to Other Modules
Tickets are directly connected to other Zeltask components:
| Module | Connection |
|---|---|
| Actions | Create or link corrective actions to resolve tickets |
| Inspections | Start inspections linked to a ticket for structured follow-up |
| Assets | Associate tickets with specific equipment |
| Locations | Link tickets to the area where the issue occurred |
| Vendors | Track vendor involvement in ticket resolution |
Related Articles
- Create a Ticket — Step-by-step guide to creating tickets
- Ticket Detail View — Understand all ticket information at a glance
- Ticket Channels — Set up external submission channels