Brief the team on a customer-facing change
Sample briefing: Northstar Services is fictional. This example describes a made-up interface change and is not a statement about a real product.
Keep confirmed change details separate from open questions. If a customer asks about an unconfirmed behavior, capture the question and ask the Product Support Lead to verify it before giving a definitive answer.
Sample product briefing
Example change: report export now asks for a file format Low priority
In this fictional update, the export panel asks the user to choose CSV or PDF before starting an export. The change affects the export step only; this sample does not specify release timing, account availability, or changes to saved reports.
Customer task and support talking point Low priority
If a customer cannot find the export action, ask which report they are using and what the panel shows. Explain that this example's updated flow requires a format choice before export; verify actual product behavior before using this wording with customers.
Open question to verify before answering Low priority
This sample does not establish whether an account can set a default format or whether prior report preferences carry over. Do not infer either behavior; route the question to Product Support for confirmation.
Questions a customer may ask
Why is the export panel asking me to choose a format?
In the fictional example, the user selects CSV or PDF before starting the export. Confirm the actual interface and available formats before using this explanation for a real product.
Will my previous report preferences still apply?
The sample briefing does not confirm how previous preferences behave. Check with the Product Support Lead before answering.
When will this change appear for my account?
No release timing or account availability is provided in this sample. Share timing only after it is confirmed for the customer's account.