---
title: Create a conditional sender
description: Build a sender that routes by audience, for example the UK People team for UK employees and the US team for everyone else.
sidebar:
  order: 2
area: settings
feature: conditional-senders
appPath: /settings/general/conditional-senders
lastVerified: 2026-10-22
version: "2026-10-16"
audience: admin
related:
  - settings/conditional-senders
  - settings/senders
  - flows/automations
intercom:
  - id: "9312783"
    title: Configure Conditional Senders
    url: https://intercom.help/pyn/en/articles/9312783-configure-conditional-senders
    note: "Pyn 1 article, kept for reference"
---

Your onboarding flow sends one welcome email, but you want it to come from the People partner for the recipient's region. A conditional sender does that with ordered rules and a fallback, and you pick it on the step like any other sender.

## Before you start

- You are an admin or owner.
- The real senders exist and are **Active** under [Senders](https://support.pynhq.com/settings/senders/), all for the same medium.
- The [employee groups](https://support.pynhq.com/directory/employee-groups/) you want to route by exist.

![Create Conditional Sender: a name, a medium, a fallback and ordered rules.](https://support.pynhq.com/media/settings/conditional-senders/settings-conditional-senders-create.png)

## Steps

1. In Pyn, open **Settings** in the left navigation, then **Conditional Senders** under **General**.

2. Select **Add**. The **Create Conditional Sender** dialog opens.

3. Enter a **Name** and choose the **Medium**: **Email**, **Slack** or **Teams**. The medium cannot be changed once the conditional sender exists.

4. Choose the **Fallback sender**. It is used when no rule matches and is required.

5. Open **Rule 1**. Set its audience (lifecycle stages, included and excluded groups) and choose **Send from**. The **Audience Preview** underneath shows who the rule covers.

6. Select **Add rule** for each further case. Use **Move rule up**, **Move rule down** and **Remove rule** to order them; the first matching rule wins.

7. Select **Save**. The button stays disabled until the name, fallback and every rule's sender and lifecycle are set.

> **Tip:** Put the most specific rule first. A broad rule such as "Current employees" at the top matches everyone and the rules below it never run.

## What you should see

The new row lists the name, medium and rule count. Open a step in [Automations](https://support.pynhq.com/flows/automations/), choose the same medium and the conditional sender appears in the **From** list. Enrol a test employee and check [Activity](https://support.pynhq.com/activity/) to confirm the delivery shows the sender the rule chose. If saving fails the dialog shows "Could not save conditional sender" or the server's reason; check that every rule's sender is still active.

## Related

- [Conditional Senders](https://support.pynhq.com/settings/conditional-senders/) for how matching works.
- [Senders](https://support.pynhq.com/settings/senders/) to add the senders rules point to.
- [Automations](https://support.pynhq.com/flows/automations/) to use the conditional sender on a step.

## Related Intercom articles

- [Configure Conditional Senders](https://intercom.help/pyn/en/articles/9312783-configure-conditional-senders) — Pyn 1 article, kept for reference
