---
title: "Run a buddy programme"
description: "Let the manager pick a buddy from a Slack message a week before the start date, brief the buddy the moment the choice reaches the record, and check in with both sides through the first month."
sidebar:
  order: 1
area: use-cases
appPath: /flows/home
lastVerified: 2026-10-29
version: "2026-10-29"
audience: admin
related:
  - flows/automations/tutorial-buddy-programme
  - flows/forms/tutorial-buddy-selection-form
  - flows/automations/configure-a-team-change-trigger
  - flows/forms/build-a-form
  - use-cases/pre-boarding
---

Every new starter has a buddy who knows they are a buddy before day one, chosen by the manager in two clicks from a Slack message. Pyn briefs the buddy the moment the choice reaches the record and checks in with both sides for a month. **For:** admins and owners. **Time:** about an hour; about 40 minutes if you stop at the briefing.

![The finished Buddy briefing automation: the Buddy Assigned trigger and one step to the buddy on the day, with a button to the buddy guide.](https://support.pyn.ai/media/use-cases/buddy-programme/use-cases-buddy-programme-automation.png)

## What you'll need

- Slack connected, so the manager picks inside the message; see [Slack](https://support.pyn.ai/integrations/slack/). Without Slack the nomination goes by email and the manager picks by name on the respond page.
- A published pre-boarding or first-day automation for the nomination step, with **Manager** synced; see [HRIS fields](https://support.pyn.ai/integrations/hris-fields/).
- A short buddy guide published in **Library** > **Content**; see [Publish content](https://support.pyn.ai/library/content/publish-content/).
- Optional: a buddy field in your HRIS (HiBob has one as a custom field); the briefing automation then needs no form.

## Build it

1. Build a `Buddy selection` form with one **Buddy** field from **Employee Fields**, write the question in its **Description** because Slack shows the description rather than the label, tick **Required** and publish it; see [Build a form](https://support.pyn.ai/flows/forms/build-a-form/).

2. In your pre-boarding automation, add a **Send Direct Message** step with **To** set to **Manager**, scheduled **1 week before** the start date, and place the form in it with **Insert widget** > **Embed Form**; see [Embed a form in a message](https://support.pyn.ai/flows/forms/embed-a-form-in-a-message/).

3. Add a reminder **2 days after send** and an escalation to **Skip-level Manager** a few days later, both worded as a check-in rather than a chase; see [Add reminders](https://support.pyn.ai/flows/steps/add-reminders/) and [Add escalations](https://support.pyn.ai/flows/steps/add-escalations/).

4. Create a second automation, `Buddy briefing`, on the **Buddy Assigned** trigger under **Team and Org Changes**, and add **Joiner** to **Current** in its audience because the principal is the new starter; see [Configure a team change trigger](https://support.pyn.ai/flows/automations/configure-a-team-change-trigger/).

5. Add a **Send Direct Message** step with **To** set to **Buddy**, **on the day of**, with a **Link to Library Content** button to the buddy guide; see [Choose recipients and Cc](https://support.pyn.ai/flows/steps/choose-recipients-and-cc/) and [Link to content from a message](https://support.pyn.ai/library/content/use-content-in-a-step/).

6. In your **Start of Onboarding** automation, add check-ins to **Buddy** **on the day of** and **2 weeks after**, and a one-month poll to **Employee** asking how their buddy has been; see [Tutorial: buddy programme](https://support.pyn.ai/flows/automations/tutorial-buddy-programme/).

7. Publish both automations in **Automated** mode, then preview the nomination step for an upcoming joiner to confirm it resolves to their manager; see [Preview and send a test](https://support.pyn.ai/flows/steps/preview-and-send-a-test/).

## Variations

**Slack**

Every step is a direct message. The manager answers the picker inside the message, the submission appears in the form's **Activity** drawer and the buddy is written to the starter's record; see [Pick a buddy](https://support.pyn.ai/for-employees/for-managers/pick-a-buddy/) for what the manager sees.

**No Slack**

Send the nomination as a **Send Email to Employee** step to **Manager**. Its button opens the respond page, where the **Buddy** field is a name search that answers for 14 days after the message is sent; see [Form field types](https://support.pyn.ai/flows/forms/reference-form-field-types/). Opening the form from the email marks the step **Actioned**, so a reminder on it stops once the manager has opened it. Keep `Buddy briefing` on **Send Email to Employee** steps to **Buddy**. A buddy set in your HRIS or in the Employee File column works the same way: the **Buddy Assigned** trigger fires whether a form or a sync wrote the relationship.

To thank the manager once they have chosen, add a small automation on the **Form Submission** trigger, whose principal is the submitter; [A buddy selection form that triggers a flow](https://support.pyn.ai/flows/forms/tutorial-buddy-selection-form/) builds it alongside the briefing.

## Watch out for

- The manager submits the form but the starter is the principal. `@principal.preferredName` is the starter, `@principal.buddy.preferredName` is the buddy and `@recipient.preferredName` is whoever receives the message; see [Tokens](https://support.pyn.ai/flows/steps/reference-tokens/).
- A Slack submission never marks the step **Actioned**, so the reminder and the escalation send whether or not the manager has answered. The form's **Activity** drawer and its export are the record of who has chosen; see [Review and export submissions](https://support.pyn.ai/flows/forms/review-and-export-submissions/).
- Unpublished forms appear in the **Embed Form** list; publish the form before the step sends; see [Build a form](https://support.pyn.ai/flows/forms/build-a-form/).
- **Buddy Assigned** fires only for relationships written after the first HRIS load. A starter whose buddy was set before then never enrols in `Buddy briefing`; use [Manually enroll employees](https://support.pyn.ai/flows/automations/manually-enroll-employees/) for them.
- A step addressed to **Buddy** before the relationship exists reads **No recipient**, then **Skipped**, so keep the check-ins in the onboarding automation rather than the pre-boarding one; see [Choose recipients and Cc](https://support.pyn.ai/flows/steps/choose-recipients-and-cc/).
- If **Publish** appears to do nothing, a step has no recipient; check each step's **To** field. See [Publish an automation](https://support.pyn.ai/flows/automations/publish-an-automation/).

## Check it worked

A week before a start date, the manager's nomination shows as **Delivered** under [Enrollments](https://support.pyn.ai/activity/enrollments/) in the pre-boarding automation. When they submit, the starter's profile shows the buddy, the starter appears as a new enrollment in `Buddy briefing` with that day as **Reference Date**, and the buddy's message shows as delivered within the hour. A relationship group **Employees without a buddy** lists the starters still waiting; see [Create a relationship group](https://support.pyn.ai/directory/employee-groups/create-a-relationship-group/).

## Related

- [Tutorial: buddy programme](https://support.pyn.ai/flows/automations/tutorial-buddy-programme/) for the whole programme with the message copy.
- [A buddy selection form that triggers a flow](https://support.pyn.ai/flows/forms/tutorial-buddy-selection-form/) for the form, the thank-you flow and the briefing.
- [Pick a buddy](https://support.pyn.ai/for-employees/for-managers/pick-a-buddy/) for what the manager sees.
- [Configure a team change trigger](https://support.pyn.ai/flows/automations/configure-a-team-change-trigger/) for Buddy Assigned.
- [Reach new starters before day one](https://support.pyn.ai/use-cases/pre-boarding/) for the automation the nomination step goes in.
