How to use the Product Recall Notice Draft Generator.
Recall notices must use approved identifiers and instructions. Keep the affected product range and customer action clear and have the responsible team review the draft.
Make the workflow fit your task.
Use only approved product identifiers, affected batches and customer instructions. Put the action first, keep the contact route clear and mark missing operational details for the responsible team's review before publication.
- What you provide
- Approved recall facts and instructions.
- What you get
- Clear customer notice for responsible review.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Approved recall brief: product Example Tray, affected batch B17 only. Customers must stop use and contact recall@example.com with the batch identifier. Cause and remedy have not been approved for publication.
Completed example
Example Tray: notice for batch B17 If your Example Tray is marked batch B17, stop using it and contact recall@example.com with the batch identifier. This notice applies to the approved batch B17 only. No cause, replacement or refund commitment is included in the supplied notice. The responsible team must review the final message before publication.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Can the draft infer that nearby batches are also affected?
No. Use the approved affected range and request clarification when identifiers are incomplete. Do not expand or narrow it by guesswork.
Why does the notice create an unsupported remedy promise?
Remove refund, replacement or timing language not present in the approved instructions. The responsible team must confirm those commitments.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑