Qualification Conversation Scripts
Link 3 — Qualification · Role: script · Loop step: Repair · Version 1.0.0-draft · Status: contentreadydeliverypending
Qualification Conversation Scripts™ (RLR-19)
Link 3 — Qualification · Role: script · Loop step: Repair · Version 1.0.0-draft · Status: content_ready_delivery_pending
Usable language for gathering qualification information without making the interaction feel mechanical or adversarial. These scripts operationalize the categories in the Qualification Framework & Checklist™ (RLR-17) and produce the evidence the Lead Scoring Rubric™ (RLR-18) needs to classify a lead.
How to use these scripts
- Ask the required questions in every conversation; ask conditional
questions only when a prior answer makes them relevant (RLR-17).
- Establish what the prospect gets before asking value-heavy or personal
questions. Never open with an interrogation.
- Explain *why* you are asking when it helps the prospect answer honestly.
- Move toward the appropriate next step (book, nurture, gather-more, refer)
as soon as the evidence supports it.
- Preserve the prospect's dignity when they are not a fit.
- Do not make unsupported promises, give regulated-industry advice that has
not already been approved, or collect sensitive information you do not need.
Editable variables
[First Name] · [Business Name] · [Service] · [Location] · [Timeline] · [Responder] · [Appointment Link] · [Next Step]
1. Phone qualification opener
"Hi [First Name], this is [Responder] with [Business Name] — thanks for
reaching out. So I can point you in the right direction, can you tell me a
little about what you're looking to get help with?"
Establishes need first. Let them talk before narrowing.
2. SMS qualification sequence
Keep each message short; one question at a time.
1. "Hi [First Name], it's [Responder] at [Business Name]. Happy to help
with [Service] — what are you trying to get sorted?"
2. "Got it. Are you hoping to handle this soon, or still gathering info?"
3. "Perfect — I can line up the right next step. Want me to send a time to
talk? [Appointment Link]"
Never send a wall of questions in one text.
3. Chat qualification sequence
"Happy to help. Quick question so I route you correctly: what's the main thing
you're trying to solve today?"
*(after need)* "Thanks — and is this something you're looking to move on
soon, or planning ahead?"
*(after urgency)* "Great, I can set up the right next step for that."
4. Follow-up question transitions
Use these to move between categories without it feeling like a form:
"That helps — one more thing so I get you to the right person…"
"Makes sense. So I understand the timing…"
"Got it. Last quick thing and then I'll sort out next steps…"
5. Urgency / timeline questions
"When are you hoping to have this resolved or get started?"
"Is this something urgent, or are you planning ahead a bit?"
6. Service-fit questions
"Just so I make sure we're the right fit — is this about [Service], or
something a bit different?"
*(only where relevant)* "And are you located in / around [Location]?"
7. Decision-readiness questions
"Have you looked into this before, or is this the first time you're exploring
it?"
*(conditional, multi-stakeholder)* "Are you the right person to move this
forward, or is someone else involved in the decision?"
Ask the authority question only when multiple stakeholders are likely — not reflexively.
8. Value / context questions (where appropriate)
Only after fit and need are established, and only where the service is variable-scoped:
"To recommend the right option, it helps to know roughly the scope you have in
mind — is this a smaller [Service] need or something more involved?"
Do not push for budget or sensitive financial detail you do not need to decide the next step.
9. Appointment transition
"Based on what you've told me, the best next step is [Next Step]. I can get
you on [Responder]'s calendar — here's a link: [Appointment Link]. What time
works best?"
10. Nurture transition
"It sounds like the timing isn't quite right yet, which is totally fine. I'll
stay in touch with anything useful, and reach back out around [Timeline] — and
you can reach me any time before then."
11. Disqualification language (dignity preserved)
Use only when there is evidence of genuine non-fit — never for missing information.
"Thanks for explaining that. Honestly, [Business Name] isn't the best fit for
what you need — I don't want to waste your time. The better option for you
would be [referral / direction], and I'm glad to point you there."
Never imply the prospect did something wrong. A non-fit is about the match, not the person.
12. Escalation language
"This is important enough that I want to get you straight to [Responder], who
handles exactly this. Let me connect you now / have them reach you within
[Timeline] — can I confirm the best number?"
13. Incomplete-information follow-up
Use when a lead went quiet mid-qualification — this recovers INSUFFICIENT INFORMATION rather than disqualifying it.
"Hi [First Name], we started sorting out [Service] but I didn't want to assume
anything. Whenever you have a moment, just let me know [the one missing thing]
and I'll take it from there — no rush."
Attempt recovery on the defined cadence before any lead is closed as not-a-fit.
Guardrails (apply to every script)
- Disclosure where required: if automation/AI is sending on the business's
behalf, disclosure is required where the law or platform requires it.
- No unsupported promises: never promise outcomes, timelines, prices, or
results that have not been approved.
- No unapproved regulated advice: do not give legal, medical, financial, or
other regulated-industry advice that has not already been approved.
- Data minimization: only collect information reasonably necessary to
determine fit, decide the next action, route correctly, and book. Do not ask for sensitive information you do not need.
- Not a questionnaire: these are conversation aids, not a long form. Stop
asking once you have the evidence to decide the next step.
Verification chain
- What to measure: whether required categories are gathered in conversation
without excess questions, and whether responders use consistent language.
- How to interpret: long, form-like calls or missing categories mean the
scripts are being misused (over- or under-asking).
- Action that follows: coach to the required/conditional split; capture
evidence into the CRM for RLR-18 classification.
- Owner: intake/sales manager.
- How to implement: adopt scripts per channel, insert business variables,
brief responders, and enable conditional prompts in AI/chat.
- How to test: review 5-10 recorded/logged interactions for category
coverage, question count, and dignity on non-fit closes.
- When to remeasure: re-audit with RLR-16 at 14 and 30 days.
- How to know the leak improved: RLR-16 shows fuller records with steadier
responder consistency and no rise in questions-per-lead — better evidence, not more interrogation.
Existing-asset consolidation
These scripts reuse and improve ShiFt's prior qualification scripts and intake language (including the qualification note used in proposal templates). No competing public resource is created; those surfaces remain, and this is the canonical operational script set behind them.
Variables to replace
Keep the brackets when personalizing; replace the text inside.
[First Name][Business Name][Service][Location][Timeline][Responder][Appointment Link][Next Step][referral / direction][the one missing thing]
How to implement
Install the change exactly as the playbook describes; log it on the Repair Plan.
How to verify
Installing a workflow is implementation, not closure. QA the repair before you trust it.
Related in this link
Rather not do this part yourself?
You can repair your Revenue Chain yourself with this Kit — or bring in ShiFt at any point. You do not need to finish the DIY path first.
Done with you
Revenue Leak Scan
A ShiFt specialist runs the diagnosis with you and hands you a prioritized repair plan.
Get My Revenue Leak ScanDone for you
ShiFt RevenueOS
ShiFt installs and operates the full Revenue Chain system for you — ConvertOS included.
See RevenueOS