Your Leave RequestIs Now a Slack Command
Every People team has the same gap. The system of record lives behind a login, and the conversation lives in chat. At Taleemabad we closed it by turning the most frequent HR request, time off, into a Slack command. This is how it works, what it took, and how any HR team can do the same.
The problem every HR team recognises
It is 8:40 on a Monday. An employee’s daughter has a fever, the school has called, and they need to tell work they will not be in. They know the drill. Find the HR portal. Remember the password. Wait for the page. Fill in the form. Then open Slack and message the manager anyway, because a form nobody sees is not a request, it is a wish.
Four minutes to file. Half a morning to get noticed.
The HR system is rarely the problem. Ours is Markaz, a platform we built ourselves, and it was never the bottleneck. The problem is the distance between where the record lives and where the conversation lives. Teams spend their day in Slack. HR lives behind a login. Every request crosses that gap twice: once to file, once to chase.
The solution: bring the HR system to the chat
We did not build a new HR tool. We gave the existing one a seat in Slack. Four steps, and nobody leaves the conversation.
1. The request is one command
Type /timeoff. The app greets the employee by name, applies the leave policy that covers them, and opens a short form: what kind of leave, which dates, full day or half, and why. Submit creates a leave request in Markaz identical to one filed on the website. Same record, same emails, same approval chain. No tab opened, no password remembered.
Mock-up of the command and the form.
Working from home tomorrow: /wfh. Spending the day in a classroom, as many of our staff do: /schoolvisit. Neither needs approval. The day is logged, the line manager is told, and the person gets on with their work.
2. The manager decides in a tap
Each request reaches the line manager as a direct message with four buttons: Approve, Reject, Propose new dates, and Open in Markaz. Approve asks for a quick confirmation. Reject asks for the reason the policy requires. The decision is written to Markaz instantly and the message updates in place, so one thread tells the whole story.
Mock-up of the manager’s DM before and after the tap.
Get Jawwad Ali’s stories in your inbox
Join Medium for free to get updates from this writer.
Some managers prefer the website. Requests filed there appear in Slack, and decisions made there are mirrored back. One truth, whichever door anyone walks through.
3. The answer finds the employee
Filing is half the story. Waiting is where goodwill goes to die. So the answer travels back the way the request went out: a confirmation on submit, then the decision in the same conversation, comment included. If the manager proposes different dates, the proposal arrives with Accept and Decline buttons. Nobody goes looking for a status. The status finds them.
4. Presence takes care of itself
Every weekday at 9:00 am, Markaz does two things unprompted. It reminds each manager, buttons included, of anything still waiting on them. And it posts one message in the company-wide presence channel: who is on leave, who is working from home, who is out at a school, each person tagged, their team channel linked, their line manager mentioned. Leave that covers today is announced the moment it is approved.
The 9:00 am post, in its live format. Colleague names replaced.
For our People and Culture team, that one post retired an entire job. The chasing is gone.
The small choices that earn trust
Leave is the most frequent conversation an employee ever has with HR. Make it slow and people stop asking properly. Make it effortless and policy stops being a gate and becomes a service. That only works if people trust what the app says out loud.
- The channel post names the leave category, never the reason. A medical or personal matter stays between the employee and their manager.
- Leave is counted in working days, the way people actually think about it.
- Anything typed is rendered as plain text, so a stray word can never ping the whole company.
- Nothing on the web changed. Slack was added on top, not instead.
What it took
The Markaz team designed and shipped all of it in-house, working alongside AI agents, and went from the first command to company-wide rollout in days, not months. Every Slack flow was tested field for field against the website flow before it went live.
How any People team can do this
The pattern is not specific to Markaz, or to Slack. It needs an HR system with an API and the chat tool your people already live in.
- Start with the request everyone makes. Time off is the obvious one.
- Keep one record. The chat command creates the same object the portal does, never a parallel queue.
- Make the decision one tap, in the place the decider already is.
- Close the loop. Every status change goes back to the person who asked, in the same thread.
- Publish presence once a day, automatically, with the privacy rules built in.
