Convarza AI

How to qualify a lead on a phone call, and hand the script to an agent

Four questions, asked in an order that survives a real conversation. Then how to give the same script to an AI agent without it sounding like a form.

Most qualification scripts fail for the same reason: they are written as a form, so they get read as an interrogation. The caller answers four questions in a row, feels processed, and the rep gets four fields filled in and no relationship.

Here is a version that survives a real conversation, and then how to hand it to an AI agent without it reverting to a form.

The four things you need

Everything else is curiosity. These four decide whether this is worth a calendar slot.

1. What are you trying to fix?
Not "what are you looking for". The problem, in their words. This is the only question that tells you whether you can help at all, and it is the one most scripts put last.
2. What happens now?
The current workaround. If there isn't one, the pain is theoretical and the deal will stall. If the workaround is a person's time, you have a number to work with.
3. Who else has to agree?
Asked plainly, early, and without apology. "Is this your call, or is there someone else who'd need to see it?" Nobody is offended by this. Everybody is offended by discovering it in week six.
4. When does this need to be working?
A date, or the honest absence of one. "No particular rush" is a real answer and should route differently from "before the quarter ends".

Budget is deliberately not on the list. Ask it on a first call and you get a made-up number or a defensive one. It falls out of questions 2 and 4 once you know what the workaround costs and how soon it has to stop.

The order matters more than the wording

Problem first, always. It earns the right to ask the rest. Authority in the middle, while the conversation is still warm and factual. Timeline last, because it is the easiest to answer and gives the call a natural close.

If you only get through two, get through one and two.

Handing it to an agent

The temptation is to paste the four questions into the prompt as a numbered list. Do that and you get a machine reading a form — the exact thing you were trying to avoid.

Describe the job instead, and let the questions be the goal rather than the script:

You are qualifying inbound enquiries. Find out what they are trying to fix, what they do about it today, who else would need to approve, and roughly when it needs to be working. Ask in that order, one at a time, and follow up on what they actually say rather than moving on. If they answer two of the four, that is enough. Never quote custom pricing — hand to a human for anything about discounts or contracts. If they are ready, offer a slot.

Three things make that work where a numbered list does not: one at a time stops it stacking questions, follow up on what they say stops it steamrolling an interesting answer, and two of four is enough stops it grinding a reluctant caller. More on this in writing a prompt for a customer-facing agent.

Write the answers somewhere useful

A qualified lead whose answers live in a transcript is barely qualified. The four answers should land on the contact record as fields, so the next person opens the record and reads them without scrubbing audio.

This is where the schema matters. If "what are they trying to fix" has nowhere to go, it ends up in a note, and notes do not filter or report. Define the attributes first — Convarza lets an admin add them as typed fields, so a dropdown is a dropdown and a date is a date.

Then move the stage, once

Qualification produces exactly one state change: the lead stage moves. It does not also set a "call outcome" to Qualified, because the outcome describes the attempt and the stage describes the person. Keeping those separate is what lets your pipeline report agree with your call log — the distinction is worth ten minutes.

What good looks like after a month

  • Every qualified contact has answers in fields, not prose.
  • The stage moved on the call, not the next morning.
  • Unqualified callers were told so, politely, and left the calling list rather than being re-dialled by an automation that did not know.
  • Your reps' first calls start at question five, because one to four are already answered.

That last one is the whole return. See it against your own list.

See it answer your own calls

Thirty minutes, your numbers and your channels on the screen. No slide deck.

No setup fee. No per-conversation charge. Cancel from inside the product.