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.