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.

Difficulty

Medium

Revenue impact

High

Operational impact

Medium

Risk level

Low

When it runs

A website consultation form, calendar request, email inquiry, or paid consultation request enters the intake queue.

Evidence in

Contact, company, role, and source pageProblem, desired outcome, timeline, and urgencyBudget range, decision-maker status, and service fitConsent, communication preference, and booking statusExisting CRM record and prior interactionsRouting rules and disqualification criteria

What AI prepares

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

Decision rules

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.

Human approval point

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

What stays human

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.

Quality and stop gates

Confirm the trigger is specific to consultation request screening.
Verify request details.
Verify problem statement.
Confirm owner, deadline, and system-of-record update.
Pause on missing, contradictory, stale, or out-of-policy data.

How it is measured

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

Systems involved

Website formCalendarCRMEmailRouting rules

Workflow Dataset Record

Deployment evidence and duplicate boundary

This section is generated from the enriched workflow dataset. It is designed for pilot planning, not as validated outcome evidence.

Buyer Problem

Consultation Request Screening is weak when lead qualification teams rely on scattered notes, incomplete fields, and informal judgment instead of a source-backed operating record. The problem is not a missing AI draft; it is the missing owner, evidence, exception status, and review path that decide whether the work can safely move forward.

Economic Logic

The value of Consultation Request Screening comes from reducing avoidable rework, misrouting, stalled decisions, and unsupported customer or revenue actions. The pilot should prove that required evidence is captured earlier, exceptions are reviewed by Sales development manager, and the team can measure readiness without claiming validated outcome lift.

Baseline Metric

consultation_request_screening_review_ready_rate

Share of consultation request screening records with source evidence, required business fields, named owner, human review status, exception outcome, and measurable follow-up result before the workflow is expanded.

Source system: CRM record store, workflow owner notes, pilot evidence log, exception review queue, HubSpot, risk review notes

Minimum Viable Pilot

Duration: 30 to 60 days
Sample: First 100 consultation request screening records, or all records from one lead qualification segment over 45 days
Owner: Sales development manager
Threshold: At least 90% of sampled consultation request screening records include source evidence, owner decision, and exception status; 100% of high-impact or customer-visible exceptions receive human review before action.

Unique Workflow Test

Audit 100 consultation request screening records for source link, required fields, timestamp, owner, exception status, review decision, downstream action, and result. The test passes only when the workflow can separate approved action from blocked, low-confidence, or not-ready records.

Duplicate Guard

Keep consultation request screening separate from adjacent lead qualification workflows by requiring consultation_request_screening_review_ready_rate, the Sales development manager review point, and the source boundary hubspot-sales-automation, nist-ai-rmf. Adjacent pages may share data, but this record owns the sampled decision path and exception outcome.

Not Ready If

Consultation Request Screening does not have stable source records, owner fields, or status fields to sample.
No accountable lead qualification owner can approve exceptions or customer-visible actions.
The team cannot track timestamp, source, owner, exception, and outcome fields across the pilot sample.

Claim level: Pilot-shaped. Sources support workflow mechanics and pilot design unless field evidence is attached.

HubSpot Sales Automation Guide

Sales automation should start with repetitive revenue work, clean CRM data, routing, sequences, baseline metrics, and regular audit.

NIST AI Risk Management Framework

AI workflows should include risk mapping, measurement, governance, and accountable human oversight.

Keep moving

Where this workflow connects next

A useful AI build rarely lives on one page. Check the surrounding workflow, the decision rule, and the deployment path before you commit budget.

Workflow group

Lead Qualification

Compare the nearby workflows that usually break before or after this one.

Open

Sales pillar

AI Sales Workflow Deployment

See how sales teams can use AI for pipeline briefs, meeting prep, follow-up, account plans, and stalled deals.

Open

Decision tool

First workflow selection rubric

Score this against other revenue workflows before you commit build time.

Open

Industry fit

Browse industries

See how this workflow changes by revenue model, buyer urgency, delivery risk, and customer handoff.

Open

Service path

AI Workflow Implementation

Build the first version around a sales or revenue workflow that already has demand.

Open

Sales review

Pressure-test this sales workflow

Bring the sales motion, the source evidence, and the number this workflow should move.

Open

Adjacent workflows

Website Demo Request Qualification Inbound Lead Qualification Priority Lead Routing Sales Meeting Preparation

TL;DR

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.

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?

Trigger: A website consultation form, calendar request, email inquiry, or paid consultation request enters the intake queue.
Inputs collected: capture source record, contact/company context, fit evidence, authority, urgency, duplicate status, consent, and routing rules.
AI/system action: summarize qualification evidence, classify fit, identify missing context, suggest route, and flag review issues.
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.
Output generated: create the approved owner task, qualification note, follow-up route, decline path, or discovery question set.
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.

Related Workflow Group

AI Workflows for Lead Qualification

Compare this workflow against nearby operating problems before choosing the first build. The group shows what usually breaks together, what evidence is needed, and where review still matters.

View Workflow Group

Related Workflows

Inbound Lead Qualification Website Demo Request Qualification B2B Lead Scoring

Speed-to-lead AI workflow

A field report on faster lead response without losing evidence, routing, consent, or owner review.

Read Report