What you'll achieve
A published Procedure has a verified result and sensitive actions remain approval or handoff controlled.
Create a Procedure
Open Settings > AI > Procedures and choose a template or create a Procedure from the supported action registry. Keep the trigger, Inbox or audience and action scope explicit.
Save a draft first. Drafts do not run and do not change an existing published version.
Run a dry test before publishing
- Choose a synthetic or already safe Conversation in the Procedure test panel.
- Check every condition, planned action and approval result. A dry test does not send a customer message or execute a provider mutation.
- Fix missing Inbox targets, invalid conditions or safety blocks, then run the test again until the expected result is shown.
Publish and verify the runtime result
Publish only after the dry test is understood. A published Procedure is versioned. Later drafts do not replace the active version until you publish them.
Trigger one controlled runtime test and confirm the completed run in the Procedure history. Setup Center uses that successful run as evidence that the published action is executable, not merely saved.
Billing, account, privacy, legal, security, abuse and angry-customer actions keep their approval or human handoff requirement. Never weaken that policy to make a test pass.