How to use the Empty State Copy Generator.
An empty state should explain why the area is empty and offer a useful first action. Distinguish a new account from a failed load.
Make the workflow fit your task.
Determine whether the empty area reflects a new state, no matching results or a failed load. Explain that reason and offer the action that fits it, avoiding an onboarding invitation when existing data may be unavailable.
- What you provide
- Product context and available first actions.
- What you get
- Helpful empty-state text and action label.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
A new account has no saved comparisons.
Completed example
No comparisons yet. Start with two supplier files to create your first comparison.
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 all empty screens invite the user to create something?
No. A failed load or filtered-out result needs a different explanation and recovery action from a genuinely new account.
Why does the empty state make users think their work was deleted?
Clarify the actual condition and offer the relevant recovery or filter action. Do not imply absence when data could not be loaded.
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 ↑