ZANUS AI FOR HUMAN RESOURCES — AUTOMATIONS
Describe the job in plain words — “when an offer is signed, assemble the onboarding packet, request the accounts and schedule the check-ins” — and it becomes connected blocks on a canvas, running on its own, with every run visible.
Private tenant or your own server · unlimited users · EEOC-conscious workflows
A real flow: signature trigger, record sources, AI assembly step, three outputs — drawn from a description.
A signed offer triggers the packet, the account requests, the day-one schedule and the 30/60/90 check-in drafts — each queued for approval, none forgotten.
A policy update goes out; the system tracks who has signed and drafts the reminders — escalating to managers only when your rules say so.
A departure date triggers the checklist: access reviews, equipment returns, exit-survey invitation, final-pay confirmation draft — tracked to completion.
Run states live on the flow: green success, red failure on the exact block. A benefits deadline missed silently is an employee problem and a liability — here, nothing fails silently.
Your rules: queue everything for human approval, or auto-send only the categories you designate as safe — reminders, say, but never disciplinary correspondence.
← Previous: Team Training · Sharing with a colleague? 📄 Get the PDF · ✉️ Email this page ·