Client: Ticketmaster
Context: Implementation phase
Priority: Medium–High (workflow efficiency)
Summary:
Allow users to run AI Draft on multiple sections within a project consecutively without requiring them to first apply or discard the results of a prior AI Draft run.
Current Behavior:
After initiating AI Draft on a section, users must either apply or discard the generated content before they can run AI Draft on another section.
Requested Enhancement:
Introduce the ability for users to:
- Run AI Draft on Section A
- Navigate to Section B and initiate a new AI Draft run
- Continue this process across multiple sections
- Return later to review, apply, or discard each AI Draft independently
Business Impact:
This limitation disrupts user workflow, particularly for large projects where users prefer to:
- Generate drafts across multiple sections in a single pass
- Review and refine content in a separate, dedicated step
For Ticketmaster, this impacts efficiency during initial content generation and increases friction in adoption of AI Draft capabilities.
Proposed Solution Options:
- Session-Based Drafting: Allow multiple AI Draft outputs to remain in a “pending” state across sections
- Section-Level Draft State: Track AI Draft status independently per section without blocking other sections
- Draft Queue or Batch Mode: Enable users to queue or trigger AI Draft across multiple sections before review
Expected Outcome:
- Streamlined drafting workflow
- Reduced context switching and decision fatigue
- Increased usage and value realization of AI Draft functionality
Additional Notes:
This capability is particularly important for enterprise users managing complex, multi-section projects and aligns with common “draft first, review later” workflows.
@Tyler Richard @Autumn
