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 passwordless app, secure messaging, document upload, stage videos and NPS-driven review prompts are all conventional software, and the CMS sync that feeds them is an integration rather than a model. On top of that sits a named set of model-driven 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. That is the B band: the models power a core capability layered on a product that would still function without them as a communication and status system. Pages read 1 September 2026.

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, education — is conventional communication software that predates Lia and is still sold. Remove the models and a working client-update product remains. B on the band: the models are the engine of a core capability layered on a product that would still function without them. Pages read 1 September 2026.

Nothing published on accuracy or grounding for a system that drafts and translates messages sent to represented clients. The home page, the security commitment page, the Terms of Use and its Limitation on Liability subpage and the privacy notice were read on 1 September 2026; no accuracy figure, no evaluation, no test set, no error rate and no description of how a drafted reply is grounded in the case record was located. The exposure is specific rather than theoretical: Agentic AI Translation renders a firm's message into another language for a client who by definition cannot check it against the original, and Agentic AI Case Summary condenses a matter for a lay reader. D rather than C because C requires accuracy to at least be asserted or grounding to be claimed, and neither was found; the individual AI feature pages were not opened and are the rebuttal route.

Accuracy is asserted in operational 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 auto-captured, but none of those describes how often Lia records a symptom, provider or appointment correctly, and no evaluation, test set or error rate was located on any page read on 1 September 2026. 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 propagates into the case file. The primary-authority and citator limbs of the higher bands do not apply, since Lia is expressly barred from producing legal assertions. C: accuracy asserted without measurement.

A review point is published and the rest of the control structure is not. The home page states that Case Status uses case context to suggest responses that staff can review and send in seconds, which places a human between the model and the client on the drafting path, and 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 a claim that up to 80% of routine client communication is handled automatically, which implies messages reaching clients without a per-message review, and nothing published reconciles the two or says which categories run unattended. No threshold, no escalation route and no statement of what happens after a wrong message is sent were located on 1 September 2026. B on the strength of the stated review-before-send point, held there by the unexplained automation claim.

The most complete control structure located in this pull, and it is published rather than implied. What runs alone is stated: Lia manages routine treatment-phase communication on her own, opening contact by text and running check-ins without per-message approval. What constrains her is customer-written and specific — escalation rules composed in plain language, with the vendor's own worked examples being alerts when a client mentions stopping treatment or when a provider appears that is not on the preferred list. Thresholds are published: missed physical therapy twice in a row, no response for 48 hours, and high-priority issues re-pinging the case manager every hour until resolved. Review surfaces are published: every conversation is visible to the team, staff can step in at any time, each case manager sees their own book, and provider-facing drafts require human sign-off before anything goes out. The route back to human judgement is explicit and covers the highest-risk case — a legal question escalates immediately to the assigned case manager, and a call placed from the dashboard is transcribed back into Lia. Enrolment is optional case by case, with the vendor advising firms to exclude clients unlikely to respond well to text.

One named firm with a dated figure, and everything else anonymised. 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, and a before-and-after review metric with a stated window: 4.6 with 417 reviews before, 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 deliberately unattributed, identified only by practice and city: an SSD firm in Charleston WV doubling caseload in a year, a PI firm in Chicago at 40% year-over-year growth, a large PI firm in Kansas City with a 35% increase in case velocity. Firm count is internally inconsistent, 600-plus in the page header and more than 500 in the body. B: real deployment evidence with substance, short of full attribution. G2 ratings, badges and review quotes were excluded as directory material.

Named users at named firms, and figures that belong to the platform rather than to any of them. Individuals are on record with titles and employers: 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; Bridgett Sanne at Inserra Kelley Cooper Sewell. Firm logos include Isaacs & Isaacs and Nachawati Law. Separately the vendor publishes 500-plus personal injury firms, a 94% average client intake completion rate and a sub-four-minute average response time. None of the quoted users carries a figure and none of the figures carries a customer, a date or a stated method. The market statistics on the product page — a 30% reduction in payouts where treatment gaps occur, 20%-plus of cases showing a two-week gap in the first six weeks — are claims about the industry rather than about Hona, and are not treated as outcome evidence. B.

Confidentiality is asserted in general terms while the instrument that would carry it is absent. The security commitment page describes multiple layers of encryption, least-privilege development, mandatory two-factor authentication, background checks and ongoing security training, and the GDPR section states plainly that Case Status acts as a data processor for law firms. But no law firm customer agreement is published anywhere: the only agreement on the site is 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 here 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 geolocation, a permission scope wider than a case-status app needs, and nothing published explains why. C.

The agreement is published and substantive on confidentiality, and silent on the question that decides this axis. Terms and Conditions clause 8 runs a mutual confidentiality regime with a three-year tail and perpetual protection for trade secrets, clause 13.4(b) requires Provider to cease all use of Customer Data on termination and return or destroy it with certification in a signed instrument, and the compliance section states PHI is handled under a BAA with end-to-end encryption. Clause 9.2 leaves the customer owning Customer Data. But nothing anywhere 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-level or tenant segregation is documented, and privilege and work product are not addressed for a system carrying communications between a firm and its clients. C rather than B because B requires substantive commitments on training use and there are none.

Nothing published on the advice line for a product that generates and translates messages to represented clients. This is the category where that matters most, because the reader is a claimant who cannot judge whether what arrives is legal advice. No disclaimer of any kind, no statement that AI-generated or AI-translated content is not legal advice, no requirement that a firm disclose AI involvement to its client, and no reference to ABA Formal Opinion 512 or any state bar guidance was located across the home page, security commitment page, privacy notice, the Terms of Use and its Limitation on Liability subpage on 1 September 2026. The End User Terms do address the reader as a client, and they use that space to disclaim liability rather than to explain what the technology does. The individual AI feature pages were not opened and are the rebuttal route.

Two published commitments that are rare anywhere in this index and unique in this lane. First, the advice line is stated as a product guardrail rather than a disclaimer: Lia is configured never to provide legal advice or legal opinions, and any question touching legal strategy is escalated directly to the assigned case manager. Second, and more unusual, the vendor commits to disclosing the AI to the client — Lia introduces herself as an AI from the firm in her very first message, described as a requirement rather than an option, with the recommended practice that a human sends an intro first. In a category whose editorial turns on a client being unable to tell whether an answer is legal advice, that is the disclosure the category asks for. B rather than A because 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 on 1 September 2026.

No governance position located. There is no responsible AI page, no named accountable owner for the AI, no pre-release testing regime and no ISO 42001 or equivalent across every surface read on 1 September 2026. The security commitment page names a Chief Technology Officer, Charles Lane, and the privacy notice names a Data Protection Officer, Andy Seavers, but both 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 populations, which is the live question for a product whose clients include immigration and workers compensation claimants communicating in languages the firm may not read. Security certifications are a different subject under this band and are graded on Security Certifications.

No governance position 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 on 1 September 2026; there is no responsible AI page, no named accountable owner for the AI, no pre-release testing regime and no ISO 42001 or equivalent. Nothing addresses whether Lia performs evenly across client populations, which 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 enrolment — an exclusion that implies known performance limits that are never described. The legal-advice guardrail and escalation rules are real but they are oversight controls graded on Autonomy, and TCPA and HIPAA compliance are regulatory posture rather than model governance.

A generic privacy notice plus 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: no subprocessor list of any kind, no incident or breach notification practice, and no retention period. The retention section is the specific finding, and it is unusual enough to name. Under the heading on how long information is kept, the privacy notice of 17 July 2025 reads that 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 committed to once no legitimate business need remains, with an exception preserved for backup archives. C.

Deletion is well handled and almost nothing else is. Terms clause 13.4 requires Provider on termination to cease use of 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. Against that: no retention period during the term, no incident or breach notification practice, and no subprocessor list — clause 1.6 reserves the right to engage subcontractors from time to time in Provider's discretion with no list and no notice obligation. Clause 6 defines the security commitment by pointing at the privacy policy, which is dated 12 September 2022 and predates Lia entirely. C: 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, expressly naming 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. That the excluded heads of damage are personal injury, pain and suffering and emotional distress, in a product sold into personal injury, workers compensation, disability and mass tort practice, is worth a buyer reading twice. No firm-facing agreement, indemnity, warranty on output or insurance position is published. C rather than D because a specific and readable allocation exists; C rather than B because nothing runs toward either the firm or its client.

A complete, readable and openly published allocation, which is more than most of this pull offers. Terms clause 12.2 caps aggregate liability at the fees paid in the twelve months before the act giving rise to it, clause 12.1 excludes the usual heads of consequential loss, and clause 11.1 gives the customer a genuine indemnity — Provider defends and holds the customer harmless against third-party US intellectual property claims arising from use of the Services, with the carve-outs itemised and clause 11.4 obliging Provider to procure rights, modify or terminate if the Services are enjoined. Clause 10.2 carries an express warranty that Provider will perform using personnel of required skill and in a professional and workmanlike manner to generally recognised industry standards, and clause 4 adds a 95% availability commitment with service credits. B rather than A because none of it reaches output: clause 10.4 expressly 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 the strongest part of the product proposition and 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. Eight of those are systems this index already covers, which tells a buyer the product genuinely sits in the plaintiff and small-firm stack rather than beside it. The positioning is explicit and useful: 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, and one published customer account describes it running inside Litify in a frame. B rather than A because what syncs, in which direction and what a firm must configure is not described on any page read on 1 September 2026; the individual integration pages were not opened and are the rebuttal route.

Real, numerous and precisely 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 — the plaintiff-side stack rather than a generic connector list, and eight of them are vendors this index already covers. Direction is stated at a high level, with the vendor saying Lia lives alongside the case management system and pulls data both ways, and the mechanism is named: enrolment happens through a Chrome extension that gives Lia the case context, with enrolment optionally triggered by case status changes in the underlying system. B rather than A because no page read on 1 September 2026 describes which fields move, in which direction, or what a firm must configure, and the FAQ routes specifics to a sales rep. The dedicated integrations page was not opened and is the rebuttal route.

Cloud delivery is named and neither dimension a buyer needs is stated. The security commitment page states that Case Status runs on Amazon Web Services and describes the reasoning as scale and redundancy rather than as a tenancy architecture. The privacy notice states that servers are located in the United States and that information from users outside the US will be transferred to and processed there, which 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 distinguished from storage. For a product whose stated practice areas include immigration, and whose users therefore include clients outside the United States, the absence of any region choice is worth noting. C on the band's words: cloud delivery is evident and neither the tenancy model nor a selectable region is stated.

Cloud delivery is evident and neither dimension is stated. No tenancy model is published anywhere, and no region option is offered. The only location material is in the privacy policy of 12 September 2022, which states personal data may be stored and processed in any country where Hona or its service providers do business, including the United States, and that officials in those countries may be entitled to access it, with EU Standard Contractual Clauses 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 distinguishes where data is processed from where it is stored. C on the band's words.

The best attestation particulars located in this pull, with no way to obtain the report. The security commitment page names the auditor, Modern Assurance, describes it as an independent third-party accounting and auditing firm, states the scope as all five trust services criteria by name (security, confidentiality, availability, privacy and processing integrity), and gives completion dates for both audits: 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 things hold this at B. There is no trust centre or portal and no stated route by which a buyer could request any report, so the evidence is described rather than accessible. And the most recent attestation stated is now over two years old, with the commitment to ongoing audits expressed as intention rather than as a published subsequent report.

The compliance section of the product page states SOC 2 Type II audited annually with the report available on request, alongside HIPAA with PHI handled under a BAA and end-to-end encryption, and TCPA with consent tracked per outreach and opt-outs honoured — the last being the right standard to name for a product whose core function is automated texting to consumers. Full documentation is said to be available on request. What is absent is everything that would let a buyer test it: no auditor is named, no scope or trust services criteria are given, no coverage period or report date appears, and there is no trust centre or portal of any kind. The request route is stated but not described, so under the three-tier rule it does not reach the top band. B rather than C because the standard is named in prose with an annual cadence rather than appearing only as a badge.

Nothing published about the model supply chain a customer inherits. The product markets six separately named AI capabilities and an entire Data and Agentic AI solution page, and across every surface read on 1 September 2026 no model, no model provider, no inference location and no change-notification commitment appears. There is no subprocessor list of any kind on the site, which is the ordinary route to this disclosure and which several vendors in this pull publish openly. AWS is named on the security commitment page but hosting answers where the software runs rather than whose model reads client messages, and cannot be spent here. D rather than C because C requires the vendor at least to refer to the models underneath in some form, and no reference to a model layer was located at all.

Nothing 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 operates in two languages, and across the home page, the AI case agents page including its compliance and FAQ sections, the privacy policy and the full Terms and Conditions read on 1 September 2026, no model, no model provider, no inference location and no change-notification commitment appears. There is no subprocessor list, and the agreement runs the other way: clause 1.6 reserves the right to engage subcontractors to perform the Services from time to time in Provider's sole discretion, with no obligation to name them or notify the customer. D rather than C because C requires the vendor at least to refer to the models underneath, and no reference to a model layer was located at all.

No pricing information at any level. There is no pricing page: the navigation, the footer and the resource menus were checked on 1 September 2026 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, no packaging structure, no unit of charge and no figure are published, and every commercial route is a demo booking, a tour or a calendar link. D rather than C because C requires the shape to be visible with only the number withheld, and here neither is. Under the pricing-row rule there is no published structure, so no VendorPricing row was written.

An unusual case: there is no pricing page, and the charging structure is nonetheless published in detail — in the contract. The site's Pricing link routes to a demo booking and the FAQ answers both pricing and contract-term questions by referring the buyer to a sales rep. But the Terms and Conditions publish the whole model: fees are structured as 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 stated as a formula, the Case Tier Limit multiplied by fifty, with the vendor's own worked example of 12,500 texts for a 250-case tier over twelve months; and one real rate is published, 1.5 cents per text beyond the allowance. Fee increases require thirty days' notice and renewal is annual and automatic. B on the band's second limb, the unit and structure stated without the figure. No plan price is published at any level, which is what keeps it off A.

Practice coverage is unusually specific and firm segmentation is not. Eight practice areas each have their own page with copy 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 is coherent, since all eight are high-volume matters where a client waits a long time with little news. What is missing is the other half of the band: no firm-size segmentation, no in-house or government position, and no statement of where the product stops. The customer evidence points at plaintiff-side and claimant-side firms of varying size but the vendor never says so directly. B rather than A because the limits are not stated.

The focus is stated more sharply than most vendors dare. Hona describes itself as built for personal injury firms and repeats it in the site footer, and the product page is written entirely around the treatment phase of a PI case — providers, appointments, treatment gaps, symptom capture. Eight practice types carry their own pages: personal injury, workers compensation, bankruptcy, mass tort, employment, criminal, immigration and family law. The vendor also states real limits, which is rare: enrolment is optional per client and firms are advised to start with active-treatment soft-tissue cases and to exclude clients unlikely to respond well to text outreach, naming elderly clients and catastrophic-injury cases. B rather than A because firm segmentation is absent — nothing addresses solo versus large firm, in-house or government use — and the practice pages beyond personal injury are not evidenced as deeply as the core.

No located term or policy addresses whether client content is used to train models. The privacy notice of 17 July 2025 was read in full and does not mention artificial intelligence, models or training anywhere. The home page, the Data and Agentic AI solution listing, the security commitment page, the Terms of Use and its Limitation on Liability subpage were also checked on 1 September 2026. No law firm customer agreement is published. The Terms of Use are split across roughly two dozen subpages, of which a Contribution License subpage exists and could not be retrieved; that is the rebuttal route and nothing is graded against the vendor for it.

No located term or policy addresses whether client content is used to train models. The full Terms and Conditions, the privacy policy of 12 September 2022, the home page and the AI case agents page including its compliance and FAQ sections were read on 1 September 2026, and none mentions training. One clause runs toward the vendor and a buyer should read it: clause 9.1 has the customer unconditionally and irrevocably assign to Provider all right, title and interest in Resultant Data, a term defined only in a separate Definitions Exhibit at hona.com/definitions that was not retrieved. Recorded as silent rather than permitted because no located term expressly reserves a right to train.

Retention is acknowledged and the period is missing from the published document. The privacy notice of 17 July 2025 commits to keeping personal information only as long as necessary for the stated purposes unless a longer period is required or permitted by law, and then states that no purpose in the notice will require keeping it for longer than, with the sentence ending there and no figure supplied. Deletion or anonymisation is committed to once no legitimate business need remains, with information in backup archives isolated from further processing until deletion is possible. Nothing separately addresses retention of client messages, AI-drafted replies or translations.

Retention is acknowledged and no period is given. The privacy policy commits to keeping personal data as long as the services are provided and afterwards for legal and reporting obligations, without a period. The Terms are more specific at the end of the relationship than during it: clause 13.4 requires Provider on termination to cease all use of Customer Data and return or destroy it, certified in a signed written instrument, while permitting retention where required by law and in backups, archives and disaster recovery systems until deleted in the ordinary course. Nothing states how long client messages, transcripts or generated treatment records persist while the contract is live, and no customer control is offered.

No located public material addresses ethical walls, matter-level segregation or tenant separation. The security commitment page describes least-privilege development practice, two-factor authentication and employee access discipline, which are internal controls on Case Status staff rather than a segregation model between a firm's matters or between firms on the platform. One published customer account describes co-counsel and branding features, implying some access partitioning, but no document describes how any boundary is defined or enforced. Checked across the home page, security commitment page, privacy notice and Terms of Use on 1 September 2026.

Segregation is asserted at the level of what a user sees, with no published detail on enforcement. The product page states that each case manager sees their own book through per-case-manager dashboards, while also stating that every conversation Lia has is visible to the team and that staff can step into any conversation at any time, which are pulling in different directions and are not reconciled anywhere. No document read on 1 September 2026 describes an access model, a permission inheritance from the underlying case management system, or how any boundary is enforced when Lia retrieves case context through the Chrome extension.

The privacy notice addresses compelled disclosure under a Legal Obligations heading covering applicable law, governmental requests, judicial proceedings, court orders, subpoenas and national security or law enforcement requirements. A separate Vital Interests limb reaches further, permitting disclosure where Case Status believes it necessary to investigate suspected policy violations or fraud, to address safety threats, or to use the information as evidence in litigation it is itself involved in. No commitment to notify the customer or the client, and no carve-out for notice where lawfully permitted, was located on 1 September 2026, and no transparency report is published.

The agreement commits to notice before disclosure. Terms clause 8.4 provides that where a party is compelled by law to disclose the other's Confidential Information it shall, to the extent permitted by law, notify the disclosing party in writing promptly and before disclosing, so that the disclosing party can seek a protective order or other remedy, and shall provide reasonable assistance in opposing the disclosure. It further limits disclosure to the portion legally required. The obligation is mutual and appears in the published customer agreement rather than a policy page. Recorded at the committed tier rather than higher because no transparency report was located on 1 September 2026.

The product does not retrieve primary law, so there is no legal corpus to source. Case Status draws on the firm's own case record synced from its case management system, plus the message history between firm and client, to generate summaries, translations, urgency rankings and suggested replies. No public material identifies any statutory or case law source, licence basis or update cadence, checked across the home page, solution and security pages, privacy notice and Terms of Use on 1 September 2026. Recorded as not addressed because the question does not arise for this product class.

The product does not retrieve primary law, so there is no legal corpus to source. Lia operates on the firm's own case record and on what a client says by text or call about appointments, providers and symptoms. No public material identifies any statutory or case law source, licence basis or update cadence, checked across the home page, product page, privacy policy and Terms and Conditions on 1 September 2026. Recorded as not addressed because the question does not arise for this product class rather than because the vendor declined to answer it.

No citator, and none would apply. The product summarises case progress and drafts client-facing messages rather than citing legal authority whose subsequent history could be checked. Nothing on the home page or the AI feature listings addresses legal authority at all. Checked 1 September 2026.

No citator, and none would apply. Lia produces client communications and structured treatment records, and is expressly configured not to give legal advice or opinions, so there is no authority whose subsequent history could be checked. Nothing on any page read on 1 September 2026 addresses legal authority.

No located public material addresses what the product does when it cannot ground an answer or is uncertain. The AI features are described as suggesting responses, summarising a case, translating a message and ranking urgency, and in each case the published description assumes an output is produced; no confidence signal, no fallback to manual handling and no abstention path is documented. Checked across the home page, the Data and Agentic AI listing, the security commitment page, the privacy notice and the Terms of Use on 1 September 2026. The individual AI feature pages were not opened and are the rebuttal route.

The vendor documents a category of question the system will not answer and describes what happens instead. The FAQ states the guardrail is built in, that Lia never provides legal advice or legal opinions, and that any question touching legal strategy is escalated directly to the assigned case manager. The same section states that a client mentioning they want to stop treatment or flagging a new provider also triggers immediate escalation. That is an abstention path with a defined handoff rather than a confidence score. Recorded as documented rather than demonstrable because no published evaluation or observable test of the behaviour was located on 1 September 2026.

No court order, opinion or disciplinary record naming this product has been located. The AI Hallucination Cases database maintained by Damien Charlotin was searched on 1 September 2026 on the product name alongside general sanctions coverage, and nothing naming the product was found. This is a statement about the public record rather than a finding about the product. Case Status generates client communications rather than citations to legal authority, so the failure mode this signal tracks is not one the product exhibits.

No court order, opinion or disciplinary record naming this product has been located. The AI Hallucination Cases database maintained by Damien Charlotin was searched on 1 September 2026 on both the company name and the agent name Lia, alongside general sanctions coverage, and nothing naming the product was found. This is a statement about the public record rather than a finding about the product. Lia produces client correspondence and treatment records rather than citations to legal authority.

No located public material engages with bar or ethics guidance. ABA Formal Opinion 512 is not named and no state bar opinion appears across the home page, security commitment page, privacy notice, Terms of Use or Limitation on Liability subpage, checked 1 September 2026. The gap is worth naming because the product operates in the area bar guidance speaks to most directly for this category: communication with represented clients, solicitation of reviews and referrals, and the firm's supervisory duty over messages sent in its name.

No located public material engages with bar or ethics guidance. ABA Formal Opinion 512 is not named and no state bar opinion appears across the home page, the AI case agents page, the privacy policy or the Terms and Conditions, checked 1 September 2026. The vendor does name two statutory regimes it operates under, HIPAA and TCPA, and Terms clause 3.1(c) places responsibility on the firm to obtain client approvals for automated text messages, but neither is engagement with the professional responsibility guidance its buyers are bound by.

Public materials claim time and capacity savings, including that up to 80% of routine client communication is handled automatically and that firms doubled caseload or grew 40% year over year without proportional staff increases, without addressing how AI-assisted work should be recorded or disclosed on a bill. No audit record of which client communications were AI-drafted or AI-translated is described. The question is attenuated for the contingency-fee practices the product mainly serves, where the fee does not turn on hours, but it is not absent, since the same firms bill costs and handle fee petitions in workers compensation and disability matters. Checked 1 September 2026.

Time savings are published prominently and the billing consequence is not addressed. The product interface advertises hours saved per week and the site claims Lia manages 2,000 clients at once. The FAQ raises the question directly, asking how pricing works and whether the cost can be passed through to clients, and answers it by referring the buyer to a sales rep and noting how other firms handle it. That is technology cost pass-through rather than treatment of AI-assisted work on a bill, which is the distinction this signal turns on. No audit record identifying which client communications were AI-generated is described. Checked 1 September 2026.

No located public material supports a client-side disclosure obligation. No subprocessor list is published anywhere on the site, no model provider is named, and no trust centre, disclosure pack or client-facing consent material exists. The security commitment page describes the SOC 2 audits and names the auditor but offers no artifact a firm could forward. Checked across the home page, security commitment page, privacy notice, Terms of Use and Limitation on Liability subpage on 1 September 2026. Notable because the platform holds attorney-client communications by its own description.

The material exists behind a request. The compliance section states that full documentation is available on request and that the SOC 2 Type II report is available on request, and no subprocessor list is published anywhere on the site. Terms clause 1.6 reserves the right to engage subcontractors to perform the Services in Provider's discretion without naming them or notifying the customer, and no model provider is identified, so a firm could not evidence whose systems see client content without contacting Hona. Checked 1 September 2026.

No located public material addresses court disclosure or AI-use certification. Nothing describes an exportable record identifying which messages were AI-drafted or AI-translated, which model produced them, or who reviewed them before sending. Checked across the home page, the Data and Agentic AI listing, the security commitment page, the privacy notice and the Terms of Use on 1 September 2026. The product generates client correspondence rather than court filings, so a standing order would rarely reach it directly, though the same record would answer a firm's own supervisory question about what was sent in its name.

Some elements of a record exist without a disclosure-oriented export. The product page states every conversation Lia has is visible to the team, that escalations carry context including what happened, what she tried and what the client said, and that calls placed from the dashboard are recorded, transcribed and fed back, so what the AI sent and what the client replied is captured and attributable. No model is identified against any message, no human verification step is recorded, and nothing describes an export framed for a disclosure obligation. Checked 1 September 2026. The product generates client correspondence rather than court filings, so the question rarely reaches it directly.