Quilia-Branded Account Emails

Portal 2026.4.6 cleans up every email your team receives from Quilia and restores the voice fallback on the sign-in screen.

Branded Account Emails portal

Every account email your team can receive is now a Quilia-designed template. The old default templates — with the broken hero image and the leftover "Record System, Inc." footer — are gone.

• Sign-in and password-reset codes: The 6-digit code email now uses a branded Quilia template with a large, legible, letter-spaced code. The verification path is unchanged — the code is still issued by our authentication provider — we just deliver it in our own envelope.
• Staff invitations: Invites sent from Settings → Team, resent from the admin audit log, or created via the public API all use the new branded invite template.
• Email-change confirmation: When someone on your team changes their email address, the confirmation message sent to the new address is now branded, too. We also fixed a stale-profile edge case where the old address could linger if the change was never confirmed.
• Cleaner footer: Transactional emails no longer repeat the Quilia logo at the bottom or carry a physical mailing address they don't need. Every template gets a tighter, single-line footer.

Call Me Instead Works Again for Clients app

Your clients have a voice fallback on the mobile app's sign-in screen — "Call me instead" — that places a verification phone call when the text-message code doesn't arrive. It was silently failing in production, leaving some clients unable to sign in without re-trying the text code. The voice call now goes through reliably.

Behind the Scenes portal

• More reliable CMS imports: Every case-import failure across all ten supported case management systems (Clio, Filevine, MyCase, Neos, SmartAdvocate, CasePeer, Smokeball, Litify, Salesforce, and Zapier) is now recorded and classified. If an import silently fails because credentials expired or a remote API hiccupped, the Quilia team can now see it and act on it — instead of the failure disappearing into the void.
• Clearer sync failure messages: When a note, document, or message fails to sync to your case management system, our internal tooling now captures the actual error returned by the CMS. When something doesn't land where you expect, our support team can tell you why instead of guessing.