> For the complete documentation index, see [llms.txt](https://university.kurvpay.com/1roOeoqsO7DNkeNJG2xS/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.kurvpay.com/1roOeoqsO7DNkeNJG2xS/selling-kurv/objection-handling.md).

# Objection Handling

The pushback you'll hear — and confident, honest answers.

**Why This Matters**

Objections aren't rejections — they're requests for more information. A prospect who objects is still engaged. The goal isn't to overcome the objection by force, but to understand the concern behind it and address it with confidence.

**The LAER Framework**

Use this simple structure for any objection:

* **Listen** — Let the prospect finish. Don't interrupt or jump to a rebuttal.
* **Acknowledge** — Validate the concern ("That's a fair question," "I hear that a lot").
* **Explore** — Ask a clarifying question to find the real issue behind the stated objection.
* **Respond** — Address the specific concern with facts, proof points, or a reframe.

***

**Common Objections & How to Handle Them**

**1. "I'm happy with my current processor."**

* *Explore:* "What do you like most about them? Anything you wish worked better?"
* *Respond:* Position Kurv as a comparison, not a replacement pitch. Offer a free rate analysis or statement review to show concrete savings — let the numbers make the case.

**2. "Your rates/fees are too high."**

* *Explore:* "Compared to what you're paying now, or what you expected going in?"
* *Respond:* Reframe around total value — hardware, support, funding speed, chargeback protection — not just the rate. If pricing is genuinely not competitive, use the Altus pricing page to show transparent, itemized costs instead of a bundled number.

**3. "I need to think about it."**

* *Explore:* "Totally understand. Is it the pricing, the switch process, or something else you want to think through?"
* *Respond:* This is often a stall for a deeper objection. Narrowing it down lets you solve the real issue instead of just following up blind.

**4. "Switching processors sounds like a hassle."**

* *Respond:* Walk through the actual onboarding timeline and what Kurv handles for them (equipment setup, migration, training). Most switches take days, not weeks — say so specifically.

**5. "I'm locked into a contract."**

* *Explore:* "When does it renew? Do you know if there's an early termination fee?"
* *Respond:* Offer to review their contract for hidden fees or auto-renewal terms. Many merchants don't realize what they've signed — this builds trust even if they can't switch today.

**6. "I don't have time for this right now."**

* *Respond:* Don't push for the full pitch. Ask for 5 minutes or offer to leave a one-page leave-behind (slick) and follow up. Protect the relationship over the immediate close.

**7. "I've never heard of Kurv."**

* *Respond:* Lean on credibility — client count, years in business, partner brands (NMI, Payliance, MaxxPay). A short case study or testimonial goes a long way here.

***

**Quick Reference: Reframing Phrases**

| Instead of...             | Try...                                                           |
| ------------------------- | ---------------------------------------------------------------- |
| "But our rates are lower" | "Let's look at what you're actually paying today"                |
| "You should switch"       | "Here's what switching would look like for you"                  |
| "That's not true"         | "I can see why it might seem that way — here's the full picture" |

***

**Tips for Agents**

* Always ask one more question before responding — most objections have a second layer.
* Keep a merchant statement or rate analysis handy; specifics beat generalities every time.
* Never argue. Reframe.
* If you can't resolve it live, it's okay to say "Let me get you the right answer" and follow up — don't guess.

{% hint style="info" %}
**Principle:** acknowledge, ask a question, then reframe to value. Never argue a merchant into a corner — be the honest broker who makes the decision easy.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://university.kurvpay.com/1roOeoqsO7DNkeNJG2xS/selling-kurv/objection-handling.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
