Operational rollout checklist

Before you go live

• Default workflow is selected and enabled
• workflow routing is enabled only after review
• There is a clear Inbox handoff path for uncertain/edge cases
• Hours behavior is configured (only if needed)
• Departments + assignment conventions match your top-level workflow lanes

After you go live

• Watch the handoff rate: a sudden drop can mean customers are stuck in automation; a sudden spike can mean automation is under-routing.
• Scan for ambiguous states: avoid situations where automation continues sending messages after handoff.
• Keep early branching stable: make incremental changes and avoid “big bang” refactors of the entrypoint.

When changing production workflows

Treat edits like a release:

• document the intent of the change (what it improves, what it risks)
• verify the fallback path (Inbox handoff) is still reachable
• validate off-hours behavior if you use hours controls

Next:

• Troubleshooting