Flo is the AI HR manager inside hiFlo. It listens to the shape of your team, reads the policy, files the form. It does the work — quietly, in the background — and shows you what it did.
We built Flo the way we'd build a senior HR partner — observant, precise, and unafraid to act. Then we put it inside the system.
An agent with structured access to tools — leave, calendars, policy, payroll exports.
A first reader. Drafts every review, summary, and outreach so you start at 80%.
A continuous auditor. Flagging the skill gap, the team dipping in sentiment, the contract about to expire.
Citing. Always with the source — handbook, BCEA, calendar event, signed offer letter.
A chatbot. There is no avatar, no face, no personality theatre.
A black box. Every tool call is logged with the asking user's identity, the inputs, the outputs.
A judge. Flo prepares; it doesn't decide promotions, terminations, or compensation. You do.
Trained on your data. Customer data never leaves the boundary. Zero retention with the LLM provider.
Every interaction follows the same shape — and you can see exactly what happened.
Flo reads every signal it has access to — calendars, OKR check-ins, surveys, leave balances, contract expirations, sentiment shifts. Streaming, real-time, structured.
context · streams · 12 signal typesA frontier LLM, prompted with the asking user's scope, the org's policy, and the relevant context window. No hallucinated facts — only what's in the system.
llm · scoped · retrieval-groundedFlo chooses from thirty-plus narrowly-scoped tools — submit leave, schedule check-in, generate EMP201, draft review. Tools run as the user, not as Flo.
tool use · per-tenant rlsEvery action is logged. Every answer carries its source. You can replay Flo's reasoning, see which records it read, audit which tools it called and why.
audit · replay · cite-with-linkFlo doesn't have one big magic button. It has a curated toolkit — each tool narrowly scoped, logged, and gated to the asking user.
Flo can read, plan, and submit leave on behalf of any employee in their scope.
From offer-signed to day-30, Flo runs the choreography.
Tools that listen to your team and surface what matters.
Flo finds the person, walks the org chart, and reads the skill matrix — every answer scoped to what the asking user can see.
An AI inside an HR system needs hard boundaries — not soft ones in a prompt. Flo's are enforced in the architecture.
Every tool call inherits the asking employee's permissions. Flo can't see records you can't see. The audit log records you, not Flo.
Submitting leave, sending an email, generating a SARS form — Flo proposes, you confirm. Org admins can elevate specific tools to auto-confirm within policy.
Performance ratings, salary changes, hiring decisions, terminations. Flo can draft, summarize, and prepare. The decision is yours.
We use frontier LLMs with zero-retention API access. Customer prompts and responses are not used for training, by us or our providers. Signed in our DPA.
When Flo summarizes survey themes, it can't reach back to who said what. The boundary is enforced in the database, not the prompt.
Don't want Flo touching payroll? Turn off the tool group. Don't want auto-approvals? Turn off auto. Granular, per-customer, in plain settings.
Real activity, real tool calls. Compressed from an actual customer log (with names changed).
Flo's visual signature is a single breathing aperture — a quiet point of light, a slowly-pulsing ring. You'll see it in the corner of the app, in chat, in this site's hero. It breathes whether Flo is doing anything or not. It's not a mascot. It's not a face. It's the way an attentive presence shows itself in the room.
7-day free trial. Free under 10 employees, forever. BambooHR migration in an afternoon.