How to use the Restaurant Specials Announcement Generator.
A specials announcement should include the confirmed dish, availability and ordering route. Avoid unsupported scarcity or dietary claims, and state price and serving period only when verified.
Make the workflow fit your task.
Use the confirmed dish, price, availability window and ordering route to write a short announcement. Preserve limitations such as dine-in availability and avoid invented scarcity. Verify dietary or sourcing claims with the kitchen before adding them.
- What you provide
- Actual special dishes, prices and dates.
- What you get
- Accurate promotional message.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Restaurant offers mushroom risotto tonight at USD 14; service starts at 18:00; no reservation link supplied.
Completed example
Tonight's special: mushroom risotto, USD 14, available from 18:00. Add the restaurant's approved ordering or booking details and confirm availability with the kitchen before publishing.
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.
Should a special be described as almost sold out without stock evidence?
No. Use the actual availability information and leave urgency claims out unless confirmed.
Why do customers request the special outside its serving period?
The announcement may omit dates, hours or service restrictions. Make those details explicit.
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 ↑