'There's a package here for you, but it doesn't fit in your mailbox.'
Front desk staff field some version of this situation multiple times a week. Without a clear procedure for what comes next, every package becomes a judgment call. And judgment calls, at scale, create inconsistency.
This guide covers the four package scenarios every virtual office center encounter and gives your team a clear, repeatable SOP for each one.
Standard mail has a defined workflow: log it, notify the client, store it in the assigned slot. Packages don't fit that workflow cleanly. They vary in size, weight, fragility, and urgency. They arrive from carriers who have different delivery requirements. And some clients treat package pickup as on demand, which it isn't, unless you say it is.
The most effective package SOPs address this upfront: packages are a managed service with defined parameters, not unlimited accommodation. Setting that expectation with clients before the first package arrives prevents most of the friction.
This is the most common situation. The package is within a reasonable size; it just doesn't fit the assigned slot.
Default SOP:
Log the package with the carrier's name, tracking number, and arrival time.
Store it in your designated overflow area.
Notify the client on the same day using your standard notification channel: email, phone, or Delivered if you are with Alliance.
Set a pickup window: clients should collect the package within 5 business days. After that, a storage fee applies or the package is returned.
If you don't already have an overflow storage area designated, that's the first fix. Packages sitting on the front desk are a liability and a visual signal that your process isn't working
Pallets, large equipment, or freight deliveries require a different response. Your center is not a receiving dock. Most virtual office agreements explicitly exclude freight.
Default SOP:
Do not accept freight shipments.
If a carrier attempts delivery, politely decline and direct them to the consignee. Immediately notify the client that a freight delivery was attempted and that your center cannot accept shipments of that type.
Follow up in writing the same day.
If you have clients who regularly receive large shipments, address this directly during onboarding. It's easier to set the boundary before the first delivery than after.
Clients sometimes request that specific mail be refused or returned. This could be from creditors, former business partners, or senders the client wants to cut contact with.
Default SOP:
Acceptance policy is yours to set. If you accept and log a piece of mail, it's in your system.
If you want the option to refuse at the door, that requires staff to actively screen deliveries, which is operationally complex.
Most centers find it easier to accept all mail and let clients handle the return-to-sender process themselves.
If a client asks you to write 'Return to Sender' and hand it back to the carrier, confirm this is permissible under your agreement. Document the request and your response in writing.
'I need to pick up my package today. Can you stay late?' This request is more common than it should be, and the answer needs to be consistent.
Default SOP:
Set your pickup hours clearly in your client agreement and enforce them.
If a client needs outside-hours access, a special accommodation fee is appropriate. Don't create an informal exception culture because it will be expected by everyone who hears about it.
The better solution is proactive notification. If clients are notified just after a package arrives via Delivered, they can plan their pickup within business hours without urgency.
The best time to communicate your package policy is during onboarding, not when a problem occurs. Your virtual office agreement should include maximum package dimensions you'll accept, storage duration before returning or fees, freight exclusion language, and your notification process.
Review your current agreement against these four points. If any are missing, add them. A client who signs an agreement that includes your package SOP cannot later claim they didn't know.
Further Reading: