Skip to main content

Changelog

Stay up to date with the latest additions and improvements to Quilia.

77 releases in total.
  1. Attorney Portal v2026.10.268iOS v2026.10.5Android v2026.10.5Extension v2026.10.4

    By Kenny Eliason

    October: Clients Reach You from Anywhere, Rides and Mileage, and Neostella

    This roundup covers the month of October: portal releases 2026.10.8 through 2026.10.268, app store releases 2026.10.1 through 2026.10.5 with their over-the-air updates through October 31, and CaseConnect extension releases 2026.10.0 through 2026.10.4.

    The short version: clients can reach your team from a browser or by email, not only the app. A client can ask your firm for a ride to an appointment and keep a mileage log without a notebook. And Neostella joins the case management systems Quilia works with, while importing cases from any of them takes fewer clicks.

    Clients can reach you from anywhere

    Many clients never install an app. They can now use app.quilia.com as a full client website, with the same Home, Appointments, Prescriptions, Providers and Settings screens as the app. CaseChat is on the website too, with live updates, a typing indicator, attachments up to 25 MB, and a "Your legal team" strip showing each person's photo, name and title.

    Email works as well. When a client replies to an invitation or a new message email, the reply goes to ℚ instead of an inbox nobody watches. ℚ saves the message and any attachments to the case, answers by email, and passes anything only your team can handle to your team. A client who has no push notifications and no phone that takes texts gets your CaseChat messages by email. When a client answers your message by text, the reply now lands in that CaseChat conversation.

    On your side, the CaseConnect extension now actually notifies you when a client sends a CaseChat message. Each message gets its own alert, and clicking it opens that conversation.

    Rides and mileage

    Getting to appointments is one of the most common reasons treatment stalls. With Ride Requests turned on for a case type, a client taps Request a ride in the app, gives the destination, appointment time and pickup address with 24 hours' notice, and your case team gets an email with everything needed to book the ride. Requests are listed under the case's Incident → Rides tab. Ride Requests is off until your firm turns it on.

    Mileage is now tracked where it happens. After a client confirms they went to a visit, the app asks "Did you drive to this visit?" and logs the trip with the driving distance filled in. A client can also photograph a paper mileage log, and Quilia reads the trips from it. You'll find every trip on the case's Mileage tab, with a PDF or CSV export ready for the demand.

    On vehicle case types, the app has a new Vehicle tab. Rental is now Transportation, which covers the rental car, time without a car, mileage and rides.

    More case management systems, fewer clicks

    Neostella is connected end to end. Projects import as cases, new projects and stage changes come in automatically, and Quilia writes the activity feed, CaseChat, documents and staff back to Neostella. Uploads go into a Quilia folder on the project, and you can rename that folder.

    Importing is faster everywhere:

    • Import by phase: choose phases (or matter types in Smokeball, and case types in Neostella and Filevine), see how many open cases each one holds and how many are already in Quilia, and decide whether to invite those clients.
    • Pick from a list: Import Existing Case now searches your open cases in Smokeball, Neos, Clio, MyCase, Filevine, SmartAdvocate and CasePeer, so nobody has to paste an ID. CasePacer gets Import Existing Case for the first time.
    • Faster sync: connected systems are checked every five minutes, and a case re-syncs only when your system reports a change.
    • Minors: a child who shares a parent's phone imports as their own client, with the parent added as a delegate. How importing minors works.
    • Smokeball court dates: court dates can become appointments on the client's calendar, with their own reminder texts in English and Spanish. A per-firm switch turns this on.

    Also new

    • Providers on Quilia: an Invite button on the Providers page asks a practice to claim its free listing. A claimed practice's profile, office hours and updates (bills, payments, appointments) show up on your cases. What happens when a provider joins.
    • Shared by Provider: the case Uploads area has a new tab for files a practice shared with your firm.
    • Head injury banner: a possible head injury shows a banner on every tab of the case, with one Mark handled button that records who handled it.
    • Score requests by text and email: "Ask for a score" automations can reach clients the app can't. A client who scores you 9 or 10 gets your Google review link.
    • Payments in the app: clients can open Pay Legal Fees to see their balance and invoices and pay through your firm's payment link. It's set per case type.
    • Export My Case: clients can save a PDF of everything on their case from the app's settings.
    • Visit check: with the client's permission, the app notices a visit to a provider and asks "Did you go?" Nothing reaches the case until the client says yes.
    • Family law: Assets, Debts and Income each get their own tab, and the app shows a Court Calendar on family law cases.
    • Smarter uploads: files can be filtered by document type, people and topic.
    • Tap buttons in forms: a short-choice question shows clients buttons to tap, and existing forms switched over on their own.
    • One place for templates: forms, documents and task lists each have one page, templates first, and you can copy an existing one.
    • Phase Messages folded into Automations: the old page is gone. Every message it sent still runs as an automation.
    • Import FAQs: bring your firm's FAQs in from a PDF, Word file, image, pasted text or a link.
    • Sample client: "See what your clients see" in Settings sets up a test client you can sign in as.
    • ℚ: it writes to each client in the language on their profile, says plainly that it's a digital case assistant when asked, and follows family law and estate guidance instead of injury questions. It also handles "stop texting me" with one confirmation and records care that's on hold, with the reason, instead of marking it missed.
    • Speed: the portal server now runs next to its database, so pages load noticeably faster, and the Cases page loads only what's on screen.

    Bug fixes and stability

    • Live chat in the app: new messages show up in an open conversation within seconds, and translations appear without reopening the chat.
    • iPhone uploads: a crash on upload is fixed, iCloud photos upload again, and long uploads keep their files.
    • CaseConnect sign-in: a crash that stopped sign-in in extension 2026.10.3 is fixed in 2026.10.4. Visits and providers staff add from the panel are now recorded under the staff member, so the client is notified.
    • Texted photos reach your CMS: photos clients text in are now uploaded to your case management system.
    • CasePacer imports: firms whose imports had stopped get them again.
    • Filevine documents: sync no longer drops documents Filevine briefly withholds.
    • Large firms: the Cases, Dashboard, Providers and activity pages stop timing out.
    • Signatures: typed signatures appear in the signed PDF.
    • Quiet hours: texts no longer go out late at night to clients with no time zone on file.

    Security work continued through the month: the extension's libraries were updated to clear two critical advisories, and deactivated staff lose access the moment they are deactivated.

  2. Attorney Portal v2026.10.7iOS v2026.10.0Android v2026.10.0

    By Kenny Eliason

    September: ℚ for Every Firm, Your CMS Both Ways, and Alerts That Reach Your Team

    This is the first of our monthly roundups, so it covers a full month: portal releases 2026.9.15 through 2026.10.7, and two app store releases, 2026.9.1 and 2026.10.0.

    The short version: ℚ started September as a pilot and ends it on for every firm, answering clients by text as well as in the app and writing what they say into your case file. Quilia reads your case management system more deeply and now writes back to it. Your case team hears about the moments that need a person. And the family members helping a client can finally do something about it.

    ℚ works for every firm, by text or in the app

    ℚ, the guide that reads a client their own file, is now on for every firm.

    Clients don't need the app to use it. They can text ℚ, and a text lands in the same conversation as the app. ℚ replies on whichever channel the client last used. A photo or PDF sent by text becomes a document on the case, and a client with more than one case is asked which one they mean. Calls to ℚ's number are answered too, with your office number and a follow-up text.

    In the app, ℚ moved onto the home screen as a conversation that stays put. The questions the app used to ask on a separate screen now arrive in that thread one at a time. Before, 84% of those questions were never answered.

    What matters most for your team is where the answers go. When a client tells ℚ about a visit, a provider, missed work, an employer, insurance, a police report, a witness or what happened to their car, ℚ writes it to the right place on the case. The client gets a receipt they can undo. Anything ℚ can't place becomes a case note in the client's words. You can read the whole conversation on the case. After each conversation, ℚ also writes one short summary note, which syncs to your case management system like any other client note.

    ℚ also reads your side of the file. It reads your firm's case notes from Filevine, Clio, MyCase, Neos, CasePeer, CasePacer, Salesforce and FileMaker, so it knows where the case stands before it answers. It hands questions about money, fault or treatment choices back to your team, with buttons to message, call or email your office. See how Quilia uses AI.

    Your case management system, both directions

    Your own fields come in. Clio, MyCase and Salesforce now have custom field mapping, as Neos and Filevine already did. Mappings are set once per firm and can be suggested from your own cases. Clio, MyCase and Filevine re-read cases nightly, so a change made in your system reaches Quilia without anyone touching the case.

    What clients add goes back. When a client adds a provider, Quilia can write it into Filevine as a contact and medical entry, into Salesforce or Litify on the treatment list, or into CasePacer as a medical provider party. It's off by default, with a switch on each integration's page.

    More of your systems are covered.

    • CasePacer runs entirely on its API. Cases import every 15 minutes, and notes and documents are written back to the file.
    • A firm can connect more than one case management system, and each case reads from the one it's linked to.
    • A client update that fails to reach CasePeer, Clio, Salesforce, Litify or SmartAdvocate is retried instead of being marked sent.

    Documents land where your office works. Quilia files into your own folder structure in Dropbox, SharePoint and now Google Drive, with a naming pattern you choose. You can pick a client's existing folder, and each file shows whether it synced.

    Your team hears about the moments that need a person

    Most of what clients tell Quilia can go straight into the file. Some of it shouldn't wait in a file at all. When a client says something that needs a human, the case team now gets an email that quotes the client. That covers a client who has just been hurt or is heading to the ER, a client who doesn't feel safe, signs of serious distress, treatment that has stalled, and evidence of a possible head injury. The head-injury email has buttons to record what your team decided.

    To make sure those emails reach someone, Settings → Team has an Every Case option that puts a staff member on every case, including open ones. The activity feed also shows who was emailed about each event, and flags "nobody" in amber.

    The people around a client can act on the case

    A spouse, an adult child, a power of attorney: the people who help a client used to be added only by the firm, and almost never were. Clients can now add and remove these case delegates themselves in the app, as View only or Collaborator. Delegates are free.

    A delegate now sees what your firm has asked the client for. A Collaborator can fill in requests, sign them and check off task lists. A View only delegate can read them. A Social Security number is never something a delegate can enter: those requests wait for the client.

    Two more ways for clients to reach you shipped in the 2026.10.0 app:

    • Book a Call: when your firm connects Calendly, clients can book time on the firm's calendar, or with one person on their team.
    • Text my team: a client whose firm has CaseChat replies off can start a group text with their case team, and the thread is filed onto the case.

    Also new

    • Group texts in CaseChat: a group text with a client is captured into the case's CaseChat thread, photos included. Learn how.
    • Texts that ask a question: every automated text to a client now comes from ℚ, asks one question and invites a reply. Texts that ask a question get 16 to 25% replies within a day, against 0 to 6% for texts that only inform.
    • Invitations from ℚ: the invitation introduces ℚ by text and email. Follow-ups go out the next day at a different time of day each time, and stop once the client joins.
    • Zapier 4.0: "Sign in with Quilia" replaces API keys. The update adds Find Case and Find Client searches, plus New Document and Case Phase or Status Changed triggers. Zapier integration.
    • One cases list: a single list with a row per client replaces the separate clients list.
    • Providers from the Quilia directory: case providers take their address, phone and specialty from the directory, so clients see an office they can reach. ℚ confirms which office by street before adding one.
    • Property damage recovery: the incident page tracks recovery status, offers, settlement, GAP coverage and repair estimates.
    • CreoRx prescription cards: firms can send a complete enrollment to CreoRx, approve client card requests, and get cards to clients within the hour.
    • Missed work over several days: a client can record time off that spans days, and verification letters show the range.
    • Mental Check-in: clients can log how they feel with a tap, next to the physical check-in, and it shows on the treatment chart.
    • Preferred names: clients can give a preferred name for ℚ and their messages, without touching the legal name on the case.
    • Reputation opens on All time: it covers your full Google review history.
    • Messaging in the sidebar: Outbox, Automations and Audiences are listed under Messaging.
    • Per-client invoices calculate sales tax: Stripe works out the tax from your billing address.

    Bug fixes and stability

    • App notifications: the conversation open on screen no longer buzzes the phone. Reading a conversation on one device quiets the others.
    • Uploads: a multi-page scan uploads as one PDF, and an interrupted upload no longer leads clients to send the same file twice.
    • Appointment times: the app never records a time the client didn't give, and a past visit asks one question (attended, missed, rescheduled or canceled).
    • Accident dates: imported accident dates no longer lose a day, and affected dates were restored.
    • Smokeball: chat export works again, and contact edits made in Smokeball reach Quilia.
    • Duplicates: duplicate providers and insurance merge on their own, and imports stop creating them.
    • Speed: the cases list and activity pages load faster at large firms.
    • Dark mode: the app uses one color palette, so light patches no longer leak into dark screens.

    Security work continued through the month. Case files open only for people on the case, only admins can change roles or integration settings, and every Zapier, Claude or ChatGPT connection is tied to a single firm.

  3. Attorney Portal v2026.9.14iOS v2026.9.0Android v2026.9.0

    By Kenny Eliason

    Quilia on the Web, an App for Every Case Type, and a First Look at ℚ

    Your clients can now use Quilia from a computer, not just a phone. The app stopped being a personal-injury app that other case types borrow: probate and vehicle property damage cases get a workspace built for them. Your case management system's own fields, the ones your firm built and fills in every day, reach Quilia instead of being guessed at. And ℚ, a guide that reads a client their own file, begins its pilot with clients able to answer it back.

    Those first, then everything else.

    Quilia works in a browser

    Clients have been asking for this one directly: some work is simply easier on a computer than on a phone, and uploading documents is top of that list.

    Now they can. Clients sign in with the same phone number they use in the app and do the desktop-shaped work from a browser: send documents by dragging them off their computer, read messages from your team with pictures and attachments rendering properly, and work through forms, signatures, file requests and checklists.

    Nothing changes on your side. Everything a client does on the web lands in your portal, your activity feed, and your case management system by exactly the path the app already uses, document analysis included. A client with more than one case now sees each named by your own case type, date of injury and stage, rather than a list of identical rows.

    One thing behind it is worth knowing: request links now open behind the client's own sign-in rather than a public page anyone holding the address could fill in, so the link is no longer the credential.

    An app that fits the case your client actually has

    A store release, so everyone gets a fresh binary from the App Store and Play rather than a background update. It carries everything published over the air since early August, plus the work that needed a native build.

    The through line: Quilia stopped being a personal-injury app that other case types borrow. Probate clients get a workspace organized around administering an estate, bringing together assets, debts, beneficiaries, executors and heirs alongside the documents and tasks that already existed. A vehicle property damage case gets its own two tabs and the twelve things that matter to a damaged vehicle, with no pain scores anywhere in it. Every case type now carries its own icon rather than sharing a fallback.

    Your firm's symptom list is finally the one clients see. The Symptom Tracker offered Quilia's built-in list no matter what you had configured, so a curated list was ignored on the client's phone. It now reads your per-case-type settings. A symptom added by mistake can also be removed outright, rather than only "resolved". Resolving says I had this and it went away, which on a mis-tap writes a lie onto a damages exhibit.

    Two more worth knowing. A client can correct an AI suggestion in place rather than declining the whole card over one wrong character, with the original answer and the correction both kept. And an email address your firm already has on file now works for sign-in, so a client who gets an email notification is no longer stopped at a screen their email could not open.

    Your own case fields, mapped by you

    Every firm's case management system is shaped differently, and Quilia used to guess at yours.

    For Neos it read a fixed set of standard columns and looked for tabs by their stock names. If your firm had renamed a tab, or built your own, none of it matched, and the fields your team actually fills every day went unread while the stock equivalents sat empty.

    You pick the fields now. Your own fields appear grouped under your own tab names, and tabs your case type does not use are left out rather than offered and never filled. Mapped values only ever fill a blank, so nothing you have already entered in Quilia is overwritten. Reading them costs no extra request: they ride the search Quilia already sends on every import and sync.

    The same mapper covers Filevine fields and case types, and you can apply a case type to the cases you already have rather than only new ones. Neos firms can also map their contact types to treating providers, employers and police departments, route imported cases to the right office from one Neos field, and have insurance, providers and police reports stay current instead of being read once at intake and never again.

    ℚ, now in pilot

    ℚ is a guide that reads a client their own file and writes them a short daily note about it. Not an answers engine, and never a substitute for talking to you: ℚ will not discuss fault, insurance, liens or what a case is worth, and it never tells a client their case has ended. That news comes from a person.

    What is new is that clients can talk back to it. A client can tell ℚ about a visit, a new provider, a prescription, a pain score, a symptom or a diagnosis, and confirm it with one tap. ℚ asks whether they made it to a visit and records the answer. It asks whether they are still treating or were released. Everything it records lands on the case the same way anything else does.

    This is a pilot. ℚ is rolling out to a first group of firms while we watch how it behaves, and every change to how it writes is tested and graded before it reaches a client. If you want your firm in the next group, ask your account contact to put you on the list.

    The rest

    • FileMaker: activity reaches Chronology with its documents attached, firms can switch on their own imports, delivery retries back off on their own schedule so one held-up item does not slow the rest of your firm's activity, and any item can be resent with one button.
    • Document sharing now reaches Filevine and CasePeer, and clients hear about a shared document right away.
    • Plain-language case status: status cards explain what the current part of the legal process means rather than repeating your internal phase label, and say nothing at all when there is no reviewed explanation to give.
    • Provider addresses now carry Google's own classification, so a geofence stops treating an insurance head office as a place a client is being treated.
    • Injury narratives from your CMS are read onto the body map instead of being discarded.
    • Invitations: one progress bar with something to say to the client while they wait, and clicking Invite several times no longer texts the client again or starts a second import.
    • Failed imports name the client instead of a bare matter id, and the email about a client who cannot sign in now goes to the staff on that case rather than every administrator, names the case by your own case number, and opens the screen where you fix it.
    • Appointments a client confirms are saved to the case, and CMS notes lead with what happened instead of a constant subject line.
    • CaseChat stays reachable in the sidebar, so a firm that switched it off can switch it back on.
    • In the app: documents your team shared are marked as yours and cannot be deleted by the client, a file shows every place it is attached on the case, messages linking to Case Notes and other screens land where they say, and clients can reach their legal team straight from a message or help topic where CaseChat is on.

    Fixes across the range also cover recurring automations keeping their schedule, phase messages firing only on real phase changes, case update emails sending once, insurance duplicates across CMS imports, and picking a location for a team member who has none.

  4. Attorney Portal v2026.8.33iOS v2026.8.1Android v2026.8.1Extension v2026.8.4

    By Kenny Eliason

    Clio Documents for Clients, Notifications You Can Actually Read, and Every Case in the Panel

    Fourteen portal releases, two client app releases carrying nine over-the-air updates, and five extension releases. Four things worth your time, then the rest.

    Your documents reach your client

    Documents have only ever moved one way: your client sends you theirs. Now yours can go back.

    Turn on Share Clio Documents with Clients in your Clio integration's General settings, and anything your team puts in a matter's folder named Quilia appears in that client's documents. They run through the same AI analysis as everything else, stay read-only, and never sync back. Off by default, per firm.

    In the app they are marked as yours. A shared file reads Shared by your legal team, carries a scales of justice badge on thumbnails, and opens under the filename you gave it rather than a description the AI guessed at. Clients cannot delete them. Until now a firm-shared document looked exactly like a client's own upload, right down to long-press-to-delete.

    Notification emails carry the message

    A new-message notification used to hold the message behind a sign-in prompt, which made every notification a dead end for clients who don't use the app. The message now ships in the email itself, for every firm, with your logo in the header.

    The view count changed with it. A client who reads everything in their inbox and never opens the app used to show zero views, indistinguishable from one ignoring you. Opening or clicking through from the email now counts.

    The extension shows every case you have

    The case list in the browser extension was really a list of chat rooms. A case with chat switched off matched nothing and vanished: 917 of 15,907 active cases hidden, and at firms with chat off entirely, roughly 7% of the caseload visible.

    It is a list of cases now.

    • My Cases reaches every assigned case. It filtered a single page of the firm's rooms sorted by chat recency, so an assigned case nobody had chatted about lately was never in the data being filtered.
    • Search covers the whole firm, matching client name, case name, case type and CMS case ID. The largest firms were searching under 10% of their cases.
    • Cases are named after the client, not the case type, so three people no longer appear as three rows reading "personal injury".
    • Chat controls sit in the case header, matching the portal: Enable CaseChat on a case with chat off, Join CaseChat on one you are not in. Selecting a case now opens its activity feed instead of quietly creating a room.
    • Blank conversations are fixed. Four faults were stacking into one dead chat, the worst a frozen access token retrying against a dead credential. Your messages now appear the moment you send them.
    • The panel stops losing track of which case you are on. Chrome shuts down an idle extension worker, severing the connection that hears about tab changes, and nothing reconnected. It reconnects now and replays what it missed.

    Uploading from the app works

    Uploading is the thing your clients do most, and it was failing several ways at once, none of them loud.

    • Videos send. iPhone video upload had failed since April, because it held the whole file in memory first. Uploads stream from storage now and keep running when the client locks the phone. Videos kept in iCloud download on demand.
    • Files arrive one at a time, instead of eight photos sitting at 100% waiting on one video.
    • A file is recorded once, and only if it arrived. Recording was two steps taken on trust, so storage could record a file that never landed, or the same file twice.
    • Videos play, and thumbnails are framed correctly rather than magnified into a close-up of a numberplate.
    • Files loads quickly. Nothing had ever generated a thumbnail, so every tile downloaded the full-resolution original and resized it on the phone.
    • A camera button on every screen, floating above the Files tab, opening the same Camera, Scan, Gallery and Files chooser. Uploading used to be a tab and a button deep.

    What clients could not see

    Files stopped hiding documents. The screen filtered against a hand-written list 14 document types behind the database and silently dropped anything missing from it. Every estate document type was on that list, so a trusts and estates client who uploaded a will could not see it. So were request-completion PDFs and both types the car-accident checklist asks for. Separately, a case with more than a thousand files showed only the first thousand.

    The right document clears the checklist item. A correct, correctly-classified upload could still read as outstanding, because your name for it and the classifier's name for it were synonyms. On one car-accident case type that was 2 of 8 items. Matching is by meaning now. Three equivalences were removed in the same pass: a utility bill could clear a medical-bills item, and a passport could stand in for a driver's licence.

    Confirmation stops asking about work that isn't waiting. A case with 6 things to review said "Item 1 of 33", several cards blank, because every record ever created was being shown. The queue and the home badge now read through one filter. The card also asks rather than grades: "Add it to your case?" with Add to Case and Don't Add, replacing "Is this right?" under a button saying "Looks Good".

    Messages you can trust

    Open Sent at a firm with ten thousand messages and it said "645 messages", a count of rows on screen. Search a client and it said nothing found, which reads as we never wrote to them, when the search only looked inside the newest thousand.

    • Every message is its own row. Sent folded messages by the rule that produced them, so one automation reaching six people drew as a single line wearing the first recipient's name and photograph.
    • Dates run in order, sorted in the database rather than by whichever message led a group.
    • Your whole history is reachable and searchable. At a firm with ten thousand messages, only the newest thousand could be opened.
    • Each automation has its own Messages tab showing what went out and what is queued.

    Automations that send what you meant

    The portal let you build an automation, tick "Send a message", leave the body empty, and save. It ran on schedule and delivered nothing. The editor now refuses to save a message with no subject or body, and automations saved before this are worth a quick check.

    • Clients who asked not to be messaged are checked again. That check didn't survive the move of phase messages onto automations. The check now sits at the single point every send passes through rather than in each audience.
    • Settled clients are off phase mailing lists. Status and case stage only agreed in one direction, so a client finished in February kept advancing through stages all spring. Closing stages stay unfiltered on purpose.
    • A client who leaves an audience no longer gets the queued message.
    • You can move when an automation fires. The scheduling controls weren't in the automation tools at all, and the only route to a corrected send time was deleting and rebuilding, losing the copy and every translation with it.
    • Feedback automations stop looking broken. An automation that asks for a rating has no subject or body on purpose, since the content is assembled when it sends. It was displaying as blank, which looked identical to copy that had failed to save.

    FileMaker, CasePacer and Neostella

    FileMaker is now an integration, with guided setup and its own settings page. An import brings in the case detail, not just names: accident date, time and location, treating providers, insurance, injuries, employment and property damage. Medical visits arrive as appointments attached to the provider each visit was with. Anything the client already entered is left alone.

    CasePacer works without an API. A case is matched by the ID inside the filing address you paste in, the same ID its URL carries, and the extension offers a one-button import that reads the case off the page: client, contact, phone, email, address, title, phase, accident date, statute of limitations, attorney, paralegal, defendant and description.

    Neostella pages are recognized too, kept distinct from Neos.

    Cases your CMS turned away are visible. A case carrying an unmapped type is turned away, and only MyCase and Filevine ever recorded it. Clio, Neos, SmartAdvocate, Salesforce, Smokeball, CasePeer and Zapier now do, and the Case Types table shows "N new cases missing out on Quilia" under each.

    Case management

    • Some people belong on every case. Your CMS decides who hears about a case, which has no answer for the office manager who touches every file and is attorney of record on none. Settings, Integrations, Staff on Case now has an Always on every case list. At one firm the admin who does all the imports held zero case memberships, so the activity log read "was invited to Quilia by" her name and sent the digest to someone else.
    • Staff you add to a case stay on it. On Clio, MyCase, Neos, CasePeer, Salesforce and SmartAdvocate, a colleague added by hand was removed on the next sync, usually within the hour, with no error.
    • CaseChat, per case. The firm-wide switch couldn't represent chat on for some clients and off for others. Staff toggle it per case now, and chat enabled for one case actually reaches that client, where before it was gated firm-wide and simply never appeared.
    • A focused workflow for vehicle property damage. These cases fell through to the injury experience, so a client with a damaged car and no injuries got pain scores and appointments. The portal now shows Vehicle, Repairs, Rental, Towing and Storage on the Incident tab, and the app gives the client the twelve things that matter to a damaged vehicle. Tow and rental receipts and body shop estimates classify automatically.
    • Symptom checklists per case type. Case type settings has a Symptoms tab for picking exactly what a case type asks about. The app reads that choice now, where before it showed the built-in list regardless of what you configured.
    • Print the filtered view. A Print entry at the top of the cases table's View dropdown prints every filtered row with the visible columns, not just the page on screen.
    • Know what languages your clients read. The firm profile reports the real distribution. Regional variants count together, and clients with no language recorded show as unset rather than being dropped.
    • Case Members is now Case Team, and clients on a multi-claimant case read Clients.
    • Your own office is one of your locations. The Locations API listed every office except the main one. 51 of 79 firms have a main address and no others, so for most firms the API returned an empty list.

    Fixes worth naming

    The incident screen was deleting the time your client gave you. The Time field on Edit incident details rendered empty whatever was stored, and saving erased the client's answer. The app then asked again, because the only thing clearing that task is a time being present. Of 175 affected cases, 118 have had the time restored; the other 57 are left blank, because on a liability field a time on the wrong day is worse than none.

    Neos phase syncing is fully restored. The org-wide sweep that walks every open case and asks Neos whether its phase moved had stopped running. Phases kept arriving for cases Quilia was already watching, so this affected cases that changed quietly in Neos with nothing else prompting a look. Firms on Neos should see those phases correct themselves, including on older cases, and it is worth a glance at any case whose phase looked stale.

    Links in your messages stop flashing a "not found" screen. Every quilia.com/app/... link opened against a route the app didn't recognize: a steady trickle of not-found screens. And a message can now link to Providers, Documents or Ask a Question, the three destinations firms most want and the three that previously opened on Home with no error at either end.

    83% of workers comp insurance was filed as "Other". The AI read the carrier, policy and claim numbers correctly and never recorded the coverage type, so a field defaulting to "Other" made a good answer look unclassifiable. Workers Compensation is a real category now, in both the portal and the app.

    Duplicates. A provider with no name was copied onto a case on every appointment. Appointments, insurance and employment now match on a partner's own ID, so a re-push is safe.

    Smokeball case creation was sending no staff invitations at all, silently, from a mismatched field name. MyCase document uploads stopped failing with a signature error.

    For your intake partners

    An entire case can be pushed in one request. POST /v2/cases accepts the incident, damage, providers, policies, employment and staff alongside the case, where it used to take eight round trips, and one bad record no longer costs the case: each child validates as it is written and the response says what happened to each.

    The theme is accepting what partners send. Roughly a third of one partner's nightly sync was being refused over input we could have accepted. An unreadable date in an optional field now drops the value and keeps the case, insurance can be recorded before the carrier is known, and contact types accept all 23 categories rather than the 8 the API exposed. Rejections are now recorded with the field that failed, so a partner can see and fix what was refused.

    Privacy and security

    This release includes a set of security hardening fixes from our monthly audit. A client's chat list is now scoped to that client's own conversations rather than to the firm. The voice option on the sign-in code screen only calls a number belonging to a real account, and a hardcoded fallback number was removed from the app. The MyCase connection settings endpoint now requires a signed-in admin at the firm in question. The tables holding manual and AI-suggested labels on an upload are now covered by row-level security and scoped to the owning firm, with catalog changes limited to admins.

    Alongside those: deactivating a firm member now ends their browser extension access, test environments redirect all client messaging to an internal recipient by default, and diagnostic breadcrumbs were narrowed to screen and identifier only, carrying no contact details.

    Also fixed

    • Deactivated accounts no longer loop at sign-in. The sign-out never took effect, so the next click put the person back where they started.
    • The welcome message stops promising a reply. The default copy invited clients to "just reply to this message". There is no reply button, and no error either, so a client who tried concluded their firm had ignored them. Firms who wrote their own are untouched.
    • A sync that half-failed no longer reports complete success.
    • Phase message migration carries everything, including phases you wrote copy for but never armed, and arrives switched off so the timing is yours.
    • Prospect conversations reach the CRM.
    • Chat log exports run on the export setting alone. Firms with exports on but the new-case CaseChat default off were exporting nothing.
    • Video analysis works again, and large videos stream rather than loading whole into memory. Audio transcription moved onto Vertex Gemini.
    • Document uploads no longer hold whole batches in memory. One 113 MB video peaked near 570 MB, killing uploads to Neos and MyCase.
    • Columns stop painting over each other on Case Team and on long client names.
    • Staff with no timezone show "not set" rather than Eastern, which had a western-state firm conclude Quilia had assigned all its people the wrong timezone.
    • New staff accounts stop saving the literal text "not provided" as a phone number. Roughly 800 rows corrected.
    • The video embed tab tells the truth. It advertised YouTube, Vimeo, Loom and Wistia; only YouTube survived the save, and the others showed a player in the editor while the client got a message with no video.
    • Messages sent to a case without a named recipient now reach every client on it, rather than failing every time.
    • Firms running two CMS integrations no longer have phase messages resolving whichever sorted first alphabetically.
    • In the app: the launch crash is fixed, sideways videos fill the screen, incident dates hold their time in every timezone, the inbox loads for long histories, the Wage Loss upload buttons work, a read message stops coming back unread, double-tapping no longer strands clients on a blank screen, prescription attachments show previews, new suggestions appear on pull to refresh, and document signing has a working Save and Close.
  5. Attorney Portal v2026.8.19

    By Kenny Eliason

    Answers That File Themselves, Automations You Can Aim, and Case Emails

    Twelve portal releases in a week. Four things worth your time, and then the usual polish.

    What a client types now files itself

    A client who photographs five business cards gets five provider records. A client who types those same five names into an intake form should get the same thing.

    Now they do. On submit, free-text answers are split apart and routed: doctors to the provider list, insurers to insurance records, past employers to employer and supervisor records. Each runs through the same handler that already owns that destination, so it inherits the same duplicate checking and the same guards a photographed document gets.

    There is no new step for your firm. No field tagging, no mapping screen, nothing to configure. The question's own wording is the mapping, and it carries more meaning than any dropdown label would.

    Medical documents also review better. A document now produces one card per kind of thing it found, so a provider, four injuries and two prescriptions are three separate questions you can answer independently rather than one Accept button covering all of it.

    Automations you can aim

    Automations shipped last release. This one is about pointing them precisely.

    • Whose name is on the message. The "Send a message" card has a From picker: the firm, or a named member of staff. Changing it reaches messages already sitting in the queue, not just the automation.
    • Which channels it uses. Narrow an automation to SMS, email, or both. Push is always on, since the app is your client's only Quilia surface.
    • Send yourself one first. Pick a client and the message goes out right now, exactly as they would receive it. It runs on the same path as the real send, so language, variables and formatting are the genuine article rather than a preview that could disagree.
    • Count from the incident. The incident date joins case opened, case closed, client invited, phase changed and birthday as a trigger.
    • A variable picker in the editor, on the English tab and every translated tab, so a client's name no longer means typing the exact spelling from memory.
    • Audiences use the case types you actually have, read from your Case Types settings rather than inferred from case history.

    Your case management system, even without an API

    Every integration we have built so far needed an API to build against. Some systems do not have one. What they do have is a per-case inbound email address: anything sent there files itself into the right case.

    Switch on Case Emails in Settings, Features, Integrations. The add-case modal and Edit case details gain a field for that case's address, and the client activity feed is delivered there automatically. Same feed, same window, same duplicate protection as every other integration. Email is the only thing that changes.

    One email per case per run, carrying every new update for that case, sent from integrations@quilia.com and stamped so nothing arrives twice. Two opt-ins bound it: the firm-level toggle, then a pasted address per case.

    CasePacer comes along with it. A CasePacer case email carries the case's own ID, and so does the case page URL, so pasting the address once lets the browser extension match a CasePacer case page to the right Quilia case.

    A form can ask for an SSN without storing one

    Firms have been asking for a Social Security number on intake for a while, using plain text fields because there was nothing better. There is now a dedicated SSN field, and it is a pointer rather than a store.

    The answer is encrypted straight onto the client's own record through the path that already existed, and the form itself keeps no value at all. Nothing downstream has to strip one, because none ever arrives. Revealing it runs through the same audited, admin-only path as before.

    The builder will not save a form that asks twice. Your existing text fields keep working exactly as they do today, and switching them over is your call.

    Set up your firm from an AI assistant

    Your firm's configuration is now readable and writable through the Quilia assistant, not just the portal.

    Intake forms can be built and edited by describing them, which matters most if your intake is a stack of hand-built forms placed one field at a time. Editing happens in place, and forms already sent to clients keep the version they were sent with, so no submitted data moves. Case types can be set in bulk instead of one checkbox at a time, and the setup checklist notices. Staff can edit their own profiles and headshots, and location branding can be set the same way.

    Reliability and polish

    • Appointment reminders reach clients who turned off push notifications. Every reminder workflow now falls back to text.
    • Clio calendar sync says when it needs reconnecting, with a Reconnect button on your integrations page.
    • The Clients page loads for firms of any size.
    • The AI assistant answers from the current knowledge base, now 142 articles.
    • Merge variables with underscores render correctly wherever a message is written.
    • Documents are filed as what they are rather than as "Other," whatever capitalization the AI answers in.
    • Large video files no longer hold up document analysis.
    • The Phase column on the cases list shows the live phase.
    • Insurance documents are told apart. Auto policies, health insurance cards and carrier letters no longer share one bucket, so a photographed insurance card closes the checklist item it was meant to.
    • A utility bill is no longer recorded as a medical expense.
    • Task-list reminders respect a paused firm.
    • Location branding stays saved, and inline images and video keep working past the hour they were written.
    • Automations that ask for something report who they reached.
  6. Attorney Portal v2026.8.7iOS v2026.7.1Android v2026.7.1

    By Kenny Eliason

    Automations, Your Firm Run From an AI Assistant, and Symptom Tracking

    Twelve portal releases (2026.7.26 through 2026.8.7) and two over-the-air updates to the client app. The big one is automations.

    Automations

    An automation is a rule you build once and leave running. It answers three questions, in the order you would say them out loud.

    Who it goes to. An audience, described rather than picked. You set conditions (case status is closed, case type is motor vehicle collision) and a panel shows how many clients that currently describes while you build it. You can also just type what you want in plain English and let it draft the conditions for you. Only the rules are stored, so clients join and leave on their own as their cases move. An audience never goes stale the way a hand-picked list does.

    When it fires. A date plus an offset, across five triggers: the case opened, the case closed, the client was invited, the case last changed phase, and the client's birthday. It reads as a sentence, Send 9 months after the case opened, it goes out at an hour you pick in each client's own timezone, and it can repeat on that same interval. A date already in the past counts as missed and that client is skipped, so switching an automation on never messages your back catalog.

    What it does. An open list of actions. Today: send a message, ask for feedback, or send a form. A message carries a body per language, with a tab per translation you can edit directly. A feedback ask can request an NPS score and, if the client comes back a promoter, ask them for a Google review.

    Two controls for the moment you point one at real clients. Pause holds the queue and tells you how many sends are in it before you confirm. Stop cancels everything scheduled, leaving what has already gone out alone.

    Set up and run your firm from an AI assistant

    The Quilia assistant connector could only read. Now it can write, which means setup is a conversation instead of a form: your firm's name, address, hours, offices, FAQs, brand colors, logo, invite templates and client alert banner can all be filled in by answering questions.

    Setup is just the way in. Once connected, you can ask about cases, look up clients, invite them, and send messages from whichever assistant you already use. It is offered on the first onboarding screen, again when you finish, permanently under Settings, API, and on the dashboard until you dismiss it.

    You can also tell us when it gets something wrong. Most assistant bugs are confident wrong answers rather than errors, so a person noticing is the only detector there is. A report becomes a ticket with the technical detail already filled in, and a guard rejects anything carrying a client's contact details.

    Symptom tracking

    Clients now keep a roster of what they are living with, on the Health tab of the app, each symptom showing when it started and a switch to mark it resolved. The health check-in asks about that roster rather than a blank grid, and a quiet day never resolves anything, because an intermittent symptom is not gone.

    Your side is a Symptoms tab on the case, and it leads with the interval rather than the list:

    numbness, reported 4 March, still ongoing 173 days later

    Ongoing symptoms sort first, then longest running. It works on day one: 2,738 symptoms across 472 clients were seeded from existing check-in history.

    Firms can shape the list itself. From Settings, Symptoms, hide the Quilia symptoms that do not fit your cases, add your own, or upload a PDF or CSV checklist you already use and review what was found before accepting any of it. Hiding only governs what clients can add, never what they have already reported. That editor is off for every firm until you switch on Custom Symptoms.

    Reliability and polish

    • Deactivate a client. Cuts app access and stops every text, email, push and automation, without deleting the case file. One click puts it back.
    • Repeating messages can end. Never, on a date, or after a number of sends.
    • Automatic NPS can ask promoters for a review. Opt in from the cadence box on your Reputation page.
    • Check-in asks repeat until answered, capped at three, and a dismissal now sticks. The police report, insurance and appointment asks were reworded or narrowed after an audit of 3,477 asks.
    • Task-list reminders stop after 21 days, and the cadence screen shows how many reminders you will actually get.
    • The Active Cases group no longer stops at 1,000 clients.
    • Email is a full invite channel. The invite modal has Text message and Email checkboxes, automated invites send by email, and clients with only an email stop landing in Failed Imports.
    • Clients invited by email can add a phone for login from a card on the app's home tab.
    • Signing up with an email that already has an account says so instead of sending you to a confirmation that never arrives.
    • Signing in is faster for everyone, including the mobile app.
    • A firm whose real-time sync has silently died is caught the same day. One sat broken for four months across 34 all-green reports.
    • A connection test no longer calls itself dead on one bad call.
    • Turning off case import asks first, since it silently stops new cases while existing ones keep syncing.
    • No more doubled-up texts on appointment reminders, appointments added for you, and feedback requests.
    • Reminders queued before a case closed no longer fire after it closes.
    • No texts to clients with no phone number. 611 clients were in that state.
    • The daily digest gives each case its own card, and you can mute one case instead of the whole email.
    • Client activity reaches your webhooks at all. 12,817 events in 30 days had been dropped silently.
    • Firm logos render consistently in the app, including dark mode.
    • A client whose firm access ended sees an explanation, not an error.
    • Staff come back with real names in the assistant instead of "Unknown," and lookups no longer cap at 10 results.
    • The provider directory no longer fails on every authenticated page load.
  7. Attorney Portal v2026.7.25iOS v2026.7.1Android v2026.7.1Extension v2026.7.0

    By Kenny Eliason

    Email Sign-In for Clients, Check-Ins on Every Channel, and Smokeball in the Extension

    Ten portal releases (2026.7.16 through 2026.7.25), a full client app release with three over-the-air updates, and four extension releases (2026.5.2 through 2026.7.0) ship together. The headline: email is now a full front door to Quilia, for invites and sign-in alike. Around it, check-ins reach clients on every channel, AI suggestions apply instantly, and the extension gains Smokeball.

    Email is now a front door

    Clients can now sign in with their email: enter the address, get a 6-digit code, done. It is the same passwordless flow as text-message login, and only emails a firm has invited can sign in.

    Invites match. Clients imported with only an email address can now be invited, and clients with both a phone and an email get both sends, attached to one account either can sign into. The invite email leads with your firm's logo and name, offers app download and web access, and ships in 11 languages. Clients whose firm has an email on file can verify it from a home-tab card and turn it into a login, and every sign-in and account email is now Quilia-branded.

    Check-ins reach clients on every channel

    Every case check-in now sends an email alongside the push, saying how many quick items are waiting but never what they are, and falls back to SMS when a client's push channel has gone quiet. "Remind me later" is now a real answer: snoozes are recorded, a recent snooze pauses that day's nudge, and repeated snoozes stop the nudging and flag the gap to the firm instead. Document asks (insurance card, police report, vehicle details) appear only on a case's first check-in, where they actually get answered.

    In the app, a case with an active check-in opens straight into it and walks the client through every item, with each answer recorded with the legal team. Rolling out with pilot firms now.

    AI suggestions apply instantly

    Accepting an AI suggestion now applies it the moment the client taps accept, with lists refreshing immediately. The review cards are clearer too: plain language ("Left Leg" instead of a chart quote), a lead warning when a document appears to belong to someone other than the client, and uploads with nothing to do with the case are quietly set aside instead of becoming a confusing confirmation card. Very large medical-record PDFs and signed request documents now feed the case's analysis as well.

    The extension gains Smokeball, and chat that keeps up

    The Quilia CaseConnect extension can now import cases straight from a Smokeball matter page, joining Clio, Filevine, MyCase, and the other CMSs it already detects, and Smokeball matters display their real matter names and numbers throughout.

    Live chat now keeps up with your busiest staff: updates arrive reliably no matter how many cases you are on. Unread threads stand out with a blue dot and bolded name, an "Unread" filter shows just what needs attention, and chat rows update and reorder live as messages arrive.

    A new HIPAA BAA with Google Cloud

    We signed a new HIPAA Business Associate Agreement with Google Cloud and consolidated every AI feature that touches case data (document, audio, and video analysis, translation, summaries, case memory, message composition) onto Vertex AI, Google's enterprise AI platform, running state-of-the-art Gemini models. One top-tier stack, one covered vendor, enforced at runtime.

    Reliability and polish

    In the portal

    • CMS outages announce themselves: admins are emailed the moment a Clio, Filevine, or MyCase connection drops, if case imports get switched off, or when a firm's new CMS cases stop arriving.
    • CMS fixes across the board: Smokeball webhooks self-heal after re-authentication, SmartAdvocate imports work without the "is client" checkbox, MyCase syncs ride out rate limits, and Salesforce handles heavily customized orgs with reconnects taking effect immediately.
    • Truthful connection tests: saving CMS credentials now validates them for real instead of reporting success from a stale session.
    • Team offboarding reaches cases: deactivating a team member removes them from their clients' cases everywhere, with their work history preserved.
    • Case chat for co-counsel: staff at a different firm than the client can open case chat when they are on the case.
    • Clear Add Case errors: a duplicate phone number now prompts you to add the person as an existing client instead of a generic error.
    • Phase messages in one view: pending and sent tabs with live counts and client-name search across all history.
    • The right words for premises cases: slip-and-fall and product cases say "incident report", not "police report", across check-ins and the incident tab.
    • No empty signature sends: templates without signature fields are held back from the send list until fields are added.
    • Cases close on archive: a case whose last client was archived now closes instead of reading as active forever.
    • One-click unsubscribe: client notification emails carry a working unsubscribe link, no login required.

    In the app

    • Pull-to-refresh works everywhere: every list refreshes, including screens still waiting on data, and seven screens gained it.
    • Steadier under the hood: the top launch-time crash is fixed, and a crash inside one screen shows an error card with retry instead of blanking the app.
    • Cancelled requests disappear: no lingering "Sign here" cards or task lists stuck at "1 of 2 done."
    • Appointments stay honest: date-only visits show no made-up time, hold their day across time zones, and the home tab asks the client to fill in the missing time.
    • Treatment review answers inline: "next visit" and "done treating" right on the provider list.
    • Better on tablets and foldables: free rotation and resizing on Android, with the split-view header fixed.
    • Uploads recover: interrupted large uploads resume instead of giving up, and signed documents always keep their PDF.
    • Offline and edge cases: clear messaging on network dropouts, no more voice-note crash, insurance can be added without a policy number, and web links land on the intended page after sign-in.
    • Every language: payments and vehicle-rental sections show translated text again, and new copy ships in all 24 locales.

    In the extension

    • Case search with keyboard navigation: the case list search is rebuilt on the same command palette as the rest of the platform, matching client name, case type, and case ID.
    • Multi-firm accounts work everywhere: staff who belong to more than one firm no longer hit errors in case lists, chat, team pickers, and settings.
    • An honest unread badge: the toolbar badge counts only rooms in your current firm.
  8. Attorney Portal v2026.7.15

    By Kenny Eliason

    Task Lists That Route Themselves, Case Details You Can Trust, and Reputation That Reads Google Right

    Fourteen portal releases shipping together (2026.7.2 through 2026.7.15). The headline work lets you route a task list and its Clio tasks to whoever actually owns the work, closes a case automatically once every client on it is done, and checks the details a client confirms from a document before they are ever written to the case. Alongside it: the Reputation page reads your Google replies correctly, the provider directory de-duplicates itself and links doctors to their clinics, check-in answers finally take effect, appointment reminders are restored, and a long tail of integration, sign-up, and reliability fixes.

    Task lists route to the right person, and cases close themselves

    This work came straight off a customer call. A firm admin was receiving every task-completion email himself and forwarding each one by hand to the staffer who did the work, with no way to point a task list or its Clio tasks at a specific person.

    Now the routing lives on the task list itself. You pick who owns the list, with an "Email when complete" checkbox, and an "Assigned to" dropdown on each of the two Clio-task steps: the task created when the list is sent, and the one created when the client finishes it. Everything defaults to you, so nothing changes unless you choose someone else. The Clio task lands on that step's chosen staffer, and the completion email goes to the owner.

    To make that routing reach everyone, a new "Sync from Clio" button on the Team page asks Clio for your firm's active users, matches them to your team by email, and fills in the missing Clio ids. Anyone it cannot match shows a small "Not in Clio" tag. The Tasks page also gets the same "..." menu that Signatures and Forms already have, so you can finally resend, cancel, or delete a task, or clear out an old list.

    Separately, a case now rolls up to closed on its own the moment its last active client member closes. Before this, a fully-closed matter kept reading as active everywhere the portal shows case status until someone opened it and pressed Save. One firm had a large batch of cases stuck this way, and those have been cleaned up.

    Confirmed case details are checked before they are saved

    When a client confirms information Quilia found in a document, that confirmation now writes what the document actually says, and only what it says. This bundle closes a series of defects in that pipeline that could put wrong facts into a case.

    An explanation-of-benefits could add a client's health insurer to their case as a treating provider, then queue them to schedule a follow-up with their insurance company. A misread VIN was saved exactly as read, so one case could hold two different numbers for the same car. When the AI could not find a field, it sometimes wrote the literal word "null", and 24 cases ended up with a company on file named "null". An adjuster whose name was the most prominent on a letter could be saved as the carrier.

    VINs are now validated before they are shown or saved and a misread one is dropped, empty is recognized as empty, billing documents no longer create appointments, and Quilia can report that a letter names no carrier instead of guessing at one. Documents describing a single subject (the vehicle, the police report, the client's ID) now build one confirmation card that fills in as more documents arrive, instead of a separate fragment-holding card each. Genuinely separate providers, visits, and injuries stay separate. And the case activity entry for a confirmed suggestion now names the fields that actually changed rather than reporting details that were never saved.

    Insurance is easier to record, and providers are no longer mistaken for insurers

    Recording insurance used to require a policy number, so a client who knew they had Blue Cross but could not find the card had no way to record the carrier, which is the part your firm actually needs. The policy number, claim number, and group number are now all optional.

    The guard that stops an insurance company being saved as a treating provider was also over-matching: it refused genuine practices like "Nationwide OBGYN" because the insurer's name appeared anywhere in the provider's. It now only triggers when the name starts with the insurer, and car-insurance carriers are excluded entirely. The same correction reaches CMS imports, so a Filevine medical-provider list that includes insurers keeps those contacts on the case as general contacts rather than filing them as doctors.

    Medical visits without a time land on the right day

    A firm's system that records only the date of a doctor visit sends it with a zeroed time. Quilia had been storing that as a literal instant, so a visit on July 22 could read as July 21 at 5:00 PM on the west coast. About 3,250 visits across 15+ firms were affected, and it drove real client reminders on the wrong day, including an "appointment in 2 hours" text sent the day before.

    A visit that arrives without a time is now recorded as missing its time and placed on the correct calendar day. The two reminders that depend on knowing a time are skipped rather than guessing, the earlier reminder still goes out, and the treatment table shows the date with no invented time. Calendar dates in the case summary also no longer read a day early for clients west of UTC.

    Check-in answers finally stick

    Clients can answer a check-in question two ways: give the information, or say it does not apply and their firm already has it. Only the first kind was being recorded, so a client could honestly work through every item and, as far as Quilia was concerned, have done nothing. The next morning asked the same questions again and the nudges kept coming.

    Both kinds of answer are now remembered, completion is recorded on the server rather than only on the device, and a dismissal lifts on its own once the client contradicts it (one client marked "no upcoming appointment" as handled, then added an appointment six minutes later). Those answers now also feed the case's own memory, so "I have no upcoming appointment" can prompt your firm to confirm whether treatment has paused instead of the client simply being asked again. And a client with push notifications enabled now gets a single push for a check-in nudge, not a push and a duplicate text.

    Reputation reads your Google replies correctly

    The Reputation page was reading the wrong field for an owner's reply, so a reply was never stored on any review: 972 reviews across all five connected firms, not one with a reply on file, every one reported as needing a response even where the firm had answered them all on Google. Worse, a reply posted from the portal was quietly overwritten by the next sync.

    Replies now read back correctly, and each review repairs itself the first time someone opens the Reputation page. Edited reviews behave too: Google moves an edited review to the top of its listing by edit date, and the page now filters, counts, and charts on that effective date so an older review edited into your selected range no longer vanishes. A review card shows the original post date alongside an "Edited" pill.

    A provider directory that cleans itself up

    The public provider directory gained a typo-tolerant name search, so you can find a provider by name instead of only filtering by state, specialty, and city, and it keeps working with JavaScript disabled. A daily job now automatically merges identity-grade duplicate listings (a near-identical name backed by a shared phone or address), so the same provider stops appearing as several separate entries. The merges are deliberately conservative, fully audited, and reversible, and a doctor is kept separate from the clinic they practice at.

    About 1,000 unambiguous doctor-to-clinic affiliations were then applied, each reversible, so browsing shows the clinic rather than separately listing every affiliated doctor while searching by a doctor's name still finds them directly. Claimed listings without a verified phone now show a "verify your phone" call to action on the dashboard and cases page, and the "similar providers" section no longer times out in provider-dense states.

    Case-type mapping made clearer and safer

    The email that asks you to confirm how your CMS case types map to Quilia types now shows the date range of each type's backlog ("added Jun 29 to Jul 10"), so you can gauge how recent the waiting cases are before confirming. The confirmation page spells out each mapping (your CMS's label and the Quilia type it maps to), how many cases will import, and states plainly that only those cases import, all on a single firm-scoped link instead of one button per type.

    Confirming now requires an explicit click on that page, so an email link-preview scanner or a double-click can no longer apply a mapping on its own. And case names like "Real Estate Purchase Review" now map to the right type instead of being pulled into "trusts and estates" by a broad "estate" keyword.

    Getting started is smoother

    Creating a new firm through public sign-up failed for a stretch with "Database error saving new user" after a database cleanup dropped a table the flow still referenced. Sign-up works again, the Full Name field no longer clears itself after a failed submit, and new self-serve firms now start with 5 free cases so they can run real matters before setting up billing. A firm that arrives from a partner listing (CasePeer's integrations page, the Add-to-Clio flow) now keeps that CMS context through account creation and email confirmation, so onboarding pre-selects it instead of making them find it in the picker.

    Reliability and polish

    • Appointment reminder scheduling is restored: the job that schedules them had been returning an error on every request.
    • Honest connection tests: saving case-management credentials no longer shows a green "API key added successfully" when the connection test behind it actually failed, so a firm can no longer believe it is connected when it is not.
    • Retry on Failed Imports works for every CMS: not just Neos, and cases the automatic retry had written off before it learned to recognize a temporary outage are re-examined and healed.
    • No duplicate Filevine updates: each client update now carries a permanent identifier, so a partial post is never re-pasted.
    • Steadier integrations: Clio matters missing a practice area are surfaced as a firm action instead of retried forever, and a Salesforce sync no longer fails with a header-size error.
    • Notifications reach everyone: chat notifications now arrive for staff in more than 100 chat rooms, deactivated team members stop receiving case emails, and firms are once again told when a client has been waiting over an hour for a reply in CaseChat (two email paths had silently failed for 39 days).
    • Faster, lighter photos: inline images across case messages and CaseChat load a right-sized preview and cache on the CDN, so photo-heavy conversations load faster and use less data.
    • Smaller touches: the case Activity tab no longer counts an entry it does not show, structured activity details no longer render as "[object Object]", the case page shows a plain "Active in your CMS" badge instead of explaining its own reasoning, and the partner appointment API now names the field a sender got wrong instead of failing opaquely.

    This bundle also includes a set of security hardening fixes: case chats and their messages are now scoped at the database level to the case's firm, a cross-firm visibility gap in chat-room lists was closed, an internal billing-setup endpoint now requires a shared secret, and writes through the partner appointment API are scoped to the sending firm's own cases.

  9. iOS v2026.7.0Android v2026.7.0

    By Kenny Eliason

    Case Notes with Attachments, Action Cards on Home, and More Reliable Uploads

    The Quilia client app (2026.7.0) makes the home tab do more of the work and makes sharing files with your firm more powerful and more reliable. Clients can attach photos and documents to a case note so the AI reads the note and its files together, each request from your firm shows up as its own action card, and a batch of upload fixes means the documents your clients send never silently disappear.

    Attach files to a case note

    Clients can now attach photos and documents directly to a case note. Each attachment runs through the same smart pipeline as their other uploads, and the AI reads the note and its files together, so the context a client adds makes the analysis better.

    Add a witness in seconds

    There is now a simple, standalone way for a client to add a witness to their case, including right from a case check-in, without walking back through the full "what happened" form.

    Requests are front and center on home

    The home tab now shows each request from your firm as its own action card, so a client sees "Sign here" instead of a generic "New Request" they had to tap into. The Case tab still lists every request in one place. Smart "Your next steps" is now the home experience for everyone, task buttons are always visible, and the spacing is cleaner.

    Screens that fit more case types

    More case types now get an experience built for them. The Health Check-in adapts its questions and symptom choices to the case type, including trauma-aware prompts, and cases with recurring events get an Incident Log instead of a single-incident form.

    Never miss a chat message

    When a client is viewing one chat thread, the other thread's tab now shows a red dot if it has unread messages, and the chat icon in the header reflects unread across all their conversations.

    Play audio and video on the Files screen

    Audio and video files now play right on the Files screen with the same players used elsewhere in the app, instead of appearing as rows a client could not open. Photos a client picks or captures also upload at higher quality, so pictures of documents, injuries, and damage stay legible.

    A better web layout

    For clients using Quilia in a browser, every screen now shares a consistent, wider layout: the header and content line up, and the file grid shows at least three columns.

    Bug fixes and stability

    • Documents no longer vanish after upload: some files (like medical bills) were being classified into categories the app did not recognize and silently dropped from the client's document views. Everything a client uploads now shows up.
    • Reliable uploads: a double-tap on the upload button no longer creates duplicate files, retrying an interrupted upload no longer fails with an error, and saving a batch of files no longer fails partway through.
    • Live chat for busy clients: clients with a very large number of chat conversations, who had stopped receiving live message updates entirely, now get messages instantly again.
    • The right case at launch: relaunching the app no longer flashes a previously open case on screens where the client has not picked one yet.
    • Signing without interruptions: on iPhone, a signature stroke that starts near the left edge no longer swipes the client back off the signing page mid-signature.
    • Ratings and announcements: submitting a firm-requested rating now works even when the client has no open case, and a multi-firm client with no open case now sees every firm's announcements in their inbox.
    • Crash and web fixes: a handful of crashes are resolved (editing a provider, a case note that failed to save, going offline, a web launch and sign-in loop), and the web app's tabs now line up with the mobile app.

    This release shipped as an over-the-air update to existing 2026.6.1 installs first, followed by the 2026.7.0 store binaries.

  10. Attorney Portal v2026.7.1

    By Kenny Eliason

    A Real Reputation Dashboard, Auto-Detected Signing Fields, and Smarter CMS Sync

    Four portal releases shipping together (2026.6.36 through 2026.7.1). The headline work turns the Reputation page into a dashboard you can actually work with, detects the fields on a document you send for signature so you do not have to place them by hand, and makes every CMS sync bring in the right staff with their real roles. Alongside it: invite a client straight from any CMS import, let Quilia invite a client the moment their case shows real activity, reconnect an integration without leaving its page, and a long tail of integration and reliability fixes.

    Reputation reporting you can actually work with

    The Reputation page now has real date controls. The date filter offers Month to date, Quarter to date, Year to date, Last 12 months, each prior full calendar year, and All time, alongside a custom range. It defaults to year to date, works on both the overview and the single case-manager views, remembers the range you pick for your next visit, and computes every preset in your firm's timezone so a range never starts or ends a day early.

    The Team Member Performance section gained a Sort by control (NPS score, average NPS rating, number of NPS responses, Google reviews, or average Google rating), and the NPS by Time in Case chart splits the old long-tail bucket into finer 91 to 120, 121 to 150, and 151+ bands so the later life of a case is legible. The review and NPS request pickers now list every client in your organization, not just recently active ones, and when two clients share a name each is shown with a differentiator so you can pick the right person with confidence.

    Manual and automatic requests no longer collide. Sending a satisfaction or Google review request by hand now takes over any pending automated NPS enrollment for that client, so nobody gets contacted twice, and recording an NPS score by hand now attaches to the client's case so the rating is stored correctly.

    Signing fields detected for you

    When you upload a document to send for signature, the builder now scans it for signature, initial, and date fields and places them for you, so you no longer drop every field by hand. Click to place is fixed too: a field now lands exactly where you click instead of drifting off its anchor.

    The right staff, with their roles, on every CMS sync

    Syncing a case from Neos, Clio, CasePeer, SmartAdvocate, Salesforce, or MyCase now adds the staff the CMS itself reports on the case. Neos cases that used to come back with no team members, because a job title like "Lead Attorney" did not match a fixed list, now show the assigned staff, and each staff member's CMS role is stored alongside them. When a case re-syncs, a staff member is removed only when the CMS's own staff id says they are gone, so a teammate you added by hand who happens to share your firm's email domain is no longer dropped by accident. Case types also display their actual name now, instead of mangled abbreviations like "(Mm)" or "(Mva)".

    Invite the client from any CMS import

    The optional "Also text the client an invite" checkbox on the Import Existing Case modal now works for every CMS (Clio, Filevine, CasePeer, Neos, Smokeball, Salesforce, SmartAdvocate), not just MyCase. It defaults to your firm's auto-invite preference, the billing note only mentions a per-client charge when the next invite is actually billable, and an import blocked by billing shows a clear "needs a paid plan" state instead of a false "All tasks completed".

    Invite a client once their case shows real activity

    Instead of inviting at case creation or leaving it entirely up to you, Quilia can now send a client's app invite when their case shows genuine activity in your case-management system, so the invite lands when the case is actually moving. It is a per-firm option and stays off until you turn it on.

    Reconnect an integration without leaving its page

    A disconnected integration no longer bounces you out to Settings to reconnect. The integration page now shows an inline Reconnect banner right where you are, the OAuth button for Clio, MyCase, Smokeball, and CasePeer, or the credentials form for Filevine, Neos, SmartAdvocate, and Salesforce, and reconnecting returns you to the same page. A Filevine connection whose credentials are no longer valid is now flagged as expired, prompting a reconnect, instead of showing an opaque error.

    A Smokeball task when a client finishes a task list

    When a client completes a task list on a Smokeball-connected matter, Quilia can now create a task on the Smokeball matter so the firm sees it right where they work, mirroring the existing Clio task sync. The task is assigned to the matter's responsible staff, and the per-list toggle keeps it opt-in.

    Video files show a preview thumbnail

    Uploaded videos now generate a poster frame, so the Files grid shows a preview image with a play button instead of a blank tile. Existing videos are backfilled, so older uploads light up too.

    Reliability and polish

    CMS imports interrupted by a brief outage now recover on their own: cases that fail because a firm's case-management system is temporarily unreachable are retried automatically and re-driven once the connection returns, instead of being quietly set aside for a human and forgotten. Client-uploaded bills and photos no longer vanish from the mobile app when the categorizer labels them slightly differently, and previously mislabeled items were backfilled. Photos edited in place (a HEIC heal, an auto-rotate, a conversion to JPEG, or a regenerated thumbnail) now refresh immediately instead of serving a stale copy.

    Quick find (Cmd+K) now lists only real clients, never firm staff, and a case page never renders a staff member as the client. When a firm's Clio subscription lapses, Quilia now tells them their subscription is past due and to update payment, the actual remedy, instead of a reconnect link that could not fix it. An integration's Staff-on-Case preview accepts the human case number you see throughout the app instead of requiring the CMS's internal id. Inactivity check-in reminders meant for the client no longer reach a delegate on the case, a MyCase staff member taken off a matter is now removed from the Quilia case, and a redirect triggered while a case is loading (for example being sent to sign in) now goes through instead of being surfaced as an error.

    A few smaller touches round it out: the Cases table pins its column headers while you scroll, the Invited badge updates on its own without reloading the whole list, and a handful of import rough edges are gone (no invite to a staff member with no email, no double credential form on a disconnected Filevine, no false "no active subscription" during a Stripe hiccup, and no progress bar that reads 100% before the import is actually done).

  11. Attorney Portal v2026.6.35

    By Kenny Eliason

    Two-Way Provider Sync, CaseChat in Your CMS, Multi-Firm Staff, and New Practice Areas

    Twenty-five portal releases shipping together (2026.6.11 through 2026.6.35). The headline work connects your medical provider roster to your case-management system in both directions, brings the attorney-client conversation into your CMS, and lifts the long-standing limit of one staff account to one firm. Alongside it: three new practice areas, sharper AI case summaries, per-office client branding, a faster request and form builder, and a long tail of integration and reliability fixes.

    Your medical provider roster, synced both ways with your CMS

    Your provider roster is now connected to your case-management system in both directions. Firm admins can pull their medical providers into Quilia in one click from Filevine, CasePeer, or Clio (the Clio import needs Clio's Personal Injury add-on), and it is safe to run again later because already-imported providers are updated, never duplicated. For Filevine, CasePeer, and Clio firms the roster also re-imports automatically once a week, so providers added in your CMS show up without anyone clicking Import.

    Going the other way, the medical providers your clients add, along with their treatment status, can be pushed to the Medical Records tab on a Clio matter, either with a "Sync to Clio" button on the treatment page or automatically whenever a provider is added or updated. Quilia derives Clio's first and last treatment dates from the case's appointments, and only fills blank Clio fields so it never overwrites values your firm edited directly in Clio.

    The providers page itself is faster and easier to read: a pinned header row while you scroll, each provider's business name under their name, a specialty filter, and clearer matching cues, with a confidence badge on every suggested directory match (Strong for a name-and-phone match, Exact when the address matches too) and likely-match rows floated to the top of the unmatched queue. Provider mailing addresses are standardized through USPS on both sides so matching lines up reliably, the cleanup tool no longer collapses a clinic and its individual doctors into one record, and the providers-page delete button (which had silently done nothing for every firm) now works.

    CaseChat now lives in your case-management system

    Messages from the one-on-one client conversation now export to your case-management system as case notes across Clio, Neos, MyCase, Filevine, CasePeer, and Smokeball, on both the real-time and nightly paths, with no message ever posted twice. CaseChat, its CMS export, and the shared "All Parties" thread on multi-client cases are now on by default, and CaseChat is enabled automatically for brand-new firms.

    When a client sends messages and no one at the firm replies within about an hour, the case team gets an email showing the waiting messages laid out as a chat thread, with buttons to open the conversation in the app or the portal. Each staff member can turn that alert off in their notification settings. Staff also stopped getting a text for every message: clients still get an immediate text, but staff now get a single text only if a message stays unread and the thread goes quiet for about ten minutes, so the app and portal stay the primary place to follow a conversation. In the portal, CaseChat now uses the same blue iMessage-style bubbles as the mobile app.

    Sharper AI case summaries

    AI case summaries now lead with a dedicated Treating Providers roster, showing each provider's status, last-seen date, and next appointment instead of leaving that buried in the damages narrative, and an injury or treatment matter with no providers on file is called out as a gap. Timeline dates now come from the event a document describes rather than the day it was uploaded, long runs of routine "client confirmed an appointment" entries collapse into a single signal-preserving line, and any self-reported symptom that can't be confirmed from recent check-ins reads as unknown rather than assumed resolved.

    Summaries also cross-check the body parts a client reports as painful against the providers actually treating the case and nudge the client about anything no one is treating, and they now flag possible traumatic brain injury or psychological-trauma signals so they surface for the attorney. Client and delegate notes are no longer mistaken for firm activity, and automated Quilia reminders are no longer described as firm-sent, so the engagement read on each case is accurate.

    Staff who work across multiple firms

    Quilia now supports a single staff account belonging to more than one firm, for example a case-management company that works with several practices. Those users get an organization switcher and land in their last-used firm, with every screen and permission scoped to the firm they are currently in. Single-firm staff (everyone today) keep the same fast login. Initial multi-firm setup is handled by Quilia.

    Three new practice areas

    We added Legal Malpractice, Sexual Abuse, and Nursing Home Abuse & Neglect so firms importing from their CMS can map these practice areas to dedicated layouts instead of collapsing them into broad buckets like Civil or Personal Injury. Medical malpractice case layouts can also opt into an Incident Log to capture the chronology of negligent acts (failure to diagnose, medication mismanagement, failure to monitor), kept separate from the client's own medical-care record.

    Right office, right branding

    Multi-office firms can now route each imported client to the right Quilia office automatically, so the client sees the branding for the office handling their case. Tie a case to an office using a field in Filevine, SmartAdvocate, Salesforce, or Litify, and on import Quilia matches it to a Quilia location, creating one when the office isn't already there. It stays off until you configure it, so single-office firms see no change.

    Salesforce and Litify, first-class

    Salesforce and Litify firms gained a lot this cycle. A "Suggest field mappings" button scans the connected Salesforce object and fills in best-guess fields so you no longer type API names from memory. Quilia can import case staff from named Matter role fields (Primary Attorney, Case Manager, Legal Assistant, Intake Owner), with a per-field visible-to-client toggle and per-case contactability the same way Filevine works. Documents pushed to your CMS keep the client's original filename (in-app captures get a readable type-and-date title instead of a UUID), and uploads for firms on SharePoint now land in the matter's folder instead of a phantom nested copy, including older cases that self-heal.

    A faster, friendlier request and form builder

    Case-type selection is now a real search box everywhere it appears (CMS mapping, Create New Case, and SMS onboarding), alphabetically sorted, which matters now that the catalog has more than thirty types. The Send Request picker shows every matching case instead of stopping at the first ten and adds the app's phase, date-of-injury, and status filters. Smart Extract accepts images and screenshots (PNG, JPG, WebP) so a photo of a paper form builds the questions, the web document signer now renders and saves every field type (date/time, multi-line text, dropdowns), and deleting a request or signature template is recoverable for thirty days in a trash before it purges.

    Notifications that respect each client's clock

    Automated client notifications now send within an 8am to 8pm window in each client's own timezone instead of firing at any hour or queuing overnight and going out all at once at 8am. Attorney-initiated invites from the Invite button still send immediately so onboarding isn't held back. A firm's timezone is now derived from its address rather than defaulting to Eastern, and Quilia-sourced notes pushed into your CMS use your firm's local time and include a due date so they sort chronologically.

    Reputation reporting by person and period

    The Reputation screen has a single date-range filter at the top that drives the whole page, plus a chart of when Google Reviews arrived across the selected period. You can scope the Google Reviews counter, list, and printable to a single staff member, an easy way to confirm how many reviews someone brought in over a window and hand them a printable of every one. The Google Reviews list now shows reviewer avatars, and unassigning a teammate from a review no longer means scrolling the whole team list.

    Reliable images and documents

    Older iPhone (HEIC) photos that showed as broken images now convert to JPEG the first time anyone views them, with a recurring sweep that heals any that slipped through across chat and other upload paths. Images in case-summary and notification emails use durable links that no longer expire in the inbox, uploaded photos auto-rotate to the right orientation before they reach your CMS, and PDF first-page thumbnails render cleanly even for scanned documents.

    And a few more

    • System announcement banner. The portal now shows a banner for platform-wide notices like scheduled maintenance, with dismissible non-critical messages.
    • Simpler per-case billing. Per-case billing creates a one-off invoice instead of requiring a card on file up front, and manual case creation no longer blocks when no card is saved.
    • Smokeball calendar sync. Firms on Smokeball can now push Quilia appointments into the matter calendar, the Smokeball counterpart to the Clio calendar sync.
    • New partner API. Integration partners can read a case's injury and body-part data through a new read-only GET /v2/cases/{id}/injuries endpoint.
    • MyCase staff on the case. Importing or syncing a MyCase case now adds the firm's assigned staff as case members, not just the client, so your team receives the client-activity notifications they were missing. Importing a case no longer auto-texts the client unless you opt in.

    Privacy and reliability fixes

    • Signed documents stay behind login. The public completed-request page no longer offers a download link that exposed a signed PDF to anyone holding the request link; the signed copy stays available in the app behind login.
    • Connection status owned by the health check. Routine CMS calls no longer flip a firm to "disconnected" on a single transient 401/403, so flaky or high-volume firms stop latching a false disconnected state.
    • Case deletion works and can be done from the client detail page's case list, not just the Cases page.
    • Cleaner case detail and navigation. The case detail page uses a header back arrow, broken case links return you to your case list, and the announcement banner no longer overlaps CaseChat.
    • Multi-firm and multi-case display fixes. A client who belongs to more than one firm no longer appears twice in Edit case details, and a client on more than one case sees the correct status and phase on each case.
    • Friendlier errors throughout. Clearer messages for a phone number already in use, unmapped practice areas no longer lock re-import, and several CMS sync failures (Clio rate limiting, expired Clio/Smokeball/CasePeer tokens, SmartAdvocate notes, unknown case types) now recover instead of stopping a case from syncing.
    • No more double-logged activity. Appointment actions, employer changes, and incident-translation entries each log once and read naturally in the feed.
  12. iOS v2026.6.1Android v2026.6.1

    By Andre Hammons

    Faster Client App Launch, Real-Time CaseChat, and Smoother Sign-In

    The Quilia client app 2026.6.1 is a speed and reliability release for the moments clients feel most often: opening the app, checking messages, signing in, uploading photos, and reading documents. Returning clients get back to their case faster, CaseChat feels live, and common support paths now stay inside one clearer app experience.

    The app opens where clients left off app

    Returning clients no longer have to wait on a full session check before the app shows something useful. On cold launch, Quilia uses the saved session and last route to open the right screen immediately, then checks the server in the background and corrects only if something actually changed.

    Home content also paints from cache. Tasks, requests, appointments, and case details can appear right away from the last known state while the app quietly refreshes, so clients are not staring at a spinner before they can act.

    CaseChat feels live on mobile app

    CaseChat now receives new messages instantly over a live connection. Opening a conversation loads recent history reliably, and reopening a chat uses the app's local cache first, so active conversations come back without a full reload.

    The app still reconciles messages by id across history, live delivery, and optimistic sends, so the client sees the new message quickly without duplicate rows.

    Sign-in and case selection are steadier app

    Single-case clients now land directly on Home after sign-in instead of briefly flashing through the case picker. Clients with more than one active case keep the case picker, but the picker has its own cleaner header without in-case branding or chat controls before a case has been selected.

    A deeper cold-start bug is fixed too. Multi-case clients could sometimes be sent back to sign-in when launching the app from a closed state. The sign-in screens now live outside the authenticated app shell, so the logged-in app no longer has a sign-in fallback to snap back to.

    One clearer ℚ Help experience app

    Help screens across the app now open as one consistent ℚ Help conversation. Instead of many separate help pop-ups with different shapes, each topic appears as a simple chat-style thread with clearer, friendlier guidance.

    Localized help is repaired as part of the same release. Non-English help content now renders correctly instead of showing broken object text, and the ℚ Help title itself is translated.

    Photos and documents behave better app

    iPhone photos selected or captured in the app now upload as JPEG at the source. That means new photos display correctly in browsers and the portal without waiting for downstream conversion work.

    PDFs now open inside the app on iOS through the in-app viewer, so clients can read documents without being kicked out to another app. Android continues to use the system viewer where the platform handles PDFs more reliably.

    Check-ins, notifications, and language fixes app

    • Case check-in notifications open the right place. Tapping a case check-in notification now opens the check-in screen for that case.
    • Lost-time check-ins open the editable list. When a check-in asks a client to review missed work time, the app opens the missed-times list so the client can fix an existing entry or add a new one.
    • The app uses the client's language immediately. If a client's account language is not English, the app applies it during sign-in instead of waiting until a case opens.
    • More labels are translated. Case check-in, Complete Requests, ℚ Help, and the renamed Health Check-in screen now use localized copy. Tagalog and Mongolian translations were also cleaned up where prior syncs had pulled in the wrong language.
    • iOS headers are more reliable. Home, Case, Health, and Files now use the app's custom header on iOS, preventing content from drawing under the notch and avoiding a stuck first-load refresh spinner.
  13. Attorney Portal v2026.6.10

    By Kenny Eliason

    Health Check-ins, Data You Can Trace to Quilia, a Unified Tasks Workspace, and Calendar Sync

    Nine portal releases shipping together (2026.6.2 through 2026.6.10). The headline work makes a client's recovery easier to read at a glance, shows your team exactly which case data Quilia contributed, and turns scattered task tools into one workspace. Alongside it: appointments that sync to your CMS calendar, forms that build and send themselves, automatic satisfaction surveys, and a long list of integration and reliability fixes.

    Health Check-ins on the treatment timeline

    The daily "pain score" on a client's treatment timeline is now a full Health Check-in. Each entry surfaces the client's mood and reported symptoms alongside the overall pain score and a pain rating for each individual injury, so a case manager can see not just how much a client hurts but how they are actually doing.

    The Check-ins tab now leads with a stat strip above the chart, showing latest pain, latest mood, the pain trend, and the check-in count, so you can read how a client is trending without opening every entry. That richer picture also flows into the case-activity feed, which labels these as Health Check-ins, and into the AI case summary, which now reflects the client's recent mood, symptoms, and injury ratings.

    See what Quilia added, field by field

    When Quilia's AI fills in case data, your team can now see it. A new "Added by Quilia" mark labels details that Quilia contributed, so you and your case management system always know what came from the firm versus what Quilia supplied.

    It started with medical providers pulled from an uploaded document and now extends to vehicle data. When Quilia decodes a VIN, fills in a year, make, and model, or pulls a photo from a license plate, those fields carry the mark in the activity feed and on the vehicle display inside the portal, where they show as a verified-source chip. Attorney-triggered look-ups in the Edit Vehicle form earn the mark too, and if you correct one of those fields by hand, the mark comes off it. Client-entered fields stay unmarked.

    One unified Tasks workspace

    The old "Task Lists" area is now simply Tasks: one place that shows standalone action and upload tasks right alongside full task lists. A new single-task dialog lets you send one to-do to a client with a built-in client and case picker, and case options show the CMS matter name with date-of-incident context so you pick the right case at a glance.

    You no longer need to build a whole list or save a template to send a quick reminder. A Send a task button on a case's Requests page lets you type a task ("Confirm you scheduled your MRI"), add optional instructions or a link, and send. Existing task-list bookmarks keep working through automatic redirects.

    Plain task completions finally reach the case feed, too. Until now only document, form, and signature submissions showed up, so simple "mark complete" tasks and any action item inside a task list were invisible to the firm. Now when a client checks off a task, your CMS case feed shows it, along with any optional note the client left ("saw Dr. Lee Tuesday, back in 2 weeks").

    Smarter Clio task automation

    For firms on Clio, sending a task list now creates an open "waiting on the client" task on the matter right away, so your Clio board reflects where each client actually stands. When the client finishes, Quilia checks that task off and opens a fresh task for your team to review.

    You control each side independently with two switches, "When sent, open a Clio task" and "When complete, create a Clio task," each with its own title and description, and the on-send task can carry an optional due date. All of these settings travel with a task list when you save it as a template.

    Forms that build and send themselves

    Reusable form templates now have an Auto-send control in the Form Builder. Pick when a form should fire (when a case opens, closes, or changes phase) with an optional day offset, and every matching case gets that form automatically. Turn it off anytime and anything already queued is cancelled.

    Building a form is faster as well. The New Signature Request and New Form modals lead with a drag-and-drop PDF upload that goes straight into Smart Extract, which now also accepts screenshots and photos (PNG, JPG, WebP), so you can snap a picture of a paper form and it builds the questions. Copy Web Link is now a visible button on every sent request row, "Form Requests" is now just "Forms," and the "Request Builder" is now the Form Builder.

    Automatic NPS surveys

    Reputation has a new Automatic NPS setting. Pick a cadence (every 30 days by default) and clients with an open case get the satisfaction survey in the app on their case anniversary, nudged by a push notification during their daytime hours. It is push-only, so there is no SMS or message to write and no more hand-creating a recurring message for each firm.

    Appointments on your CMS calendar

    Firms can now opt in, per integration, to push Quilia appointments onto their CMS calendar, starting with Clio. Synced entries carry a useful title, location, and description built from the appointment's provider and type, and Clio entries are tagged with type-aware Quilia event types, ℚ Medical and ℚ Legal, each with its own color so you can recognize and filter them.

    Entries land on the calendar of the attorney responsible for that case, rather than the integration's connected user, so they show up where that attorney actually looks. Appointments also now have a dedicated online meeting link field for remote depositions, Zoom mediations, and telehealth visits: staff paste the link once, and the client gets a tappable Join button in the portal and the app.

    Prescriptions and a clearer activity feed

    Medications a client adds in the app now show up as prescriptions in your activity feed and CMS feed, listing the medication, dosage, frequency, duration, instructions, and prescribing provider, instead of a generic "added case details" entry.

    The feed is more trustworthy in other ways too. It now marks a request "Completed" only when a client actually submits it, not when they merely open it, and it keeps client and sender names properly capitalized in both the Feed and List views.

    Smokeball parity and integration reliability

    Smokeball firms now get more of the safety nets available across Quilia's other integrations: scheduled daily CaseChat exports, broader matter-staff discovery, staff refreshes during normal sync, and recent-matter polling to catch imports a webhook missed. Smokeball cases also show the real matter number, title, and description throughout the portal, duplicate feed memos no longer post twice, and co-client phone warnings now surface in the import dialog instead of being dropped silently.

    Across integrations, stuck SmartAdvocate message attachments now retry automatically, recovered incidents clear from the Integration Health Digest on the next run, and the Cases list shows the resolved Quilia case type instead of Filevine's broad parent project type. Clients who belong to more than one firm can now sign in reliably, and MyCase document uploads, which had quietly been failing since April, work again.

    Clearer billing

    Pay-per-case billing now starts at the right moment: an imported client can remain pending without a charge, and billing begins once, when the client is first invited or opens the app, whichever comes first. The billing page explains this rule for pay-per-case firms, and the billing card now shows contract price overrides or scheduled renewal pricing instead of a technical $0/year placeholder.

    For partners and AI agents

    Quilia's public API and MCP server are now a much better interface for working with a case. Integration partners and AI assistants can read a case's documents and their case-manager memos, resolve a client and pull their case summary in a single call, follow a client's treatment status, read their case notes, and send a client a one-off task. Cross-firm boundaries on these endpoints were tightened so a request only ever touches data belonging to the API key's firm.

    Reliability and fixes

    • Requests and forms. A form built right after a signature request in the same session no longer sends against the wrong template, so forms reliably reach clients. Publishing a request that was already created now shows a clear message, and Requests sub-pages have a proper back arrow.
    • Chat notifications. Photo and document messages sent without a caption now summarize the attachments ("3 photos," "2 attachments") instead of arriving as empty alerts.
    • Damage photos. The Incident → Vehicle Damage gallery lets you open, close, and re-open photos freely again.
    • Staff invites. Invites no longer stall on a leftover login record with no active user, so the rest of a batch goes through.
    • Reputation at scale. The Reputation dashboard and per-case-manager NPS view now load for firms with large caseloads.
    • Salesforce and Litify. Firms that store a client's preferred language on the matter now import it correctly, with a setting to point Quilia at the right field.
    • Organization switcher. The search box no longer loses focus or jumps after a keystroke.
  14. Attorney Portal v2026.6.1

    By Kenny Eliason

    Vehicle Lookup by Plate or VIN, an Interactive Injury Body Map, and Cleaner Provider Records

    Six portal releases shipping together (2026.5.19 through 2026.6.1). The headline work makes incident and treatment records faster to build and cleaner to keep: pull a vehicle's details from a plate or VIN, mark injuries on a body diagram, and clear out duplicate providers right where you work the case. Alongside it, a proper Incident tab for non-vehicle matters, reputation search, smoother CMS setup, and a long list of reliability fixes.

    Look up a vehicle by license plate or VIN

    You no longer have to type a vehicle's details by hand. On the incident vehicle form, enter a license plate with its state, or a 17-character VIN, and Quilia fills in the year, make, model, and trim, and fetches a photo of the vehicle. When a plate lookup comes back incomplete, it falls back to authoritative VIN data so the record stays accurate.

    Vehicle details read from uploaded documents are now cross-checked against the VIN before saving, which catches OCR and AI misreads when the VIN is the reliable source. And because not every loss is a car, you can now capture damage to non-vehicle property on a case as well.

    An interactive injury body map

    Current Injuries now includes a front and back body-part figure, so your team can see highlighted injury areas at a glance. In the edit dialog you can click the body map to toggle injuries directly, and the portal now matches the mobile app's more detailed taxonomy for groin, forearm, thigh, and lower-leg injuries (the hip gets its own marker instead of being folded into the back).

    AI injury suggestions are cleaner too. They now show just the body part, and spinal or radiology terms (for example "L4-L5" or "lumbar spine MRI") are normalized to canonical body parts, so suggestions group together instead of creating near-duplicate entries.

    Fewer duplicate providers

    When a provider gets imported twice, you can now merge the duplicates directly from a case's Treatment table. A merge dialog lets you choose which details to keep, and a cleanup banner surfaces likely duplicates so they are easy to find and resolve.

    New providers are cleaner from the start. Names and phone numbers are normalized when providers are created from Treatment or the contacts API, and Quilia checks for likely duplicates, so inconsistent capitalization, phone formatting, or name order stops producing repeat records.

    A clearer experience for every case type

    General-negligence and personal-injury cases now have an Incident tab that captures the client's account of what happened, including the date, the location, and what occurred before, during, and after. For matters like slip-and-fall, premises, or product cases, that account is often the heart of the liability story, so it now has a home instead of being limited to medical, notes, and lost income.

    The case sub-tabs are tidier as well. Vehicle, Repairs, Rental, Towing, Storage, and Insurance now appear only on motor-vehicle case types, so premises, slip-and-fall, product, and animal-attack cases no longer show empty auto-damage tabs.

    Reputation: edited reviews and review search

    The reputation view now surfaces Google reviews that a reviewer has edited, and adds search across reviews so you can find a specific one by keyword instead of scrolling.

    Faster case intake and request cleanup

    Importing an existing case from your connected case management system is now a single, self-explanatory step across every integration. The modal shows your CMS's logo, explains exactly what to copy right inline (with examples), and accepts either a case URL or an ID wherever that makes sense.

    Case-type auto-mapping picked up bulk controls: Accept all and Reject all let you apply or dismiss every suggested mapping in one action instead of reviewing them one at a time. And you can now remove a request that has already been sent, soft-deleting mistaken or duplicate sends so they stop cluttering the case.

    Integration improvements

    • Salesforce and Litify matter team import. Case imports now bring over the matter's team members as case staff, with an optional auto-invite so they are added in Quilia without manual setup. Import settings also save correctly when optional field mappings are left blank, with validation that rejects unresolved merge-field placeholders and bad import IDs up front, and Person Account imports read preferred language from the Account-side field when it lives on the underlying Contact.
    • Client activity feed on by default. New CMS integrations now have the client activity feed enabled by default, so client-facing updates flow without an extra manual toggle.
    • Document permission alerts. When a connected case management system permanently blocks document uploads because the connected user lacks write permission, Quilia now emails the firm so the gap can be fixed, instead of staying invisible until support notices it.
    • For firms with custom or API integrations. A case's summary is now available read-only through the v2 API and as a matching resource for AI assistants, and the case members and invite endpoints now report any users they skipped (and why) instead of returning a silent success.

    Reliability and fixes

    • Sign-in and team invites. Resolved an authentication failure that could appear while loading a user during sign-in, and fixed team invitations that could fail when an email address was left behind as an orphaned login record (existing ones now self-heal on invite).
    • Graceful error recovery. An unexpected error now shows a recovery screen instead of a blank page, and delete actions on requests and templates return a clear message instead of an unexpected error.
    • Correct names in automated check-ins. Fixed scheduled automated check-in messages that could greet a client with another client's name, and repaired the affected messages so they personalize correctly again.
    • Accessible organization switcher. The organization switcher is now fully keyboard and screen-reader accessible, and shows organization initials when a logo image fails to load.
    • Settings and case pages. The Operation Hours "Available Weekends" toggle now saves correctly instead of flipping back on after a refresh, the integration settings page no longer returns a 404 for custom integrations, and opening a case-type detail page with no matching record no longer errors.
    • Cases and notifications. Fixed a foreign-key error that could block case deletion, and removed a duplicate appointment-created notification so firm-scheduled appointments send the intended notice only once.
    • PDF previews in chat and messages. PDFs sent in CaseChat or client messages that were showing as blank tiles can now be backfilled to display a real first-page preview.
    • Quieter AI suggestions. Stopped the asset pipeline from generating duplicate AI suggestions for the same asset and from running the same suggestion more than once.
  15. iOS v2026.6.0Android v2026.6.0

    By Kenny Eliason

    Appointment Reminders, an Injury Body Map, and Vehicle Lookup by Plate or VIN

    The Quilia client app (2026.6.0) gives your clients several things they will notice right away. Appointments now guide clients to every visit, injuries are marked on a body diagram, and the inbox shows the right office's branding. Clients can also look up a vehicle by plate or VIN, and general-negligence matters get the full case experience.

    Appointment reminders that guide clients to every visit

    The appointment screens now power Quilia's reminder flow end to end. A reminder push or text deep-links the client straight to the right appointment, where quick-action buttons let them confirm, reschedule, or log a missed visit without hunting through the app. One tap drops the appointment onto their device calendar, so the visit lands where they already keep their schedule.

    Mark injuries on a body map

    The Current Injuries screen now includes a body diagram. Clients tap where they are hurt to mark an injury, backed by a finer-grained taxonomy, so the record maps more precisely (the hip, for example, now has its own marker instead of being grouped with the back).

    A rebuilt inbox with the right firm branding

    The home inbox was rebuilt around a single shared message view for a more consistent experience. Firm branding (logo, colors, and name) now reflects the client's specific office location instead of one organization-wide default, so multi-location firms show up correctly to each client.

    Look up a vehicle by plate or VIN

    On the case screen, a client enters their license plate and registration state, or their VIN, and the app fills in the year, make, model, and VIN automatically, along with a photo of the car. The property-damage picker now routes motor vehicles into this lookup form (with a place to add a registration photo), while bicycles, scooters, and other items get a simpler form with a description, purchase price and date, and an optional link. The vehicle photo and plate state are saved and stay put across reloads.

    The full experience for general-negligence cases

    General-negligence cases now get the complete mobile experience (Treatment, the narrative Incident log, and Lost Income) instead of a stripped-down default layout. Vehicle screens are hidden for this case type since it is not a car case, while Insurance stays available.

    Armenian translations repaired

    Corrected hundreds of Armenian strings across the app, including missing body-part labels, untranslated text, and garbled machine translations on request cards, the tab bar, and screen titles, so the Armenian experience reads cleanly.

    Smaller improvements

    • Ask a Question respects the firm's setting. The Ask a Question button on the firm screen is now hidden when a firm has turned it off.
    • Language choices stick. Picking a language in app settings now records it as the client's explicit choice, so a later locale sync will not override it.

    Reliability and fixes

    • Message detail always shows sender and date. The message detail view now always renders who sent a message and when, instead of occasionally dropping them.
    • Uploaded files refresh immediately. Attaching or removing a file now updates every screen that lists it without a manual refresh, and injury photos appear right after an asset is attached.
    • Uploads only count as done once the file is really stored. The app now verifies the storage object exists before treating a resumable upload as successful, so a partial upload no longer shows as complete.
    • Files work for case delegates. Case delegates can now view the Files tab, upload, and delete files like the primary client.
    • Steadier sign-in. Hardened an auth path that could briefly report a signed-in user as logged out, and resolved a native file-reader crash surfaced through observability.

Earlier releases