Objection Handling Best Practices

Objections are a natural part of any sales conversation. When a visitor pushes back on pricing, mentions a competitor, or says "not right now," Synaptiq's AI needs to respond in a way that addresses the concern without being pushy. This guide covers how to configure and refine that behavior.

How AI Handles Objections

When Synaptiq detects an objection in a visitor's message, it follows a structured response pattern:

1. Acknowledge -- Validate the visitor's concern. Never dismiss or argue.
2. Reframe -- Provide context or a different perspective without being defensive.
3. Bridge -- Redirect toward value or a logical next step.
4. Check -- Confirm the response landed and ask if they have other questions.

This pattern is built into the AI's base behavior. Your job is to supply the specific language and positioning for each objection category so the AI's responses align with how your sales team actually handles these situations.

Common Objection Categories

Navigate to Admin Dashboard > Settings > AI Configuration > Objection Handling to configure responses for each category.

Pricing Objections

Visitors who object to pricing are often signaling that they don't yet see enough value, not that your product is actually too expensive. Your configured responses should connect price to outcomes.

Common triggers the AI detects:

• "That's too expensive"
• "We don't have the budget"
• "Your competitor is cheaper"
• "Can you offer a discount?"

Example configured response:

"Totally fair to weigh cost carefully. Most of our customers found that [Product] pays for itself within the first few months through [specific benefit]. Would it help to see a quick breakdown of what the ROI looks like for a team your size?"

Configuration tips:

• Add your actual ROI data points. Generic claims about "saving money" are weak. Specific numbers ("teams save an average of 12 hours per week") are strong.
• If you offer a free trial or money-back guarantee, make sure it's mentioned in the pricing objection response.
• For "can I get a discount" objections, configure whether the AI should offer a discount code, redirect to a sales call, or present a lower tier.

Timing Objections

"Not right now" is the most common objection in any sales context. The goal is to keep the door open without pressure.

Common triggers:

• "Not right now"
• "Maybe next quarter"
• "We're not ready yet"
• "Just browsing / researching"

Example configured response:

"No problem at all -- timing is everything. Would it be helpful if I sent you a quick summary of what we talked about so you have it when the time is right? I can also flag any updates that might be relevant to what you're working on."

Configuration tips:

• Always offer to send a recap or resource. This captures the lead's email for follow-up without being pushy.
• Avoid "urgency tactics" like fake deadlines. They destroy trust and Synaptiq is designed for relationship-building, not pressure selling.
• Configure a follow-up sequence in your CRM integration to re-engage these leads at the interval they mentioned.

Competitor Objections

When a visitor mentions a competitor, the AI needs to differentiate your product without badmouthing the competition.

Common triggers:

• "We're already using [Competitor]"
• "How are you different from [Competitor]?"
• "[Competitor] does the same thing"
• "We're evaluating [Competitor] too"

Example configured response:

"Nice -- [Competitor] is a solid tool. The main difference our customers point to is [specific differentiator]. If you want, I can pull up a quick comparison based on what matters most to your team?"

Configuration tips:

• Add entries for each major competitor under Objection Handling > Competitors. For each competitor, provide 2-3 honest differentiators that your sales team uses in real conversations.
• Never configure the AI to disparage competitors. Visitors respect a confident, fact-based comparison far more.
• If a visitor is already a paying customer of a competitor, adjust the response to acknowledge switching costs and emphasize migration support.

Trust Objections

New visitors often hesitate because they don't know or trust your company yet. The AI should offer proof, not persuasion.

Common triggers:

• "I've never heard of you"
• "How do I know this works?"
• "Do you have references?"
• "Is my data safe?"

Example configured response:

"Great question. We work with [notable customer or number of customers] and have a [certification/rating]. I can share a case study from a company in your space if that would help?"

Configuration tips:

• Include real social proof: customer count, notable logos (with permission), G2/Capterra ratings, certifications.
• For data security concerns, link to your security page or trust center.
• Configure different trust responses for different verticals if your customer base is diverse.

Configuring Custom Objection Responses

Beyond the four default categories, you can create custom objection categories for situations unique to your business.

Adding a Custom Category

1. Go to Objection Handling and click + Add Category.
2. Name the category (e.g., "Contract Length", "Implementation Complexity", "Team Adoption").
3. Add trigger phrases -- the expressions visitors commonly use when raising this objection.
4. Write 2-3 response templates. The AI will adapt these to the specific conversation context rather than repeating them verbatim.
5. Set the severity level: Low, Medium, or High. High-severity objections can trigger escalation rules (see below).

Writing Good Response Templates

Your templates should sound like your best sales reps, not like marketing copy. A few guidelines:

• Use first person. "I can help with that" feels more natural than "Our team can assist you."
• Be specific. Replace "many customers" with "over 500 companies." Replace "it's affordable" with "the average team spends about $X/month."
• Include a next step. Every objection response should end with a soft call-to-action: share a resource, offer a demo, or ask a follow-up question.
• Keep it concise. Two to four sentences maximum. Long responses feel like lectures.

Training the AI with Your Responses

The most powerful way to improve objection handling is to teach Synaptiq from your actual sales conversations.

Importing from Conversation History

1. Go to Objection Handling > Training.
2. Click Import from Conversations.
3. Synaptiq scans your conversation history and surfaces moments where visitors raised objections.
4. For each objection, you'll see the visitor's message, the AI's response, and the outcome (did the visitor continue the conversation or drop off?).
5. Mark good responses as Approved and poor responses as Needs Improvement.
6. For improved responses, write what your best rep would have said instead.

Approved responses get added to the AI's training data. Over time, this feedback loop makes the AI's objection handling increasingly aligned with your team's style and positioning.

Manually Adding Training Examples

Under Training > Add Example, paste real objections from emails, call transcripts, or support tickets along with your ideal response. This is especially useful during initial setup when you don't yet have Synaptiq conversation history.

Aim for at least 5-10 examples per objection category to give the AI enough variety to adapt naturally.

Escalation Rules for Tough Objections

Some objections should be handed off to a human rather than handled by the AI. Configure escalation rules under Objection Handling > Escalation.

When to Escalate

Set rules for automatic escalation based on:

| Trigger | Example | |---|---| | Objection category | Always escalate legal or compliance questions | | Severity level | Escalate any High-severity objection | | Repeat objections | Escalate if the visitor raises the same objection twice after the AI responds | | Visitor score | Escalate if a high-scoring lead (above your threshold) raises any objection | | Sentiment drop | Escalate if the AI detects frustration or negative sentiment shift |

How Escalation Works

When an escalation rule triggers:

1. The AI tells the visitor it's connecting them with a team member.
2. A notification is sent to the assigned rep or team channel (Slack, email, or in-app -- configured under Integrations).
3. The conversation is flagged in the dashboard with the escalation reason.
4. If a rep is available and live chat is enabled, the handoff happens in real time. If no one is available, the AI collects contact information and promises a follow-up within a timeframe you configure.

Example escalation message the AI sends:

"That's a really important question and I want to make sure you get the best answer. Let me connect you with someone on our team who can speak to that directly."

Configuring the Escalation Fallback

Under Escalation > Fallback, define what happens when no rep is available:

• Collect contact info: The AI asks for email and phone, then creates a high-priority task for your team.
• Schedule a callback: If integrated with your calendar tool, the AI offers available time slots.
• Send resources: The AI shares relevant documentation or a pre-recorded demo to keep the visitor engaged until a rep follows up.

Choose the fallback that matches your team's responsiveness. If your reps typically respond within an hour, collecting contact info works fine. If response times are longer, scheduling a callback sets clearer expectations.