For people & HR teams
One front door, instead of being everyone’s front door.
Employee requests are individually trivial and collectively enormous. They arrive by DM, by email, and by someone catching you in the kitchen — and every one of them makes you the router, the reminder service, and the only record that it happened.
Free plan, no card required. Submitters are always free.
What people teams get
- Cost
- Unlimited free submitters — every employee, every plan
- Cover
- OOO delegation routes around absent approvers
- Mobile
- PWA install, web push, decide from the email
- Intake
- In-app, AI-drafted, public link, or inbound email
- Record
- Actor and timestamp on every decision
Being helpful has quietly become a full-time queue
Nobody built a process for employee requests because each one takes ninety seconds. It's the aggregate — and the interruption cost — that does the damage.
Requests arriving at you personally
- Leave agreed in a DM with a thumbs-up, recorded in nobody's system.
- You forward the request to a manager, then chase the manager, then report back.
- The same five questions asked every week by different people.
- A dispute months later about what was actually agreed, with no record either way.
Requests arriving at a process
- A structured form captures what you'd otherwise have to ask for.
- It routes to the manager directly, and reminds them without you.
- The submitter watches live status instead of asking you for an update.
- Every decision has a name and a timestamp behind it.
Four interruptions that stop reaching you
Covering for absent approvers
OOO delegation routes assignments to a delegate automatically, audited — the highest-value feature for leave approvals for obvious reasons.
Chasing managers
Step SLAs remind and workspace escalation raises what reminders don't move. You stop being the escalation path.
Being the memory
The audit log and AI decision narrative mean “was this approved?” is a search, not a recollection.
Fielding status questions
Submitters see live status on My Requests, and can be given a shareable read-only tracker link.
Start with leave, then keep going
Time off & leave
Date ranges, cover arrangements, and a manager approval that survives them being away.
Learn moreEquipment requests
Laptops, monitors, and desk kit routed by cost with finance joining above the threshold.
Learn moreOnboarding & access
New-starter access requests with the system owner's sign-off captured properly.
Learn moreExpense claims
High volume, low drama — auto-approve the routine, question rather than reject.
Learn moreCharge per submitter and the tool everyone needs becomes the tool only some people get. Requester charges for approvers, so the whole company can ask.
The bar is “easier than sending a message”
Any employee-facing process that's harder than a DM loses to the DM. These are the three things that decide it.
Describe it, don't fill it
Someone can type what they need in plain English and the AI builds the request, asking the follow-ups a human would.
Learn moreIt works on a phone
PWA install and web push, so requesting and approving both happen from a home screen.
Learn moreFour ways in
In-app, AI-drafted, public link, or inbound email — including for the people who will never change how they ask.
Learn moreWhat people teams ask
- Do we pay for every employee?
- No — and for people teams this is the whole argument. Submitters are unlimited and free on every plan. Seats are consumed only by owners, admins, and members flagged as reviewers, so a 300-person company might have twenty billable seats.
- Does this replace our HRIS?
- No. Your HRIS owns employee records and leave balances. Requester owns the request and the decision — what was asked, who approved it, when, and on what basis. Push approved outcomes across with a lifecycle webhook.
- What about sensitive requests?
- Route them to a small reviewer group rather than a team, and keep the template scoped to the people who should see it. Every access to the request is governed by row-level security and recorded in the audit log with an actor and a timestamp.
- How do we handle managers who never respond?
- Step SLAs remind them on the step's own clock, workspace escalation raises it to admins when reminders don't work, and out-of-office delegation routes around them entirely when they're away. You stop being the chaser.
- Will people actually use it instead of messaging us?
- Give them more than one way in and most will. Requests can arrive in-app, drafted by AI from a plain description, from a public link, or from inbound email — so the person who will only ever email you still ends up in the same queue.
Your whole company can submit. You pay for the few who approve.
Put one leave form in front of your team this week and watch how much of your inbox was really just routing. Free to start, no card required.