Staff Leave & Cover

Leave requests, approvals, affected-booking alerts, and bulk reassignment — one joined-up flow.

Leave RequestsAuto-Flag CoverBulk Reassign
iOSAndroidWeb Dashboard
Team member submits leaveSelects dates · adds reason · taps SubmitOperator sees pending badgeDashboard badge · dates · affected bookings previewApproved (or denied with note)Team member notified either way3 bookings flagged for cover"3 bookings need cover" badge appearsBulk cover screenOne row per booking · picker · Reassign allAll covered ✓

Leave management in most pet care businesses is a string of WhatsApp messages, a shared calendar that's six weeks out of date, and a frantic rearrangement of bookings on the morning someone calls in sick. Wagify replaces that with a proper workflow from first request to last booking covered.

A team member who needs time off opens their own calendar, selects the dates, adds a reason if they want to, and submits. That's it on their end. A notification lands with the operator and a badge appears on the team management screen: "1 pending leave request." The operator sees the request with dates, reason, and a view of what's currently booked for that person on those days — so they know before they approve whether cover is needed and roughly how much.

Approve or deny with an optional note. The team member is notified either way — "Your leave request for 14–16 May has been approved" or "Your request for 14–16 May wasn't approved — please see the note from Sarah." Professional, clear, no ambiguity.

On approval, Wagify checks every booking assigned to that resource on the leave dates and flags them. A "3 bookings need cover" badge appears on the operator's dashboard. Tap it and a bulk cover screen opens: one row per affected booking, showing the time, client name, service, and a resource picker on each row. The picker shows only resources with capacity at that time, so you're not accidentally double-booking someone else. Assign cover for all of them in one pass and tap "Reassign 3 bookings" to commit. Clients are notified that their booking has been reassigned — with the new team member's name, if your notification settings are configured that way.

If you can't cover all of them at once — maybe you're waiting for a team member to confirm — you can resolve some now and leave others flagged. The badge stays on your dashboard showing the remaining count until every affected booking is covered or the leave dates have passed. Nothing falls through the cracks quietly.

Key highlights

  • Team member submits leave from their calendar — operator sees it immediately
  • Approve or deny with a note — requester notified either way
  • Affected bookings auto-flagged on approval with dashboard badge
  • Bulk cover screen — assign all affected bookings in one go or handle in batches

Available on

iOSAndroidWeb Dashboard

Use this with launch access

Get started

No plan tiers during launch