Who this is for: Product teams briefing an accurate and useful update explanation.
What to prepare
- The approved preference labels and initial state.
- The specific alert types and channels affected.
- Verified saving and confirmation behavior.
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Plan a 30-second update explanation for a fictional collaboration tool adding control over comment-summary notifications. Open with a labeled illustrative summary notification, then connect it to the exact preference that controls it. Show the current state before selecting the supplied alternative. Include the real save or confirmation step and hold on the stored preference. State which comment summaries are affected, using approved wording. Keep unrelated direct mentions or urgent notices out of the claim unless the release explicitly includes them. Do not invent a delivery schedule, channel or unsubscribe guarantee. Use a neutral tone that respects either choice. End with the selected preference and a short note about where to return to change it again, if that route is verified.
Make it your own
- Alert scope
- Identify the exact notification type and channel.
- Available options
- Supply labels and their documented effects.
- Saved state
- Show the actual confirmation, not an assumed persistence effect.
Name the controlled alert
Use a sample notification that belongs to the preference being shown. A direct mention is a misleading opening if the setting only controls summaries. Keep personal content illustrative and avoid exposing real message text.
Adapt for a workspace-level setting
If administrators control the preference, show that role and state who is affected. Do not imply ordinary members can override the choice unless documented. A personal-setting asset and a team-setting asset need different closing instructions.
Repair broad silence promises
Replace “Stop all interruptions” with the actual alert scope. If the choice affects future summaries but not already queued messages, use the owner's approved explanation. The final state should make the selected option clear without suggesting an unsupported immediate effect.
Review checklist
- The example alert belongs to the controlled scope.
- Initial and saved states are both visible.
- Role and channel boundaries are accurate.
- No all-notifications promise is inferred.