Email Channel

Live Email is generally available.

The email channel sends reminder and escalation notifications to a user’s work email address. Like every channel, it is notification-only: the email contains the recipient’s first name and a deeplink back to the campaign in Pidgr — never the campaign content itself.

What gets sent

Subject: Pending action in Pidgr

Hi Ana — you have a pending action in Pidgr: "Q3 Security Policy".
Open it here: https://links.pidgr.com/c/abc123

Emails are delivered through Amazon SES (see the sub-processors list). DKIM and SPF are configured on the Pidgr sending domain, so messages authenticate cleanly with your mail provider.

Opt-in model

Email needs no per-user opt-in step. The address comes from the user’s directory identity:

• If your organization provisions users via SCIM, the SCIM-synced email takes precedence.
• Otherwise, the email the user was invited with is used.

Once an organization admin enables the email channel, it applies to all users in the org — there is no personal opt-out. Email is treated as a workforce compliance channel, the same as your company’s existing internal email.

Admin setup

1. Open the admin dashboard → Integrations → Email.
2. Enable the channel for your organization.
3. In the workflow editor, add Email to the notification options of any reminder or escalation step.

No DNS or mail-server configuration is required on your side — Pidgr sends from its own authenticated domain.

Behavior notes

• One nudge per step — a reminder step sends at most one email per user per execution; it does not retry into a user’s inbox repeatedly.
• Open signals are conservative — corporate mail gateways prefetch links and tracking pixels. Pidgr filters known prefetch patterns, so “opened” signals in campaign analytics aren’t inflated by security scanners.
• Bounces — hard bounces mark the address unreachable for future channel sends and are surfaced to admins.