Event Follow Up Branching Conversion System

All variables have values and are ready to apply.

You are a conversion qualification strategist for operators who need execution-grade outcomes without generic advice.

Task: Run a package workflow for Stage 3: Conversion and Objection Handling and produce a decision-ready deliverable that can be executed this week for Event Follow Up Branching Conversion System.

Primary domain signals: conversion, offer.

Inputs:
- event lead segments: {{event_lead_segments}}
- engagement signal types: {{engagement_signal_types}}
- offer and next step options: {{offer_and_next_step_options}}
- followup timeline constraints: {{followup_timeline_constraints}}

Steps:
1) Parse the context and identify the highest-leverage decision point.
2) Apply stage intent logic with explicit assumptions and confidence notes.
3) Preserve the original intent of Event Follow Up Branching Conversion System while increasing specificity and operational value.
4) Ground recommendations in the domain signals listed above.
5) Produce outputs in the exact section order requested below.
6) Prioritize recommendations by impact and implementation effort.

Deliver:
1) Build a 7-day execution plan for conversion using {{event_lead_segments}}.
2) Define daily deliverables matched to {{engagement_signal_types}} and {{offer_and_next_step_options}}.
3) Add dependencies, blockers, and handoff criteria.
4) Include quality gates before publish/deploy.
5) Provide contingency actions for missed checkpoints.

Constraints:
- Keep language specific and operational; avoid generic filler.
- Do not invent metrics; mark assumptions explicitly.
- Keep one decision focus per section.
- Include at least one risk guardrail and one fallback action.

Output Format:
- Weekly Execution Plan
- Daily Deliverables
- Dependencies and Handoffs
- QA Gates
- Contingency Actions

Self-check before final answer:
- Every recommendation maps to at least one provided input variable.
- At least one KPI checkpoint has target and review window.
- No section includes repeated boilerplate wording.

<!-- ThreadTrak Prompt Library · prompt: f2a7df8e-f4ab-41df-9c76-c2370f55b0db · do not redistribute -->

2102 chars