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.