Vacation Handoff

Vacation handoff lets a workspace member choose who covers their work during planned absence.

During an active vacation period, Bnder treats the away member as unavailable for capacity and routing. Their replacement can receive direct task and ticket handoffs so open work still has an owner.

Add your own vacation period

Open User Settings -> Calendar and find the availability section.

Add:

  • Start date
  • End date
  • Replacement member
  • Optional note

The replacement must be another active member of the same workspace. Dates use the away member's local calendar date, so the period starts and ends according to that member's timezone.

In Discord workspaces, members can also use:

  • /preferences vacation
  • /preferences vacation_clear

Add a period as an admin

Admins can also edit a member's planned absence from Workspace Settings -> Organization.

Open the member row, edit the profile, and add a vacation replacement period. This is useful when an admin maintains schedules for a support or operations team.

What happens during the period

When the period is active:

  • The away member is skipped by ticket routing.
  • The replacement is considered in fallback pools where appropriate.
  • Task assignee pickers show an availability indicator.
  • Open tasks assigned directly to the away member can be assigned to the replacement.
  • Open tickets assigned to the away member can move to the replacement.
  • Normal assignment notifications are sent.
  • Task history and ticket activity record that the move was an availability handoff.

For team-owned tasks, the team assignment stays in place. Bnder can add the replacement as a temporary direct assignee so someone is accountable while the team member is away.

What happens when the period ends

Bnder can hand work back automatically when it can still identify the assignment as an automatic vacation handoff.

Automatic handback only happens when:

  • The original member is still active in the workspace.
  • The replacement assignment still matches the recorded handoff.
  • The work was not manually reassigned in a way that breaks the handoff.

If a manager manually changes the assignee during the absence, Bnder respects that change and does not force the work back.

If one replacement covers several people at the same time, each original assignee is handled separately.

Tips

  • Choose a replacement who has enough context and permission to work the items.
  • Add a short note if the replacement needs special instructions.
  • Use Ticket Routing with People if ticket queues should automatically skip unavailable people.
  • Use Organization Structure to keep team leads, managers, and backup users current before absence starts.