Service requests
PT TSI uses email-based intake to help organize device, network, deployment, maintenance, and documentation needs before work begins.
Request routes
A clear request does not need to be long. Start with the work type, then add site context, devices, impact, and expected output.
Choose from work devices, access networking, deployment, changes, maintenance, or support follow-up.
Send the site, work area, devices, connections, impact, timing, and expected output so the initial scope can be organized.
Use a clear subject and include a short requirement summary. Unconfirmed details can be completed during clarification.
Request desk
The initial request does not need to be perfect. Basic information is organized into work scope, category, site needs, and expected outputs.
Request categories
Clear classification helps determine the information needed at the start, the parties to involve, and the records to prepare.
Computers, laptops, work tablets, monitors, printers, scanners, peripherals, and communication devices that need preparation or records.
Routers, switches, access points, cables, ports, work area connections, and practical connection notes.
Device installation, workstation moves, device additions, connection changes, and coordination with involved parties.
Device issues, repair follow-up, record updates, rechecks, and readable status summaries.
Work status
For requests that need follow-up, status helps the work owner see what is already clear, what is waiting for information, and what has been closed.
The initial email or brief is received and the main context is recorded.
Site, device, access, or involved-party information is completed.
The agenda, work sequence, and preparation needs are organized.
Work, changes, issues, and open status are recorded.
Final output, device records, and follow-up notes are handed over.
Initial information
If details are incomplete, send the known condition first. PT TSI can help shape clarification questions before the scope is agreed.
Keeps the need, site, work category, involved parties, priority, and clarification items together.
Connects timing, workstations, responsibility, action sequence, status, changes, and issues that appear.
Creates material for the next operational step so the relevant team understands devices, connections, output, and follow-up.
Start by email
Use the company channel to send the initial need. Once the context is clear enough, the request can be shaped into a scope note, work schedule, and handover record.
