Flows workflow logoFlows
Customer Support Inbox
0/5 steps0%

Step 1 of 5

Define the ticket model

Tickets, messages, and statuses need shapes before UI.

First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.

Prompt Capsule
Define the support system model: the ticket (id, owner userId, subject, category from a fixed set, status open/in-progress/resolved, createdAt/updatedAt) and its messages (ticket id, author user/admin, body, timestamp) as a thread; the status transition rules and who can change them; visibility rules (owners see theirs, admins see all); and what notifies the user when a reply lands (in-app indicator at minimum).
Paste into EmergentFull Build: complete implementation prompt with explicit requirements

Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.

Actual change check

Expected after this step

A ticket/message model with transitions and visibility rules.

Should NOT happen

  • An existing feature broke
  • A button only logs to console
  • Data disappears after refresh
  • Errors fail silently with no visible state

This is what should exist before you continue. If reality does not match, do not move on.

Track what changed, failed, or needs follow-up. Notes export with the flow.

Made with Emergent