Summary
Drafts and approvals are where the product’s automation meets real human control. The current app makes it clear that draft review is not a generic content-edit step. It is tied to:- channel type
- run context
- approval state
- provider readiness
- retry behavior
- draft history over time
Who this is for
- Operators responsible for review and send readiness
- Campaign managers validating outbound quality
- Teammates debugging why a draft is stuck, rejected, failed, or not sendable yet
Where to find it in the app
- Drafts
- individual draft detail pages
- linked run and communication contexts
What the current draft flow suggests
Draft list
The main drafts area appears to support broad queue review, filtering, and pagination across all drafts.Draft detail
The draft detail view appears to include:- current status
- action buttons for approval, rejection, and retry where relevant
- draft history
- contact and campaign context
- channel-specific behavior
- warnings when required sending infrastructure is not configured
What to look at first on a draft
When a draft looks wrong or stuck, inspect these in order:- current status
- whether it is waiting on a human or still processing
- infrastructure warnings
- draft history
- related contact, campaign, and run context
Draft triage order
- identify the current draft status
- decide whether it is still processing or waiting on a human
- check whether infrastructure warnings are present
- review the draft history before retrying or rejecting
- only then decide whether the fix belongs in content, setup, or campaign design
How to think about retry
Retry is useful when the draft likely failed because of a transient or corrected problem. Retry is a bad habit when the team has not yet answered:- what failed
- whether infrastructure is fixed
- whether the content itself is still inappropriate
What different draft situations usually mean
Processing
The system is still working. Changing campaign setup too early can create more confusion than signal.Waiting for approval
This is a human decision point, not a system failure.Failed or failed to send
This may be content-related, but it may also point to email or phone setup problems.Rejected
The right next action may be campaign, agent, or messaging refinement rather than blind regeneration.Why approvals matter operationally
The app explicitly distinguishes between drafts that are still processing, drafts waiting on user action, and drafts that reached final states. That means approval is part of a larger operational state machine, not just a button click.Important blocking conditions
The current product flow suggests that a draft can be operationally blocked if required infrastructure is missing, such as email or phone delivery configuration.Example decision table
| Situation | Safer first response |
|---|---|
| Draft is still processing | Wait and re-check before changing campaign settings |
| Draft is waiting for approval | Review content and context before approving |
| Draft failed and provider setup is incomplete | Fix infrastructure first |
| Draft failed but setup looks healthy | Inspect history, campaign setup, and retry intentionally |
What not to do
- do not use retry as a substitute for diagnosis
- do not approve drafts just because the queue is building up
- do not assume every draft problem is a prompt or content problem
Good reviewer habits
- compare the draft to campaign intent before approving
- use infrastructure warnings as real blockers
- review history before deciding the same action again
- separate channel/setup problems from wording problems
Success checklist
- Reviewers know which drafts are waiting for action versus still processing.
- The team can tell whether a draft problem is content-related or infrastructure-related.
- Retry behavior is used intentionally rather than as a blind fix.
- Approval and rejection are understood in the context of campaign runs and communications, not as isolated actions.