# Marcus Delgado, Intake & Operations Manager at Reyes Delgado Injury Law — read of LawLineAI, May 11 2026 > 8 years running intake and ops for a 14-attorney PI firm in Phoenix. We handle about 400 inbound calls a month, roughly 30% land after 5 PM. I coach my son's little league Saturday mornings, which means Friday nights I'm not watching dashboards. --- ## How I got here Googled "after hours AI legal intake cost" last Tuesday because our answering service just raised rates again and I'm tired of paying $1.80 a call for someone in a Manila call center reading from a script they don't understand. A Reddit thread in r/LegalTech linked to this page. I clicked expecting another Answering Service Dressed Up In An AI Costume situation. --- ## What I clicked first The lede worked on me. "Your phone rings at midnight. A personal injury case. A new arrest. A family in crisis. But your intake team is gone. By morning, they called someone else." That's not abstract. That happened to us three weeks ago with a wrongful death inquiry. I know the specific feeling of reading a 2 AM voicemail at 8:15 and knowing it's gone. So I kept reading. The hero pulled me in. --- ## Where I paused The FAQ answer about AI disclosure: "LawLineAI is transparent. It introduces itself as an intake system powered by AI. Callers can request to leave a message for a human callback if they prefer. Most do not." That "Most do not" stopped me. Where does that number come from? Is that a statistic from actual call data or is someone guessing? Because in PI specifically, callers are often rattled, in pain, not tech-savvy, sometimes elderly. The question of whether a confused 65-year-old accident victim will just hang up when she hears "AI intake system" is not answered by "most do not." That's a claim that needs a number behind it, or a story, or literally anything other than an assertion. --- ## What I distrusted Scroll down far enough and you hit this: "Honest disclosure: we don't have live customers on this idea yet. We shipped the strategy package; you ship the customer conversations." So this isn't a product. It's a blueprint. The whole page is written like a SaaS landing page, there's pricing, there are FAQ sections about setup time, there are integration names (Clio, Rocket Matter, Practice Panther) that imply it works with those tools today, and then buried at the bottom it says nobody has actually used this. That's the kind of bait-and-switch that would get me to close the tab. The pricing section ($499/mo Starter, $999/mo Professional) is listed with no asterisk, no "coming soon," nothing to indicate those are theoretical prices for a product that doesn't exist yet. Someone who doesn't scroll to the bottom might fill out a trial form before realizing there's nothing to trial. Also: "Reduces Liability -- Every missed call is a potential malpractice exposure." Legal liability claims in marketing copy always make me nervous. That's not how malpractice works. A prospective client who couldn't reach you and went elsewhere is not a malpractice claim. Somebody who wrote that doesn't practice law and doesn't know law firm risk profiles. It makes me trust the other claims less. --- ## What would convince me A recording. One actual call, end to end, with a real PI scenario. Not a demo script, an actual midnight call where someone is upset and not following the prompt flow. That's the test. Answering services fall apart when the caller is crying, or drunk, or doesn't speak English well, or gives contradictory information about the accident date. Show me the AI handling that. And if this is still pre-launch: tell me what stage the product is actually at. Is there a working prototype I can hear? Are there beta firms testing it? "No live customers yet" is fine if you're honest about what I'd actually be getting into by adopting it. --- ## What I'd ask in an email reply 1. What does the actual AI voice sound like in a crisis situation, and can I hear a real call where it handled a confused or distressed caller? 2. The page says it integrates with Clio but we're on Clio Grow specifically, not Clio Manage. Has anyone tested this integration, and what does "routes to your CMS" actually mean in practice, a webhook, an email trigger, a native two-way sync? 3. You disclose no live customers. If I wanted to be a pilot firm, what does that actually look like -- is there working software I'd be testing, or would I be funding the build? --- ## Verdict: on-the-fence The pain point is real and the page describes it well. But it's selling a product concept as if it's a live product, and I almost didn't notice. If they have a working demo and a clear answer on the pilot question, I'd talk to them. --- *Memo by skeptic persona, generated 2026-05-11. Studio breaks own self-grading loop.*