Platform · Orchestration
Every talent moment, connected and automated.
Hires, promotions, reviews and manager changes, turned into the right coaching, mentoring and follow-up. Same steps, same approvals, same audit trail, every time.
- Promoted to people managertrigger · Workday event
- First-time manager?condition · yes
- Offer a first-1:1 rehearsalcoach agent
- Propose a mentormatching agent
- Notify their managerMicrosoft Teams
- Day-21 check-inschedule
Connect
Once
Shared by every product
Event
Driven
Starts on every talent moment
Plain
Language
Describe a playbook
Audited
End to end
Every run, logged
Agents and orchestration
Orchestration sets the rules. Agents do the work. People make the calls.
One system, three layers. Here’s how they work together when an employee is promoted.
RulesYou are here
Orchestration
Set what happens after a promotion, hire or role change, who must approve and what gets logged. Same trigger, same steps, every time.
Priya is promoted. Start the new-manager playbook, require HRBP sign-off on her mentor match, check in at day 21.
Designed by HR · governed by IT
Execution
Agents
Carry out each step for each person: matching, nudges, prep, check-ins and follow-ups, adapted to their role and goals.
Her first 1:1s are Thursday, so the AI coach offers to rehearse the hardest one. The agent matches her with Alicia, who managed that team before, and preps them both for their first meeting.
Scoped access · every action loggedAgents →
Calls
People
Approve, mentor and manage. Agents bring the context; decisions about people stay with people.
Her HRBP approves Alicia as mentor. Alicia and Priya meet. Her manager joins the day-21 check-in.
Agents assist · people decide
For CHROs
Run development on events, not calendars.
Hires, promotions and manager changes already live in your HRIS. Each talent moment triggers the right playbooks as it happens.
Every moment, caught
No one waits for the next intake, or for a manager to remember.
Consistent and fair
People in the same moment get the same playbook, whatever their team or manager.
Owned by HR
Program teams build and change playbooks. IT connects systems once.
Playbook builder
Plain language in. Explicit workflow out.
HR describes the playbook in a sentence. Rumi drafts every trigger, condition, approval and step for review, so policy never hides inside a prompt.
From a sentence to a workflow
Say what should happen and when. Rumi drafts the steps and marks which are rules and which are agent steps.
Explicit and reviewable
Every rule, approval and agent step is visible before it goes live.
Versioned
Draft, test on sample employees, publish and roll back.
- Returns from leavetrigger · HRIS
- Opted in to supportcondition · profile
- Offer a returner coachcoach agent
- Propose a peer mentormatching agent
In action
One promotion, start to finish.
Rules start it. Agents run it. People decide it.
Rules
Agents
People
Day 0
- Rule: Priya promoted (Workday). First-time manager: yes. Playbook starts.
- Agent: Coach offers to rehearse her hardest first 1:1
Day 1
- Rule: Mentor match requires HRBP approval
- Agent: Matching proposes Alicia, with reasons
- Person: HRBP approves Alicia
Day 3
- Agent: Prep drafts the agenda from Priya’s goals
- Person: Priya and Alicia meet
- Person: Daniel, her manager, gets a heads-up
Day 21
- Rule: Scheduled check-in
- Agent: Nudge waits until quarter-end is over
For CTOs
Policy you can read. Every run on the record.
Approvals, guardrails and data scope are configuration, not code. Each run records the trigger, the rules applied, what agents did, who approved and which records changed.
Human in the loop where it matters
Require sign-off on matches, sensitive messages or any step you choose.
Step-level audit trail
One record per run, from trigger to records touched.
Retries and alerts
Failed steps retry on their own. Anything stuck is flagged before employees notice.
| Run | Trigger | Rules | Agent steps | Approved by | Status |
|---|---|---|---|---|---|
| #4812 | Promoted · Workday | 4 | 2 | HRBP · J. Park | Done |
| #4811 | Hired · Workday | 3 | 1 | Auto | Done |
| #4810 | Manager change · SAP SF | 2 | 1 | Pending | Awaiting approval |
Architecture
Fits your stack and your control plane.
Connect your systems once. Every Rumi product and playbook shares them, through open standards and enterprise identity.
Event-driven
Acts on HRIS changes as they land, not on nightly batch files.
Standards-based
MCP today, agent-to-agent handoff on the roadmap.
Visible to your control plane
Rumi agents appear in the agent registries you already use, such as Microsoft Entra Agent ID, Workday or ServiceNow.
Only the data you choose
Sync the fields you pick. Leave out compensation and other sensitive fields.
Questions buyers ask.
- How is orchestration different from agents?
- Orchestration sets the rules: what happens when a talent moment hits, who approves, what’s logged. Agents do the work inside those rules, for each person.
- Is the workflow deterministic?
- Yes. Triggers, conditions, approvals and step order are explicit and the same on every run. Agents act only in steps marked as agent steps.
- Do we need IT to build playbooks?
- No, HR and program teams build and edit playbooks themselves. IT connects systems.
- What if a step is sensitive?
- You can add an approval step, so a manager or HRBP signs off before Rumi continues.
- What data do you sync?
- Only the fields you choose. Leave out compensation and other sensitive fields.
- Does it work with the agent platforms we already run?
- Rumi connects through MCP, with agent-to-agent handoff on the roadmap.
