Build a procedure in plain English
Open Automations and describe the customer signal, checks, and desired outcome. klaxify turns the instruction into a structured draft with an explicit trigger, conditions, messages, internal notifications, and governed commerce actions.
Every change creates an immutable procedure version. A newer version never inherits the testing status of an older one.
Run the Procedure Simulator
Expand Procedure Simulator on a workflow. Select representative tenant conversations, including examples that should match and examples that should not, then select Run safe simulation.
The simulator:
- Uses the current tenant-owned conversation, customer, and cached commerce context.
- Runs the same deterministic trigger and condition logic used by the procedure.
- Shows which steps would prepare a message or request live validation.
- Verifies that customer messages and commerce steps have approval policies.
- Verifies the procedure declares live context, final validation, workspace policy, and audit requirements.
- Sends no customer message, consumes no AI credit, and changes no commerce record.
Understand the results
Matched means the trigger and every required condition fit the scenario. Safely did not match means the procedure correctly avoided an unrelated conversation. A missing-context warning means the procedure stayed inactive because a required fact was unavailable. A failed safety review identifies the exact unguarded or malformed step.
Activate the tested version
A manager can activate only the current version after all selected scenarios pass and at least one scenario genuinely matches. Activation does not grant unlimited authority: live runs still fetch current commerce context, apply tenant policy and amount limits, require approval when configured, use duplicate protection, and write to the audit history.