This guide lists 12 workflows most facilities can automate. For each one: the trigger, the steps, and what to check. For how these fit together, see self storage automation.

Before you automate any workflow

Write the workflow down as it runs today, step by step, including who does each step and how long it takes. Then mark which steps need judgment and which don't. Automate the ones that don't. Keep a person on the ones that do, and make sure the software hands those off clearly.

Every automated workflow also needs:

  • A record. What was sent or done, when, and to whom.
  • An exception path. What happens when a step fails, and who is told.
  • An owner. One person who checks that it ran.

12 self storage workflows to automate

1. Online move-in

  • Trigger: a tenant completes an online rental.
  • Steps: create tenant and lease in the FMS, charge the payment, issue access, send move-in instructions.
  • Check: the unit status changed and access works. See contactless move-in.

2. Abandoned rental follow-up

  • Trigger: a shopper starts a rental, gives contact details and doesn't finish.
  • Steps: send a reminder with a link back to the same unit, within your consent rules.
  • Check: the unit is still available before the reminder goes out. See abandoned rental recovery.

3. Reservation expiry

  • Trigger: a reservation reaches its hold date.
  • Steps: send a reminder before expiry; release the unit after it.
  • Check: released units show as available on the website.

4. Payment reminder

  • Trigger: a set number of days before rent is due.
  • Steps: send an email or text with the amount and a payment link.
  • Check: tenants on autopay get a receipt instead of a demand. See automated reminders.

5. Failed autopay

  • Trigger: a scheduled charge is declined.
  • Steps: notify the tenant, retry on a set schedule, and ask them to update the card.
  • Check: the tenant isn't charged a late fee before the retry window ends, if that's your policy. See autopay enrollment.

6. Late notice and late fee

  • Trigger: rent remains unpaid after the grace period in your lease.
  • Steps: apply the fee your lease and state law allow; send the notice.
  • Check: fee amounts and timing match your lease and statute.

7. Access suspension and restoration

  • Trigger: account reaches the delinquency stage set in your lease; or the balance is paid.
  • Steps: suspend the gate code or app access; restore it on payment.
  • Check: restoration happens within minutes of payment, including payments made after hours.

8. Lien notices and sale scheduling

  • Trigger: the delinquency stages set by your state's lien statute.
  • Steps: generate the required notices, send them by the method the statute allows, log delivery, schedule the sale.
  • Check: every notice and date against the statute, with counsel's review of the templates. See automating delinquency and lien notices.

9. Rate change notice

  • Trigger: a tenant is selected for a rate change.
  • Steps: send the notice with the required lead time, then apply the new rate on the effective date.
  • Check: the notice period meets your lease and state law. See rate increase notices.

10. Move-out

  • Trigger: a tenant submits a move-out request.
  • Steps: confirm the date, check the balance, deactivate access after move-out, mark the unit for inspection.
  • Check: the unit isn't shown as available until it has been inspected.

11. Review request

  • Trigger: a set number of days after move-in.
  • Steps: send a short message with a link to your review page.
  • Check: review requests go to every tenant, not only ones you expect to be happy. Selective review requests can break platform rules.

12. Daily exception report

  • Trigger: every morning.
  • Steps: send the owner a summary of failed payments, failed rentals, gate errors, offline devices and overdue tasks.
  • Check: someone acts on it the same day. See the daily remote monitoring checklist.

Where workflow automation lives

Most of these workflows run inside the management software, with the website, payment gateway, access control and messaging tools as connected parts. Some operators add a general-purpose automation tool to connect systems that don't integrate directly. That can work, but every extra tool is another place for a workflow to fail silently. Prefer direct integrations where they exist, and make sure every workflow writes its record back to the FMS. The automation stack map lists vendors by category.

Messaging rules to know

Several of these workflows send emails or texts. Two federal rules matter most:

  • Email: the CAN-SPAM Act covers commercial email. The FTC's compliance guide says commercial messages need accurate headers, honest subject lines, a valid postal address and a working opt-out honored within 10 business days.[1] Messages whose primary purpose is a transaction the tenant already agreed to are largely exempt, but the FTC reads that category narrowly.[1]
  • Texts: text messages are covered by the Telephone Consumer Protection Act and the FCC's rules.[2] Get documented consent before texting, keep marketing texts separate from account texts, and honor opt-out replies such as STOP.[2]

State laws can add requirements. Have counsel review your message templates and consent language once before you automate them.

Frequently asked questions

What is workflow automation in self storage?

It is software running a facility's repeatable sequences, such as move-ins, payment reminders, access changes and notices, automatically when a trigger occurs, with a record of each step.

Which workflow should I automate first?

Online move-in, because it touches rentals, payments and access at once. Then payment reminders and failed autopay.

Do I need a separate workflow automation tool?

Usually not. Most of these workflows can run inside management software and its integrations. Add a separate tool only to fill a gap, and monitor it.

How do I know an automated workflow failed?

Each workflow should report its exceptions somewhere a person checks daily. A daily exception report is the simplest way.

Sources

  1. CAN-SPAM Act: A Compliance Guide for Business, Federal Trade Commission (accessed November 2, 2026)
  2. Strengthening the Ability of Consumers To Stop Robocalls, Federal Register, March 5, 2024 (accessed November 2, 2026)
Reviewed More in Unmanned