The Call a Law Firm Misses at 7 p.m.

19:04, a car park in Leverkusen

Claudia has been head of sales at a machine builder for nine years. At 17:30 on a Tuesday the managing director hands her a letter in a meeting room on the second floor, and by 18:15 her laptop and her badge are on his desk. At 19:04 she is sitting in her car in the company car park, the letter on the passenger seat, calling employment lawyers.

She has three names from a former colleague. The first number plays a recording with the office hours. The second, a firm in central Cologne, rings through to a voicemail box, and she leaves her name, her number and one sentence: "I received a notice of dismissal today and I need advice quickly." The third firm is closed too, but a partner there calls her back at 19:40 from his kitchen. By 20:15 she has sent him the letter.

The firm with the voicemail box is the one this story is about, and it is invented: 24 lawyers in Cologne, employment and commercial law, acting mostly for employers and for senior executives like Claudia, in German and English. She is exactly the client it wants. It will find out the next morning.

08:40, eleven messages from the night before

On Wednesday morning Nadine, one of two intake assistants, opens the shared intake inbox. The voicemail box forwards recordings there as email, and the inbox belongs to no one in particular, so it waits for whoever gets to it first. Eleven inquiries came in after six: four voicemails, five web forms and two emails.

She works through them the way the firm always has. She listens to each voicemail, types the names into a spreadsheet, asks a secretary to search them in RA-MICRO, and hands the promising ones to associates to call back. When Felix, an employment associate, reaches Claudia at 10:30, she has already instructed someone else. She is polite about it.

The rest of the morning goes the usual way. Felix spends twenty minutes on the phone with the author of a web form from 20:15 before it is clear that it is a tenancy dispute, which the firm does not handle. Another associate calls back the managing director of a software company who emailed at 22:40: she wants to dismiss her head of development for cause. He hears the whole story, takes notes and asks her to send the documents. At 11:40 the secretary's search comes back clean, because she searched the software company's name.

Nobody searched the group it belongs to. The firm is on the other side of that group in a commercial dispute it runs for another client. Whether it can act for one of the group's subsidiaries is a question for a partner, and by the time anyone asks it, an associate has already heard everything.

The order things happen in

Martin, the managing partner, calls me that Friday. His first question is whether I can put a chatbot on the website. I ask him to share the spreadsheet instead, and to play me one of the voicemails.

The spreadsheet does not show a missing chatbot. It shows three problems in the order they happen. Evening inquiries wait for whoever opens a shared inbox. Every inquiry, including the ones the firm will never take, costs an associate a phone call to find out what it is. And the callback comes before the conflict check, which searches one name at a time, the name the prospect happened to give, with no record of who searched what.

The third is the one that keeps a managing partner awake. Section 43a(4) of the Federal Lawyers' Act, the BRAO, bars acting for conflicting interests in the same matter, and whether to act for a company whose group the firm is suing for someone else is a judgment on top of that. A firm that talks first and checks second can end up holding confidential information from someone it cannot act for.

So the plan fits in one line: conflicts first, conversation second, at any hour. The chatbot Martin asked about is the last and smallest part of it.

Conflicts first, then the callback

Everything lands in one queue: the voicemail transcripts that arrive in the intake mailbox, read through Microsoft Graph, the emails and the web form. Spam goes first, and so do the scams aimed at law firms, the new client keen to pay money in before anything is agreed, which go to the compliance partner rather than to intake.

A model then fills a fixed schema for each inquiry: matter type, which side, the parties and their roles, key dates, what the person wants, in German or English. It records what was said, marks anything it infers as an inference, and never invents a party. The rest is code:

• Deadline flags from the employment group's own table. Three weeks to challenge a dismissal after the notice arrives, under section 4 KSchG. Two weeks to dismiss for cause after learning the facts, under section 626(2) BGB. A hit marks the inquiry urgent and alerts the duty lawyer. It is never shown to the prospect as advice.
• A conflict search that covers the group. Every party is looked up in company data from the commercial register, and its parents, subsidiaries and managing directors are searched with it against clients, contacts, adverse parties and closed matters. The matching is fuzzy on purpose: legal forms stripped, umlauts and spellings normalized, former names included. The risk partner sets the thresholds.
• Triage by the practice groups' rules. The employment group takes employers and senior executives and refers employees below management level. Nobody takes tenancy. A misfit gets a polite referral drafted, pointing to the bar association's lawyer search.

The firm decides one rule for the evenings: the employment partners keep a duty rota until nine. If the search is clean, the duty lawyer may call back that evening. If it shows a possible match, nobody calls until the conflicts person has looked at it in the morning. The whole design, with the flow and the hard parts, is in the blueprint for law firm client intake.

The same Tuesday evening, run again

Here are three of the eleven inquiries, as the firm handled them and as the workflow would:

The third row is the one Martin reads twice. The conflicts person opens it first at 07:30, and a partner decides whether the firm can act. If the answer is no, the managing director hears it by ten, with time left inside her two weeks to find another firm. Nobody at the firm has heard her story, so nobody has to forget it.

One thing the table leaves out is the chat. Once the rest has run for a while, a website chat answers out of hours. It opens every conversation by saying it is the firm's AI intake assistant and not a lawyer, as Article 50 of the EU AI Act has required since 2 August 2026, and it asks for parties and dates, not documents. To "Do I have a case?", the question every prospect asks, it gives one fixed answer: a lawyer will tell you, and here is when.

What the shadow weeks turn up

None of this answers anyone at first. For the first weeks the workflow runs in shadow: it builds intake records and conflict reports beside the old process, and Nadine and the conflicts person compare them with their own. The rule for ending the shadow run is strict. If the manual search finds a possible conflict the automated one missed, even once, manual searching does not stop.

The shadow run shows the opposite problem first. The group search raises far more possible matches than a name search ever did, such as a GmbH with a similar name in another city. That is deliberate, and it is why a person clears every hit, with who cleared it and why kept on the matter. Among the noise is one real find: an existing client listed in RA-MICRO under the name it had before a merger.

It also shows what prospects send when nobody stops them. Employment inquiries arrive with sick notes and diagnoses attached, and health data is a special category under the GDPR. So the form and the chat ask only for parties and dates, and anything sent anyway goes into a restricted record that only the conflicts person can open until the matter is accepted. If the firm declines, it is deleted on the retention date.

And the chat earns its evenings. It answers alone only after a month of reviewed transcripts with no advice given and every urgent flag caught, and its fixed answer is tested against real questions, including indirect ones such as "was my employer allowed to do that?"

Who says yes

The model prepares, code checks, people decide. The conflicts person clears every possible hit. A lawyer accepts or declines each matter and sets the scope and the fee, and only a lawyer tells a prospect the firm will act. Accepting finds a consultation slot in that lawyer's calendar, creates the client and matter in RA-MICRO with the conflict record attached, and files a draft engagement letter in iManage for the lawyer to finish.

Martin's partners want to know where the client data goes. German lawyers may involve service providers only under section 43e BRAO, which requires a contract in text form binding the provider to confidentiality. So the model runs with an EU-processing provider under such a contract, nothing is used for training, and every AI action is logged per matter. If that is not enough for the partners, the reading runs on a self-hosted model in Europe instead. RA-MICRO is a desktop system, so the connection needs a connector on the firm's own server or an interface agreed with the vendor, and that is scoped in the first week.

The next call at seven

Nadine's Wednesday no longer starts with a shared inbox and a spreadsheet. It starts with a sorted queue: urgent inquiries already called back by the duty lawyer, possible conflicts in the order the conflicts person should see them, referrals waiting for one click. The associates' mornings go to matters the firm has accepted, not to finding out what a voicemail was about.

If you are a US or UK firm on Clio, try Clio Grow before building anything; Lawmatics and Intaker cover similar ground, and for one practice area one of them is probably enough. A build earns its cost where they stop: a German practice management system they do not connect to, several practice groups with their own rules and deadline tables, or a conflict search that has to cover whole groups and record who cleared each hit. It usually fits the multi-step tier of AI workflow automation. The full blueprint covers the rollout stages, and once a matter is open, its court deadlines belong to court deadline docketing.

Frequently asked questions