How to run a conflict check during a live intake call

A real-time conflict check is the practice of screening a caller — and every person and company connected to their matter — against your firm's existing clients and known adverse parties during the intake call itself, before the caller describes the facts of their case. It is the same conflict-of-interest search most firms already run, moved to the one moment it actually protects you: while the prospective client is still on the line and has not yet told you anything that can disqualify you.

The difference from the status quo is timing, and timing is the whole point. A conflict caught the next morning is a routine clearance task. A conflict caught after the consultation is wasted attorney time. A conflict caught after the engagement letter is signed is an ethics problem — the kind that ends in a motion to disqualify, a returned fee, and an awkward call to the client you now have to drop.

Why most firms check conflicts later, not live

Here is the honest status quo at most firms. The caller's name gets typed into a CRM or onto a legal pad during the call. The actual conflict search happens afterward — when the intake coordinator gets to it, when the file lands on a paralegal's desk, or in a batch the next morning. The consult, meanwhile, is already booked. Sometimes it has already happened.

That gap is survivable when callers wait around. They don't. In the 2026 ClaireAI legal intake benchmark, firms that responded within five minutes converted prospective clients at roughly four times the rate of firms that called back the next business day. High-intent callers — the injured, the arrested, the served — sign with whoever answers first. By the time an overnight conflict check clears or flags them, they are someone else's client, or they have already told your attorney things you now wish they hadn't.

What the ethics rules actually expect

The compliance angle is where 'we'll check later' stops being merely inefficient. Under ABA Model Rule 1.18 (Duties to a Prospective Client), the duty attaches the moment a person 'consults with a lawyer about the possibility of forming a client-lawyer relationship.' From that point, Rule 1.18(c) bars the firm from representing someone with materially adverse interests in the same or a substantially related matter if the prospective client shared information that 'could be significantly harmful to that person in the matter.' You do not have to sign the caller to be disqualified by them.

The Rule 1.18 trap.A stranger calls, describes their divorce or their arrest in detail, and hangs up without retaining you. Two weeks later the opposing party walks in. If the first caller told you something that could be significantly harmful to them in that matter, your firm may be barred from the second representation — for a client you never signed. The conflict check that would have caught it had to run before the first caller started talking, not after.

What counts as a conflict — and why a CRM name-match isn't enough

The easy case is a direct party match: the caller is already your client, or is already on the other side of a matter you are handling. A name search in your case-management system catches these, and they are the conflicts everyone pictures when they say 'we run conflict checks.'

The conflicts that actually disqualify firms are the ones a single name field never sees, because the person creating the conflict is not the caller. A name lookup on the caller alone clears the call and hides the problem.

This is also where ABA Model Rule 1.7 (Conflict of Interest: Current Clients) does its work. A 'concurrent conflict of interest' exists when representing one client 'will be directly adverse to another client,' or when there is a 'significant risk' that the representation 'will be materially limited' by the firm's responsibilities to someone else. 'Someone else' is exactly the co-defendant, the subsidiary, or the opposing spouse that a caller-name search never surfaced.

Why criminal defense is the hardest version

Every practice area has a relationship graph; criminal defense has the densest one, under the most time pressure, with the least cooperative information. A single arrest can produce several co-defendants whose interests diverge the instant one of them considers cooperating. The caller frequently has only a partial name for a co-defendant ('they booked my cousin Ray too'), a street name, or no name at all. And callers from a detention facility are often guarded about who else was involved — sometimes deliberately. Representing two co-defendants is one of the most common ways a firm walks into a disqualifying conflict, and it almost never shows up in a search of the caller's name alone. See how this plays out in ClaireAI for criminal defense intake.

How to run a conflict check during a live intake call, step by step

A real-time conflict check is four moves, in order. The goal is to clear or flag the matter before the caller narrates the facts — and to do it without making the call feel like an interrogation.

1. Capture the right identifiers first — not just the caller. Before the story, get the names that define the matter: the caller, the other side, and anyone connected. Full name plus at least one disambiguator (date of birth, employer, or address), because adverse parties share common names. Ask for aliases and nicknames explicitly. The legal intake question bank has practice-area question sets for exactly this.
2. Screen against the full relationship graph, not one name field. Run every captured name — caller and non-caller — against current clients, former clients, and known adverse parties. Match fuzzily: nicknames, maiden names, business d/b/a names, and parent/subsidiary relationships. A search that only checks the caller's exact name is not a conflict check; it's a duplicate-contact check.
3. When information is partial, flag and hold — never clear. A first name, a nickname, or 'I think his last name starts with M' is not a clearance. Record the partial identifier, mark the matter conflict-pending, and route it for attorney review before any consult is confirmed. The fail-safe direction is always to hold, not to wave through.
4. If it's a true conflict, decline gracefully — on the call. Don't book a consult you will have to cancel. Politely tell the caller your firm isn't able to take the matter, offer a neutral referral (your local bar's lawyer-referral service is a safe one), and end the call without taking facts or giving legal advice.

What to do when you only have a first name or a nickname

Partial information is the normal case, not the exception, and the worst response is to treat 'no exact match' as 'no conflict.' Capture whatever the caller can give — first name, approximate spelling, the relationship to the caller, the jurisdiction, the rough date. Mark the matter conflict-pending and escalate to the attorney or conflicts staff before the consult. A held matter costs you a few minutes. A missed conflict costs you the matter, the fee, and possibly a bar complaint.

The graceful decline, without giving legal advice

Turning someone away on the call is a skill, and it has a script. Be warm, be brief, and do not explain the conflict. Something like: 'I'm sorry — it turns out our firm isn't able to represent you on this one. I don't want to hold you up, so let me point you to the county bar's lawyer-referral line, which can match you with someone today.' Then stop. You are not their lawyer, and the call should not become a mini-consultation.

Never tell the caller who the conflict is.Saying 'we already represent the other driver' confirms that you represent the other driver — which is itself confidential. Decline without naming the reason or the party. 'We're not able to take this matter' is complete and correct. Anything more can breach the duty you owe the existing client.

What to document so the check holds up later

A conflict check that isn't recorded didn't happen, as far as a later disqualification motion or bar inquiry is concerned. The point of documentation is to show that screening occurred, when it occurred, and on what information — so a reviewing attorney, or a court, can see the firm acted reasonably.

At a minimum, capture for every intake:

• Timestamp. When the screen ran, relative to the call and to any consult.
• Every name screened. Caller and all connected parties — not just the person who was retained or declined.
• Sources checked. Which systems the names ran against: case management, former-client archive, adverse-party list.
• Result and disposition. Clear, flagged, or conflict-pending — and what happened next (booked, held, declined, referred).
• Who cleared it. The person or system that made the call, and the attorney who reviewed any flag.

Then structure the result so the reviewing attorney sees the flag before the consult, not after. A conflict note buried in a CRM field that no one opens until the matter is already open is documentation in name only. The flag has to travel to the front of the file — surfaced on the intake summary the attorney reads before they walk into the room.

How an AI receptionist handles this.Conflict screening is a good fit for automation precisely because it is mechanical and time-sensitive. ClaireAI runs a Rule 1.18 conflict pre-screen against the firm's existing client database during the call, before substantive facts are collected, captures every connected party the caller names, fails safe to attorney escalation on any partial match, and writes a timestamped record to the matter. The flag reaches the attorney on the intake summary — before the consult, not after. See ClaireAI for legal intake.

A conflict-check protocol you can adopt this week

Copy this into your intake script and your training docs. It works the same whether a human or an AI receptionist runs the front door.

1. Capture the caller's full legal name plus one disambiguator (date of birth, address, or employer).
2. Ask for, and record, the caller's aliases, nicknames, maiden or former names.
3. Identify and capture the other side — the adverse party or parties — by name.
4. Capture every connected party the matter touches: co-defendants, spouse, witnesses, related businesses, guarantors, insurers, prior counsel.
5. Run all of those names — not just the caller's — against current clients, former clients, and your adverse-party list.
6. Match fuzzily: nicknames, common-name variants, and d/b/a and parent/subsidiary relationships.
7. Treat any partial-information match as conflict-pending. Hold; do not clear.
8. Escalate every flag to an attorney before a consult is confirmed.
9. If it's a true conflict, decline on the call, offer a neutral referral, take no facts, give no advice.
10. Never disclose the reason for the decline or the conflicting party.
11. Timestamp and log the screen: names checked, sources, result, disposition, and who cleared it.
12. Surface the result on the intake summary the attorney reads before the consult.

The hard step everyone names and skips

Intake quality is decided by the steps everyone agrees are essential and quietly skips because they are inconvenient in the moment. Conflict checking is the cleanest example. Every firm will tell you they screen for conflicts. Far fewer screen the people who actually create conflicts, and far fewer still do it while the caller is on the line — when it is the only version of the check that protects both the client and the firm.

The reason it gets skipped is that doing it live is harder than doing it later: it takes a disciplined script, the patience to capture the whole relationship graph, and the nerve to decline a paying caller politely. That difficulty is exactly why it is worth getting right. The firms that screen at the door don't waste consults on conflicts, and they don't sign matters they have to give back.