Objection Handling Mandates
Equip SI to handle pushback with confidence and strategy
What It Is
An Objection Handling mandate teaches SI how to respond when a contact pushes back. Instead of relying on generic deflection or immediately escalating to a human, SI uses structured strategies to acknowledge concerns, address the underlying issue, and guide the conversation forward.
Each objection in the mandate defines: the objection pattern (what the contact might say), detection signals (phrases or behaviors that indicate this objection is emerging), the core concern behind the objection (the real worry, not just the surface complaint), a response strategy, specific elements to use and avoid in the response, and an outline example.
The mandate also defines a default handling style — for example, "consultative and empathetic, using the NEPQ (Neuro-Emotional Persuasion Questions) framework" — which sets the overall approach SI takes with all objections in this context.
Objection Handling mandates are different from the Objections in your Reusable Knowledge Base. RK Objections provide content — the actual responses. Objection Handling mandates provide *strategy* — how SI should approach the conversation, what to probe for, and when to pivot.
Why It Matters
Objections are the most delicate moments in any business conversation. Handled well, they deepen trust and move the relationship forward. Handled poorly, they end it.
The default behavior of most AI systems when encountering pushback is to either agree (undermining your position), deflect vaguely (frustrating the contact), or escalate immediately (losing the opportunity to address the concern). None of these are good outcomes.
Objection Handling mandates give SI a playbook. When a prospect says "this is too expensive," SI does not panic or cave. It recognizes the pricing objection pattern, identifies the core concern (usually value uncertainty, not budget), and responds with a strategy that acknowledges the concern, asks a clarifying question to understand the real issue, and then presents value in terms the contact cares about.
This is especially valuable in longer sales cycles where objections surface repeatedly in different forms across emails, calls, and chats. A consistent, strategic approach across all channels builds credibility rather than creating contradictions.
How It Works
When you create an Objection Handling mandate, the AI structures each objection into these components:
Objection Pattern — A description of what the contact says or implies. This is not a single phrase — it is a pattern that covers multiple variations. For example: "The contact questions whether the price is justified relative to perceived value."
Detection Signals — Specific phrases, keywords, or behaviors that indicate this objection is emerging: "too expensive," "out of budget," "not sure it's worth it," "looking at cheaper alternatives," "what do I get for that price?"
Core Concern — The real worry behind the surface objection. For pricing: "The contact is uncertain whether the investment will produce results that justify the cost." This reframing helps SI address the root issue, not the symptom.
Response Strategy — The approach SI should take. For example: "Acknowledge the concern without defending. Ask what outcome would make the investment feel worthwhile. Then connect specific platform capabilities to that outcome with concrete examples."
Do Use / Avoid Elements — Specific approaches to include or exclude. Do use: social proof, specific ROI examples, trial or pilot offers. Avoid: discounting, comparison to competitors, pressure language.
Outline Example — A sample response structure (not a template) that illustrates how the strategy plays out in practice. SI uses this as a reference pattern, not as copy-paste text.
Examples
A SaaS company handles pricing objections during the Win phase
Objection pattern: contact questions whether the subscription cost is justified. Detection signals: "too expensive," "over budget," "cheaper alternatives." Core concern: value uncertainty. Strategy: ask what specific outcomes would justify the investment, then map those outcomes to platform features with quantified results from similar customers. Do use: case study references, ROI calculator link, trial extension offer. Avoid: discounting, apologizing for pricing, comparing to free tools.
A coach addresses skepticism about AI-generated communication
Objection pattern: contact worries that AI communication will feel robotic or impersonal. Detection signals: "sounds automated," "can you tell it's AI," "I want a personal touch." Core concern: fear of losing authenticity. Strategy: explain that SI uses their specific brand voice, show examples of AI-generated vs. hand-written messages (indistinguishable), and emphasize that they review and control autonomy levels. Avoid: being defensive about AI, making claims about AI being "better" than human communication.
A financial advisor handles objections about switching providers
Objection pattern: contact is hesitant to move from their current advisor. Detection signals: "I've been with them for years," "not sure about changing," "what if it doesn't work out." Core concern: fear of disruption and loss of existing relationship. Strategy: validate the existing relationship, focus on what is missing rather than what is wrong, position the switch as an addition of capability rather than a replacement of trust. Do use: transition support details, parallel-run option, specific pain points the contact has mentioned. Avoid: criticizing the current provider.
