Ticketing system
The ticketing system for vending service
A ticket here is not a mail thread but a work order: it knows which machine sits at which site for which customer — and who is driving out.
- Customer, site, machine
- Deadlines in working days
- Hosted in the EU (Frankfurt)
Built for vending service
Three things a ticket can do here
The ticket knows customer, site and machine
In Vecodesk a ticket hangs off a customer and an address — or off your own warehouse for depot repairs — and points at the machines involved.
Every assignment comes back with an answer
Each assignment is its own record with an acceptance deadline: accepted, en route, on site, done. Declines need a reason and stay in the history.
Deadlines count in working days
Three clocks run on every ticket: first response, resolution, no movement — with targets per priority, counted in working days and around your public holidays.
In the browser
The office workplace
Dispatch, service management and leadership work on the same data, with different views onto it.
- 1
A ticket that knows where it belongs
Customer with address or your own warehouse, the machines involved, a contact — and separately the technicians in the field.
- Anchor: customer and address — or your own warehouse for depot repairs
- Ownership in the office, separate from assignment in the field
- Four priority levels, your own statuses, your own fields
- 2
Lists, board, saved views
Switch between list and board, group by status or technician. Four views ship with it — All, Mine, Unassigned, Overdue — and you add as many as you like.
- Show and hide columns as needed
- Share your own views and set one as the start page
- 3
Everything about the job in one timeline
Comments and work entries sit under one another, each public or internal. A work entry carries machines, tasks, parts with quantity, duration, kilometres and attachments.
Features
What belongs to the office
Customer → site → machine
The register mirrors reality, down to the machine on the third floor.
Warehouses and number ranges
Depot stock, repair tickets against the warehouse, placement history per machine. Number ranges to your own scheme.
Permissions down to the button
Technicians their own jobs, the office everything. What someone may not do is refused server-side.
Trash and change history
Deleted tickets can be restored. Every field change sits in the history with time and person.
Closing with evidence
Enforceable if you want it: no closing without an issued service report and an answered parts question.
FAQ
Questions about the ticketing system
Isn't this just a helpdesk?
No. In a helpdesk a ticket hangs off a mailbox; here it hangs off a customer, a site and a machine, and is dispatched to technicians — with an acceptance deadline, a status and an assignment history.
Can we create our own fields and statuses?
Yes. Custom fields come in six types, optionally required, for customers, machines and tickets. You name your own statuses; they hang off five fixed base types.
How does our existing data get in?
Customers, sites and machines sync in from 4Vending, machine data additionally from Televend Cloud. Operations running neither use the data import.
Related
Let's create a ticket for one of your machines.
A personal demo, 30 minutes, along your own use cases.