How to Automate Case Qualification Scoring with AI

Not every inquiry is worth pursuing, and the firms that grow fastest are disciplined about which ones they take on. The problem is that qualification quality usually depends on who happens to pick up the phone. A new coordinator at 9pm and a senior one at 9am reach different conclusions about the same matter, strong opportunities get under-prioritized, and decline decisions are rarely documented.

This guide builds an AI case qualification scoring workflow in n8n. It applies your firm's own criteria to every inquiry consistently, grades each one with a written reason, and ranks them so attention flows to the strongest first. This is the practical build behind Play 2 (Lead Qualification and Booking).

Expected setup time: 3 to 5 hours, most of it spent writing and refining the rubric rather than wiring nodes. Expected ROI: firms that score every inquiry stop spreading attention evenly across the queue and concentrate it on the matters most likely to convert and be worth converting, which lifts both signing rate and margin without adding headcount.

Before you start, confirm you have:

• A running n8n instance
• An AI provider API APIApplication Programming Interface. The connection point that lets two pieces of software exchange data. How n8n talks to your CRM. key (OpenAI or Anthropic)
• CRM CRMCustomer Relationship Management software. The system of record for contacts, deals, and client communication. Examples: HubSpot, Salesforce, Pipedrive. or case-system access (HubSpot, Lawmatics, Filevine, or Litify)
• An intake source that produces new lead records (a form, a call tracking tool, or an existing intake triage workflow)
• Your real signing criteria written down, ideally with a few past examples of clear-yes and clear-no matters

If this is your first time using the AI node, read how to use the AI/LLM node in n8n with OpenAI. If you have not yet built intake capture, build client intake triage first and add scoring inside it.

1. Encode your qualification criteria into a rubric

This is the most important step and the one most firms skip. Write down, in plain language, how your firm actually decides to take on work. Group it into criteria, for example:

• Fit: Is this the kind of work we do well?
• Value: Is the engagement size or potential worth our capacity?
• Urgency and timing: Is there a deadline or window that affects priority?
• Disqualifiers: Conflicts, scope we decline, or red flags that mean an automatic no.

Save this as a single text block. It becomes the rubric the model scores against, and keeping it in one place is what makes the scoring identical on every run.

2. Trigger scoring on every new inquiry

Start a workflow that fires on each new lead. If you already run intake triage, this is the same trigger; if not, add a Webhook WebhookA way for one app to send real-time data to another the instant an event happens. Example: DocuSign pings n8n the moment a contract is signed. node fed by your form and call tracking, or a CRM trigger node that fires when a new contact is created. The point is that scoring happens automatically, not when someone remembers.

3. Score the inquiry and explain the grade

Add an OpenAI or Anthropic node. Build the prompt from your rubric:

You are a qualification analyst for our firm. Using the rubric below, grade the inquiry from A (clear pursue) to D (clear decline). Return JSON with grade, rationale (one or two sentences tied to the specific criteria), confidence (high, medium, or low), and disqualifiers (a list, empty if none). Do not invent facts. Rubric: {{ rubric }}. Inquiry: {{ $json.rawMessage }}

Set temperature to around 0.2 and enable JSON output. The written rationale is what turns a number into an auditable recommendation.

4. Validate the score before trusting it

Add an IF node. If confidence is low, or the JSON is malformed, or disqualifiers is non-empty, route the inquiry to a human review queue rather than acting on the grade automatically. This keeps the system honest: it acts confidently where it is confident and asks for a person where it is not.

5. Surface the score where decisions happen

On the validated path, add your CRM node to write the grade, rationale, confidence, and any disqualifiers to the lead record. Then add a step that appends the lead to a daily pipeline summary: a Slack message, an email digest, or a row in a Google Sheet sorted by grade. Now the team triages by case strength instead of by arrival time.

6. Review and tune the rubric on a schedule

Add a separate scheduled workflow (a Cron node, monthly) that pulls the last month of scored leads and their real outcomes and reports where the grade and the result diverged. Use that report to adjust the rubric so it keeps tracking how the firm actually signs work. A rubric that is never reviewed slowly drifts out of date.

• n8n runs the scoring pipeline. See n8n examples and best practices.
• OpenAI or Anthropic applies the rubric to each inquiry. See the AI/LLM node guide.
• HubSpot, Lawmatics, Filevine, or Litify stores the grade against the lead or matter. See how to connect HubSpot to n8n.
• Google Sheets or Slack for the daily pipeline summary, if you do not want it living only in the CRM.

• Scoring without a written rubric. If the criteria live in people's heads, the AI cannot apply them consistently. Write the rubric first; the rest is wiring.
• Treating the grade as a decision. The score prioritizes and prepares. A person still signs. Keep the human in the loop, especially for high-value matters.
• High temperature. A high temperature makes the model improvise and the grades wobble. Keep it low so the same inquiry scores the same way twice.
• Never validating low-confidence scores. Acting automatically on a shaky grade erodes trust fast. Route uncertainty to a person.
• Setting the rubric and forgetting it. Markets, services, and the firm's appetite change. Without the monthly review, the rubric quietly stops matching reality.

This is the industry-agnostic build. For the vertical-specific version with named systems and a worked example rubric, see AI for Case Qualification Scoring for Personal Injury Law Firms. The same pattern fits accounting and advisory firms grading engagements, agencies scoring inbound projects, and consulting firms qualifying opportunities. Replace the criteria and the system of record; the workflow shape holds.

For the full strategy this build sits inside, see Play 2: Lead Qualification and Booking.