# Request → OOO email in 30 seconds. Not 3 emails.

Employees hate HR portals. Managers hate approval emails. Mukh.1 turns the entire leave flow into a 30-second chat — apply, approve, auto-block calendar, auto-set OOO. Done.

30 sec

Apply → OOO time  
1 tap  
Manager approval  
0  
Spreadsheets needed  
[See the journey](/content/demos/leave-approval#stages/index.html)

## Leave flow is a 1990s relic.

Open HR portal. Find leave form. Pick dates. Submit. Email manager. Manager forgets. Email again. Manager approves. Calendar still not blocked. OOO never set.

### Painful for everyone
- HR portal needs login + 5 clicks
- Manager gets email, forgets to approve
- Calendar not auto-blocked → conflicts
- OOO email forgotten → urgent emails missed
- Team doesn't know who's out when
- No conflict-check (everyone gone same week)

### Painless for everyone
- Apply in chat — 30 seconds total
- Manager: 1 tap to approve
- Calendar auto-blocked once approved
- OOO email auto-drafted + set
- Team gets a "who's out next week" digest
- Smart conflict alerts to manager

## How it works — every stage interactive.

Scroll to see exactly what happens, end-to-end.

### 01 EMPLOYEE APPLIES

### 30 seconds in Slack/Teams

No portal. No form. Just chat. Bot recognizes the employee, knows their leave balance, fills in the boring stuff.
- Knows employee's leave balance from HRIS
- Auto-detects working days (skips weekends/holidays)
- Multilingual

<30 secSlack · Teams · WhatsApp

Mukh Leave Bot

Apply + approve in chat

### 02 SMART CONFLICT CHECK

### Bot warns about coverage gaps before manager sees it

Detects if multiple team members are gone at same time, if employee is the only one in a critical role, or if it's peak season. Surfaces these to manager.
- Cross-references team coverage
- Flags single-point-of-failure roles
- Suggests alternatives (e.g., loop in another team member)

Auto-flaggedHRIS data + smart rules

### 03 MANAGER APPROVES

### One tap from manager · everything else auto

Manager taps "Approve" in chat. Bot does the rest: blocks calendar, sets OOO email, notifies team, updates HRIS, deducts balance.
- One-tap approval (no portal login)
- Auto cascade: calendar + OOO + HRIS + team digest
- Audit trail for compliance

### 04 TEAM AWARENESS

### "Who's out next week?" — answered before asked

Auto-digest to the team every Monday morning: who's out, when, who's covering. No more "wait, Sara is on leave?"
- Weekly team OOO digest
- Per-employee "next 30 days" view
- Slack/Teams reactions to acknowledge

### 05 HR ANALYTICS

### Patterns + insights, not just data entry

See leave trends, identify burnout signals (someone hasn't taken leave in 9 months?), forecast staffing gaps.
- Burnout detection (employees not taking earned leave)
- Staffing gap forecasts
- Per-team leave fairness analysis

##### Leave analytics · April 2026

247 employees · 1,247 leave requests YTD

Avg approval time

47 min

Auto-approved (within rules)

68%

Burnout flags

3 (auto-nudged)

Coverage gaps avoided

12 (smart routing)

Insights
- Average approval time dropped from 4 days to 47 min
- 3 employees haven't taken leave in 6+ months — burnout risk · auto-nudged
- May 5–9 saw 12 leave requests (peak) — flagged for HR planning
- 0 calendar conflicts caused by leave this quarter (vs 47 last year)

## Leave done, the modern way.

Numbers from Mukh.1 leave management customers (50–500 employees).

30 sec

Apply → OOO time  
vs 3 days

+47 NPS

Employee satisfaction  
vs HR portal

68%

Auto-approved  
Within manager rules

0

Spreadsheets  
No more Excel for leave

### Connects to your HRIS + calendar

Teams · OutlookSlackGoogle CalBambooHRWorkdayZoho PeopleSAP SuccessFactors

## Stop running leave on email + Excel.

Connect your HRIS + calendar. We'll roll out chat-based leave for your team in 7 days.