Your systems
Official source
The employee record stays in your HRIS, and the policies stay in your policy library. The AI layer reads them where they are, and nothing moves out of them.
Delivering the answer is still someone's job. Botable builds and runs the AI layer that closes this gap. Sensitive cases stay with HR.
Today
With your AI layer
Human decisionEvery sensitive case, and every question the policy leaves to judgment.
Employee asked
I start approved leave in March. Do I lose the PTO I have already accrued?
Answer sent
No. Accrued PTO is retained through an approved leave and is available when you return.
Answered from
Benefits §7.1
current revision
The answer traces here
Also logged
topic and time, for HR
Available on every shift.
Today
With your AI layer
Human decisionWhat the reply says, and whether it is sent at all.
Incoming · K. Dunn, Clinic 42
Returning from leave in March. Does my unused PTO carry over, or reset on my return?
Draft prepared
Hi Kara, accrued PTO carries over for 90 days after you return. Your balance of 47 hours stays available until 12 June.
Drafted from
HR-207 §3
with HR-212 on carryover
Every line traces to a policy
Sorted as
Benefits · 1 of 14
HR edits and sends. The draft stops here.
Today
With your AI layer
Human decisionThe grade, the range, and whether the match is right.
City 2 · job description
Directs two junior engineers, reviews designs.
they call it Civil Engineer III, Grade 15
City 3 · job description
Supervises engineering staff on public works.
they call it Engineer II, Grade 15
Matched title
Civil Engineer II
our equivalent role
From the highlighted duties
Suggested grade
15 · up from 14
HR makes every pay-grade decision. This one is not made.
Today
With your AI layer
Human decisionEvery approval and every exception, held by people you name.
Your record. Your rule. Your approver.
The same frame, built around your process.You answer four questions before we build anything. The answers are decisions on record, not settings somebody flips later.
Your systems
The employee record stays in your HRIS, and the policies stay in your policy library. The AI layer reads them where they are, and nothing moves out of them.
What it may touch
You name the employee data it may read, field by field, and what it may write or draft. Anything you leave off the list stays out of reach, before the build and after it.
When the rule fits
You decide what answers on its own and what a person sees first.
When it does not
A sensitive case, or one the policy does not cover, stops on the spot and goes to a person you name. Nothing is decided quietly.
Examples, not a partner list. What we connect to, and what it is allowed to write back, is agreed for your build, and it stays your call.
Your systems keep their jobs. The AI layer carries the work between them.
The employee record: role, status, and the facts a case turns on.
The policy as it reads today: the source behind every answer and every draft.
The mailbox your team already runs: questions in, HR's replies out.
Every open case: who holds it, and where it stands.
We map the work, build the step no system owns, and stay to run it as policies are revised, benefits change, and new people arrive with the same questions.
Start with one gap