Onboarding that greets each new hire by name — and walks them through day one.

The configuration that makes onboarding feel personal and run itself: the guided journey plans, the stages a new hire moves through, the activities each person completes, recommended learning and links, and the branded landing page where it all comes together.

The live journey belonging to a specific new hire stays with your team — Phyllis builds the templates and the experience, not a real person's onboarding record.

A generic request opens a case and fires off tasks. A journey is the guided, personalized experience on top of that — a plan with stages and check-off activities where the new hire, their manager and their mentor each see their own view. Phyllis builds that guided experience and can tie it to the moment someone joins, so it launches on its own.

Each journey is persona-aware — the new hire, the manager and the mentor each get their own activities and their own view of progress. Phyllis configures those per-persona pieces. Where a programme has no mentor named, she calls it out rather than leaving a silent gap.

Correct. Phyllis explores, proposes a plan, and only builds on your explicit approval, with every change staged for review. She also flags the manual finishing steps an admin completes — like placing the journey on your Employee Center homepage — so the experience actually surfaces for staff.

Every claim is cited to where it came from in your own instance — the journey types already defined, the plans still in draft, the stage names your team reuses. She reads your live setup rather than assuming out-of-box defaults, because onboarding content drifts heavily from the shipped baseline.