Stop Manually Screening Potential Clients. Seriously.
Your phone rings. Is it the perfect new client or someone asking for a practice area you haven’t touched in a decade? You pay a paralegal or an associate good money to find out. They spend ten, maybe fifteen minutes on the phone, only to discover the person has no case, can’t pay, or is a potential conflict. That’s ten minutes of billable time gone. Forever. Multiply that by five or ten junk inquiries a day, and you’re losing thousands of dollars a month on low-value screening. This isn’t a cost of doing business. It’s a process failure. The goal isn’t just to get more leads. It’s to get qualified, conflict-checked consultations booked directly on your calendar with almost no human intervention. This tutorial on building AI workflows from scratch shows you exactly how to build that system.
What Most Small Law Firms Get Wrong With Intake
The standard approach to client intake is broken. Most firms fall into one of three traps. The first is throwing people at the problem. You have a smart, capable paralegal spending a quarter of their day acting as a human voicemail filter. They could be drafting documents or preparing for trial, but instead, they’re politely telling someone for the tenth time that you don’t handle landlord-tenant disputes. It’s a massive waste of talent and money.
The second trap is buying expensive, all-in-one software. You see a demo for something like Clio Grow, which promises to solve your intake problems. It looks great on the surface. But then you get into it and realize you’re stuck with their rigid forms and inflexible logic. My big gripe with these systems is they are built for the average of all law firms, which means they aren’t a perfect fit for any single one. You can’t easily add a sophisticated AI check or a custom routing rule. You’re stuck in their ecosystem, paying a premium for features you’ll never use.
The third trap is the simplest and maybe the worst: the basic website contact form. A potential client fills it out, it sends an email to your inbox, and… that’s it. Now you have a new manual task. Someone has to read it, decide if it’s worth a response, copy-paste the information into your practice management software, and then maybe email them back a day later. By then, that high-intent lead has already called three other attorneys. You’ve lost them because your front-office automation is nonexistent.
A Step-by-Step Tutorial on Building AI Workflows From Scratch
You don’t need a computer science degree to build a better system. You just need to connect a few modern tools. This is a vertical AI stack you can build in an afternoon. We’re going to create a workflow that acts as a 24/7 front desk manager who never gets tired and makes perfect decisions based on your rules.
- The Front Door: A Smarter Web Form
Everything starts with the information you collect. Ditch your basic contact form and use a tool like Jotform or Typeform. The key is to ask specific, qualifying questions. Don’t just ask for a name and email. Ask about the type of legal issue, who the other parties are (for conflict checks), and for a brief summary of their situation. You can use conditional logic in the form itself to ask follow-up questions. For example, if they select “Family Law,” you can ask if it involves a divorce or a custody issue.
- The Engine: An Automation Platform
This is the central nervous system of your intake machine. The form submission needs to trigger a series of actions. We’ll use a platform called Make.com(formerly Integromat) for this. I prefer it over Zapier automations for this kind of work because its visual interface makes it easier to see the logic, and its pricing is much more reasonable for multi-step workflows. Make’s Pro plan is about $29 a month. It’s a no-brainer. The free plan is honestly a joke for any real business use. When a new form is submitted, Make will grab all the data and start the workflow.
- The Brain: AI-Powered Qualification
Here’s the core of the automation. Make will take the text from the form submission (the summary of their legal issue) and send it to an AI model like OpenAI’s GPT-4 via an API call. You’ll give the AI a very specific prompt. It’s not a conversation; it’s an instruction. Your prompt should look something like this: “You are a paralegal for a small law firm specializing in family law and estate planning. Analyze the following client inquiry. Determine if it fits our practice areas. Identify any names of other parties for a potential conflict check. Based on the text, classify the inquiry as ‘Qualified,’ ‘Unqualified,’ or ‘Conflict Check Needed.’ Return your answer in JSON format.”
- The Router: Sorting Good from Bad
The AI will send back a clean, simple response, like `{“status”: “Qualified”, “conflict_names”: [“Jane Doe”]}`. Now, back in Make, you use a simple router to split the workflow into different paths based on that status. It’s just an if/then statement. If the status is “Qualified,” it goes down Path A. If it’s “Unqualified,” it goes down Path B. If it’s “Conflict Check Needed,” it goes down Path C.
- Path A: Automatic Booking for Good Leads
For qualified leads, the workflow immediately sends a personalized email. It can pull the person’s name from the form and say, “Hi John, thank you for reaching out. Based on your information, it looks like we can help. Please use this link to book a 30-minute consultation directly with one of our attorneys.” The link goes to your Calendly or another scheduling tool. The client books a time, it’s automatically added to your calendar, and you’ve secured a qualified lead without lifting a finger.
- Path B: The Professional ‘No’ for Bad Leads
This is just as important. For unqualified leads, you send a different automated email. It should be polite and professional. “Hi Sarah, thank you for your inquiry. Unfortunately, your issue falls outside of our firm’s practice areas. We are unable to assist you, but we recommend contacting the [Your State] Bar Association’s referral service. We wish you the best.” This prevents you from looking unresponsive and provides a helpful next step.
- Path C: Flagging for Human Review
If the AI flags a potential conflict, you don’t automate a response. Instead, the workflow creates a task in your practice management software (like Clio, MyCase, or PracticePanther) and assigns it to your paralegal. The task should contain all the form information and the names flagged for the conflict check. This way, a human makes the final, critical decision while the machine does all the initial legwork.
