Function: Lead qualification

Consultation Request Screening

Deployment Brief

Start with a short screen for problem, urgency, company, role, budget range, decision status, and missing context. Route exceptions to an owner.

Related Field Report

Speed-to-lead AI workflow: A field report on faster lead response without losing evidence, routing, consent, or owner review.

Quick Answer

A consultation request screening workflow turns an inbound consultation request into a fit summary before someone spends time on a call. AI can summarize need, urgency, budget range, authority, and missing context, but a person should review disqualification, sensitive issues, strategic accounts, and custom requests.

TL;DR

What is consultation request screening?

Consultation Request Screening is a lead qualification workflow that decides whether an inquiry is ready for sales time, needs more context, should be routed elsewhere, or should be declined with care. The useful version is evidence-based, not just a score.

Who is this workflow for?

This workflow is for service businesses, agencies, consultants, SaaS companies, local operators, and partner teams where bad-fit calls waste time and good-fit inquiries need fast owner attention.

What breaks in the manual process?

Manual qualification often confuses interest with readiness. Someone fills out a form, sounds urgent, or comes through a partner, and the team assumes the lead is worth immediate sales time. The better process checks fit, authority, urgency, context, ownership, and risk before routing.

How does the AI-enabled process work?

AI prepares a qualification summary from the source record, enrichment, prior history, and routing rules. It can suggest fit tier, owner, missing questions, and next path. A person still reviews disqualification, strategic routing, pricing, partner attribution, sensitive issues, and any customer-visible promise.

What does this look like in practice?

Example scenario: A founder requests a consultation and says they need help with AI deployment but gives no budget or timeline. The workflow checks role, company, source page, need, urgency, prior activity, and missing fields. It prepares a fit summary, asks one clarifying question about business impact, and routes the request for owner review because the company looks like a strong fit.

What decision rules should govern this workflow?

Screen for fit, urgency, authority, and service match before booking high-value consultation time.
Ask for missing context without making the form feel like a full discovery call.
Route sensitive, strategic, or ambiguous requests to a person.
Do not auto-decline when fit evidence is incomplete but the account looks valuable.
Do not promise pricing, timing, or outcomes before review.

What are the implementation steps?

1. Trigger: A website consultation form, calendar request, email inquiry, or paid consultation request enters the intake queue. 2. Inputs collected: capture source record, contact/company context, fit evidence, authority, urgency, duplicate status, consent, and routing rules. 3. AI/system action: summarize qualification evidence, classify fit, identify missing context, suggest route, and flag review issues. 4. Human review point: A sales or service owner reviews disqualification, sensitive requests, strategic accounts, low-fit but high-context inquiries, budget exceptions, and any rejection message. 5. Output generated: create the approved owner task, qualification note, follow-up route, decline path, or discovery question set. 6. Follow-up or next action: assign owner, log the decision, ask missing questions, and measure whether qualification improved sales time quality.

Required inputs

Contact, company, role, and source page
Problem, desired outcome, timeline, and urgency
Budget range, decision-maker status, and service fit
Consent, communication preference, and booking status
Existing CRM record and prior interactions
Routing rules and disqualification criteria

Expected outputs

Consultation fit summary
Suggested route, owner, or nurture path
Missing-context question
Review flag for exceptions or sensitive requests
Measurement log for accepted, declined, and no-show requests

Human review point

A sales or service owner reviews disqualification, sensitive requests, strategic accounts, low-fit but high-context inquiries, budget exceptions, and any rejection message.

Risks and stop rules

Booking calls with tire-kickers
Blocking good prospects with too much friction
Declining a strategic account too quickly
Letting AI send a rejection that feels cold or wrong
Missing sensitive details that require careful handling

Stop the workflow when fit evidence is missing, authority is unclear, consent is incomplete, duplicate ownership conflicts, the inquiry is strategic or sensitive, or the route would imply pricing, scope, procurement, partner, or customer-facing commitments.

Best first version

Start with a short screen for problem, urgency, company, role, budget range, decision status, and missing context. Route exceptions to an owner.

Advanced version

The advanced version connects CRM history, enrichment, routing, source attribution, owner capacity, and outcome tracking. It can suggest more precise fit tiers and next questions, but it still needs review for disqualification, strategic accounts, partner attribution, pricing, and custom commitments.

Related workflows

Measurement plan

Consultation requests accepted
Requests declined after review
Missing-context rate
No-show rate
Wrong-route corrections
Consultation-to-opportunity conversion

What not to automate

Do not auto-reject unusual but potentially valuable requests.
Do not make price, scope, or outcome promises.
Do not classify sensitive requests without human review.
Do not let form fields replace actual discovery.

FAQ

What is consultation request screening?

It reviews an inbound consultation request for fit, urgency, authority, budget range, missing context, and the right next step.

What should AI prepare for a consultation request?

AI can prepare a fit summary, urgency note, missing-context question, suggested owner, route, and review flag.

What should stay under human review?

Disqualification, sensitive issues, strategic accounts, budget exceptions, custom requests, and rejection messages should stay under review.

What is the simplest first version?

Start with a short form plus fit summary, missing-field flag, suggested route, and owner review for exceptions.

How should consultation screening be measured?

Track accepted requests, declined requests, no-shows, missing context, wrong routes, and consultation-to-opportunity conversion.