AI Objection Handling Workflow

5 steps to a reviewable draft

1. 01

   Capture the objection in context

   Record the buyer's wording, account context and the decision it blocks.

   Result: An objection record without seller interpretation.

2. 02

   Gather approved proof

   List product facts, case evidence and limits the seller can state.

   Result: A checked response boundary.

3. 03

   Draft response options

   Ask for clarification questions and options that expose when the seller must escalate.

   Result: A response sheet grounded in allowed facts.

   Your prompt

   Copy prompt

   Prepare objection responses. Buyer wording: {{objection}}. Account context: {{context}}. Approved proof and limits: {{facts}}. Return clarification questions, response options, proof source, boundary and escalation rule. Mark missing facts [ESCALATE]. Do not invent discounts, capabilities, security claims, customer results or legal terms.

   Example input

   Buyer says the team cannot change reporting tools this quarter.

   Example output

   Clarify: is the blocker timing, migration effort or approval? Commercial exception: [ESCALATE].

4. 04

   Check the boundary

   Review every claim with the product or commercial owner when it affects a commitment.

   Result: Safe response options.

5. 05

   Save the learning

   Record the objection pattern and any required product or sales follow-up.

   Result: A reusable enablement note.