Product and UX Content

Notification Content Matrix

Decide each notification's trigger, audience, channel, urgency, timing, repetition, required content, action, privacy exposure, and opt-out behavior.

Free editable Markdown · Product teams, content designers, and lifecycle teams · Updated July 30, 2026

Download Markdown

Accessible HTML preview

Blank template

The downloaded file contains the same fields in editable Markdown.

Notification purpose

Notification ID and event: [Enter]
Verified trigger source: [Enter]
Recipient role and account state: [Enter]
User need: [Why is interruption useful?]
Consequence if missed: [Enter]
Urgency and action window: [Enter]
Type: [Transactional / Security / Task / Reminder / Educational / Promotional]
Owner: [Product/content]

Content and action

Sender or product identity: [Enter]
Message: [What happened and why it matters]
Sensitive detail omitted: [List]
Action label and destination: [Enter]
Authentication and live-state check: [Enter]
Alternative or dismiss behavior: [Enter]
Consent or opt-out rule: [Enter]
Variable fallback: [Enter]

QA and monitoring

Delivery and action signals: [Enter]
Complaint/opt-out guardrail: [Enter]
Review trigger and owner: [Enter]

Stale, duplicate, delayed, and cross-device events were tested.
Lock-screen and shared-device privacy were reviewed.
Meaning does not rely only on sound, icon, color, or emoji.
Long localization and timezone behavior were tested.
Message stops after action or expiry.

How to use this template

Inventory events and define the user need, consequence, urgency, and current-state source.
Decide whether to notify, then select channels, timing, batching, expiry, and suppression.
Draft privacy-aware content and an authenticated action that reflects live state.
Review consent, accessibility, localization, security, frequency, and cross-device cases.
Test event delivery and stale states, then monitor value, complaints, and opt-outs.

Start with the event and user need

Define the verified trigger, affected user, consequence of missing the information, and the decision or action enabled. Distinguish transactional, security, task, collaboration, reminder, educational, and promotional messages. A system event is not automatically worth interrupting someone. If the information can wait until the user returns to the product, use an inbox or status area. Choose urgency from harm and time window, not campaign importance. Identify quiet hours, timezone, role, account, locale, and whether multiple users or devices may receive the same event.

Choose channel, timing, and repetition deliberately

Compare in-product, inbox, email, push, SMS, and other approved channels for durability, privacy, immediacy, cost, and user control. Use multiple channels only when each has a reason, and define deduplication. State delay, batching, expiration, retry, maximum frequency, and suppression after the user acts. A reminder should stop when the task is complete. Security and privacy teams should review sensitive alerts and lock-screen previews. Marketing consent and opt-out behavior must be distinguished from necessary service communications under applicable policy.

Write for recognition and safe action

Include what happened, relevant object or actor, time sensitivity, and next action without exposing more than the channel permits. Link to an authenticated destination that shows current state rather than embedding risky details. Provide accessible language and avoid emoji, color, or sound as the only urgency cue. Test stale notifications, revoked access, expired links, duplicate events, localization, and actions taken on another device. Monitor delivery, action quality, complaints, opt-outs, and support confusion—not only opens.

See the fields in context

Fictional example: expiring collaboration invitation

TeamBirch and its invitation system are invented and do not describe GPTHuman notifications.

Event: An imaginary invitation will expire in 24 hours and remains unaccepted.
Channel: One in-product inbox item and one email; push is omitted because the consequence is low.
Content: Name the fictional workspace but omit the inviter's private email from lock-screen contexts.
Suppression: Cancel the reminder if the invitation is accepted or revoked on another device.
Expiry: The destination explains the current state if opened after expiration.

Frequently asked questions

Should every product event trigger a notification?

No. Notify only when the information is useful outside the normal product context or required for a timely decision.

When should several channels be used?

When each channel serves a documented need, with deduplication, consent, privacy, and suppression rules.

How should urgency be expressed?

State the real deadline and consequence. Avoid artificial pressure or alarm styling unsupported by the event.

What metrics indicate notification quality?

Consider task completion, errors, complaints, opt-outs, support evidence, delivery, and stale-action rates alongside opens.