Delinquency by Space Type

Delinquency by Space Type allows individual space types to have their own unique delinquency flows, allowing operators to have more control over how tenants are affected by delinquency within Hummingbird.

It also introduces a hierarchy of delinquency flows, where properties can either adopt the corporate settings for a portfolio, or have their own unique delinquency automations based on their operating procedures.

Delinquency by Space Type can be accessed by going to Automations within Hummingbird settings. This replaces the former Delinquency Automation page within Settings.

Delinquency by Space Type displays delinquency workflows not only for every state or territory where you have facilities, but also every Space Type configured within Hummingbird. This enables you to affect tenants storing at standard storage differently than those who are using parking spaces or other niche space types.
Note: Delinquency by Space Type supports Storage and Parking Space Types.

Each state or territory's workflow can be disabled at the Corporate level, or at the Space Type level. Turning off the workflow at the space type or state level will pause all delinquencies and will not initiate any new delinquencies. Turning the workflows back on will resume all paused delinquencies.

Delinquent tenants who were left unaffected by the pause in delinquency will be enrolled into delinquency once the next rent invoice is issued.

Each delinquency workflow can be Enabled or Disabled at both the Corporate level and the Space Type level:

• Disabling a workflow at either the space type or state level will:
  • pause all delinquencies currently in progress.
  • not initiate delinquency for tenants who should become delinquent during the pause.
• Enabling the workflow again will:
  • resume any paused delinquencies at the same stage where they were paused.
  • initiate delinquencies when new invoice payments are missed.
  • not initiate delinquency for tenants that would have become delinquent during the pause. They will only become delinquent once a new invoice is due and payment is missed.

Hovering your mouse over the icon next to the toggle switch shows the last user who activated or deactivated Delinquency, along with the timestamp of when the action occurred.

Additionally, there are three different statuses for the delinquency workflows based on their edited status: Tenant Process, Corporate Modified, and Property Modified. These levels of specificity enable operators to have full control over the delinquency workflows applied across their properties.

• Tenant Process is our standard workflow, based on industry standards and best practices.
• Corporate Modified means the workflow has been edited at the corporate level.
• Property Modified means that the workflow has been edited specifically at the property level.

You can view which properties are affected by a workflow, and what level of modification has occurred for each property, by hovering over the Applies to X Properties text.

Conditional Delinquency

Currently, delinquency automation is purely time-based, and when delays or errors occur, there’s a high risk of falling out of legal compliance. This risk is increased because delinquency flows often have a mix of manual and automated actions.

With the introduction of Conditional Delinquency, actions are now triggered by real-time events or conditions rather than fixed dates. This improvement ensures that actions are executed at the right time, reducing confusion and enhancing the overall effectiveness of the delinquency management process.

Conditional Delinquency allows operators to create delinquency stages dependent on key delinquency actions and is triggered based on specific conditions such as “After Action” or “After Delinquency.” For example, in most states, lien notices can only be sent out after the auction date has been set. With Conditional Delinquency, the lien notice depends on the auction date being set within Hummingbird before it can be automatically sent out via the delinquency workflow.

When a manual task is created, such as a phone call, that action may not be completed on the same day. A dependent action, such as adding a fee, can be relative to that action being completed rather than being mapped to a specific day on the delinquency timeline.

This allows operators to create flexible delinquency workflows that account for delays or failed critical actions.

How does Conditional Delinquency Work?

Conditional Delinquency introduces the ability to create Linked Stages, which depend on past successfully completed actions.

Creating a Linked Stage follows the same process as creating a Delinquency Workflow as before.

When creating a Stage, the operator provides a name and a description and defines the timeframe when this stage occurs and what event this Stage is linked to.

Using the previous example, the Lien Notice document generation and delivery can be tied to the Schedule Auction action in a previous delinquency stage. This ensures that the Lien Notice does not go out unless the Auction has been scheduled.

Linked Stages can be tied to various events, from fees being applied to status changes.

Conditional Delinquency interacts alongside our standard time-based delinquency stages. Thus, introducing conditional delinquency does not affect or break any existing delinquency workflows. 

Additionally, Hummingbird's Delinquency Automation settings page has new UI changes. This page outlines which stages follow the standard time-based process and which stages are action-based.

Configuring Conditional Delinquency

To create a New Stage via Delinquency Workflow in Hummingbird:

1. Add a New Stage: In the Delinquency Workflow, click Add New Stage to create a new dependent stage.

2. Select Dependent Task: Choose the task that must be completed for this stage to trigger. A dropdown menu will display all available actions programmed into the workflow. Select the desired action.

3. Define the Activation Timeframe: Specify when this stage will activate - either immediately after the dependent task is completed or after a set number of days. For instance, you can schedule the Schedule Auction task to occur 20 days after the Lien Notice is sent, ensuring compliance even with delays.

4. Set Stage Actions: Define the actions that will be triggered when the dependent task is successfully completed.

5. Save the Stage: Click Save Stage to finalize and save the new stage.

The newly created stage appears in orange, marked with a link icon next to it, indicating the dependent action and its stage.

Workflow

This flow improves flexibility and precision in the delinquency-handling process.

• Day 0: Tenant Rent Assessment.
• Delinquency actions are now triggered based on conditional events:
  • After Action: Actions are initiated after the completion of a specific action.
  • After Delinquency: Actions are initiated after the start or completion of the delinquency period.

This ensures that actions are executed only when the specified conditions are met, providing better control over the delinquency process.

Action Definitions

These actions are available with Conditional Delinquency in the October 14th release.

Note: Currently, you cannot set a dependency based on the Generate Notice action due to technical limitations with third-party integrations used to deliver documents.