Your policies answer most questions. Your team answers all 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.

Some ways to close the gap

04/04

  1. 01

    Employee policy answers

    Today

    The same benefits, time-off and pay questions arrive by phone and email, and each one waits for a person in HR.

    With your AI layer

    Answers in plain language from your own approved policies, and cites the section the answer came from.

    Human decisionEvery sensitive case, and every question the policy leaves to judgment.

    Employee app · 5:12 p.m.Botable AI layer

    Policy answer

    After hours

    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

    Ask a follow-up

    Available on every shift.

  2. 02

    Shared-inbox drafting

    Today

    Someone opens each message, works out what it is asking, and answers it from policy.

    With your AI layer

    Sorts each message the way your team already divides the work, and drafts the reply with every line traced to a policy.

    Human decisionWhat the reply says, and whether it is sent at all.

    Shared mailbox · HRBotable AI layer

    Draft ready

    Not yet sent

    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

    Review draftReassign

    HR edits and sends. The draft stops here.

  3. 03

    Compensation benchmarking

    Today

    Benchmarking means collecting job descriptions from comparable cities and matching them to your own roles, title by title.

    With your AI layer

    Gathers the descriptions from the cities you agreed on, matches comparable work to your roles, and prepares a suggested grade with the evidence beside it.

    Human decisionThe grade, the range, and whether the match is right.

    Comp study · Civil Engineer IIBotable AI layer

    Role match

    Awaiting HR

    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

    Approve G15Adjust

    HR makes every pay-grade decision. This one is not made.

  4. 04

    Your specific workflow

    Today

    A person carries the checks and handoffs between systems, by hand.

    With your AI layer

    We build around your rules, not ours.

    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 set the boundary. We build inside it.

You answer four questions before we build anything. The answers are decisions on record, not settings somebody flips later.

01

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.

02

What it may touch

Access and action

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.

03

When the rule fits

Human approval

You decide what answers on its own and what a person sees first.

04

When it does not

Exception path

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.

It runs on the systems you already own.

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.

01

HRIS

6 systems

The employee record: role, status, and the facts a case turns on.

  • ADP
  • SAP SuccessFactors
  • UKG
  • Workday
  • BambooHR
  • Dayforce
02

Policy management

6 systems

The policy as it reads today: the source behind every answer and every draft.

  • OneDrive
  • PolicyStat
  • PolicyTech
  • SharePoint
  • Google Drive
  • symplr
03

Email

3 systems

The mailbox your team already runs: questions in, HR's replies out.

  • Exchange Online
  • Microsoft Outlook
  • Gmail
04

Service desk

6 systems

Every open case: who holds it, and where it stands.

  • ServiceNow
  • Jira Service Management
  • Workday Help
  • Zendesk
  • Freshservice
  • HaloITSM

Bring us the question that returns every week with a different name on it.

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