Outbound
Outbound
Section titled “Outbound”Outbound is the final-stage module in the current public workflow. It is responsible for generating drafts, supporting operator review, and controlling delivery posture for already-qualified work.
What it owns
Section titled “What it owns”- Campaign-scoped message settings
- Draft generation
- Queue audit
- Review and edit posture
- Delivery controls
What it assumes upstream
Section titled “What it assumes upstream”Outbound is intentionally downstream of:
- campaign selection
- enrichment
- scoring
- contact readiness
That boundary matters because psi* is designed to make outbound reviewable and governable, not just faster.
Operator path
Section titled “Operator path”1. Confirm message posture
Section titled “1. Confirm message posture”Work begins with campaign settings and contextual inputs that were already established upstream.
2. Generate drafts for ready work
Section titled “2. Generate drafts for ready work”Drafts should be created from stored context for qualified leads, not from an improvised live browsing step at send time.
3. Review and deliver
Section titled “3. Review and deliver”Operators can audit queue state, review drafts, and send with the right policy posture, whether that means direct sends or approval-linked delivery paths.
Commercial implication
Section titled “Commercial implication”The public product page for Outbound is intentionally honest about what the module does. It is not the place where psi* claims to solve all upstream qualification problems. It is the place where the product turns readiness into controlled execution.