Aura LogoAura

Objections

Track, categorize, and analyze objections across your sales conversations

Objections

Objections are a natural part of sales conversations. Aura identifies objections in your calls, categorizes them, and tracks patterns—helping you prepare better responses and improve your win rates.

How Objection Tracking Works

┌─────────────────────────────────────────────────────────────────────────────┐
│                       OBJECTION TRACKING FLOW                                │
└─────────────────────────────────────────────────────────────────────────────┘

    Call Recording          AI Analysis           Objection Database
         │                      │                        │
         ▼                      ▼                        ▼
    ┌─────────┐            ┌─────────┐              ┌─────────┐
    │Transcript│───────────▶│Detect   │─────────────▶│Store &  │
    │Generated │            │Objections│              │Categorize│
    └─────────┘            └─────────┘              └─────────┘
                               │                        │
                               ▼                        ▼
                         ┌─────────┐              ┌─────────┐
                         │Track    │              │Analytics │
                         │Handling │              │& Reports │
                         └─────────┘              └─────────┘

Objection Detection

What AI Identifies

The AI looks for:

  • Direct concerns ("We're worried about...")
  • Questions implying doubt ("How do we know if...")
  • Hesitation signals ("I'm not sure about...")
  • Pushback on specifics ("That seems expensive...")
  • Competitor mentions ("We're also looking at...")

Objection Properties

Each detected objection includes:

PropertyDescription
TextWhat was said
TimestampWhen in the call
CategoryType of objection
HandledWhether it was addressed
ResponseHow it was handled (if at all)

Objection Categories

Default Categories

Aura includes common objection types:

CategoryDescriptionExample
PriceCost-related concerns"That's more than we budgeted"
TimingNot-now concerns"We're not ready for this yet"
CompetitionCompetitor-related"We're also evaluating X"
ProductFeature/capability"Does it integrate with Y?"
RiskChange/implementation"What if it doesn't work?"
AuthorityDecision process"I need to check with my boss"
PriorityUrgency concerns"We have other priorities"

Custom Categories

Add your own categories:

  1. Go to SettingsObjections
  2. Click Add Category
  3. Name and describe the category
  4. Save

Custom categories appear in:

  • Call analysis
  • Analytics dashboards
  • Manual tagging

Viewing Objections

In Call Details

For any call:

  1. Open call details
  2. Scroll to Objections section
  3. See all detected objections

Each objection shows:

  • The text/quote
  • Timestamp (click to jump)
  • Category
  • Whether handled

Objection Timeline

┌────────────────────────────────────────────────────────────────┐
│ OBJECTIONS IN THIS CALL                                        │
├────────────────────────────────────────────────────────────────┤
│                                                                 │
│  [12:34] PRICE                                            ✓    │
│  "That's quite a bit more than we're spending now"             │
│  Handling: Discussed ROI and payback period                    │
│                                                                 │
│  [18:45] TIMING                                           ✗    │
│  "We're in the middle of a migration right now"                │
│  Not addressed - consider following up                         │
│                                                                 │
│  [24:12] COMPETITION                                      ✓    │
│  "How do you compare to CompetitorX?"                          │
│  Handling: Highlighted key differentiators                     │
│                                                                 │
└────────────────────────────────────────────────────────────────┘

Manual Tagging

Add objections AI missed:

  1. In call details, click Add Objection
  2. Select timestamp or enter manually
  3. Enter the objection text
  4. Choose category
  5. Save

Objection Analytics

Analytics Dashboard

Go to AnalyticsObjections to see:

  • Objection frequency: Most common objections
  • Category breakdown: By type
  • Resolution rate: How often objections are handled
  • Correlation with outcomes: Objections vs. win rates

Heat Map View

┌────────────────────────────────────────────────────────────────┐
│ OBJECTION HEAT MAP - Last 30 Days                              │
├────────────────────────────────────────────────────────────────┤
│                                                                 │
│  Price        ████████████████████████  42 (35%)               │
│  Timing       ██████████████            28 (23%)               │
│  Competition  █████████████             26 (22%)               │
│  Risk         ██████████                12 (10%)               │
│  Authority    ██████                     8 (7%)                │
│  Other        ███                        4 (3%)                │
│                                                                 │
│  Total Objections: 120                                          │
└────────────────────────────────────────────────────────────────┘

By Team Member

Compare objection handling across team:

RepTotal ObjectionsHandledResolution Rate
Alice453884%
Bob524179%
Carol383592%

Handling Objections Better

Preparation

Use objection data to prepare:

  1. Know common objections: Review top categories
  2. Prepare responses: Have talking points ready
  3. Learn from top performers: See how others handle them

During Calls

When objections arise:

  1. Listen fully: Don't interrupt
  2. Acknowledge: "That's a fair concern"
  3. Clarify: Make sure you understand
  4. Respond: Use prepared talking points
  5. Confirm: "Does that address your concern?"

After Calls

Review your handling:

  1. Watch objection moments
  2. Evaluate your response
  3. Note what worked
  4. Plan improvements

Objection Response Library

Building a Library

Create standard responses:

  1. Review most common objections
  2. Document best responses
  3. Include proof points/evidence
  4. Share with team

Example Response Templates

Price Objection:

"I understand budget is a consideration. Let me share how [Customer] saw a 3x ROI within 6 months by [specific benefit]. When we factor in the time saved, most customers find it pays for itself within [timeframe]. Would it help to walk through the ROI calculation together?"

Timing Objection:

"I hear you're in the middle of [their situation]. What I've found is that companies in a similar position benefit from having the new solution ready when their [migration/project] completes. If we start planning now, we can have you fully ramped by [date]. What would need to happen for the timing to work?"


Configuration

Organization Settings

Customize objection tracking:

  1. SettingsObjections
  2. Configure:
    • Default categories
    • Custom categories
    • Category descriptions
    • Display order

Per-Call Settings

Mark objections manually:

  • Add missed objections
  • Recategorize
  • Mark as handled/unhandled
  • Add notes

API Access

Get Call Objections

query GetCallObjections($callId: ID!) {
  call(id: $callId) {
    objections {
      id
      text
      timestamp
      category {
        id
        name
      }
      handled
      response
    }
  }
}

Objection Analytics

query ObjectionAnalytics($dateRange: DateRange!) {
  objectionAnalytics(dateRange: $dateRange) {
    totalObjections
    byCategory {
      category
      count
      resolutionRate
    }
    correlationWithOutcome {
      objectionsVsWinRate
    }
  }
}

Best Practices

For Sales Reps

  1. Prepare: Know your top objections
  2. Practice: Role-play responses
  3. Learn: Study successful handling
  4. Improve: Review your own calls

For Managers

  1. Track trends: Monitor objection patterns
  2. Train: Create objection-handling sessions
  3. Share: Distribute best practices
  4. Measure: Track resolution rates

For Organizations

  1. Document: Build response library
  2. Update: Refresh based on market changes
  3. Align: Ensure consistent messaging
  4. Iterate: Continuously improve

Common Patterns

Objections That Kill Deals

Watch for unhandled:

  • Budget/price without ROI discussion
  • Multiple stakeholders not identified
  • Timeline concerns left unaddressed
  • Competitor advantages not countered

Objections That Lead to Wins

When handled well:

  • Price concerns with ROI evidence
  • Risk concerns with case studies
  • Timing concerns with implementation support
  • Competition comparisons with honest differentiation

Troubleshooting

Objections Not Detected

Possible causes:

  • Subtle phrasing
  • Technical audio quality
  • Non-standard language

Solution: Add manually via UI

Wrong Category

If miscategorized:

  1. Open the objection
  2. Change category
  3. Save

This improves future detection.

Missing From Analytics

Check:

  • Call has completed processing
  • Objections exist on the call
  • Date range includes the call

Next Steps

On this page