Funnelfeedr Logo

The Objection Library

The Objections page is your account's shared library of the pushback your buyers actually give — and the responses your team has agreed on. Funnelfeedr builds it from your recorded conversations, and you refine it by hand.

Objections live under Settings → Playbooks → Objections.

1. How objections get into the library

There are two paths:

  • Discovered from conversations. Funnelfeedr listens for objections in calls, external meetings and shared emails of users with a Close seat. When the same pushback shows up in two different conversations, it is created as a Candidate. Once it reaches three different conversations, it is proposed for approval — you will find it under Todo → Approvals. Approving it makes it Active.
  • Added by hand. Click New objection and write it yourself. Do this for the objections you already know you get, without waiting for them to be heard three times.

Every objection carries a status (Candidate, Active, Rejected, Archived) and a source (Seeded, Discovered, Manual, AI proposed, Mined, Found on the web), both shown as badges at the top of the detail page.

2. Find an objection

The list view gives you:

  • A search box.
  • Filters for Status and Category.
  • Sortable columns for Name, Occurrences and Last seen.

Columns show how many times an objection has come up (Occurrences), across how many separate calls (Conversations), and how many responses you have written for it (Handlings).

Categories are fixed: Price, Budget, Timing, Need & fit, Trust & credibility, Product gap, Competitor or incumbent, Security & compliance, Procurement & legal, Integration & technical, and Other.

3. Edit the details

Open an objection and use the Details tab:

  • Name — what your team calls it. For example Too expensive.
  • Category — one of the categories above.
  • Intent descriptor — a short description of what the buyer actually means, for example The buyer thinks the price is too high relative to the value. This is what Funnelfeedr matches new occurrences against, so it is worth writing carefully.
  • Description — internal context for your team.
  • Talking points — the notes shown to the rep when this objection comes up on a live call.
  • Status — set an objection to Archived to retire it without losing its history.

Aliases

Aliases are the other ways the same objection gets phrased — "that's out of our budget", "we can get it cheaper elsewhere". Type one into Add alias in the Aliases card and press Enter (or click Create) to save it. Remove one by clicking the × on its chip. Aliases are matched literally during a call, so they trigger faster than intent matching.

4. Write responses

The Handlings tab holds the responses your team should use.

Click Add handling and fill in:

  • Line to say (required) — what the rep should say in response.
  • Label (optional) — a short name for the response.
  • Technique (optional) — Clarify, Acknowledge, Reframe, Evidence, Concede or Defer.
  • Competitor, Pipeline stage and Product — leave these on Any context to make this the default response. Fill one in to write a variant for that specific situation, for example a different answer when the buyer is comparing you to a named competitor. Only active competitors can be picked.

Drag handlings to reorder them. The first active handling is the one suggested first during a call. To keep a handling around without using it, edit it and turn off Active instead of deleting it.

5. Read the history

The Statistics card on the Details tab tells you whether an objection is actually costing you deals:

  • Occurrences, Conversations, First seen and Last seen.
  • How it was meant — Genuine, Brush-off, Condition, or Unspecified.
  • How it ended — how many times it was Addressed in the moment, Left unresolved, or Came back.

An objection with a high Left unresolved or Came back count is a signal that the current handling is not working.

The Occurrences tab shows the individual moments the objection was raised, so you can jump into the conversation it came from.

6. Merge duplicates

If the same objection ended up in the library twice, open one of them and click Merge. Pick the row to merge in — its occurrences, handlings and aliases move over to the one you kept, its name becomes an alias, and the duplicate is deleted.

7. What happens on a live call

During a call with real-time transcription on, Funnelfeedr matches what the buyer says against your library — either by alias (an exact phrasing you listed) or by intent (the meaning matches the intent descriptor). When it hits, a card appears in the coaching panel with the objection's talking points and its handlings, most relevant first.

Only Active objections are matched, and only ones with talking points or at least one active handling. The list warns Won't show during calls next to an objection that has neither. Live coaching needs a Prospect or Close seat.

Tips

  • Write the intent descriptor as what the buyer means, not what they say. The aliases cover what they say.
  • One objection, several handlings, beats several near-identical objections.
  • Review the How it ended breakdown once a month and rewrite the handlings for the objections that keep coming back.
  • Editing the library, and approving candidates, requires the playbooks:write permission, which only the Admin role has by default. Reps without it can still see the library.