I spent nine years listening to thousands of intake calls. I’ve seen law firms blow their entire marketing budget on high-quality traffic, only to let those leads vanish into the black hole of a voicemail inbox at 8:00 p.m. on a Tuesday. I always ask my clients this: Who answers at 2:17 a.m. on a holiday? If your answer is "my voicemail," you aren't running a law firm; you’re running a charity for your competitors.
But when you finally decide to outsource that coverage, a massive red flag appears: Conflict checks. Everyone wants to know if their virtual receptionist can run a conflicts check, but nobody wants to talk about the mess that happens when you don't define what "intake" actually means. Let’s cut through the fluff and look at the reality of legal intake compliance.
The Cost of "We'll Get Back To You"
In the legal world, speed-to-lead is not just a buzzword; it is the currency of conversion. If a lead hits your website and gets a busy signal or a generic "please leave a message" prompt, they are already on the next tab, calling your competitor. Voicemail abandonment is real, and it is costing you tens of thousands of dollars in annual billables.
You need 24/7 coverage, but hiring a full-time staff member to work graveyard shifts and weekends is a payroll nightmare. Answering services are the logical solution, provided you actually understand what they can—and cannot—do regarding your firm's integrity.
Can Answering Services Perform Conflict Checks?
The short answer is: Yes, but it depends on your definition of "check."
Most answering services are not legal professionals. They cannot provide legal advice, and they cannot interpret the nuances of your state's specific bar rules regarding conflicts. However, they can act as a data-gathering gatekeeper. The effectiveness of this depends entirely on your tech stack and your protocols.
The Landscape of Providers
- Smith.ai conflict checks: Smith.ai is widely recognized for its robust integration capabilities. They allow for customized intake workflows that can ping your CRM or Case Management Software (CMS) to see if a name already exists in your system. Ruby Receptionists: Known for the "human touch," Ruby is excellent at empathy-driven intake. They are fantastic at collecting the necessary information to perform a conflict check later, though they are less focused on the "hard" data-entry side of conflicts than some of the more automation-heavy players. Veza Reception: Positioned specifically for law firms, Veza understands the legal context better than generic answering services. Their focus is often on the intake quality itself, ensuring that when the information reaches you, it’s actually useful.
The Intake Reality: Integrating with Clio and MyCase
If you aren't integrating your answering service with your CMS—like Clio or MyCase—you are flying blind. When an answering service performs "optional conflict checks," they are usually doing one of three things:
From my experience auditing intake workflows, Method 3 is almost always the safest and most effective. You should be the one identifying the legal conflict, not a $15-an-hour receptionist. Your job is to set the fields, define the eligibility criteria, and ensure the service knows exactly what lawfuel.com to ask to screen out "un-winnable" or low-value cases.
Comparison of Intake Capabilities
Feature Generic Service Legal-Focused Service (e.g., Smith.ai) 24/7 Availability Yes Yes Conflict Check Integration Rarely Yes (via API/Webhooks) Intake Compliance Basic High (Customized scripts) CMS Sync (Clio/MyCase) Limited SeamlessThe "Intake Questions That Kill" List
I keep a running list of questions that cause callers to hang up. If your answering service is asking these during the first 60 seconds, you are losing business:
- "What is your Social Security number?" (Ask this only after they are hooked). "Are you currently represented by another attorney?" (Save this for the conflict check phase). "What is your budget for legal fees?" (This sounds like a sales call, not a legal consultation).
A good answering service should focus on eligibility screening rather than interrogation. The goal is to establish rapport and collect enough information to perform a conflict check while reassuring the caller that someone competent will call them back.
Why "We Do Intake" is a Dangerous Promise
When a vendor says "we do intake," I roll my eyes. What does that mean? Does it mean they take a message? Does it mean they qualify the lead based on your specific practice area? Does it mean they trigger a conflict check? Does it mean they sync the lead into Clio as a contact?
Vague promises are the enemy of your bottom line. You must define:
- The Field: What data are they capturing? (Name, opponent, case type, injury location). The Workflow: What happens when a potential conflict is identified? Do they alert you? Do they finish the intake? The Outcome: Is the goal to book an appointment directly on your calendar, or to send you a lead for your review?
Final Thoughts: Integrity Matters
If you don't have a system for 24/7 intake, you are intentionally choosing to be less profitable than your competitors. However, do not fall for the myth that an answering service will handle your ethics for you. Use them to gather the data. Use your MyCase or Clio integration to run the checks. Keep your intake script tight, professional, and compliant.
And remember: when a potential client calls at 2:17 a.m. on a holiday, they are in a state of crisis. If you have a professional, live person answering that call, performing an efficient intake, and assuring them that a conflict check will be performed promptly, you haven't just captured a lead—you’ve won a client.