Writing effective prompts
assess.one builds your workflow from the description you write. A clear, complete description produces a clear, complete workflow — so it’s worth a little thought.
What to include
Section titled “What to include”Describe the process end to end, and try to cover:
- The goal — what the process achieves (“handle customer complaints”, “approve purchase orders”).
- What to collect — the information captured at the start (name, email, amount, order number, a description…).
- Who does what — which steps are done by staff, and who (by role): support agent, manager, finance.
- Decisions and conditions — anything with different outcomes: “if the amount is over $10,000, require manager approval”, “escalate urgent issues”, “if rejected, send it back for revision”.
- Notifications — when to email or text the customer or team.
- Outcomes / statuses — the stages a record moves through and how it ends (Resolved, Approved, Declined).
A good example
Section titled “A good example”“Create a purchase order approval workflow. Capture the requester’s name and email, the supplier, a description, and the amount. If the amount is over $5,000, require manager approval; otherwise approve automatically. When approved, email the requester and mark the order Approved; when rejected, email the requester with the reason and mark it Declined. Show a dashboard of orders by status and total value approved this month.”
Notice it names the data, the decision (an amount threshold), both outcomes, the notifications, and the reporting.
- Be specific about numbers and choices. “Over $5,000” and “High / Medium / Low priority” give the workflow concrete rules to branch on.
- Mention integrations you’ll need. Say if you want to send SMS, send email, or collect payment — these may require connecting an integration.
- You don’t have to get it perfect. Generate a first version, then refine it in plain language.
- Prefer fewer, clearer steps. Describe the real process; assess.one keeps the workflow as simple as it can.