ITSM module

Field tickets, contracts and customer quotas — in the same system as your employee data

IT service companies have to issue tickets, dispatch engineers, follow the work on site and collect customer signatures — usually on paper or over LINE.

WO-2569-0873 · Firewall replacement
External · IT Field Engineer · Siam Tech Co., Ltd.
In progress
Urgency: HighType: MA2 engineers
Work checklist (pulled from the MA template)
Back up the existing config
Install the new device
Test the connection
Customer signs off
3 ticket modes

Covering both internal work and customer work

Internal — IT Service Desk

Service work inside the organization: employees report issues, the IT team picks them up. No sign-off signature needed.

External — IT Field Engineer

Engineers going out to the customer's site. Both the engineer's and the customer's signature must be captured when the job is closed.

Lab Room

Work done in the lab or repair center. No sign-off signature needed.

DimensionOptions in the system
Job type (5 kinds)MA (maintenance contract) · Repair · Installation · Consulting · Other
Urgency (5 levels)Critical · High · Medium · Low · Unspecified
Ticket statusDraft → Open → In progress → Completed (and Cancelled) — the system switches it to “In progress” automatically when an engineer is assigned at creation time
AssignmentSeveral engineers can be assigned to one ticket
Work on site

Engineers miss nothing, and customers sign off digitally

Checklist templates by job type

Create them in advance and they are pulled into the ticket automatically — MA jobs get the MA checklist, installation jobs get the installation checklist.

E-signature

Captures both the engineer's and the customer's signature when the job is closed. Attach files and photos from the site. Produce a PDF ticket report to send to the customer.

Operations dashboard

Upcoming jobs · job counts by status per year · latest jobs.

Dashboard for customers

End customers can see the status of their own jobs, with a list of overdue jobs and a summary of remaining credit.

Cancelling a ticket is a soft delete — the data is not lost, it can always be audited, and any credit that was deducted is returned automatically.
Internal service requests

Cross-department work does not stall, because it has an owner and a clock

A stage-by-stage hand-off route: Engineer → Procurement.

Request statuses

Open · Waiting on Engineer · Waiting on Procurement · Completed · Cancelled · Rejected — each stage has its own owner and its own deadline.

Pass on and reassign

Pass closes the current stage and opens the next one; only the actual owner of that stage may pass it on. Reassign is available when the original owner is on leave or has moved roles. Only the procurement stage can reject.

Automatic SLA tracking

Warns when 80% of the deadline has elapsed (SLA Warning) and alerts when it is exceeded (SLA Breached), with an email to every owner involved.

Every event is logged — create, edit, assign, reassign, close stage, reject, close request, update procurement item, SLA warning, SLA breach. There are separate role-based engineer-queue and procurement-queue screens. Procurement items are recorded with their quotation files and can be linked to assets taken into the system.

A ticketing system tied to contracts and customer quotas

Book a walkthrough and our team will run a real ticket from open to close.