Leave Requests in Slack

An Employee types “can I take Friday off?” and the bot takes it from there. It gathers the dates, files the Request, and starts the Approval Chain in the same step — there is no form to fill in, and no separate “send for approval” button to forget.

Nobody is turned down for being new. A Leave Policy governs only how a Leave Balance grows, never who may spend one — so an Employee in their first week can ask, and what happens next is the Approval Chain’s business rather than a rule about length of service.

A Leave Policy sets one number: the days added each month. Accrual lands on the Employee’s own monthiversary, in your Workspace’s timezone, clamped to the last day of short months so someone hired on the 31st keeps their date instead of drifting earlier through the year. It counts from the later of their Hire Date and the day you created the Policy, so switching Accrual on never owes back-pay for service that predates it. A missed run is deferred, not lost: the next one grants every full month that has since elapsed. An Employee with no Hire Date on file accrues nothing rather than being credited from a guessed one — they can still ask for leave in the meantime. And where you have set no Policy at all for a leave type, that type does not accrue: its balance moves only when an HR Head sets it.

A Leave Balance is fractional, because an Accrual Rate need not divide cleanly into a month: 20 days a year is 1.6667 days a month. The bot quotes it to two decimal places at most, rounding towards zero rather than to the nearest, so it never overstates days an Employee still has to spend.

Approval is what moves a balance. A vacation Request draws the working days between its start and end date from the vacation balance; a paid day-off draws one day per date from the paid day-off balance. Sick and unpaid day-offs consume nothing at all, and neither does a remote-work or late-arrival Request.