HR automation in Slack — four chores that stop being anyone's job

Most of what gets sold as HR automation is a form moved from one tool to another: somebody still fills it in, somebody still chases the approval, somebody still does the arithmetic. The automation worth having is the kind where a chore stops being anyone's job. The honest version of that sentence names which chores — because not every step should disappear, and a decision is not a chore.

The boundary before the argument: the Free tier covers up to 5 Employees, with policy answers, Leave Requests, and up to 25 Knowledge Base entries. Leave Policies with monthly Accrual — the arithmetic below — sit in the Team tier at $4 per employee per month, and birthdays are part of the assistant on every plan, including the free one. Nothing below depends on reading the pricing page generously.

Here is the flavor of automation this post means. Nobody typed anything, and two messages arrived:

A calendar nobody checks

A Birthday Reminder goes out up to seven days ahead — to the HR Heads and to that Employee's own Lead, batched into one message when several fall due together, and nobody is reminded about their own birthday. The Wish itself is posted to the channel you choose, never before nine in the morning in the workspace's own timezone, and two people who share the date share one combined Wish.

What this automation stores is a month and a day, never a year — the year is stripped on arrival, so nothing in the system can answer how old somebody is. And it runs on consent: the bot asks once whether celebrating is welcome, declining is a first-class answer honored as no Wish and no Reminder, and anyone can change their mind in conversation. The Birthdays page carries the full rules.

The questions that repeat

The same five questions arrive every week in any team, and the handbook that answers them goes unread because looking things up costs more attention than asking. The automated half here: a policy question is answered from your own Knowledge Base entries, matched against the question that was asked. The manual half is deliberately small: on a miss, the question is recorded as a Knowledge Gap and the first HR Head listed for the Workspace gets a direct message asking to be taught — answer once, and that answer is served to the next person who asks.

What the bot does at that moment instead of guessing — and why the refusal is the feature — is what happens when an HR bot doesn't know the answer.

The arithmetic nobody should do by hand

Leave tracking is the spreadsheet chore: formulas someone maintains, a number that was right in March. With a Leave Policy set, each Employee's Leave Balance grows by a monthly grant on the anniversary of their hire date — held to four decimal places, reported to two and rounded down, so the bot never states more days than are actually held. And the one edge is surfaced rather than guessed: without a hire date, nothing accrues, and the missing date is raised to your HR Head as the failure only a person can fix.

The full arithmetic — short months, the 31st, where the granting anchors — is worked through in how a Leave Balance accrues.

The routing, not the decision

Approvals are where automation pitches usually overreach, so here is the honest split: filing and routing are automated, judgment is not. "Can I take next Friday off?" files the Leave Request and starts the Approval Chain in the same step, and the card lands in the approver's Slack as a direct message with Approve and Deny buttons — no queue, no chasing. A person still clicks. Denying asks for a reason, and the Employee sees it. The Leave Balance moves when the Request is approved, not when it was filed.

Here are both steps of the default chain, from the approvers' side:

The Approval Chains page draws the whole card set, including what the Employee sees at each step.

What stays manual on purpose

Three steps are left to people, each deliberately. The approve-or-deny click, because a balance is arithmetic but an absence is judgment. The teaching, because an answer joins the Knowledge Base only when your HR Head uploads it or teaches it — the bot has no browsing tool and will not improvise your policy from the internet's. And the policy itself: someone states how many days a year and from when, once, and the HR Head guide covers keeping both the policy and the Knowledge Base honest.

Connecting the bot is one Slack consent screen, and the install guide walks through what follows — a fresh install seeds every Request type with an Approval Chain, so the routing above works before anyone configures anything. If "HR automation in Slack" was your search, the fair test of any tool claiming it is to ask, chore by chore: who used to do this, and who does it now? For the four above the answer is nobody. For the three that remain, it is still you — on purpose.