---
title: "Why you received a message from Pyn"
description: "A message from Pyn was written by your People team, sent from a person or address they chose, and timed by a date on your employee record such as your start date or anniversary."
sidebar:
  order: 2
area: for-employees
feature: messages
lastVerified: 2026-10-22
version: "2026-10-16"
audience: employee
related:
  - for-employees/reply-to-a-message
  - for-employees/privacy-and-your-data
  - for-employees
intercom:
  - id: "6767588"
    title: Using Pyn with Slack
    url: https://intercom.help/pyn/en/articles/6767588-using-pyn-with-slack
    note: draws on
---

A message from Pyn is a message from your company. Someone on the People team wrote it, chose who it should go to and when, and Pyn delivered it. The timing comes from your employee record, so a "welcome to your first week" email arrives in your first week and an anniversary note arrives on your anniversary.

## Who wrote it

Your company's People team, or whoever they have given access to Pyn, builds automations: a trigger (for example, a start date), an audience (for example, everyone in Engineering) and a sequence of messages. When your record meets the trigger, you are enrolled and each message is scheduled relative to that date. Every message was written by a person before you were ever enrolled; Pyn fills in details such as your first name, your manager's name or your start date when it sends.

## Who it comes from

The People team picks a sender for each message, so the name you see is deliberate:

- **An email from a colleague's address**, such as your manager or the head of People. Pyn sent it through their connected Google Workspace or Microsoft 365 mailbox, so a reply goes to them.
- **An email from a company address**, such as `people@yourcompany.com`. It is a verified sending address that the People team set up.
- **A Slack direct message from a colleague.** They connected their Slack account to Pyn so messages can come from them.
- **A Slack direct message or channel post from the Pyn app**, or a Microsoft Teams message from the Pyn app. The company's Pyn installation sent it.

## Why now

Most messages are tied to a date on your record: start date, anniversary, birthday, a return from leave, the day you became a manager. Others fire when something changes, such as being added to a team or being named as someone's buddy, and some run on a timetable such as a monthly pulse. The People team can also enrol people by hand, for example to send a campaign to a group on a chosen day.

Pyn sends at the time of day the People team chose, in your time zone where your record has one, otherwise in the company's time zone.

## Why you got it twice

A message can carry a button or a form the People team wants you to act on. If you have not acted after a set number of days, Pyn sends the same message again as a reminder, up to three times. Acting on any copy stops the rest. If you still do not act, Pyn can notify your manager; see [What nudges and escalations look like](https://support.pynhq.com/for-employees/for-managers/what-nudges-and-escalations-look-like/).

## Related

- [Reply to a message](https://support.pynhq.com/for-employees/reply-to-a-message/) for where a reply lands, by channel.
- [Privacy and your data](https://support.pynhq.com/for-employees/privacy-and-your-data/) for what Pyn holds and records.
- [For employees and managers](https://support.pynhq.com/for-employees/) for everything you might receive.

## Related Intercom articles

- [Using Pyn with Slack](https://intercom.help/pyn/en/articles/6767588-using-pyn-with-slack) — draws on