Lead Qualification Over iMessage
The short answer
Ask two questions over iMessage, get answers in minutes, route before reps open calendars. Forms scare leads. Blue bubbles read 98%, 90% in three minutes, 2-3x email. Answers branch workflows; reps see qualified leads.
6 use cases in this category
Trigger
Event in your CRM
Under 60s
Send iMessage
Result
Reply in the thread
Key takeaways
- Forms ask all questions at once, from a stranger, with nothing back.
- A bad call costs more than 30 minutes: prep, notes, CRM cleanup, context switch.
- Ask only what changes where the lead goes next.
- Two clocks run inside it. Fast (questions one and two): event-driven, firing via API in seconds.
- Qualification messages work like one person typing to another.
- Map your routes: rep call, self-serve, lower tier, nurture.
Where iMessage runs in the funnel
Why texts get answers forms don't
Forms ask all questions at once, from a stranger, with nothing back. Every field screens bad fit and busy buyers. Cold email: 0.45% reply (Belkins, 7.5M, 2025), 27.7% opens. Qualification questions mostly don't get read.
- iMessage: 98% open, 90% read in three minutes, under 3% spam (vs 85%). Reply runs 2-3x cold email. Answers come as sentences you route on, not dropdowns. A text reads like a person, so it tends real.
The cost of an unqualified call
A bad call costs more than 30 minutes: prep, notes, CRM cleanup, context switch. A wrong-fit call runs an hour. Salesforce found the rep spends 28% of the week selling, so that hour drains the smallest bucket.
- On a three-rep team with 200 inbound leads a month and 40% booking (80 calls), if 55% are wrong fit, that's 44 hours a month, over a full working week of one rep.
- Slow qualification costs the lead. Lead Response Management study (Oldroyd, InsideSales.com, 2007, 15,000+ leads) found odds of qualifying drop 21x when response time slides from five to thirty minutes.
Those are our assumptions. The Blue Funnel Map runs the same arithmetic on the funnel you actually have, and you keep the map either way.
Run these numbers on your funnelThe two-question play mechanics
Ask only what changes where the lead goes next. Everything else waits for the call. Timing between steps does as much work as wording.
- Trigger and check. A form submit, ad lead, or list import fires the sequence from your CRM, and iMessage availability checking confirms the number is reachable before anything sends.
- Question one, on the trigger. One message, one question, aimed at the hardest gate your offer has. For most B2B offers that's scale or current setup, almost never budget.
- Wait for the answer. Firing both questions together gets you one reply and loses the other. Per-message delivery states and read receipts tell you whether the question landed and whether it was read.
- Question two, on the reply. Fires only when answer one passes, triggered by the inbound reply rather than a timer, and written as a follow-up in the same thread so it reads like a conversation, not page two of a form.
- Route on the answer. A pass drops a calendar link into the thread or hands a rep a live conversation. A fail sends a real alternative: self-serve, a lower tier, a resource, a partner. Anything ambiguous goes to a human queue.
- Two nudges, then stop. Silence gets one short message later the same day and one the next, then the contact moves to nurture.
The qualification cadence
Two clocks run inside it. Fast (questions one and two): event-driven, firing via API in seconds. Slow (nudges and exit): sequence steps with delays from 15 minutes to 90 days inside the recipient's local window.
Availability check
- Timing
- On the trigger
- What sends
- Nothing
- What you route on
- Reachable or not
Question one
- Timing
- Seconds after the trigger
- What sends
- One question, one line
- What you route on
- Reply or silence
Question two
- Timing
- On the reply to question one
- What sends
- One follow-up question
- What you route on
- Pass, fail, or unclear
Rep takeover
- Timing
- Any point after a reply
- What sends
- Live, same thread
- What you route on
- Rep judgment
Routing
- Timing
- On the second answer
- What sends
- Calendar link, alternative, or queue
- What you route on
- Qualified or not
Nudge one
- Timing
- 3 hours later, same day
- What sends
- Short re-ask
- What you route on
- Reply or silence
Nudge two
- Timing
- 24 hours later
- What sends
- Final short message
- What you route on
- Reply or silence
Exit to nurture
- Timing
- 48 hours later
- What sends
- Nothing further here
- What you route on
- Long-cycle sequence
What to say and what to avoid
What to say and what to avoid
Qualification messages work like one person typing to another. Short, lowercase, one question per message, no signature. A qualification question earns its slot when a different answer sends the lead somewhere different.
- First touch, question one: "hey marcus, it's dana. saw you grabbed the pricing sheet this morning. quick one before I take up any of your time, how many reps are you running outbound today?"
- Question two, after a passing answer: "got it, 12 is a real team. are they sending from a CRM already or is it manual right now?"
- The fail route, which earns more than people expect: "makes sense. at two reps you don't need a call with us, our self-serve plan does everything you'd want. want the link?"
- Never ask budget in the first message. People guess low when a stranger asks, and the number they type becomes the number you're stuck with for the rest of the deal.
- Never ask for anything already in your record. Company size, industry, the field they filled in ten minutes ago. Asking for data you hold tells them nobody read their submission.
- Never open discovery over text. "What are your biggest challenges right now?" is a call question. In a thread it gets skipped, or it gets a paragraph your workflow can't branch on.
- Never ask yes or no when you need a range. "Are you doing outbound?" tells you nothing. "How many reps" tells you tier, urgency, and who owns the thread.
Setting up qualification in your CRM
Setting up qualification in your CRM
Map your routes: rep call, self-serve, lower tier, nurture. Work backwards to the smallest separator question. GoHighLevel is native on form, tag, or stage change. Replies come through webhooks.
- Write replies into a custom field and branch. Per-message delivery states and read receipts separate leads who never saw the question from those who read it and chose silence.
- Other stacks connect via REST API and webhooks (HubSpot, Salesforce, Pipedrive, Close). Sequences run 1-12 steps, 15-minute to 90-day delays. STOP and plain-language opt-outs enforced. Activation is white-glove.
Measuring whether it worked
Measuring whether it worked
Key metric: rep hours per closed deal. Everything else is diagnostic. Baseline two weeks before switching; qualification changes the denominator. Watch answer rate against route accuracy ignoring soft-question inflation.
- Answer rate on question one. Delivered first questions that got a reply. The health metric for the question itself.
- Median time to first answer. Should sit in minutes. Hours means your send window is set wrong.
- Route accuracy. After each call the rep marks whether the lead was correctly qualified. The most important number here and the one most teams skip.
- Calls per closed deal. Should fall. If it holds steady, your questions aren't separating anything.
- Revenue from the fail route. Self-serve and lower-tier signups from leads who never reached a rep. Count it, or the fail route reads as pure loss.
- Opt-out rate. Should stay flat against your other campaigns. A rise means the question reads like a screen instead of a person.
Frequently asked questions
How many qualification questions should I ask over text?
Two, in nearly every case. One data point usually isn't enough to route on; three feels like an intake form, adding chances for the thread to go quiet. Sent one at a time with a real answer in between, two questions separate most B2B leads. Anything else belongs on the call.
Won't prospects feel like they're being screened?
No, if the question frames around their time, not yours. "Quick one before I take up any of your time" does most of that work. Buyers resent forms because they give nothing back and never explain. A text ending with "you don't need a call for this, here's the link" reads as respect for their afternoon.
Does the lead need an iPhone for this to work?
No. iMessage availability checking runs before the send. Numbers on iMessage get the blue bubble, read receipts and tapbacks, and everyone else falls back to RCS, then SMS. The thread works either way, you just lose the read receipt signal on the fallbacks, so silence is harder to diagnose there.
Can a rep take over mid-qualification?
Yes, they should on anything ambiguous. The sequence handles the two questions and nudges; a rep steps into the same thread the moment a reply needs judgment. Same conversation, same number, no handoff the prospect notices. Media, voice memos, and group messaging pull in second decision makers.
What happens to the leads who don't qualify?
Unqualified leads get a route, never silence. Send them to self-serve, a lower tier, a partner, or content that genuinely helps, then nurture with week-long delays. Companies grow. The two-rep shop that failed your gate in March is a nine-rep shop by December, and the thread is still there.
Do qualification texts need A2P registration?
No A2P registration required. A2P 10DLC governs US carrier SMS; iMessage is not carrier SMS. Registration distinction, not exemption: TCPA governs all business texting. Consent rules took effect 11 April 2025; revoke-all extends to 31 January 2027. STOP and plain-language opt-outs are automatic.
Can an AI agent handle the qualification replies?
Yes, via webhooks and REST API. Every inbound reply posts to your endpoint so an agent reads it, writes to record, and picks the route with no human loop. Keep a person on the ambiguous branch: machines handle "12 reps" perfectly but "depends how you count contractors" badly. That's usually the more interesting lead.
What does a qualification line cost?
$249/line/month or $1,949/year ($162.50/month). Unlimited iMessages (50 opted-in / 30 cold new conversations per line per day max, conversation not blast). No per-message fees; thousands of threads don't change the bill. One line per pipeline. $449 activation waived on annual. Mobile-validated B2B leads ($0.03 per contact) bill monthly.
Stop paying rep hours to find out who wasn't a fit
Two questions, sent in a blue bubble seconds after the lead arrives, route wrong-fit prospects before anyone opens a calendar. $249 per line per month, unlimited iMessages, no A2P registration required, white-glove activation waived on annual billing. Book a walkthrough and we'll map your two questions to the pipeline you already run.