# Notification Delivery

> Deliver notifications via push, SMS, email, in-app, and webhooks — manage templates, schedule delivery, track status, and respect user preferences. Use when sending notifications, managing templates, checking delivery status, scheduling alerts, or configuring preferences.

- Skill: `zavora-ai/notification-delivery` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add zavora-ai/notification-delivery`
- Raw SKILL.md: https://api.skillmd.com/api/skills/zavora-ai/notification-delivery/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- License: Apache-2.0
- Author: zavora-ai (https://skillmd.com/u/zavora-ai)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/zavora-ai/notification-delivery

---


# Notification Delivery

Multi-channel notifications with preference respect. Always check user preferences before sending. Never overwhelm recipients.

## Decision Tree
```
├── "notify", "alert", "send push"? → send_notification / send_from_template
├── "broadcast", "announce to all"? → broadcast (requires approval for large audiences)
├── "schedule", "send later"? → schedule_notification
├── "status", "delivered?"? → get_status / get_delivery_stats
├── "template", "create template"? → list_templates / create_template
├── "preferences", "opt out"? → get_preferences / update_preferences
├── "retry", "resend"? → retry_notification
```

## MUST DO
- Check user preferences before sending (respect opt-outs)
- Rate limit — don't send more than 3 notifications/hour to same user
- Use templates for consistency
- Include unsubscribe mechanism on marketing notifications

## MUST NOT DO
- Don't bypass opt-outs
- Don't use "critical" priority for non-critical content
- Don't broadcast without explicit approval