Skip to content
VEYQON
Module · Operations/SUP

A ticket that knows what the customer bought.

Tickets that already know the order, the unit and the warranty, timed against real support hours.

6 feature areas·13 record types·SLA against real support hours

Ticket
LINKED TO WHAT WAS SOLD
In warranty
Order
Delivery
Serial no.
Service levelSUPPORT HOURS ONLY
Response
ResolutionHold
Nearing targetESCALATES

ILLUSTRATIVE · NOT A REAL TICKET

Inside the module · 33 features/01

6 areas. Pick one.

Issues
Issue recordCreated from anywhereThreaded communicationLinked to the transactionIssue types and prioritiesAssignment and teamsSplitting an issue
How it runs/02

Four steps, in order.

01
Arrive

A ticket is created from email, portal, or form. The contact is matched, the customer's orders and serial numbers are linked, and entitlement is checked.

02
Commit

The applicable SLA sets a response and resolution target for that priority, measured against real support hours — and paused while you are waiting on the customer.

03
Resolve

Correspondence threads onto the issue. Where the fix needs attendance, a maintenance visit is raised with parts issued from stock and charged by entitlement.

04
Close and read

The ticket closes against its agreement status, and response time, breach rate, and failure patterns are read from the tickets rather than reconstructed.

The records · 13 types/03

Everything you can create.

IssueIssue Type / Issue PriorityService Level AgreementService Level PriorityWarranty ClaimSerial NoMaintenance ScheduleMaintenance VisitContractCommunicationStock EntrySales InvoiceSupport Settings
Reports · 10/04

Ship with it, not commissioned.

Issue SummaryIssue AnalyticsFirst Response Time for IssuesSLA Breach SummarySupport HoursSerial No Warranty ExpiryMaintenance SchedulesMaintenance Visit SummaryItem-wise Sales HistoryGross Profit
Settings/05

The switches that shape it.

Default service level agreement
Applied where a customer has none of their own
Support hours
Working windows per weekday, plus a holiday list
Hold pauses the clock
On, with hold time recorded on the ticket
Escalation
To a named person, on a set delay before breach
Track first response
Measured from creation to first outbound reply
Portal ticket raising
On, under the same login as orders and invoices
Close after days of inactivity
Automatic, or left to an agent
Assignment rule
By team, priority, or round robin

Next step

Bring one process. We will run it live.