Unit holds
Customers hold an available unit for a set period, and the hold releases automatically if no paperwork follows.
A booking and intake website for self storage operators handles unit holds, move-in appointments and tenant paperwork in one flow, so the office stops retyping the same details. SIZ Group builds these flows on WordPress, Webflow or custom code.
Self storage often sells in a hurry. A customer moving house on Friday needs a unit by Saturday, and a prospect who cannot hold a unit online will rent from the next facility. A hold function keeps the sale open while the customer finishes the paperwork.
Paperwork is short but easy to get wrong. A rental agreement, an insurance choice, an autopay setup and a copy of identification all have to be right before the gate code goes out. An intake flow that checks each step prevents the errors that delay a move-in.
Move-in appointments help busy facilities too. A truck rental, a moving crew or a long drive can make a scheduled arrival matter, so the booking calendar should show open times that the office and the gate can actually handle.
The office manager should test the hold function first. Place a hold on an available unit, try a second hold on the same unit, then let the first hold expire and confirm that the unit reappears. Each step should match what the management software shows.
Check the intake path from start to finish. A completed rental agreement, insurance choice and autopay setup should land in the tenant record with a time stamp, and the gate access code should be issued only after the account is active.
Confirm that a move-in appointment blocks the right time on the office calendar. Two customers should never be booked into the same office slot, and the confirmation should tell the customer which gate to use.
Start with unit holds. A customer selects a unit size and a location, sees the monthly rate and places a hold for a fixed number of hours or days. Holds that expire on their own keep the unit available for the next customer.
Add move-in appointments next. The customer picks an arrival time, and the confirmation includes the address, the office hours and a reminder. Keep the calendar limited to the times the office can actually staff.
Hold back the advanced features until the first two work. Truck rental, mobile gate access and add-on products can follow once holds and appointments have run for a few weeks and the team knows which requests come in most.
Customers hold an available unit for a set period, and the hold releases automatically if no paperwork follows.
Arrival times match the hours your office is staffed, with a reminder sent before the visit.
The rental agreement, insurance choice and autopay setup are completed online and filed to the tenant record.
The gate code is issued once the account is active, with clear timing in the confirmation email.
Staff see every hold, appointment and incomplete form in one list, with time stamps.
Most facilities run SiteLink, storEDGE or Storable, which hold unit availability, tenant accounts and gate settings. The booking site should read availability from that system and write holds and tenant data back into it.
Confirm the connection early. Some systems expose holds through an API, while others sync on a timer. We would test holds, expiry and tenant creation against a sample account before launch, then state the sync interval in the scope.
Payments and autopay run through the processor your software already uses, so card numbers never reach the booking site. Confirmations can come from a shared facility mailbox, hosted on Google Workspace or Microsoft 365.
The most expensive mistake is a hold that never releases. If the expiry does not match the software clock, units stay blocked and the site shows fewer options than the office really has. Test the expiry against a real clock before launch, not only in a demo.
Another mistake is a form that asks for too much before the hold. A customer who only wants to see whether a unit is free should not need to upload identification. Collect the name and move-in date first, then the rest after the hold is placed.
Avoid vague gate instructions. A confirmation that says the code will work soon leads to calls on move-in day. State the exact time the code becomes active, and what to do if the gate does not respond.
Scope grows with each location and unit type. A single facility with a few unit sizes costs far less to set up than a group with separate rates and holds at every site. Decide early which sites need their own booking pages.
The software connection is the second driver. Live holds need more testing than a contact form, and the written scope should show that difference as its own line so the trade-off is visible before work starts.
Timing depends on how fast the team confirms rates, hold periods and gate rules. Those answers come from the operations manager, so assign one person to approve them before scoping begins.
The hold reads availability from your management software, so a unit locks the moment a hold is placed. We test two competing holds and an expiry before launch, so you can watch the unit release on its own.
Yes. The tenant form is built phone first, saves progress and accepts photos of identification. The completed file lands in the tenant record, and the office sees it without a call.
The hold expires and the unit returns to the available list, and the office sees the incomplete form in its queue. A reminder email can go out before the hold ends, if you choose to send one.
No. The front desk still handles walk-ins, questions and unusual cases. The site takes routine holds, appointments and paperwork off the phone line, so the office can focus on customers who need a person.
Websites range from $300 to $2,200, depending on scope. Locations, unit types and the software connection set the price, and the written scope lists each item before any work begins.
Tell us your locations and software, and we will send back a scope covering the connection and the price.