Case Status vs Hona: how they compare in 2026

The product was a client portal before it was an AI product, and the portal still stands on its own. Real time case status, the branded app without passwords, secure messaging, document upload, stage videos and review prompts triggered by NPS scores are all conventional software. The sync with the case management system is an integration rather than a model. On top of that sits a named set of model features the vendor sells individually: Agentic AI Translation, Agentic AI Case Summary, Agentic AI Response and Prioritization, an AI Triage Agent, AI Automation Agents and Client Sentiment Tracking. The models power a core capability, and the product would still work without them as a communication and status system.

Hona has repositioned around the model, but the platform underneath still stands. The company now markets itself as AI for personal injury firms and Lia as an AI case manager, and the FAQ confirms Lia is priced and contracted separately from what the vendor calls Hona's core platform. That core (client portal, case progress updates, two way messaging, drip campaigns, branding and education) is conventional communication software that predates Lia and is still sold. Remove the models and a working client update product remains; the models power a core capability on top of it.

Nothing is published on accuracy or grounding for a system that drafts and translates messages sent to represented clients. No accuracy figure, evaluation, test set or error rate is published, and nothing describes how a drafted reply is grounded in the case record. The exposure is specific. Agentic AI Translation renders a firm's message into another language for a client who cannot check it against the original, and Agentic AI Case Summary condenses a matter for a lay reader. Accuracy is not even asserted, and grounding is not claimed. The individual AI feature pages were not opened and may say more.

Accuracy is asserted through operating metrics and never measured as accuracy. The site publishes a 94% check in rate, a response time under four minutes, and a claim that 100% of treatment updates are captured automatically. None of those says how often Lia records a symptom, provider or appointment correctly, and no evaluation, test set or error rate is published on any page read. That matters because the extraction is the product: Lia reads free text client replies and writes structured treatment records that later support a settlement demand, so a misread provider name or date carries into the case file. Tests about primary authority and citators do not apply, since Lia is expressly barred from making legal assertions.

A review point is published and the rest of the control structure is not. The home page says Case Status uses case context to suggest responses that staff can review and send in seconds, which puts a person between the model and the client on the drafting path. The Agentic AI Response and Prioritization feature is described as ranking messages by urgency for staff rather than acting on them. Against that, the product also markets AI Automation Agents and claims that up to 80% of routine client communication is handled automatically. That implies some messages reach clients without review of each one, and nothing published reconciles the two or says which categories run unattended. No threshold, escalation route or statement of what happens after a wrong message is sent is published.

The control structure is complete and published. What runs alone is stated: Lia handles routine treatment phase communication herself, opening contact by text and running check in messages without approval of each one. What constrains her is written by the customer and specific: escalation rules in plain language, with the vendor's own examples being alerts when a client mentions stopping treatment or when a provider appears who is not on the preferred list. Thresholds are published: physical therapy missed twice in a row, no response for 48 hours, and high priority issues repeating to the case manager every hour until resolved. Review is built in: every conversation is visible to the team, staff can step in at any time, each case manager sees their own cases, and drafts to providers need human sign off before anything goes out. The route back to a person covers the highest risk case: a legal question goes immediately to the assigned case manager, and a call placed from the dashboard is transcribed back into Lia. Enrollment is optional case by case, and the vendor advises firms to exclude clients unlikely to respond well to text.

One named firm with a dated figure, and everything else anonymized. Pond Lehocky is named on the home page with close to 15,000 active clients using the app across its workers compensation and social security disability departments. It gives a before and after review figure with a stated window: 4.6 with 417 reviews before, and 4.8 with more than 3,000 reviews within 24 months. Shawn Lehocky, Chief Executive Officer at Pond Lehocky Giordano, appears on record. The three growth case studies are unattributed and identified only by practice and city: an SSD firm in Charleston WV that doubled caseload in a year, a PI firm in Chicago at 40% growth year over year, and a large PI firm in Kansas City with a 35% increase in case velocity. The firm count is inconsistent: 600 plus in the page header and more than 500 in the body. G2 ratings, badges and review quotes were set aside as directory material.

Named users at named firms, and figures that belong to the platform rather than any of them. People on record with titles and employers include Sofia Escobedo, Assistant at The James Law Firm; Crisely Gonzalez, Case Manager at Omega Law Group; Alexandria Zant at Zant Law Firm; Domenic Martini at Singleton Schreiber; and Bridgett Sanne at Inserra Kelley Cooper Sewell. Firm logos include Isaacs & Isaacs and Nachawati Law. Separately, the vendor claims more than 500 personal injury firms, a 94% average client intake completion rate and an average response time under four minutes. None of the quoted users carries a figure, and none of the figures carries a customer, date or method. The market statistics on the product page, a 30% reduction in payouts where treatment gaps occur and more than 20% of cases showing a two week gap in the first six weeks, describe the industry, not Hona.

Confidentiality is asserted in general terms, and the agreement that would carry it is missing. The security commitment page describes multiple layers of encryption, least privilege development, mandatory two factor authentication, background checks and ongoing security training. The GDPR section states that Case Status acts as a data processor for law firms. But no law firm customer agreement is published; the only agreement on the site is the End User Terms of Use binding the firm's clients. Nothing addresses training on client content, matter or tenant segregation, or privilege and work product, which matters because the platform carries attorney client communications by its own description. The privacy notice also grants the app access to contacts, microphone, calendar, reminders, SMS messages and continuous location. That is wider than a case status app needs, and nothing published explains why.

The agreement is published and substantive on confidentiality, and silent on training. Terms clause 8 sets a mutual confidentiality regime with a three year tail and perpetual protection for trade secrets. Clause 13.4(b) requires Provider to stop all use of Customer Data on termination and return or destroy it, certified in a signed instrument. The compliance section states PHI is handled under a BAA with end to end encryption, and clause 9.2 leaves the customer owning Customer Data. But nothing addresses training on client content, and clause 9.1 runs the other way: the customer unconditionally and irrevocably assigns to Provider all right, title and interest in Resultant Data, a term defined only in a separate Definitions Exhibit that was not read. No matter or tenant segregation is documented, and privilege and work product are not addressed for a system carrying communications between a firm and its clients.

Nothing is published on the advice line for a product that generates and translates messages to represented clients. That matters because the reader is a claimant who cannot judge whether what arrives is legal advice. No disclaimer of any kind, no statement that AI drafted or translated content is not legal advice, no requirement that a firm tell its client about AI involvement, and no reference to ABA Formal Opinion 512 or any state bar guidance is published. Pages checked were the home page, security commitment page, privacy notice, Terms of Use and its Limitation on Liability subpage. The End User Terms do address the reader as a client, and use that space to disclaim liability rather than to explain what the technology does. The individual AI feature pages were not opened and may say more.

Two published commitments stand out. First, the advice line is a product guardrail, not a disclaimer: Lia is set never to give legal advice or legal opinions, and any question about legal strategy goes straight to the assigned case manager. Second, the vendor commits to telling the client about the AI. Lia introduces herself as an AI from the firm in her first message, described as a requirement rather than an option, with the recommended practice that a person sends an introduction first. For a client who cannot tell whether an answer is legal advice, that is the disclosure that matters. No jurisdiction limits are named, nothing addresses the firm's own supervision and competence duties beyond the escalation route, and ABA Formal Opinion 512 is not mentioned on any page read.

No governance position is published. Across every page read there is no responsible AI page, no named owner accountable for the AI, no testing regime before release and no ISO 42001 or equivalent. The security commitment page names a Chief Technology Officer, Charles Lane, and the privacy notice names a Data Protection Officer, Andy Seavers, but both roles are framed around information security and privacy rather than model governance. Nothing addresses whether sentiment scoring, urgency ranking or translation quality behaves evenly across languages or client groups. That is the live question for a product whose clients include immigration and workers compensation claimants writing in languages the firm may not read.

No governance position is published for a system that talks to injured claimants unsupervised. The home page, the AI case agents product page with its compliance and FAQ sections, the privacy policy and the full Terms and Conditions were read. There is no responsible AI page, named owner accountable for the AI, testing regime before release, or ISO 42001 or equivalent. Nothing addresses whether Lia performs evenly across client groups. That is a live question for a product that runs in English and Spanish and whose vendor advises firms to exclude elderly clients and catastrophic injury cases from enrollment, an exclusion that implies limits it never describes. The legal advice guardrail and escalation rules are oversight controls, and TCPA and HIPAA compliance are regulatory posture, not model governance.

A generic privacy notice and a narrative security page, with the operative details missing or blank. What is published: multiple layers of encryption, least privilege, mandatory two factor authentication, password and lockout policies, employee background checks, ongoing security training, AWS hosting, and continuous compliance monitoring through Secureframe. What is not: any subprocessor list, any incident or breach notification practice, or any retention period. The retention gap is specific. Under the heading on how long information is kept, the privacy notice of 17 July 2025 says no purpose in the notice will require keeping personal information for longer than, and the sentence simply ends. The number is missing from the published document. Deletion is promised once no legitimate business need remains, with an exception for backup archives.

Deletion is well handled and little else is. Terms clause 13.4 requires Provider, on termination, to stop using Customer Data and return or destroy it, certified in a signed written instrument, with carve outs for legal retention and for backups, archives and disaster recovery systems until deleted in the ordinary course. The compliance section states end to end encryption and PHI handled under a BAA, and clause 5 commits to routine backups, with restoration as the sole remedy for data loss. Missing are a retention period during the term, any incident or breach notification practice, and a subprocessor list. Clause 1.6 lets Provider engage subcontractors at its discretion with no list and no duty to give notice. Clause 6 defines the security commitment by pointing to the privacy policy, dated 12 September 2022, which predates Lia. The policy covers the product without addressing what happens to client messages and generated records after processing.

A published allocation that is total, uncapped, and pointed at the wrong party. The Limitation on Liability subpage excludes liability for damages of any kind under any legal theory arising from use or inability to use the service, direct or indirect, whether in negligence or contract and even if foreseeable. It expressly names personal injury, pain and suffering, emotional distress, loss of data and loss of goodwill among the excluded categories. There is no cap, because there is no fee: these are End User Terms binding the law firm's client, not the firm. The excluded heads of damage include personal injury, pain and suffering and emotional distress, in a product sold into personal injury, workers compensation, disability and mass tort practice. No agreement with the firm, indemnity, warranty on output or insurance position is published. A specific and readable allocation exists, and nothing in it runs toward either the firm or its client.

A complete, readable allocation is openly published. Terms clause 12.2 caps total liability at fees paid in the twelve months before the act giving rise to it, and clause 12.1 excludes the usual heads of consequential loss. Clause 11.1 gives the customer a real indemnity: Provider defends and holds the customer harmless against third party US intellectual property claims arising from use of the Services, with itemized carve outs. Clause 11.4 obliges Provider to procure rights, modify or terminate if the Services are enjoined. Clause 10.2 warrants performance by skilled personnel in a professional and workmanlike manner to generally recognized industry standards, and clause 4 adds a 95% availability commitment with service credits. None of it reaches output: clause 10.4 warrants nothing about results being accurate, complete or error free, the indemnity covers infringement rather than a wrong treatment record, and no insurance position is published.

The integration set is named in full. Thirteen case management platforms are listed with individual integration pages: Clio, Litify, MyCase, Neos by Assembly, Filevine, CASEpeer, SmartAdvocate, SmokeBall, PracticePanther, CoCounselor, Meruscase, Docketwise and Salesforce. That places the product inside the plaintiff and small firm stack rather than beside it. Case Status describes itself as the communication layer living inside the case management platform, with staff working where they always have and everything syncing automatically. One published customer account describes it running inside Litify in a frame. What syncs, in which direction, and what a firm must configure is not described on any page read. The individual integration pages were not opened and may say more.

Integrations are numerous and aimed at the systems this buyer actually runs. Fifteen platforms are named on the product page, including Filevine, Clio, MyCase, CASEpeer, SmartAdvocate, Assembly, Smokeball, Lawcus, Salesforce, Lead Docket, Cerenade, Lexamica and AttorneyShare, which is the plaintiff side stack rather than a generic connector list. Direction is stated broadly: Lia sits alongside the case management system and pulls data both ways. The mechanism is named: enrollment happens through a Chrome extension that gives Lia the case context, and can be triggered by case status changes in the underlying system. No page read says which fields move, in which direction, or what a firm must configure, and the FAQ refers specifics to a sales rep. The dedicated integrations page was not opened and may say more.

Cloud delivery is named, and neither the tenancy model nor a region choice is stated. The security commitment page says Case Status runs on Amazon Web Services and explains the choice as scale and redundancy, not as a tenancy design. The privacy notice says servers are in the United States and that information from users outside the US will be transferred to and processed there. That fixes a default location but is not a residency offering. No tenancy model is published, no region option is offered, and processing location is not separated from storage. The product's stated practice areas include immigration, so its users include clients outside the United States, which makes the lack of any region choice worth noting.

Cloud delivery is evident, and neither tenancy nor region is stated. No tenancy model is published and no region option is offered. The only location material is in the privacy policy of 12 September 2022. It says personal data may be stored and processed in any country where Hona or its service providers do business, including the United States, that officials there may be entitled to access it, and that EU Standard Contractual Clauses are used where required for transfers out of the EEA, UK or Switzerland. That is a transfer disclosure, not a residency offering, and it fixes no processing location. Nothing separates where data is processed from where it is stored.

Detailed attestation particulars are published, with no way to obtain the report. The security commitment page names the auditor, Modern Assurance, as an independent third party accounting and auditing firm. It states the scope as all five trust services criteria by name (security, confidentiality, availability, privacy and processing integrity) and gives completion dates: SOC 2 Type I in September 2023 and SOC 2 Type II in July 2024. HIPAA compliance is claimed on the basis that legal practices serve clients who are also patients, and Secureframe is named for continuous monitoring. Two gaps remain. There is no trust center or portal and no stated route for a buyer to request a report, so the evidence is described rather than accessible. And the most recent attestation stated is now over two years old, with ongoing audits expressed as an intention rather than a published later report.

The compliance section of the product page states SOC 2 Type II audited annually, with the report available on request. It also states HIPAA, with PHI handled under a BAA and end to end encryption, and TCPA, with consent tracked for each outreach and opt outs honored, which is the right standard for a product built on automated texting to consumers. Full documentation is said to be available on request. Nothing lets a buyer test any of it: no auditor, scope, trust services criteria, coverage period or report date is given, there is no trust center or portal, and the request route is stated but not described. The standard is named in prose with an annual cadence, not just as a badge.

Nothing is published about the model supply chain a customer inherits. The product markets six separately named AI capabilities and a whole Data and Agentic AI solution page. Yet no model, model provider, inference location or commitment to notify changes appears on any page read. There is no subprocessor list of any kind on the site, which is the usual place for this disclosure. AWS is named on the security commitment page, but hosting says where the software runs, not whose model reads client messages. No reference to an underlying model layer is published at all.

Nothing is published about the model supply chain a customer inherits. Hona markets an AI agent that texts and calls clients, transcribes calls, extracts structured medical information and works in two languages. Yet across the home page, the AI case agents page with its compliance and FAQ sections, the privacy policy and the full Terms and Conditions read, no model, model provider, inference location or change notice commitment appears. There is no subprocessor list, and the agreement runs the other way: clause 1.6 lets Provider engage subcontractors at its sole discretion, with no duty to name them or notify the customer. No reference to an underlying model layer is published at all.

No pricing information at any level. There is no pricing page. The navigation, footer and resource menus were checked across the home page, the security commitment page, the terms index, the Limitation on Liability subpage and the privacy notice, and none carries a pricing entry. No tier names, packaging structure, unit of charge or figure is published, and every commercial route is a demo booking, a tour or a calendar link. Neither the shape of the pricing nor a number is visible.

There is no pricing page, yet the charging structure is published in detail in the contract. The site's Pricing link leads to a demo booking, and the FAQ answers pricing and contract term questions by referring buyers to a sales rep. The Terms and Conditions publish the whole model. Fees are Recurring and One-Time Fees against an Initial User Count and a Case Tier Limit, with Excess User Fees, Case Overage Fees and Text Overage Fees defined. The text allowance is a formula, the Case Tier Limit multiplied by fifty, with the vendor's example of 12,500 texts for a 250 case tier over twelve months. One real rate is published: 1.5 cents per text beyond the allowance. Fee increases need thirty days' notice, and renewal is annual and automatic. The unit and structure are stated, but no plan price is published at any level.

Practice coverage is specific and firm segmentation is not. Eight practice areas each have their own page describing the work: personal injury, workers compensation, immigration, employment, disability, mass tort, estate planning and criminal. That is a real statement of where the product is aimed, and it hangs together: all eight are high volume matters where a client waits a long time with little news. What is missing is any segmentation by firm size, any in house or government position, and any statement of where the product stops. The customer evidence points to plaintiff and claimant firms of varying size, but the vendor never says so directly.

The focus is stated sharply. Hona describes itself as built for personal injury firms, repeats it in the site footer, and writes its product page entirely around the treatment phase of a PI case: providers, appointments, treatment gaps and symptom capture. Eight practice types have their own pages: personal injury, workers compensation, bankruptcy, mass tort, employment, criminal, immigration and family law. The vendor also states real limits. Enrollment is optional per client, and firms are advised to start with active treatment soft tissue cases and exclude clients unlikely to respond well to texts, naming elderly clients and catastrophic injury cases. Firm segmentation is missing: nothing addresses solo versus large firm, in house or government use, and the practice pages beyond personal injury are thinner than the core.