Objection Handling Reply Engine

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 Objection Handling Reply Engine.

Primary domain signals: reply, conversion, dms.

Inputs:
- offer: {{offer}}
- audience: {{audience}}
- price range: {{price_range}}

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 Objection Handling Reply Engine 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 conversation sequence for reply using {{offer}}.
2) Create branching responses based on {{audience}} intent signals.
3) Align each branch to a clear next action tied to {{price_range}}.
4) Add objection handling and escalation paths.
5) Include risk guardrails and disqualification criteria.

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:
- Conversation Flow
- Branching Responses
- Qualification and Objection Rules
- Escalation Paths
- Success Criteria

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: aaa8a1ce-1ac3-47eb-a959-04e4132add65 · do not redistribute -->

1900 chars