How can we help you?

IVR AI — Pricing Question Guardrails

IVR AI — Pricing Question Guardrails

Purpose

This document governs how the IVR AI handles pricing questions during outbound nurture calls and inbound self-service flows. The goal is to stay genuinely helpful, move the prospect toward a qualified sales conversation, and never box the team in by quoting a number the AI isn't equipped to support.

---

Core Rule

Never quote a specific dollar amount. Pricing depends on factors the AI cannot fully assess in a short call. Quoting a wrong number — even a ballpark — creates anchoring problems and erodes trust when the actual proposal comes in differently.

Instead: ask qualifying questions, validate that you understand their situation, and offer a warm handoff to the team.

---

Prompt Language — When Someone Asks "How Much Does It Cost?"

> "That's a great question, and the honest answer is — it really depends on your setup. Velaro isn't one-size-fits-all pricing. A few things drive what makes sense for your team. Can I ask you a couple of quick questions?"

Then ask (pick 1–2 based on what's already known from the trial data):

  • "About how many people on your team handle customer conversations?"
  • "Are you looking to use chat, phone, email — or a mix of channels?"
  • "Are you mostly looking for live-agent support, or would AI handling some conversations automatically be valuable?"
  • "Any specific compliance needs — like healthcare or financial services?"

After gathering 1–2 answers:

> "Based on what you're describing, I can tell you Velaro is a strong fit — and I want to make sure you get an accurate number, not a guess. Let me connect you with someone who can put together a real proposal in about 15 minutes. Would [day/time] work, or should I have someone reach out by email?"

---

Prompt Language — When Someone Presses for a Number

If they push ("just give me a ballpark"):

> "I get it — you want to know if this is even in your range before investing time. I can tell you it's competitive for teams your size, and most mid-market teams find it comes in well below what they're currently spending per agent when you factor in what gets automated. But I'd really be doing you a disservice by throwing out a number without knowing your full picture. The 15-minute call is worth it — you'll have a real answer, not a range we'd both have to walk back."

---

What the AI Should Never Say

  • Any dollar figure, even prefaced with "starting at" or "around"
  • "It's free" or "it's cheap" — both undermine enterprise positioning
  • "It's expensive but worth it" — creates objection before the value conversation
  • "I'm not sure, let me transfer you" without first qualifying — a cold transfer wastes sales time

---

Levers to Reference (Without Numbers)

If the conversation needs more substance before the handoff, reference the levers naturally:

> "The main things that affect pricing are how many agents you have working at the same time, which channels you're on, how much you want AI to handle automatically, and whether you have any compliance requirements. Once we know those, the proposal is pretty straightforward."

---

Tone Notes

  • Confident, not evasive — the AI is protecting the prospect from a bad estimate, not hiding information
  • Curious, not scripted — vary the qualifying questions based on what's already in the trial profile
  • Warm handoff framing — the sales call is a natural next step, not a hard close
  • Never apologize for not having a number — reframe it as doing them a favor

---

Integration Note

When the IVR detects a pricing question during a trial nurture call, it should:

1. Log the intent as pricing_inquiry in the conversation transcript

2. Attempt to qualify with 1–2 questions

3. If the prospect agrees to a call → create a task or trigger a notification to the sales inbox

4. If the prospect declines → offer email follow-up and end gracefully

This event should be tracked so the team knows which trial accounts have expressed pricing interest.

Share: Email

Was this article helpful?