Light Tower Extension
Review a light tower extension through reservation, site, and account facts.
A light tower extension call looks simple until you remember that the unit might already be promised to someone else. The caller in front of you wants more days on site. The next customer on the schedule wants that same tower on the date they were told. Your job as the inside sales coordinator is to gather the facts that let the branch make a real decision, not to hand out a new return date because the caller sounds stressed and the ask feels small.
Why This Call Goes Wrong
Extension requests come in fast and usually with a reason attached, rain, a permit delay, a change order from the general contractor. The caller has already decided the extension is reasonable, and they expect you to agree just as quickly. That pressure is where coordinators slip. A light tower on an active job site is not sitting in a yard waiting for nobody. It may have a firm pickup scheduled for the next morning because another crew needs it at dawn. It may sit behind a locked gate on weekends, which changes when a technician can even reach it for inspection. If you say yes before you know any of that, you have made a promise the branch cannot keep, and now two customers are frustrated instead of one.
The other failure mode is treating the call as a formality. Coordinators who rush through it skip the inspection question and the access question, then pass along a bare request to the branch. That forces someone else to make the callback and ask the questions you should have asked the first time. The customer waits longer, and it looks like nobody is coordinating anything.
Prepare Before You Pick Up
Before you say anything about a new date, get the agreement number so you can pull up the actual reservation instead of working from memory. Confirm the current return date on file, since the caller's memory of the schedule and the contract's schedule do not always match. Get the specific new end date they want, not a vague description like a few more days. Ask why the job moved, in plain terms, since weather, a permit hold, and a scope change all carry different weight when the branch reviews the file.
Ask whether the unit has been inspected recently and whether the caller has noticed anything unusual, a warning light, a fuel issue, tower damage. Ask about site access too. A yard that locks on weekends or a jobsite with restricted hours can block a branch technician from doing a checkout inspection even if the extension itself would otherwise be fine. None of this is small talk. Every one of these facts changes what the branch can approve and when.
You are also checking, in your own head, whether you have any reason to believe this unit is already committed elsewhere. You may not have full visibility into the reservation calendar from your seat, and that is fine. Your job is not to solve the scheduling puzzle on the phone. It is to hand the branch a complete, accurate picture so someone with calendar access can solve it correctly the first time.
What to Say
Delia called about a paving job. She said, "The rain cost us two nights on this pour. I just need you to extend the light tower through Friday." Ben did not answer the date question first. He said, "Let me check whether that unit is already committed after its current return date. Before I do, is it running normally, and can your site contact give a branch representative access if we need to look at it?"
Delia told him the tower was working fine, but the yard gate closes over the weekend and nobody would be there to let anyone in. Ben said, "That's useful, thank you. I'm going to record the Friday request and the weekend access issue, and I'll ask the branch to check this unit against its next reservation and your account terms. I'll call you back once I have that answer, with the actual options, not a guess."
Notice what Ben did not do. He did not repeat the word Friday back as a confirmation. He did not say anything about whether an extension usually gets approved. He gave Delia a real next step and a specific reason he could not just say yes on the spot. That is a stronger answer than a fast yes, because a fast yes that falls apart later costs more trust than an honest pause does now.
Mistakes That Cost You Later
The most common mistake is stating a new return date before the branch has reviewed the reservation. Once you say Friday works, the caller plans around Friday, and if the unit turns out to be booked for another job on Thursday, you are the one walking that back. Say what you are checking, not what you expect the answer to be.
A close second is speaking to money or waivers you are not authorized to promise. If the caller asks whether there is an extra charge for the extra days, do not guess and do not offer a waiver to keep them happy on the call. Tell them the branch will include that in the review and you will pass along the answer.
Skipping the inspection and access questions is another one. If you forward a request without asking about site access, the branch either has to call the customer again, which slows everything down, or they schedule a checkout visit that gets turned away at a locked gate. Both outcomes make the coordinator's work look incomplete.
Last, do not end the call without a specific time or method for the follow up. "I'll be in touch" is not a commitment. Tell the caller when you expect to call back, even if it is just later today or first thing tomorrow, and hold yourself to it.
Practice It Until It's Automatic
This is a hard call to get right on instinct alone, so rehearse it before it happens live. Set up a practice scenario where the requested extension overlaps a second reservation and the site has restricted access, since that combination is what actually tests whether you gather facts before you speak. Say the review sequence out loud in plain language, agreement number, current return date, requested date, reason, inspection status, access, then have the practice caller repeat the next step back to you. If they cannot repeat it, your explanation was not clear enough.
A manager scoring this exchange should listen for three things. Did the coordinator avoid stating or implying a new return date before the branch reviewed the file. Did they gather the inspection and access details that the branch actually needs to make a decision. Did the call end with a specific commitment for the follow up rather than an open ended promise to be in touch. Coordinators who are still learning to hold this line under pressure benefit from repeated practice, and DealSpeak's Equipment Rental practice conversations are built around this kind of decision point, where the right first response is a review, not an answer.
If you want to build on this skill, look at how the same discipline applies to other rental requests. The Loader Quote Follow Up post covers a different kind of pressure, a customer pushing for a number before you have the facts to give one. The post on how to Move a Portable Cooling Request Through Office Approval walks through a similar pattern in a request that needs internal sign off before you can confirm anything.
Close
An extension request is really two customers and one unit, and your only job on the call is to get the facts straight before anyone states a new date. Practice the sequence until asking about inspection and access feels as natural as asking for the agreement number. Get that habit right, and the branch gets what it needs the first time, every time.
Practice these next
Capture placement authority and route details before dispatch reviews a container delivery.
Schedule a fence collection with clear quantities, access details, and a site contact.
Turn a loader quote follow-up into a focused review of job details and timing.
Confirm rental authority and branch readiness before arranging pressure washer pickup.
Collect verified specifications, access requirements, and shutdown dates before sending a plant request for review.
Clarify transport, buried utility concerns, and approved guidance for a customer renting for the first time.