Free browser-based planning tool
Turn one workflow idea into a test brief, prompt, and SOP.
Choose one of 25 CSLM workflow designs. Add an owner and system of record, then download a planning draft. Your entries stay in this browser and are not submitted to CSLM.
Use safe inputs
Do not enter customer records, credentials, payment data, regulated information, or confidential files here. CSLM does not receive these fields.
Generated planning draft
CSLM WORKFLOW TEST BRIEF Workflow: WF-003 — Missed-call follow-up draft Business area: Sales Best-fit audience: Local services Owner: [name the accountable owner] System of record: [name the authoritative system] Problem Missed callers receive slow or inconsistent follow-up. Approved input Missed-call event and approved transcription AI role Draft a short acknowledgement and missing-information question Human checkpoint Verify recipient, consent, facts and business hours before sending Failure and stop path Create an internal task; never send when identity is uncertain Data classification Contact details and call transcript Measurement Review time; wrong-recipient incidents Safe first test Use five fictional voicemails with one unclear caller PROMPT DRAFT You are assisting with missed-call follow-up draft. Use only the approved information provided. Draft a short acknowledgement and missing-information question. Identify missing or conflicting information instead of guessing. Do not send, publish, pay, delete, merge, approve, or make a commitment. Return: (1) proposed result, (2) source fields used, (3) uncertainties, and (4) items for the human reviewer. SOP DRAFT 1. Confirm the request is in scope and the input is approved. 2. Preserve the original source and stable record identifier. 3. Run exact validation rules before the AI step. 4. Use AI only for: Draft a short acknowledgement and missing-information question. 5. Route the result to the named owner for this checkpoint: Verify recipient, consent, facts and business hours before sending. 6. If anything fails or remains uncertain: Create an internal task; never send when identity is uncertain. 7. Record the result using: Review time; wrong-recipient incidents. 8. Keep the manual process available and stop the test if risk or correction effort increases.
What this tool does not do
A plan is not a production implementation.
Verify requirements with the people who perform the work. Test with synthetic or specifically approved data, review permissions, confirm vendor terms, exercise failure cases, and keep consequential actions under accountable human approval.