Rippling launched Helpdesk on September 1, 2026: an agentic IT support agent designed to resolve routine employee requests on arrival instead of waiting for an admin to replay the same known steps across chat, ticket, HRIS, and the system of record.
The workload it targets is familiar to every desk: app access, password resets, device lockouts, and device replacements. Those requests usually follow a fixed path—identify the requester, apply policy, take the action, record what happened—but the admin still has to stitch the context together by hand.
Helpdesk's differentiator is that it sits on Rippling's existing employee, policy, app, and device context. In the company's example, a “laptop is slow” request can use MDM signals such as device age and memory patterns, guide a restart, or start a replacement through inventory when policy criteria are met—automatically or after approval, depending on role and tenure rules.
Control stays with IT. Admins decide what runs automatically, what needs approval, and what escalates. Every request, resolution, and escalation stays in a full activity log. That is the non-negotiable for any agentic desk move: automation without an audit trail is just a faster way to lose the chain of custody.
For operators evaluating vendors, the useful checklist is not the demo script. It is whether the agent can act inside your identity and device graph, whether approval boundaries are first-class, and whether every write is logged well enough to survive an audit or an incident review. Rippling's pitch is that those three come packaged with the HR/IT stack rather than bolted on afterward.