Agentic leave management, human-approved
Otto handles the leave request. The approval stays yours.
Most leave tools are trackers: they store what people type and leave the policy, the counting and the chasing to you. Otto HR treats a leave request as work to be done — Otto understands the dates, checks the balance and the leave type's rules, counts only the days that should count, and routes it to the right approver. Nothing is booked until a person says yes.
01
1 request
From plain language to an updated balance
02
0
Spreadsheets left to reconcile
03
6
Countries with built-in holiday calendars
Why Otto
Trackers record requests. Otto processes them. You keep the final say.
01
More than an absence tracker
An absence tracker stores what people enter and leaves the thinking to you. Otto HR processes the request: it reads the dates, applies the leave type's rules, counts working days against your company's calendar and routes the result down the approval chain. What reaches a manager is a decision to make, not admin to do.
02
One definition of the day math
Working days, public holidays, half-day holidays, carry-over caps, seniority tiers: the counting rules live in one place and apply identically in the employee portal, on HR's screen and when Otto files a request from chat. A balance is a fact, not an opinion — and every change to it lands on a ledger.
03
Connected to payroll, not beside it
In a standalone tracker, approved leave still has to be retyped into whatever runs payroll. In Otto HR leave, attendance and the pay run read the same records: an approved day off never shows up as an absence, and the pay period already accounts for it.
How it works
The request goes in, the approval comes to you, payroll already knows.
A request in plain language
Employees ask Otto in chat — or from any AI tool connected over MCP — and Otto reads the dates, checks the remaining balance and files the request. It passes through exactly the same checks as one filed from a form: leave type rules, day counting, notice windows, blackout periods. Asking an agent skips nothing.
How many vacation days does Deniz have left?
Routed to people, decided by people
Each leave type gets the approval flow you choose — straight to HR, the manager, manager then HR, or a multi-step chain of your own. Approvers are notified with the dates and day count, decide in one tap, and a step that waits too long gets a reminder. Days are reserved when the request is filed and move only on approval.
Time off
Sarah Kim
Annual leave · Aug 4–8 · 5 days
Everyone sees their own answer
Employees see balances, request status and upcoming company holidays in their portal. Managers see who on their team is away. HR sees requests that overlap a teammate's leave flagged before approving, and who is on leave right now. "How many days do I have left?" stops arriving by email.
Good morning, Deniz
Answered without asking HR
Approved leave lands in payroll
The moment leave is approved, it counts: the balance moves, the team calendar shows it, and the attendance timesheet treats the day correctly — no re-entry. When you open a pay run, the period's hours and leave are already reconciled.
Sarah Kim
Annual leave · Aug 4–8
Frequently asked questions
Leave management software keeps track of who is off when: employees request time off, someone approves it, and the system keeps each person's balance current instead of a spreadsheet or wall calendar. Most tools stop at recording. Otto HR is the agentic kind of employee leave management system — Otto understands a request, applies the leave type's rules, counts the days against working days and public holidays, routes the approval and updates the balance, while a person gives every approval.
An absence tracker is a shared calendar with counters: it records that someone is away and shows the total. A leave management system also carries the process around the record — leave types with their own rules, approval routing, balance arithmetic and carry-over. Otto HR goes one step further: the process is worked by an agent. The request is understood, checked against policy and routed for approval without anyone shepherding it, and the employee, their manager and HR each see their own view of the result.
No. Otto files, checks and routes. Approving is a person's job. A request filed through Otto follows the same approval chain as one filed from the portal, and every decision is recorded with who made it. If you configure a leave type with no approval step, its requests are booked directly — but that is your configuration doing it, not the agent deciding.
Each leave type defines its own entitlement: a flat number of days per year, or seniority tiers that raise it as tenure grows — with first-year rules (full allowance immediately, prorated, or after one full year of service) and carry-over caps. Balances roll over automatically at year end, and entitlement raises land on the day they are earned rather than at the end of the month. For companies in Türkiye, the statutory tiers of Labor Law Article 53 — 14, 20 and 26 days — come built in.
Yes — that is the point of keeping them on one platform. An approved leave request updates the employee's balance, appears on the team calendar, and reconciles into the attendance timesheet, so an approved day off is never counted as an absence. Pay runs read the same records, which means the hours-and-leave picture a pay period opens with is already consistent — nothing depends on someone re-typing leave into a payroll tool.
Agentic leave management, human-approved
Let Otto do the counting. You do the approving.
Create a workspace and the built-in annual leave type is ready on day one — add your own types, rules and approval chains in minutes. Ask Otto for a balance, file a request, watch it route. No credit card required.