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.

CSLM WORKFLOW TEST BRIEF

Workflow: WF-006 — Shared-inbox classification
Business area: Support
Best-fit audience: Customer-support teams
Owner: [name the accountable owner]
System of record: [name the authoritative system]

Problem
Messages wait in the wrong inbox or have no owner.

Approved input
Approved support message and account reference

AI role
Suggest topic, urgency and queue

Human checkpoint
Review legal, billing, safety, emotional and unclear messages

Failure and stop path
Route uncertainty to a monitored triage queue

Data classification
Customer correspondence

Measurement
Correct first queue; urgent-message misses

Safe first test
Test 20 synthetic messages across normal and urgent categories

PROMPT DRAFT
You are assisting with shared-inbox classification. Use only the approved information provided. Suggest topic, urgency and queue. 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: Suggest topic, urgency and queue.
5. Route the result to the named owner for this checkpoint: Review legal, billing, safety, emotional and unclear messages.
6. If anything fails or remains uncertain: Route uncertainty to a monitored triage queue.
7. Record the result using: Correct first queue; urgent-message misses.
8. Keep the manual process available and stop the test if risk or correction effort increases.

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.

← Return to the 25-workflow atlas