> ## Documentation Index
> Fetch the complete documentation index at: https://docs.octavehq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# What are Objections in Octave?

> Objections capture recurring pushback — the underlying concern, the misconceptions behind it, and the response that actually resonates.

## What is an Objection?

An Objection is a [Library](/concepts/library) entity that captures a recurring piece of pushback your team hears in the field — "you're too expensive", "we're doing this in-house", "the timing isn't right" — together with the underlying concern, the assumptions driving it, the questions that uncover it, and the reframe that handles it. Objections elevate objection handling from a tribal Slack thread into structured knowledge that agents read at runtime when writing emails, prepping calls, and qualifying accounts.

Objections work alongside [Alternatives](/concepts/alternatives) and [Competitors](/concepts/competitors) to cover the full surface of "reasons prospects don't move forward." A Competitor is a vendor in the deal. An Alternative is the status-quo path. An Objection is the specific stated reason a prospect hesitates — whatever the underlying cause.

## What an Objection contains

| Field                          | Purpose                                         |
| ------------------------------ | ----------------------------------------------- |
| Name                           | External-facing label for the objection         |
| Internal name                  | Internal alias                                  |
| Description                    | The objection as a prospect states it           |
| Underlying concern             | What the prospect is *really* worried about     |
| Assumptions and misconceptions | The beliefs behind the objection                |
| Areas to probe and clarify     | Questions that surface the real issue           |
| Reframe and response           | How to redirect the conversation and resolve it |

## How Objections connect to other entities

* **[Motions](/concepts/motions)** and Motion Playbooks — objections are recommended per Motion ICP and attached as anchor overrides on Motion Playbooks
* **Findings** ([analytics](/concepts/analytics)) — every objection raised in a call or email is captured as a finding and linked back to the matching Objection entity
* **Motion ICP learnings** — objection-typed learnings on a Motion ICP feed directly into refining the Objection's reframe and response

Over time the [analytics](/concepts/analytics) pipeline detects recurring objections in conversation evidence and proposes new Objections to add to the Library — or refinements to existing ones — so your objection handling stays in lockstep with what buyers are actually saying.

## How agents use Objections

When an agent generates outreach for a persona×segment cell where a known objection is common, it pre-handles the objection in the messaging — referencing the underlying concern, addressing the misconception, and using the prepared reframe. When the Call Prep Agent runs against an account, it surfaces the objections most likely to appear so reps walk in with a response ready.

## Managing Objections via API

* `GET /api/v2/objection/list` — list objections
* `GET /api/v2/objection/get` — get a specific objection
* `POST /api/v2/objection/create` — create an objection
* `POST /api/v2/objection/generate` — AI-generate objections from your offering and market
* `POST /api/v2/objection/update` — update an objection
* `DELETE /api/v2/objection/delete` — delete an objection