Fallback Behavior: When No One Is Available

What Fallback Behavior controls

Every team has a Fallback Behavior setting on its detail screen. It answers one question: when this team is asked for an owner and cannot produce, what should happen? A team fails to produce an owner when nobody on it is eligible. That usually means every member is inactive, on time off, outside working hours, or at their cap. 

The four options

Skip to next team (the default)
Do nothing here. Distributely moves on and tries the next eligible team in Team Order. Use this when you have a deliberate escalation order across teams and you would rather another team pick the lead up than force this one.

Fallback owner
Assign the team's designated Fallback Owner directly. This is a direct assignment, not a selection: it bypasses schedules, time off, and caps. The fallback owner gets the record even if they are off that day or already at their limit. Use it when a record must stay with this team.

Standard round robin
Plain round robin for this team.

Ignore availability (round robin)
Round robin across all active members of the team with availability ignored. Schedules and time off are disregarded, and this also bypasses caps. Use it when coverage matters more than working hours, for example on an after-hours inbound form. Expect leads to land with people who are not at their desks.

Both Fallback owner and Ignore availability (round robin) will assign to someone who is over their cap. If caps exist to protect rep workload rather than to enforce a business rule, be deliberate about choosing these.

Setting the fallback owner

The Fallback Owner dropdown stays disabled until Fallback behavior is set to Fallback owner. If the dropdown is greyed out, change the behavior first; the screen tells you the same thing under the field. Changing the behavior away from Fallback owner clears the selection, so you will need to pick the owner again if you switch back.

The order things fire in

Understanding the sequence explains most surprises.

1. A team is asked for an owner and fails. Nobody on it is eligible.
2. That team's Fallback Behavior runs. If it produces an owner, routing is done.
3. If it still produces nothing, the next eligible team in Team Order is tried. That team runs its own owner selection, and if it fails, its own Fallback Behavior.
4. If no team produces an owner at all, the portal-level fallback owner is used as a last resort.

Two consequences worth noting. Teams are tried in Team Order, so the order you set there determines which team's fallback runs first. And each team carries its own setting, so a portal can mix behaviors: a primary team set to Ignore availability (round robin) and an overflow team set to Skip to next team is a reasonable combination.

Portal-level fallback owner:

Go to Settings, then Fallback Owner, and choose a Default Fallback Owner.

This is the only thing standing between an unlucky configuration and an unassigned record. If every team is skipped, every member is unavailable, or a team has no active members at all, the portal-level fallback owner catches the record. Without it, the run ends with no owner and the record sits in HubSpot with nobody on it.

Pick someone who will actually notice. A sales manager or a rotation owner works better than a shared inbox nobody watches. See Portal Settings and Fallback Owner.

FAQ

 

Does the fallback owner have to be a member of the team?

No. Any owner in your portal can be selected. If they are a team member, their normal availability and cap state is ignored for this assignment.

Why is my Fallback Owner dropdown greyed out?

Because Fallback behavior is set to something other than Fallback owner. Change the behavior and the dropdown becomes selectable.

If a team's fallback assigns the record, does the next team still get a turn?

No. Routing stops as soon as an owner is produced. Later teams are never consulted.

Does an attribute mismatch trigger Fallback Behavior?

Yes. If no member anywhere matches the record's attribute value, or the record's property is empty, the team's Fallback Behavior decides what happens next. See Attribute-Based Routing.