Support guide7 min readUpdated 2026-06-01
Routing intake forms with StretchAutomate
How intake, routing, notifications, and automation rules should be controlled before public activation.
Routing depends on approved contracts
Automation should only process public intake after endpoint ownership, payload validation, spam posture, and notification destinations are approved.
Human review remains important
Early request-access and contact flows should preserve operator review before workspace provisioning, sales routing, or support escalation.
Safe current state
The suite can show routing concepts as documentation while keeping submission buttons disabled until the integration contract changes status.