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.