Set Expectations for an After Hours Delivery Request

A customer wants equipment on site after your yard has closed for the night, and the request usually sounds simple. It rarely is. An after hours delivery touches dispatch capacity, driver safety, site access, and sometimes a building's own security rules about who can be on a loading dock at midnight. Your job as the inside sales coordinator is not to promise a time. It is to collect the facts dispatch needs to say yes, no, or something in between, and to do that without leaving the customer thinking the delivery is already locked in.

Why This Conversation Goes Wrong

Most coordinators want to be helpful, and a customer asking for a midnight delivery usually sounds stressed or in a hurry. That pressure pushes people toward one of two bad habits. The first is agreeing to a time on the spot, because saying yes feels better than asking questions. The second is treating the request like an order that just needs processing, without checking whether the site can actually receive a delivery at that hour.

Both habits create the same problem later. Dispatch reviews the route, finds a gap, and has to call the customer back to walk something back. Now the customer heard midnight from you and something different from dispatch, and they remember the first number, not the second. The fix is not to slow down and hedge on everything. It is to ask the right questions once, at the start, so the request that reaches dispatch is complete and the customer knows a plan is still being reviewed rather than confirmed.

Gather the Facts Before You Answer

A after hours delivery request is really six or seven smaller questions wearing one trench coat. Before you send anything to dispatch, get the delivery address and any gate or access code, the name and phone number of whoever will meet the driver, and whether the site has a permit or building rule that limits delivery vehicles at certain hours. Confirm the requested equipment by model or spec rather than a general name, since a customer who says lift might mean a scissor lift, a boom lift, or a telehandler, and that mismatch causes its own headache. If you want a full walkthrough of that particular trap, the post on how to Resolve an Unclear Equipment Name at the Rental Desk covers it in detail. Finally, ask for the latest acceptable arrival time, not just the requested one, since dispatch has more room to work with a window than a single fixed clock time.

Write every answer into the order record as you get it. A dispatcher who opens that record later should not have to call the customer just to find the gate code or the receiving contact.

What to Say When the Request Comes In

Priya, a warehouse project manager, calls and says, "We close at ten tonight. Can you get the scissor lift here by midnight."

You say, "I can send that request to dispatch right now. Before I do, I need a few details. Who is going to meet the driver at the gate, how does the gate open after hours, and does the building have any rules about delivery vehicles at night."

Priya says security requires driver names to be submitted in advance, and one loading lane stays blocked overnight for another tenant.

You say, "Send me the security procedure and the name and phone number for whoever meets the driver. I will note the lane restriction on the request so dispatch can plan the route around it. I will call you back once dispatch has reviewed the schedule, and that will tell us whether midnight works or whether we need a slightly different window."

Priya asks, "So it is not confirmed yet."

You say, "Correct, nothing is confirmed until dispatch has a route and a driver assigned. I expect to have an answer for you within a few hours, and I will call you either way."

Notice what that exchange does. You gave Priya something concrete to do right away, sending the security procedure and contact details, and you were direct that the time is under review, not booked. She leaves the call with a task and a timeline instead of a promise you cannot keep.

Mistakes That Make This Harder

The most common mistake is naming a specific delivery time before dispatch has looked at the route. Even "I think midnight should work" gets remembered as a commitment. Say what you are doing, not what you expect the outcome to be.

A second mistake is skipping questions because the customer sounds rushed or annoyed. The questions take less time than the callback that happens when dispatch discovers a blocked lane or a locked gate after the truck is already loaded. A third mistake is treating the equipment name as settled without checking the spec, especially late at night when a customer is more likely to use shorthand. A fourth is closing the call without telling the customer what happens next and roughly when. Silence after a request like this reads as a stall, even when your team is actually working on it.

How to Practice This Until It Is Automatic

Pull an after hours order from the last month and check whether the record has a gate procedure, a receiving contact, and a confirmed equipment spec. If any of those are missing, that gap is exactly what a customer call would have caught, and it is worth a few minutes of roleplay to fix the habit. A manager can run this as a short scored exercise, one coordinator plays the customer with a wrinkle like a blocked lane or a locked freight elevator, and the other has to surface it before ending the call.

DealSpeak is built for that kind of repetition, since it lets a coordinator run the same after hours scenario several times with different complications until the questions come out without hesitation. The Equipment Rental practice conversations library has more scenarios built around this same skill, including how to Verify Pickup Details When a Crew Member Callswhich shares the same core discipline of confirming facts before confirming anything else.

Score the practice call on two things only, whether the coordinator got the site facts dispatch actually needs, and whether the customer hung up knowing what happens next. Everything else is secondary. Get those two right consistently, and after hours requests stop turning into callback problems.