Ship Manager

A desk that supports one office solves hardware by walking. Support a company where people work from home and the same fault becomes a different job entirely.

People underestimate how much of a service desk job this is. Interviewers ask about it constantly, because the answer shows whether you have worked to a process.

A shipping ticket is mostly record keeping. What goes wrong is the wrong address, the return that never came back, and the note nobody wrote for the colleague who picked the ticket up on Thursday.

The commonest scheduled version of this job is a new starter: somebody accepted an offer, they begin on the ninth, and they live two hundred miles from anyone in IT. A configured machine has to be in their hands before their first morning, with whatever else the role needs: a dock, a monitor, a headset, a hardware key.

When it does arrive late, and it will, the cause sits upstream of the courier. The request reached IT four days before the start date, or the hiring manager assumed a machine had already been ordered, or the build was waiting on an account HR had yet to create. Say so plainly in the ticket, and have a fallback ready: a loan machine sent express, or a first day of induction that needs no laptop.

A good desk publishes the lead time and then defends it. "Fourteen days from an approved request" is a promise you can keep. "As soon as possible" is a promise that turns every starter into an emergency.

You need the words, because you will be reading a courier portal and quoting it back to a user who is annoyed.

Waybill

The shipping document that travels with the parcel: sender, recipient, contents, service level, reference. The label on the box is the printed form of it. On an air freight leg it is the air waybill, and its number is what the freight desk quotes.

Tracking number

What a parcel courier actually hands you, and the identifier that lets anyone follow the box through the network. Quote it on the phone and put it in the ticket, and anybody can answer "where is it" without asking you.

Service level

What you bought: ground, two-day, next-day before noon, same-day courier. The biggest lever you have on when something arrives, and on what it costs.

Signature on delivery

The recipient signs, and the courier records who signed. Buy it on every laptop: the signature is your evidence that the machine reached the person it was addressed to.

Proof of delivery

The record of that signature, retrievable from the courier later. The document you produce when a machine is disputed six months afterwards.

Chain of custody

The chain Asset Management drew from the dock to disposal, with a courier added to the middle of it. A gap in it is a stretch of time where nobody can say who was holding the device.

FedEx, FedEx Ship Manager and FedEx Ground are trademarks of Federal Express Corporation. ServiceDesk Simulator is not affiliated with, endorsed by, or sponsored by them.

A laptop needs real packaging to come through a parcel network intact. The rule of thumb: nothing inside the box moves, and nothing touches the wall of the box. Manufacturer packaging is engineered for exactly that, which is the real reason a good stockroom keeps the boxes.

Practical version: lid closed with nothing resting on the keyboard, the charger bagged separately so the brick is not hammering the chassis for two days, a couple of inches of padding on every face, and the box taped so a dropped corner is absorbed rather than transmitted. Take the dongle out of the USB port before it becomes a lever.

Returns get forgotten, and they are what an auditor asks to see. Every machine you send out to replace something means a machine somewhere that has to come back. A leaver is the same problem with a deadline: their last day is fixed, their laptop has company data on it, and after that day they have no reason to think about you at all.

The box the new machine came in is the box the old machine goes back in, and the prepaid return label goes in that box. The packaging, the postage and the address are already in their hands. Every step you remove from the returning user is a percentage point of returns you actually get back.

A prepaid return label already carries the shipper’s address, so the destination is yours to choose: an IT department that processes returns, or a central warehouse that holds stock. Put the ticket reference on the return too, so the parcel that arrives can be matched to the machine it is supposed to be.

Chasing, and writing it off

Chasing is a scheduled job with somebody’s name against it. A working process has dates on it, and a defined point where the asset is marked as not recovered.

If the person stays unresponsive after their manager has asked, it stops being an IT problem. A company laptop is company property, and the escalation goes to HR while somebody is still employed and to the legal team once they have left, usually as a letter quoting what the machine is worth and giving a final date. It almost never goes that far, and the reason it can is the paper trail underneath it.

The write-off is signed above the technician chasing it, and the technician builds the file it gets signed on: what was sent, when, to what address, which label, who signed, what was chased and when. It is an accounting and security event, and a machine holding company data that is never coming back may need reporting as a data risk as well as a lost asset.

The most common way a shipping ticket fails: you shipped to an address that used to be right.

Addresses rot. People move house and tell HR, or tell nobody at all. The address on a three-year-old asset record is a guess. So confirm the delivery address with the human, in the ticket, every time, and write what they said into the ticket so the next person can see where it came from. That confirmation takes one message and prevents the failure that costs a week.

Almost every other ticket you work is finished in one sitting. This one runs for a week, and that changes what a good ticket looks like.

Assume somebody else closes it. You could be off sick on the day it arrives, and the colleague who picks it up should be able to read the whole week off the ticket. Write it for them: what was confirmed and by whom, what was sent, which unit by name or asset tag, which address, which service level, which tracking number, whether a return label went in, and what the next expected event is with a date on it.

Keep the user informed on a rhythm. A message when it ships with the tracking number, a message when it lands, a message when the return is still outstanding. Silence during a slow ticket is what turns a patient user into a complaint.

Close the ticket when the user confirms the new machine works and the old one is back or accounted for. The courier’s delivered scan usually lands days earlier than that.

Open Tools, then under Management choose Ship Manager. The header says Send hardware to an end user: the console addresses a package and sends it, and every rule it enforces comes from part one.

Recipient information holds Recipient name, chosen from the staff list, and the four address boxes: Street address, City, State and Postal code. The address comes from the person, the way it does at work: you ask them over Company Chat or on a call, and that is the exercise. A Refill last address shortcut appears once you have shipped something, and it is remembered only until you reload: useful for a second leg on the same ticket, and wrong on a different person.

Package details holds the rest. Sender (from) is the department the parcel is from, and is cosmetic. Reference carries the weight: it shows the request this shipment is booked against, by number and requester, so read it before you press anything. Equipment to ship is the contents, from cables and chargers up to Computer (laptop / desktop), which shows the number of built units in brackets beside it.

Choose the computer option and a Select a computer to ship picker appears, listing every unit on the shelf by build method, device type and hostname. With an empty shelf you get an Open Computer Deployment button instead, because the machine has to be built in Computer Deployment before it can be sent. Shipping speed offers four: Standard (5 to 7 days), Express (2 days), Priority (Same day) and Rush Priority (Instant). It is genuinely how long the package takes to arrive in here, about twenty seconds down to none.

Tick Include return label and a third panel appears. Returning to picks the depot, IT Department or Central Warehouse, and Prepaid label ships to fills in that depot’s address by itself, for the same reason a real prepaid label already carries one. Then Ship.

Three checks run before a package leaves, and they are the three failures from part one. All three hang off the request named in Reference. Address a package to somebody whose name resolves to no open request and there is nothing to check it against: it goes out with the same confirmation and credits nothing.

The recipient. The package has to reach the person on the ticket. Address it to somebody else, at however valid an address, and the console refuses it.

The address. A correct address ships. A wrong one is refused with Shipped to the wrong address, so the user never received it. In between: the console queries a postal directory with what you typed, and if the street number and postal code resolve to a real record with only a descriptive detail off, such as a misspelled city, it offers what it found under Address lookup found a matching record: with a Use this address button. It offers the record and then waits: the shipment moves once you have picked one.

The return label. A whole computer ships only with Include return label ticked. The broken machine has to come back, so the label has to be in the box before the box goes.

After you press Ship

A Shipment sent confirmation pops, a countdown runs in the panel, and Delivered! appears when it lands. The arrival is what matters: the requester messages you when the box turns up, and a correct replacement resolves the ticket at that moment.

At work the close comes when the user confirms the new machine works and the old one is back or accounted for, which is days after the delivery scan. Here the arrival does both jobs at once: the requester's message stands in for that confirmation, the ticket resolves on it, and the return leg is outside what the queue tracks. So this queue closes a shipping ticket one step earlier than a real desk does. The chasing from part one, a reminder at seven days and the manager at fourteen, belongs after the point where this ticket has already resolved, and on a real desk it is yours to do.

That timer survives a reload. A package in transit when you close the tab is re-armed when the session comes back, because the ticket needs that arrival before it can close.

What a real send hangs off

Here the countdown is the whole journey. At work the send produces a waybill and a tracking number first, and that number is what everything afterwards hangs off: into the ticket the moment it exists, quoted to the user who asks where their laptop is, quoted to the courier when the parcel is lost, damaged, or refused at a reception desk that did not recognize the name. Shipping speed here changes a wait; at work it changes a price, and across a border the commercial invoice is what decides the date. Write the same things into the ticket here that part one asked for: who confirmed the address, which unit went, which label, and what the next expected event is.