OVI is the AI-native ATS where you chat to hire. Two AI agents — Sora for sourcing and Milo for screening — find candidates, score every CV, and run AI interviews, all controlled from a single chat.

What does "chat to hire" mean?

Chat to hire is OVI's AI-native hiring workflow: instead of clicking through a traditional ATS, you describe what you need in chat and OVI's AI agents source candidates, screen applicants, run AI interviews, and send outreach for you.

What is an AI-native ATS?

An AI-native ATS is an applicant tracking system built around AI agents rather than forms and pipelines. OVI's AI chat ATS lets recruiters source, screen, interview, and follow up through conversation — the agents do the work and surface only the candidates worth meeting.

Who are Sora and Milo?

Sora is OVI's AI sourcing agent — she scans LinkedIn, the open web, and your ATS history to find best-fit candidates and reach out in your name. Milo is OVI's AI screening agent — he scores every applicant against your rubric and surfaces a ranked shortlist.

How do OVI's AI interviews work?

OVI runs async AI interviews for every shortlisted candidate and returns scores, transcripts, and recordings — so your team only meets the people worth meeting.

From Spreadsheet Jockeys to Strategic Advisors: How AI Is Rewriting the HRBP Playbook

2026-06-19

From Spreadsheet Jockeys to Strategic Advisors: How AI Is Rewriting the HRBP Playbook

The Gap Between Promise and Reality

The HR Business Partner was designed to be the connective tissue between people strategy and business outcomes — a trusted advisor who could sit with a CFO and talk talent as fluently as finance. The reality has been stubbornly different. According to AIHR, 82% of HRBPs do not perform strategic activities well, and 55% of the HRBP work week is consumed by talent management program delivery. That is not a skills gap — it is a workload trap. The strategic seat at the table remains largely unfilled because the day-to-day work never stops demanding attention.

That bottleneck now has a structural fix, and it landed in enterprise software this month.

Two Platforms Shifting the Workload

On March 24, 2026, Oracle launched Fusion Agentic Applications — a suite of AI agents embedded directly in Oracle Fusion Cloud HCM. For HR, the lead product is the Workforce Operations agent: it reduces manual data gathering, automates scheduling approvals, and flags payroll issues proactively — catching discrepancies before they become escalations. The difference from previous analytics tools is agency. The system acts on the data, not just surfaces it.

Oracle executive vice president Steve Miranda put it plainly: "With Fusion Agentic Applications, we are moving enterprise software beyond passive systems of record." That shift — from passive to active — is precisely what HRBPs have needed. Rather than spending hours pulling reports across fragmented systems, they receive synthesized, action-ready intelligence.

ServiceNow is addressing a related but distinct problem. Its Autonomous HR and HRBP Hub — targeting 2026 availability — moves the HRBP role into genuinely predictive territory. The platform monitors real-time attrition signals across the workforce and can autonomously draft manager action plans before a retention risk becomes a resignation. This is not reactive case management. It is anticipatory strategy support, delivered at scale.

Together, these launches represent a shift not just in HR technology but in what the HRBP role can realistically accomplish.

What Moves Off the HRBP's Desk

Gartner's January 2026 CHRO Future of Work Trends identified AI handling of Tier 0 and Tier 1 HR tasks as one of 2026's defining structural shifts. The tiers are specific: Tier 0 covers self-service queries, policy lookups, and benefits enrollment guidance — all moving to AI-powered portals and conversational interfaces. Tier 1 covers standard case handling, manager escalations, and routine onboarding coordination — precisely the work these new agentic platforms are now absorbing.

What moves back onto the HRBP's desk is the work the role was actually designed for: workforce planning aligned to business unit strategy, attrition prevention for high-flight-risk segments, and leadership coaching grounded in capability data rather than gut feel. These are not vague aspirations — they are specific deliverables that become feasible when the operational burden lifts.

Josh Bersin describes this moment in his Great HR Reinvention analysis as a fundamental redefinition — not an IT upgrade. When AI absorbs the operational layer, the expectation that HRBPs act as genuine strategic advisors stops being aspirational. It becomes an accountability.

The clearest indicator of whether the shift is happening is how HRBPs spend their Monday mornings. If they are still opening a spreadsheet to manually compile a turnover report that an AI agent could produce overnight, the operating model has not caught up with the technology. The tools are available. The redesign work belongs to leaders.

That is a new kind of pressure. The transactional backlog has long provided a legitimate reason why strategic work could not get done. That cover is evaporating.

What CHROs Need to Do Now

Oracle's Workforce Operations agent is live as of March 24, 2026. ServiceNow's HRBP Hub arrives later this year. The infrastructure for a strategically capable HRBP function now exists. The question is whether organizations will redesign the operating model to match it.

One practical starting point: audit the current HRBP task inventory against the Gartner Tier 0/1 framework. Tasks that qualify — routine queries, standard approvals, repetitive data pulls — should have a deprecation date on the HRBP's calendar. That audit surfaces both the immediate automation opportunities and the capability investments needed to replace that time with genuinely strategic work.

Organizations that treat these launches as talent operating model changes — rather than software upgrades — will see materially stronger HRBP performance within 12 months. Those that don't will have paid for capability they won't use.

The HRBP playbook is being rewritten. CHROs can author the next chapter now, or explain later why they waited.