Ir al contenido

Notification Channels

Esta página aún no está disponible en tu idioma.

Push notifications alone miss people — devices go silent, apps get uninstalled, on-call engineers sleep through banners. Notification channels let reminder and escalation steps in a campaign’s workflow reach users through third-party messengers they already check.

Every channel follows the same privacy rule:

Content stays in Pidgr. A channel message carries the recipient’s first name and a deeplink back to the campaign — never the campaign body, attachments, or any other message content.

A typical channel notification reads:

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

This keeps third-party providers out of your sensitive communication path: Telegram, Slack, or your SMS carrier only ever see that something is pending, not what.

Channels are attached to reminder and escalation workflow steps — not to initial delivery. The first delivery always goes through the Pidgr apps (mobile, desktop, web). If the user hasn’t acted by the time a reminder or escalation step executes, the configured channels carry the nudge.

ChannelAvailabilityOpt-in modelPersonal opt-out
EmailLiveDirectory email (automatic)No — mandatory once enabled by the org
TelegramRolling outUser follows the Pidgr botYes
SlackRolling outWorkspace OAuth install + email matchNo — mandatory once enabled by the org
SMSRolling outVerified phone numberYes — STOP keyword honored
Generic WebhookRolling outOrg-configured endpoint (no per-user step)N/A (org-level)

Availability badges:

  • Live — generally available in production.
  • Rolling out — actively shipping; behavior documented here is the launch contract and may change before general availability.

Channels never message external recipients. A channel notification is only ever sent to a user who already exists in your Pidgr organization, and only for a delivery that already exists in their Pidgr inbox.

  1. Open the admin dashboard → Integrations.
  2. Enable the channels your organization wants to use and complete each channel’s setup (see the per-channel pages).
  3. In the workflow editor, add the channel to a reminder or escalation step’s notification options.
  4. Users complete any per-channel opt-in (Telegram bot follow, phone verification) from their profile.