- 01
Name the moment work starts
Describe the trigger: a Zendesk ticket enters a queue, an email arrives with a floor plan, a calendar event is 24 hours away, or a form is submitted.
- 02
Show one real example
Use a representative, non-sensitive example and narrate the steps you take. For browser work, the desktop runner can record the sites, controls, and checkpoints used during a teaching run.
- 03
Capture the judgment
Explain how you handle missing information, priority customers, ambiguous requests, exceptions, and failures. These decision rules matter more than a perfect click recording.
- 04
Define the output
State exactly what complete means: a drafted response, an updated CRM record, a published post, or a map edit saved in the correct customer account.
- 05
Choose notifications and approval
Decide who gets notified and what must be reviewed before execution. Use approval for customer communication, publishing, money movement, deletion, and unfamiliar exceptions.
- 06
Test and correct
Run the workflow on a safe example. Edit the prepared result, explain why, and test again. Promote it to higher autonomy only after consistent results.
Workflows
Teach the work—not only the clicks
A reliable automation needs the trigger, examples, judgment calls, and definition of done. SignalDesk helps you capture all four.