Product demos & UI / Prompt

Prompt: demonstrate inbox triage using one rule

Explain one rule against a few readable messages. Keep classification, selection and the resulting action separate so viewers can see why an item moves.

By AnimroUpdated 2 min readAI-assisted · independently agent-reviewed

Who this is for: Teams demonstrating inbox organization.

What to prepare

  • Sample inbox and tags
  • Actual move behavior
  • Destination evidence

Copyable creative brief

An authored planning example. Replace illustrative details with your approved product facts and assets.

Create a 30-second illustrative inbox demo for a fictional support workspace. Show three sample messages: “Sample label question,” “Sample invoice question,” and “Sample delivery question.” The demonstrated rule is “Move messages tagged Design to the Design review queue.” Supply the actual tags: the label question is Design; the other two are Billing and Delivery. Hold the rule before selecting the label question. Show the verified move action and inspect that same message in Design review. Keep its subject and sample sender consistent. Leave the two unrelated messages unchanged. Use “One matching sample message” rather than a universal accuracy claim. If the product applies the rule automatically, show the configured trigger and observed behavior; otherwise present it as a manual triage choice. Do not invent automated classification.

Make it your own

Rule
Use one explicit condition and destination.
Messages
Choose clearly fictional matching and nonmatching examples.
Action mode
Distinguish manual action from verified configured automation.

Prepare the rule and sample set

Provide the real category or tag labels, the queue destination and a matching record. The viewer should be able to apply the rule mentally to the visible examples. Avoid messages requiring private context or ambiguous interpretation.

Adapt the task

For training, show where the rule is configured before applying it. For a shorter introduction, state the preconfigured rule and demonstrate one match. If the classification is a human judgment, say so instead of presenting it as a deterministic product result.

Correct scope errors

If all messages disappear after one is selected, verify whether the action affected a group. Restore the correct scope or explain the bulk selection. If the destination uses a new subject line, preserve another real identity marker rather than making up an identifier.

Review checklist

  • The condition explains the selected message.
  • Unselected messages remain unaffected unless scope says otherwise.
  • Automatic behavior is evidenced rather than assumed.
Explore product demos & ui ↗