Skip to content
PynPyn

By use case

Give managers a new-hire checklist

A manager is asked three times, at the right moment each time: order the equipment a week before the start date, run the first-week plan on day one, hold a check-in at 30 days. Each ask has a button to confirm, a reminder if they do not, an escalation if they still do not, and HR sees who has acted. For: admins and owners. Time: about 30 minutes.

The New-hire checklist for managers automation with its first step open on the right: the Configure tab shows the email to the manager a week before the start date with its checklist button.
The checklist step open: To is Manager, the message carries a tracked button, and the Reminders tab holds the reminders and, below them, the Escalations section.
  1. In the automation, add a Send Email to Employee step scheduled 7 days before, and under To choose Manager, so the step resolves to each new starter’s own manager; see Choose recipients and Cc.

  2. Write it to the manager with @recipient.preferredName, and name the new starter and their date with @principal.preferredName and @principal.startDate; see Tokens.

  3. Add a Link to Library Content button that opens the checklist, or a Link Button to your own page, and leave Track Action ticked so the click counts as done; see Add a button to a message and Link to content from a message.

  4. On the Reminders tab add a reminder 2 days after send and a second at 4 days; see Add reminders.

  5. Under Escalations, add one 7 days after send and change the recipient to Skip-level Manager, or a named person under People; see Add escalations.

  6. Repeat for the first-week plan on the day of and the 30-day check-in 30 days after, each with its own button; see Schedule a step.

  7. Open Preview, pick an upcoming joiner under Preview for principal and check the header shows their manager as the recipient, then Send a test to yourself; see Preview and send a test.

  8. Publish, and tick the running enrollments in Update Enrollments so starters already in the flow get the new steps; see Publish an automation.

Use Send Direct Message with To set to Manager, as in Add a direct message step. The button renders as a Slack button and the reminder is a copy of the same DM. An escalation goes out in the step’s own medium, so a Slack step can notify your People team’s channel, chosen under Channels.

For a step only some managers get, use the step’s Audience tab; it is checked against the recipient, so a department group there means the manager’s department, not the new starter’s; see Set a step audience.

  • A step without a tracked button or form is not actionable: the Reminders tab reads This step has no actionable content such as buttons or forms, and any reminder on it sends every time; see Add a button to a message.
  • An escalation that resolves to the original recipient is not created, so on a step to Manager pick Skip-level Manager or a named person; see Add escalations.
  • A reminder still pending when the manager acts is cancelled and shows as Invalid under Enrollments; the Actions view is the record to trust; see Add reminders.
  • Tokens follow roles: @principal.startDate is the new starter’s date even in a message to the manager, and @recipient.startDate is the manager’s own; see Tokens.
  • A new starter with no manager makes the step read No recipient, then Skipped once its time passes; a relationship group of Employees without a manager finds everyone affected; see Fix a missing manager, time zone or email.

Under Enrollments, each manager step lists the resolved manager by name, and a delivered step shows its reminders and escalation beneath it as Scheduled. Open Activity > Actions under Messages, filter Status to Unactioned and select Export Data for the CSV to chase from; see Track actions. A manager’s own Activity tab lists the same asks under Outstanding; see Read an employee profile.