Staff Training & Reference
Everything the portal does and exactly what your clicks trigger downstream.
The big picture
Your job in the portal is to review documents and make decisions. The portal handles everything else — chasing the client for missing docs, creating placeholder records in our legal-case system, syncing data between platforms, sending the right emails at the right time, and alerting you when something needs attention.
The basic flow:
- Client takes the quiz on lemonaidfirm.com — case automatically appears in your Workbench. (Or you create one via Manual Intake Form for phone/walk-in intakes.)
- The client is asked for all documents up front — repair orders, registration, and purchase/lease agreement — as soon as they finish the quiz. The case moves through Quiz Completed / Not Yet Uploaded → Collecting Documents as files come in. Our AI analyzes uploads in the background and the system chases anything missing automatically.
- Once the documents are in, the case reaches Push to Clio. You review everything on the Actions tab and click Push to Clio, which creates the Clio matter at the "Needs review by intake specialist" stage. This does not accept the case or email the client — it just hands the matter to Clio for review.
- The accept/reject decision is made in Clio by a different staff member who evaluates the documents and moves the matter stage. Accepting in Clio syncs back, accepts the case, and hands off to litigation (Matter Created / Pending Review → Retainer Sent → FRA → Litigation → Closed). Moving the matter to PNC-Rejected in Clio fires the same "case not qualified" path as the portal Hard Reject button.
- If the case clearly doesn't qualify — without waiting for the Clio review — use Hard Reject (fires "case not qualified", emails the client, moves the GHL opportunity to Lost, and creates a CLOSED reject matter). If the client ghosts: Soft Close. Both land the case in Closed.
What's switched on right now
Some features start Off and an admin turns them on in Settings. This list is read live from the portal, so it is always current; each Help section and Tour step for one of these features shows the same state next to its explanation. The words in Help describe both states; this says which one is true today.
Checking the switches…
Daily routine — what to do and when
Most days the work falls into a predictable rhythm. Here's the order to work through it so nothing slips:
1. Start with ★ Needs my action
Top of the Workbench. This filter surfaces every case that has unprocessed documents OR is in a stage where you owe a decision. Work it top to bottom.
- Blue +N pill = documents uploaded but not yet processed by staff. Open the case → Documents tab → download the original, clean/rename it, then click ✓ Mark processed(which will ask you to upload the cleaned version). The pill clears once everything is processed.
- 📞 Call Needed badge = a call is due, and the case shows why and by when. Open the case: the 📞 Call flagged panel has the script. See "Call flags & call scripts" below for every reason. After the call, use Record the call →.
- Amber "Settlement data required" banner = Clio moved the matter to Settled. You must fill in settlement figures so Email 6 fires.
2. Process decision-ready cases
- Push to Clio lane → Push to Clio (creates the matter for the intake specialist to review in Clio) or, if it clearly fails, Hard Reject
Always select your name in the Performed by dropdown first. Every action posts an audit note with your name to both Clio and UrVeedaOS.
3. Post-acceptance follow-through
- Settled cases (amber banner): Open → Actions → 💰 Settlement → fill in 4–6 numbers → Save. Fires Email 6.
- Check just mailed: Open → Actions → 💰 Settlement → scroll down → Mark Check as Mailed. Fires Email 7 and promotes the dashboard to "Case Closed — Won!"
The Clio task "Mark Funds Disbursed in Staff Portal" on the matter is your reminder. Closing that Clio task is NOT enough — the portal button is what fires Email 7. If you only close the task, the client never gets notified the check is on the way.
4. End-of-day check
- Switch the Workbench filter to All and scan the Quiz Completed / Not Yet Uploaded and Collecting Documents lanes. Stalled cases here often just need a one-line nudge call — especially anything showing the 📞 Call Needed badge.
- Check the Closed lane for anything closed today (hard-rejected or soft-closed) — re-open if a client called back.
The Cases Board
Checking whether it is on…
The Cases board is your home screen. Every active case lives in one of the columns based on where it is in the flow.
The columns
Each column is a stage. Cases move between columns automatically as clients upload docs and as you make decisions. You shouldn't usually need to drag cards around — if you do, it usually means something is wrong (talk to David).
Notices: who gets which notification
Every notification a staff member gets is on one list, ticked per person:
- Workbench banners: Referred out: N need a status check; refer-out firms with no licensed states.
- Today strip: calls due, documents to review, retainers unsigned 48 hours, cases closed without a reason, your week, team this week.
- Work on other people's cases: each kind of next step (call a new lead, documents to review, push to Clio, send the FRA, calendar date to share and the rest) on a case someone else owns. Your own cases always show every step, so no tick can hide your own work.
- Emails: the weekly and monthly reports, out-of-state leads and retainer resend requests (on top of the addresses typed in Settings), and the alerts UrVeedaOS sends (new lead, retainer chase ran out, partner application, help requested). Those last four are marked set in UrVeedaOS for now: the tick is saved, but who gets them is still set in each UrVeedaOS workflow.
Until an admin changes someone, they get their team's suggestion, which is how things worked before: everyone sees the Today strip and all team work; admins and the intake team see the referred-out checks; admins get the reports; nobody is added to the typed email lists. Someone on the litigation team only no longer sees the referred-out banner.
Admins: Settings → People → the Notices column → Edit on a person. Tick or untick, use tick all per group, and press Save. Use their team's suggestion undoes your changes. Changes are kept as differences from the suggestion, so if you change someone's team later, everything you didn't touch follows the new team, and a notice added later reaches the people it suits. Adding a user opens this straight away. View as on the Workbench shows a teammate's notices as they see them.
A task whose case is in the Trash
Moving a case to the Trash removes the portal case but not its tasks: a task on the Clio matter is still work, and Restore (Sync Health → Deleted cases) brings the case back with its tasks attached. On the Workbench and the Tasks page such a task reads Name (in Trash), and Open in Clio ↗ opens the task in Clio instead of a case page that no longer exists. If another live case holds the same Clio matter, Open goes to that one. A task with no case at all reads Personal task. Opening a trashed case's old link says it is in the Trash, when and by whom.
Saved views — one tap back to your daily slice
On the Workbench, set up the facets, search, and sort exactly how you triage each morning, then click + Save this view and give it a name ("Quiet 7+ days", "My partner referrals"). It becomes a chip above the list — one tap restores the whole setup. ★ is private to you; 👥 is shared with the team. Use ⤴ to share one (handy for an agreed "Monday triage" list everyone works from) and ✕ to delete it. Views follow your account rather than your browser, so the one you saved on your laptop is there on your phone, and each zone (Intake / Litigation) keeps its own set.
Start my day — everything due to you, one card at a time
Log in and you land on the Workbench. If anything is due to you, the header shows a yellow ▶ Start my day (N) button.
Your day is both kinds of work at once — the Clio tasks someone assigned you, and the cases that need you — dealt in one deck, most urgent first. You used to have to read two lists and join them in your head; now it's one. On a task: ✓ Done, → Tomorrow, → Next week, or Skip. On a case: Open the case, → Tomorrow, → 3 days, or Skip.
The deck also includes urgent work nobody has taken yet, marked unclaimed. Acting on one of those assigns it to you — so it drops out of everyone else's day and stops being a job that's technically everyone's and actually nobody's. The deck is dealt the moment you press the button, so acting on a card never reshuffles the rest.
The Tasks page is still where you plan work — create, assign, bulk-edit, apply templates. The Workbench is where you do it.
The view toggle (Open / Closed / All)
Open shows active cases needing attention. Closed shows accepted, hard rejected, and soft closed. All shows everything. Defaults to Open so your queue stays focused.
Sort (Oldest / Newest)
A toggle on both the Board and the Workbench flips the order by the date the lead entered — Oldest first by default, so the longest-waiting cases sit on top. On the Workbench, action priority still leads; the toggle orders cases within each priority band.
Search
Searches across name, email, phone, VIN, vehicle make/model, and Clio matter number. Great when a client calls and you need to pull them up fast.
The case card itself
The little badges on each card tell you what docs are uploaded:
- RO = repair orders
- Reg = vehicle registration
- Purch = purchase or lease agreement
- Add'l = any additional supporting docs
Green = uploaded. Gray = missing. 📞 = call needed (client unresponsive).
+N (blue pill) next to the client name = N uploaded docs are not yet marked processed. This is a per-document count — every file on the case where nobody has clicked ✓ Mark processed yet. It's shared across the whole staff team (since you all share a login), so it's the single source of truth for "still needs eyes." Open the case → Docs tab → click ✓ Mark processed on each file once you've reviewed it. The number drops to zero when everything is processed.
📞 next to the client name = a call is due. Hover it for when; open the case for the script. It's set early (a new lead or completed quiz within the hour, stalled documents on day 2, an unsigned retainer at 48 hours) and again when the GHL reminder emails run out. See "Call flags & call scripts".
Time-in-stage pill (top right of card) shows how long the case has been sitting in this column. Turns red after 3 days so stale cases jump out when you scan. It resets to now only when the stage actually changes — not when you open the case or edit notes.
The status pills (the row under the name) flag what needs you:
- 🆘 Help (red) = the client tapped Request for Help in their portal. It counts toward ★ Needs my action. Clear it from the case header with “mark handled” once you’ve followed up (see Request for Help).
- Reactivated (amber) = the lead was pulled back into the pipeline — via Reactivate & re-invite from the Archive, or the client’s own “Restart my case” in their portal. Tells you this isn’t a brand-new lead.
- Signed ✓ (green) = on an Accepted — Awaiting Signature card, the retainer has been signed (they’re a client now). See the stage notes below.
- Referral (violet) = lead attributed to a partner. EN / ES = the client’s language.
- ⭐ VIP = family, friends and others the firm wants looked after personally. Always set by hand: tick VIP when inviting, or press ⭐ on the case (once a Clio matter exists you'll see the matter description with “[VIP]” added before it saves). Press ⭐ again to remove it. A partner referral is not VIP unless someone marks it.
The Needs my action button
Click ☆ Needs my action at the top of the board to hide everything except the cases that need a human right now. A case shows up here if any of these are true:
- It's at Push to Clio → all docs are in and you need to push the matter to Clio for the intake specialist to review (or Hard Reject if it clearly fails).
- It has a +N blue pill → someone uploaded docs that haven't been marked processed yet. Catch-all for replacement docs and extras that landed in any stage.
- It shows 📞 Call Needed → the GHL chase workflow (LAF-006 for repair orders, LAF-010 for reg+purchase) sent all its reminder emails and got no response, so it set the per-case Call Needed badge. (It's a badge now, not a stage — the case stays in its document-collection lane.) Your job is to call the client: if they pick up, get the docs; if the case is truly dead, click Soft Close. The system will not auto-close from here — that decision is yours.
- It has a 🆘 Help pill → the client tapped Request for Help in their portal. Clear it from the case header with “mark handled” once you’ve followed up (see Request for Help).
Toggle the button off (★ → ☆) to see the whole board again. Start every morning with this filter on. Work through every card before switching to the full board.
What each stage means
The pipeline is 11 canonical stages in funnel order, organized into two staff queues on the board: Document Collection and Case Evaluation. (The first two stages are pre-queue intake.) Cases move automatically; you only act at one point — Push to Clio.
Intake (pre-queue)
New Lead — Just landed. Client hasn't started the quiz yet, or was invited via the Invite to Quiz button.
Quiz Sent — Quiz invitation sent; the client hasn’t opened it yet.
Quiz In Progress — The client opened the quiz but hasn’t submitted it yet (derived from when they started — it’s a board lane, not a separate pipeline stage). It splits out from Quiz Sent so you can tell who’s mid-quiz from who hasn’t started — a good cue for a quick nudge call.
Document Collection queue
Quiz Completed / Not Yet Uploaded — Client finished the quiz and has been asked for alldocuments up front (repair orders, registration, purchase/lease). The upload link has been emailed (LAF-030) and the chase sequence is armed.
Collecting Documents — At least one document is in; we're still waiting on the rest. Which docs are in is read from the per-document flags (the RO/Reg/Purch/Add'l dots), not the stage. Automatic reminders run (LAF-006 / LAF-010) at Day 2, 4, 6, 8; after Day 8 with no response the case gets the 📞 Call Needed badge so you call them.
Case Evaluation queue
Push to Clio — All required documents are in. Review everything and click Push to Clio to create the matter for the intake specialist — the accept/reject decision is made in Clio, not here. (Use Hard Reject only if it clearly doesn't qualify.)
Matter Created / Pending Review — The matter is in Clio at the "Needs review by intake specialist" stage. Once a specialist accepts it in Clio, the case is accepted and litigation takes over; the case keeps moving through the lanes below as Clio updates. If you move a case into this lane by hand from an earlier lane (the Stage dropdown on the case card), the Clio matter is moved to that same stage for you, so the lane and the matter can’t disagree. Moving a case that is already past acceptance back into this lane does not rewind Clio — reversing a decision goes through Hard Reject or a stage change in Clio.
Accepted — Awaiting Signature — The case is accepted and the retainer has been sent; we’re waiting on the client’s signature. Once signed, a “Signed ✓” badge appears on the card (they’re a client now) and the case advances to FRA.
FRA Sent — The Formal Repair Attempt letter has gone out to the manufacturer. On the case’s FRA panel, once the letter is sent the status banner shows a clickable USPS tracking number — click it to open USPS tracking in a new tab and confirm delivery.
FRA Delivered — Deadline Running — The FRA was delivered; the manufacturer's response deadline is running.
In Litigation — The case is active in the litigation playbook (complaint, discovery, motions, etc.).
Closed — Terminal. Covers every ending: hard-rejected, soft-closed, or resolved/won. Re-openable. Won vs. lost is read from the case outcome, not the stage.
On 📞 Call Needed: this is a per-case badge, not a stage. The case stays in its lane. It's set by the early call flags below, and also by GHL (LAF-006 / LAF-010) once the chase emails have run out.
The Today strip (top of the Workbench)
The first thing on the Workbench is Today: what needs doing now, how today's calls are going, your own week, and the team's goal. It's built to help you clear the day, not to rank anyone.
- Do now chips: calls due now (and overdue), later today, cases with documents to review, retainers unsigned 48+ hours, and reviewed cases that need a no-retainer reason. Tap one to filter the list or see the names. ▶ Start calling deals the flagged calls one at a time, soonest due first.
- Today's calls: handled vs still open. A voicemail counts as handled; the flag stays on for the follow-up.
- Your week is only visible to you: calls logged, flags you called by their due time, how fast you reached new leads, and clients who signed after you called them — each against your own last week.
- Team this week: the share of new leads reached within 1 business hour against the goal (an admin sets it in Settings → Call flags and scripts; default 80%), and this week's signed clients, named by client only, with what worked (“reached within 40 min”, “signed 2 days after the retainer call”) — the habit, not the person. Under a win you worked, a green line shows your part, only to you: “✓ you called 2 days before they signed (3 calls)”. Everyone sees their own, so the feed connects each person's work to the outcome without ranking anyone.
- 👏 Shout-outs (off unless an admin turns them on in Settings → Call flags and scripts): tap “shout-out” on a signed client to thank a colleague who helped, with an optional note. Everyone sees shout-outs, and they're the only place staff are named to each other — because a person chose to say it, not because the system counted it. You can thank the same colleague once per client.
Admins see everyone's numbers side by side in the Team table at Analytics → Team, and can look at anyone's Workbench: Viewing the Workbench as at the top of the page shows that person's cases (Mine), their tasks and their Today strip. Anything you do from there is still done as you.
Call flags & call scripts
A call is flagged early, while the client is still engaged: research on lead response finds a call within the first hour is about seven times more likely to reach a real conversation than one an hour later. Times count the firm's business hours (Settings → Business hours; holidays count as closed), so a lead that comes in at 10pm is due one hour after opening the next business day.
| Board label | When | Call by |
|---|---|---|
| 📞 Call — quiz just completed | The client finished the quiz and no one has called since | 1 business hour |
| 📞 Call new lead | A self-serve lead (quiz, ad, partner) no one has contacted | 1 business hour |
| 📞 Call — help with … | 2 days after the quiz: documents still missing, nothing uploaded, no contact in 2 days | End of that business day |
| 📞 Call — retainer unsigned | Retainer sent 48 hours ago, not signed, no call since | End of that business day |
| 📞 Check in — client gone quiet | A retained client was nudged and hasn't opened their portal in a week | — |
| Reach out for quiz / Reach out — missing … | The UrVeedaOS reminder emails ran out (quiz or documents) | — |
The script. On the case, the 📞 Call flagged panel (under the client's details) opens with the script for that reason, filled in with the client's name, vehicle and missing documents:
- the goal;
- what to say, tell and ask;
- answers for common pushback;
- a voicemail to leave;
- a follow-up text, shown only when the client agreed to texts;
- what to record afterwards.
No call flagged? The panel still offers the best-fitting script. On quiz and document calls, the step-by-step Call guide is right below it.
Out-of-state clients. A client who lives outside Florida gets the out-of-state script on any call, whatever the flag. Their claim goes to an attorney licensed in their state, which takes longer, so the script tells them why it takes longer and that we're working on it. Use the Script menu in the panel to switch to another script.
The flag clears when you record an answered call, an email or a follow-up date, when the client uploads, or when the case closes. A voicemail or no-answer leaves it on, because the client still needs reaching. It doesn't come back for the same reason once you've reached them.
Settings → Call flags and scripts (admin) is where you:
- turn each early flag on or off;
- set the callback number used in voicemails and texts;
- rewrite any part of any script (clear a box to go back to the default).
The case detail page
Click any case card to open the full case.
✉ Copy the maildrop address
Once a case has a Clio matter, ✉ Copy maildrop sits under the Clio Matter # at the top right of the case page, and ✉ Maildrop sits on its board card. One click copies the matter's maildrop address; paste it into BCC on any email to or about the client and the email files itself into the matter. The button on the board card copies without opening the case. If copying is blocked, hover the button: it shows the address.
📝 Add a note (to Clio and UrVeedaOS at once)
The Add a note box is at the bottom of the case page, under every tab. Type the note and press Add note; it's signed with your login name. It goes to the Clio matter's timeline (or the client's Clio contact if there's no matter yet) and to the UrVeedaOS contact's notes. A note written before Push to Clio is copied onto the matter when it's created.
⏱ Still running for this client (and how follow-ups stop)
Near the bottom of the case page, Still running for this client lists every automated follow-up still going: the document chase (emails and texts asking for missing documents), retainer reminders, a 📞 call flag and RO-Nurture. It only appears when something is running.
- Closing a case stops them by itself: Soft Close, Hard Reject (or PNC Rejected in Clio), referring out (from the portal or the Clio Referred Out stage), an opt-out (STOP, unsubscribe, DND), the automatic close of an unsigned retainer, and a closed Clio matter, however the portal hears of it (the live webhook, the nightly sync, the settlement sync, Refresh from Clio or a Clio import). Nothing is sent to the client; the closing step sends whatever it normally sends.
- PNC Rejected and Closed in Clio also marks every open task on the case and the matter complete, in the portal and in Clio, so nothing is left on anyone's list.
- Stop all is for the in-between cases: the case stays open but the follow-ups should end, for example a client who says they hired another firm. Type why (it goes on the case and in Clio) and press Stop all.
- Brought back? Reactivating, re-inviting to the quiz, bringing a referral back in-house or lifting an opt-out makes the case live again. To restart the document chase, use Resume document chase.
- A matter closed only to park it for RO-Nurture isn't a finished case: the nurture keeps running.
- Status page → Finished cases still in a chase lists finished cases that may still be getting follow-ups (mostly ones closed before this existed). Press Stop on a row, or Stop all. A client whose matter was closed in Clio to park them for RO-Nurture isn't listed, and Stop never ends their nurture.
The Next-action beacon — read this line first
The coloured bar at the very top answers "what does this case need next?" — the same answer, computed the same way, as the chip on the board row, so the two never disagree. It names the action ("Reach out — missing repair orders", "Review 2 docs", "Send FRA", "Retainer out — chase signature") and, where it can, how quiet it's been ("last contact 9 days ago"). The yellow button on the right jumps straight to where that action happens and scrolls you to the exact spot — the specific document row still awaiting review, the stuck video's row, the FRA wizard, the retainer panel, or the ✅ Push to Clio button itself. The thing you were sent to flashes for a moment so you don't have to hunt for it.
A beacon without a button means the action has no single screen behind it — most often a retainer that's gone quiet after the case already moved on from Retainer Sent. The line is still the reminder; there's just nowhere to jump.
No beacon = nothing for you to do — the case is waiting on the firm's own process. You don't need to open tabs to verify that; that's the point.
A grey “Case over” line means the case is finished: rejected (Hard Reject or PNC Rejected in Clio), the Clio matter is closed, or it was soft closed or opted out. No next step and no call script shows, even if an older step (an unsigned retainer, say) never finished. If it's wrong, use Reopen Case.
The card layout — two columns + a context rail
The page is two columns: the working tabs on the left, and a sticky context rail on the right that stays put as you scroll. The rail shows the hard Deadlines — the SOL date and the FRA response deadline, each with a days-left countdown that turns amber (≤ 90 days) then red (≤ 30 days or overdue) — the live Clio matter stage/status, and a Timeline: a chronological milestone feed (lead entered with its source, quiz completed, contacted, retainer sent/signed, FRA sent/delivered, and more), each row showing its date and how-long-ago.
The header carries a compact deadline chip beside the client name showing whichever hard deadline (SOL or FRA) is nearest, in the same color code. Identity, contact, vehicle, and the Clio matter # sit across the top; the denser IDs and tools (case #, contact id, UrVeedaOS / Clio / purchaser links, Re-sync, Send quiz) are tucked behind a Tools & IDs ▾ disclosure so the top stays clean. The Stage selector stays visible.
The card also opens on the tab that matters for the case's current stage — a doc-collection case lands on Documents, a Pending-Evaluation case lands on Actions — so you usually open straight to the work.
The five tabs:
Documents
All files the client (and you) uploaded. Each row has two separate buttons:
- 📥 Download — pulls the file down to your machine. Has no side effects; clicking it never changes the processed/unprocessed status.
- ✓ Mark processed — for core documents (Repair Orders, Registration, Purchase/Lease), clicking this opens a popup asking you to upload the cleaned / renamed version first. Once you upload the cleaned file(s) and confirm, the original client upload is marked processed and the cleaned version is added as a Staff document (pushed to Clio if a matter exists). For Additional docs and videos, no upload is required — clicking just marks the item directly. ✗ Mark unprocessed always clears the flag immediately with no popup.
The three-state Document completeness pills (Actions tab):
- Gray — = no document uploaded yet for that type
- Blue ● = uploaded by client, awaiting staff review
- Green ✓ = processed by staff (cleaned version uploaded) — required for Accept
You can also:
- Download all docs as a single ZIP using ⬇ Download all (ZIP)
- Request a replacement doc if something's unreadable or wrong (see "Re-requesting documents" below)
Why "Mark processed" matters: the count of unprocessed docs powers the blue +N pill on each case card. It also hard-gates Push to Clio — the button is disabled while any client-uploaded document is still blue (not just the three required types), with a blue note counting what's left, so no matter reaches Clio with unreviewed "blue-pill" documents (staff uploads and videos don't block). If a client uploads 5 ROs and you process them, then they upload 2 replacements — the +N pill correctly shows "+2" and Push stays blocked until you triage just those new ones.
🎥 Videos — review without downloading
Vehicle and RO videos appear in the Documents tab alongside everything else, each showing a status badge (Under Review → Accepted). You don't download and re-upload videos — click 🎬 Review video on the row to open a popup that plays the video inline from Google Drive and lets you handle it in one place:
- Rename + ✓ Accept & push to Clio — type a clean name, then Accept. This renames the actual Google Drive file to match, and adds a one-page PDF reference (a Drive link + case metadata) to the Clio matter's Client Folder. The video itself stays in Drive — it is never downloaded to our servers or pushed into Clio as a huge file, so attorneys stream it straight from the link. (The case must already have a Clio matter — accept the case first.)
- ↻ Request re-upload — emails the client a fresh upload link (bad angle, too dark, wrong clip). The Drive copy is kept.
- Discard — drops the portal reference. The Google Drive copy is always kept as a permanent chain-of-custody backup, even after discard.
If the Clio upload fails, the badge shows ⚠️ Clio Upload Failed and the popup's Accept button becomes Retry → push to Clio. Videos are not part of the Push-to-Clio document hard block — they have this separate flow.
Quiz Answers
Everything the client filled out on the intake quiz — their issues, repair history, dealership info, purchaser/co-purchaser, etc. Read-only.
🚗 Vehicle Intel
Pulls NHTSA recall, complaint, and Technical Service Bulletin data for the VIN. The big stat cards at the top show counts. Recalls with a red "PARK IT" badge are safety-critical. Use this to gut-check the case (e.g., a vehicle with 14 active recalls and 80+ complaints for the same problem is a strong case).
⚡ Actions
Where you make decisions. Always pick your name in "Performed by" first — every action is logged with who did it.
Compact vs. full layout. By default the Actions tab shows in Compact view: it keeps the primary decision for the case's current stage on the surface (Overview + Push to Clio, or the live post-acceptance action) and tucks the less-common controls — Hard Reject, Soft Close, Reopen, Activity Log, Time, plus the secondary boxes (Portal Access, RO Nurture, Pause Chase, Partner Assign) — under a tap More(a drop-down on desktop, a bottom sheet on mobile). Nothing is removed; it's only moved a layer down. Prefer every button and box expanded at once? Turn Compact off with the small link under the buttons, or under Account ▾ → Preferences — the choice is remembered on that device.
⟳ Keeping the card in sync with Clio
The accept/reject decision and every stage after it happen in Clio, and the card stays current through webhooks. Two safety nets cover the moments a webhook is missed:
- Auto-refresh on open — opening a case pulls its live Clio stage in the background, so the card usually reflects Clio the moment you look at it.
- ⟳ Sync from Clio (in Tools & IDs ▾) — click it if the card still looks out of date: it pulls the live matter stage, moves the card to the matching column, and repairs a deleted/duplicated Clio-contact link by re-matching on email. Read/repair only — no client emails, and it never creates a matter or contact.
- 📁 File Clio docs into folders (in Tools & IDs ▾) — use when the portal's files show up loose at the top of the matter's Documents tab instead of inside Client Folder. It moves every document the portal sent into Client Folder, and the second copy of each repair order into Letters (repair orders go to both on purpose, which is why loose ones appear twice). A repair order that only ever reached Client Folder is sent to Letters too. Safe to click more than once. If a Letters copy already failed and gave up, the button says so instead of sending another; fix that one in Sync Health. A document that lives on a different Clio matter (a card that was re-linked) is left where it is. The portal no longer drops files at the top level: if it can't find the folder, the upload waits in Sync Health with the reason instead.
- ⇄ Change matter — use when a client has two Clio matters and the card is following the wrong one. That happens when a matter already existed before the case reached the portal (a hand-off from the MAC portal, say) and Push to Clio then created a second: the notes and time entries end up in one matter and the client’s documents in the other. The picker lists every matter Clio has for that client and links the one you choose.
Two things it deliberately does not do. It won’t take a matter another card already tracks — two cards writing notes, time and stage changes to one matter is worse than the split you started with. And it moves the link only: notes and time already pushed to the old matter stay in Clio where they were written. Documents are re-filed onto the newly-linked matter automatically (it dedupes, so nothing lands twice). Afterwards you’re offered a button to close the abandoned matter in Clio.
☎ Mark contacted — log the outcome + set a reminder
Use ☎ Mark contacted (top of the case) after you reach out to a prospective client. It opens a short popup to record how it went, and the button then shows that outcome (e.g. ✓ Contacted: Call (Voicemail)). It's an internal signal — it's what turns the Contacted flag green on the Analytics PNC Watchlist. The outcomes:
- Call (Answered) · Call (No Pickup) · Call (Voicemail) · Email — internal record only; no client email, no GHL/Clio side effects.
- Abandoned / Opt-Out — routes by pipeline stage, and the popup tells you exactly what it will do before you confirm: at the quiz stage → marks the lead Quiz Abandonedand closes it; once they're sending documents → Soft Close (archived, still nurture/reactivation-eligible); anywhere else → Not Interested. One control, stage-aware.
Optional follow-up reminder. The popup lets you snooze a callback — in 1 hour, in 4 hours, tomorrow, or in 3 days. That shows as a due-date chip on the case so the next touch doesn't slip. The first staff action on a case still counts as contact automatically; this button is the precise override. Click the green pill to clear it.
Clears the 📞 Call/reach-out badge automatically when you actually reach the client (Call Answered / Email) or set a follow-up reminder; a no-pickup / voicemail with no reminder leaves the badge up (they still need reaching).
Pause automated document-request follow-up emails — a checkbox in the popup takes the client off the doc-chase drip in the same click (handy when you just spoke and they said docs are coming). It's the same as Remove from doc chase; reverse it later with ↻ Resume doc chase.
Not going ahead? Ask why, every time. When you reached them (Call Answered, Email or Abandoned / Opt-Out) the popup asks Are they going ahead with us? Choose No, not going ahead, ask “Can I ask what made you decide? It helps us do better,” and pick the reason (another firm, and which one if they say; the fee; too much paperwork; stopped responding; not eligible). It's saved as why they didn't become a client, goes into the Clio and UrVeedaOS note, and shows in Analytics → Why we lost them. It doesn't close the case: Soft Close does, and starts from the reason you picked. Every call script and the Call Guide end with this step. A client who declined the retainer is asked about on the case page until a reason is recorded.
✅ Push to Clio — create the matter for review
Push to Clio creates the Clio matter — it does NOT accept the case. The accept/reject decision is decoupled: pushing to Clio lands the matter at the "Needs review by intake specialist" stage, and a different staff member then evaluates the documents in Clio and makes the call there by moving the matter stage. No client email is sent at this step.
When to use: All required docs (RO + Reg + Purchase) are uploaded and reviewed (green ✓ completeness pills), so the matter is ready to be created and handed to the intake specialist for evaluation.
Auto-populated on push: if the case is a referral with a partner assigned, the matter's LAF Referring Law Firm, Referral Rate %, and Refferal Source fields fill from the partner, and the firm is linked to the matter as a related Referring Firm. Refferal Source is never left blank, and you never set it by hand: a partner referral is Reffering Attorney; a lead from one of our paid campaigns (search, social, programmatic, video/CTV, QR, print…) is LAF Paid Campaign; everything else is LAF website. The same rule applies to a hard reject and when a partner is removed. The Clio note at push says exactly where the lead came from (channel, platform, campaign) and how the portal knows. See How a lead is counted as paid under "Clio fields the portal writes". The manufactureris created (once) as a Clio company contact if one isn't linked, and its name also lands in Defendant Name. Fee $ stays manual / at settlement.
What you do:
- Open the case → Actions tab → click ✅ Push to Clio
- Confirm the manufacturer's legal name (required)
- Enter the dates (delivery, date of contract, warranty expiration, and the first-repair / discovery date — that one also saves to Clio as the Vehicle Inspection date), then pick the SOL jurisdiction State. The system applies that state's anchor + limitation period and the ⚡ Calculate button fills the Statute of Limitations date (still editable). You don't pick the anchor. The quiz captures both the client's Residence and the dealership/Purchase state — when they differ you get one-click chips for each, so pick whichever governs.
- Confirm vehicle details, mileage, and issue description
- Pick originating and responsible attorneys
- Enter purchase price and case evaluation (the ⚡ Calc button does the standard math for you)
- Pick who gets assigned the kickoff Clio tasks
- Click Push to Clio & Create Matter
What happens downstream:
LAF {Client} v. {Manufacturer} for a standard case, or LAF-R ({PARTNER REF CODE}): {Client} v. {Manufacturer} when the case came in through a referral partner, so referred matters are recognizable at a glance.📦 Consumer product cases (not a vehicle)
Checking whether it is on…
A warranty claim on something that isn't a vehicle — an appliance, a generator, an e-bike — runs through the same portal under the same federal law (Magnuson-Moss). It is entered by staff, not the quiz: New case → Consumer product. The option appears only while an admin has it On in Settings → Product cases.
- The serial number stands in for the VIN and the brand is the manufacturer. Type the brand and the form tells you whether its mailing address is on file. The address is in the written warranty. Best: an admin adds it in Settings → Manufacturers before Push to Clio, so Clio gets the address and the manufacturer contact by itself. Not an admin? Push anyway, then add it from the case's FRA screen with Add it now.
- Documents to collect is a list you shape. It starts as receipt or proof of purchase, the written warranty and repair or service records (required), plus photos or video and letters from the manufacturer (optional). Tick, untick, reorder, add your own. The client's upload page shows exactly that list, and each upload lands on its item. No registration, no CPO booklet.
- Nothing chases a product client by itself. On the form choose Send the document request now(one email, with the portal link) or Just send the portal link. Later, the case page's Documents to collect panel has Send document request / Send again (24-hour cooldown). If nothing is uploaded five business days after a request, a 📞 docs-help call flag appears.
- Push to Clio works as for a car: brand → manufacturer, serial → the VIN field, brand and type → Make and Model, purchase year → Year, cause of action Magnuson-Moss. No "collect registration" task is created. The intake note lists the product details.
- Push to Clio asking for a Deal #, mileage or a delivery date? Then the card is still a vehicle card (the client took the vehicle quiz first, or two cards were merged before 3 Nov). At the top of the Push to Clio form, click Make this a product case: the form switches to the product fields and the client's list becomes the product list. If the client was getting the vehicle document reminders (“send us your registration…”), those stop at the same moment. Then use Send document request to ask for the product's documents. It works only before the push (after that, change the matter in Clio), not on a card with a real 17-character VIN, and only while product cases are On. Make this a vehicle case undoes it.
- The board card shows a Product chip. The FRA wizard's product letter template is a separate, later step; ask before generating a letter on a product case.
❌ Hard Reject
When to use: The case clearly doesn't qualify and you don't need the Clio intake review — common reasons: vehicle outside warranty window, issues don't rise to lemon law threshold, wrong jurisdiction, fraud red flags, duplicate case, etc. This is the same outcome as moving the matter to PNC-Rejected in Clio — both fire the "case not qualified" path. Use one or the other, not both. (The Hard Reject button lives on the Actions tab under Decision.)
What you do:
- Open the case → Actions tab → click ❌ Hard Reject
- Pick the rejection reason (this is shown to the client)
- Add internal notes (these are NOT shown to the client — just for our records)
- Click Hard Reject Case
What happens downstream:
✍ Client signs the agreement at account setup
Checking whether it is on…
Off until an admin turns it on (Settings → Client signing). When it's on, every client who completes the quiz from then on opens their account on one step: Send me my agreement. Clients already in their portal are never affected.
- It feels like a two-step sign-in: the account shows locked, the screen shows where the agreement will go (the email partly hidden, and the phone's last four digits when they agreed to texts), what unlocks once it's signed (an attorney reviews their case, no upfront cost for us to review it, their own portal), and one button: Send me my agreement.
- UrVeedaOS emails the attorney-pre-signed agreement straight away (workflow AGREEMENT-SEND). If they agreed to texts, the link is texted too.
- Then a three-step tracker: Sent ✓ → Waiting for your signature → Your account unlocks, with the sender, the exact subject and “check Spam or Promotions”, and Resend, Change email, Change phone and I already signed. When the signature arrives the screen shows Account unlocked and carries on.
- When they sign, the account opens on its own, the signed copy appears in their Documents (and on the Clio matter if there is one), and Clio gets one note.
- The agreement is their retainer. When you move the matter to Accepted in Clio, they get a “case accepted, nothing more to sign” email instead of the retainer email, no retainer reminders, and after 5 minutes the matter moves on to Pending FRA by itself (Clio and the board), like Mark Retainer Signed. Undo within those 5 minutes cancels it.
- Which agreement: the portal picks it by the client's state (English only, one per state:
AGREE-TX, orAGREE-TX-REFERRAL; a Spanish speaker's screen says the agreement is in English and gives the number to call to go over it in Spanish), and sends the referral version when the client came through a partner's referral link, the quiz was sent as a referral, or a partner is attached. Marking or unmarking referral after they signed puts “Agreement version to check” in the Activity Log and on the Clio matter, for the attorneys.
On the board a client who asked for the agreement and hasn't signed shows Agreement sent — not signed yet on their card.
On the case page the contact line shows Agreement: where they are (sent, waiting, declined, “says they signed”, signed).
- Unlock account opens it without a portal signature, for example when they signed on paper. It asks why, and the reason goes on the case.
- “I already signed” with nothing back from UrVeedaOS after 15 minutes, or a decline, raises the 📞 call flag (Retainer script). Check the contact's Documents in UrVeedaOS first.
- Change email or phone from the client updates the portal, UrVeedaOS and Clio, with a line in the Activity Log. A new phone needs new text consent. An email or phone another case already uses is refused, and the client is asked to call.
- Texts to clients. Leads can be texted only after they tick “Text me about my case” (or staff record it on the case page). Clients are different (firm policy, 11 Nov 2026): when a retainer is marked signed, or a Clio matter is imported, the portal records consent as existing client (firm policy) and lifts the text block in UrVeedaOS, so they get case updates. It never does this for a client who replied STOP, opted out, or had texts turned off by staff on the case page. To stop texting a client, use the case page's SMS control. Clients from before this are caught up once from Settings → Communications → Texting for existing clients.
Texts: clients who said no to texts on the quiz are asked again at the agreement step, right after signing, then at most once every 30 days when they open their portal. Never after a STOP, and never after three no's. Every answer is on the case with the exact words they saw.
🕘 Business hours
The firm's one clock, set by an admin in Settings → Business hours: opening and closing time for each day (or closed) and the holidays. Everything that counts time reads it: when an early call flag is due, the Workbench's “reached within an hour”, speed to lead in Analytics and the monthly report, and when follow-ups go out. A lead that arrives on Friday night and is called at 9:15 on Monday was reached in time. The reports also show the round-the-clock time beside it, which is what the client waited.
Staff grace. Staff are timed on a slightly shorter clock: it starts 30 minutes after opening and stops 30 minutes before closing (an admin changes both under Settings → Business hours). With 9 to 5 that's 9:30 to 4:30, so you have time to get in and settled, and to wrap up. It applies to call-flag due times, “reached within an hour”, the team goal, Your week and speed to lead in the reports. A lead that comes in at 4:45 is due by 10:30 the next morning. When follow-ups go out to clients, and whether a lead arrived while we were closed, still use the firm's real hours.
📬 Follow-ups after the quiz
Checking whether it is on…
Off until an admin turns it on (Settings → Follow-ups), and only for clients who complete the quiz while Client signing is also On. Everyone else gets exactly what they get today.
- The welcome email goes as soon as the quiz is done. The usual “call within 1 business hour” flag is the setup call.
- Then, on business days only: step 1 the next day, step 2 three days later, step 3 the day after. Each step sends an email in the morning, flags a call that day, and sends a text in the afternoon (texts only to clients who agreed).
- Each step asks for what's missing next: the agreement if it isn't signed, otherwise the documents by name. It stops by itself when the agreement is signed and every document is in.
- Closeout: a client who never signed gets a closeout email and text and the case is soft-closed (“Client stopped responding”). A client who signed but still owes documents gets a 📞 call flag instead, never an automatic close.
- 📞 Call — agreement not signed on a card is a follow-up call. Open the case for the Account setup script.
- The case page's Still running panel shows the next follow-up and when. Stop all ends it.
- While it runs, the document chase isn't running. To start it after the closeout, press Resume doc chase.
- Clients in the sequence see what's left at the top of their portal home page.
🔄 Soft Close
When to use: Client has stopped responding. Usually used after chase reminders have run their course (the system tells you when this happens by setting the case's 📞 Call Needed badge).
What you do:
- Open the case → Actions tab → click 🔄 Soft Close
- Pick why they didn't become a client (usually “Client stopped responding”; for “went with another firm” add the firm if you know it). If the caller already recorded a reason in Mark Contacted, it's filled in.
- If Settings → Communications has the survey on Ask, leave Send the short survey ticked (or untick it); on Automatic it always goes, two days after the close email
- Optionally pick which doc type they ghosted on
- Add internal notes
- Optionally upload any docs you have on hand (e.g., from a phone call)
- Click Confirm Soft Close
What happens downstream:
↩ Undo a decision (5-minute window)
Every decision — Accept, Hard Reject, and Soft Close — is held for 5 minutes before the client-facing side effects fire. The portal logs the decision and reverts the stage immediately, but the client email and the UrVeedaOS/GHL tag (e.g. case not qualified) are queued on a delay. That delay is your safety net: click ↩ Undo within the window and nothing ever reaches the client.
Where to find the Undo button:
- On the case page — an amber banner appears right after you decide, showing the exact time the emails will fire, with an ↩ Undo button.
- Anywhere else (Workbench / Board) — because the card auto-closes after a decision, a floating undo bar also shows in the bottom-right corner of every page, counting down from about 4:57. This is how you catch a misclick after you’ve already moved on. It disappears when the window closes or when you dismiss it.
What Undo does — and doesn’t — do:
Two caveats: (1) the undo bar is session-local to your browser — if you close the tab, use the amber banner on the case page instead (or the Reopen action once the window passes); (2) once the 5 minutes elapse the emails have already been sent and can’t be unsent — at that point use Reopen for a fresh start rather than Undo.
🚫 Opt-outs (DND / STOP / unsubscribe)
When a contact replies STOP, unsubscribes, or is set to DND in GHL, an automated GHL workflow tells the portal, which closes the case silently as “Not Interested” — no rejection or closing email is sent (they asked us to stop). The card gets a 🚫 Opted Out pill and a banner on the case page.
What happens automatically:
- The case is closed and all chase/nurture stops.
- The GHL opportunity is set to Lost (kept at its current stage).
- The portal blocks re-invite — Invite-to-Quiz / Bulk Invite / Send-quiz will refuse with a “contact opted out” message.
If they opt back in (reply START, or call you to re-engage), reactivate them — either from the case’s Reactivate & re-invite button, or from Archive → Opted Out (their own tab, separate from Soft Closed). That clears the opt-out and re-invites. The client can also self-serve via Restart my case in their portal. Don’t re-contact an opted-out person any other way.
⚠ Reactivating clears the portal opt-out, but GHL still has them on DND — so SMS/email won’t actually deliver until DND is lifted in GHL (or they text START). Lift DND in GHL when you reactivate a STOP/DND contact.
🆘 Request for Help
Clients can raise their hand from their own portal: they tap Request for Help and the case is flagged for staff. It’s the client-initiated counterpart to the chase badges — a direct “please get in touch” signal.
How you see it
- A red 🆘 Help action-pill appears on the case card on the Board and Workbench.
- It counts toward ★ Needs my action, so a help request surfaces in the same queue you already work top-to-bottom each morning.
How you clear it
Open the case — the header shows a 🆘 Help requested — mark handled button. Call or message the client, then click mark handled to clear the flag (the pill drops off the card and it leaves the Needs-my-action queue). It doesn’t change the case’s stage — it’s purely an attention flag.
💰 Settlement & Mark Funds Disbursed
These are post-acceptance actions — only relevant once the case has been accepted, a Clio matter exists, and the litigation team has worked through to a resolution. The Settlement tab on the Actions panel becomes available once Clio moves the matter to the Settled stage (or the case is past that point).
When Clio hits Settled — the amber banner
The moment a Clio stage change pushes the matter to 13. SETTLED, the portal sets a flag on the case and an amber "Settlement data required" banner appears at the top of every tab on that case. Email 6 (Resolution Reached) is held backuntil you fill in the settlement figures, because the email template merges in the dollar amounts and we don't want the client receiving a numbers-blank email.
Entering settlement data
What you do:
- Open the case → Actions tab → click 💰 Settlement
- Review the side-by-side verification table — it shows what's currently in the portal, in Clio, and in UrVeedaOS. Mismatches are flagged with a red ⚠. Missing values (in Clio or UrVeedaOS) show ○. The portal DB is the system of record; the other two are what gets pushed.
- Fill in: Total Settlement Amount, Attorney Fee Amount, optionally Attorney Fee %, Client Payout Amount, and Litigation Costs.
- Referral fee (partner-referred cases): it auto-calculates from the partner's fee schedule applied to the net attorney fee (attorney fee − litigation costs). The resolved % / $ pre-fills and is editable; you can also enter a one-off per-case referral % override or tick class action (uses the class-action rate). The saved referral fee writes to both this case and the partner's referral record — no double entry. (Lifetime-mode partners who cross a tier get a tier-upgrade email; the new rate applies to their future cases only.)
- Click Save Settlement Data & Send Email 6.
What happens downstream:
CLIO_CUSTOM_FIELD_IDS), and an audit note titled "Settlement data entered by [you]" is added to the matter timeline with the full breakdown. The matter note always lands — even if individual Clio custom field IDs aren't populated yet, the data is in the timeline as a note.Marking funds as disbursed
When to use: Once you've physically mailed the settlement check to the client. Not before — Email 7 tells the client their money is on the way.
How you know it's time: when the matter reaches the Settled stage in Clio, a task titled "Mark Funds Disbursed in Staff Portal" is auto-created and assigned to the case's responsible staff. (It's created at Settled — not at acceptance — so accepted cases that never settle don't pile up dangling tasks.) When you mail the check and click the button below, the portal auto-completes that Clio task for you — you no longer close it by hand. If a case is closed/lost without settling, the task is cleared automatically too.
What you do:
- Open the case → Actions tab → click 💰 Settlement
- Scroll to the bottom: "Mark Check as Mailed (Email 7)"
- Click Mark Check as Mailed — Send Email 7
- Confirm the browser prompt (this is irreversible)
What happens downstream:
Why "Case Closed — Won!" depends on the disbursement, not the close
Clio doesn't have a won/lost outcome field for our practice area — matter.status=closed covers wins AND losses equally. So the only way the portal knows a case was a win is whether you clicked Mark Disbursed. If Email 7 has been sent, the client dashboard reads "Case Closed — Won!". If Email 7 hasn't been sent and the matter just closes, it reads plain "Case Closed".
✉ Sending an FRA letter (Lob certified mail)
Checking whether it is on…
FRA = Formal Repair Attempt — a letter mailed to the vehicle manufacturer via USPS Certified Mail (through Lob). It's a litigation step that happens after the case is accepted and the retainer is signed, and its delivery starts the manufacturer's response clock. The FRA-sent client email fires the moment you send it (no longer waits on the Clio stage), so the client is notified right away — and if you shared the letter (below), they can log in and view it.
Before you can send (prerequisites)
- The case is Full Accepted and the retainer is signed.
- The Clio matter exists. The wizard's Generate step creates the FRA letter from the Clio template and files it into the "Letters" folder automatically — even if generation runs long, the letter is swept into Letters on its own (no more finding it in Documents and moving it by hand). You can also generate it in Clio yourself; either way it shows up in the wizard's Letters list.
In Assemble, you designate which document is the FRA letter (auto-detected from the file name, or picked for a manually-added one) — it's pinned to the top of the packet and you can't advance until it is. Build packet shows a progress popup and confirms the merged packet actually saved into Letters before you continue — no more “Merging…” with nothing to show.
What you do
- Open the case → Actions tab → ✉ Send FRA.
- Set Performed by (your name — it's logged).
- Step 1 — pick the document: default is Pull from Clio "Letters" folder → check the FRA document(s) (use Refresh if it's not listed yet). Or switch to Upload a PDF instead. Each Clio row also has a 👁 Show client radio: tick one document to also surface it in the client's portal ("show our work") — optional, off by default, and you can only share a document you're sending. It appears in their Documents list badged ✦ From our team.
- Envelope — recipient address (the manufacturer): name, address, city, state, ZIP. The address comes whole from one place: the Clio matter's manufacturer address when street, city, state and ZIP are all filled there, otherwise the address in Settings → Manufacturers. It is never half one and half the other. If the envelope address is not the Settings one, an amber note shows both and a Use the Settings address button. Mailing is not blocked: a case can really go somewhere else (a newer address, a registered agent). An empty recipient blocks Send (Lob has nowhere to mail it).
- Letter check: the Required matter fields list only shows that the Clio matter has the values. After Generate, the portal reads the letter Clio made and checks that it actually prints this client's surname, the defendant, year, make and model and VIN, and that nothing is left as a placeholder (like <<Field>> or [TRACKING NUMBER]). A red result blocks Next until you open the letter and tick that it's correct. Every letter in the list has Open and Check.
- Before mailing: the Send step reads the whole packet the same way and has Open the packet. Mail stays off until you tick that you opened it and the name, vehicle, VIN and manufacturer's address are right. The tick is logged on the case.
- Click Send FRA Letter via Lob.
You do not enter a tracking number or delivered date — those fill in automatically.
Two letters to two recipients (manufacturer, dealership, opposing counsel…)
Every letter says who it is for: on the Packet step pick Manufacturer, Dealership, Opposing counsel, or Other and type it (the portal fixes capitals and spacing, so “registered agent” shows as “Registered Agent”). The label names the packet in Letters (FRA Packet - Smith - Dealership), the Lob mailing, the Clio expense, and the Clio note (“FRA Letter Sent: Dealership”).
- Put both letters in the matter's Letters folder in Clio.
- Mail the first one as usual (normally to the manufacturer). Its delivery starts the response deadline.
- Open ✉ Send FRA again. The banner lists the letters already sent; choose Mail another letter to someone else.
- Pick the second letter and its attachments, choose who it is for, build its packet, type its address on the Envelope step (it starts empty; Fill with the manufacturer's address is there if you need it), tick that you opened it, and mail.
The second letter has its own tracking and delivered date, shown on its own line in the banner. It never changes the first letter's tracking, the response deadline, the case stage or the client emails, and it is not shared to the client portal. Replace the first letter is only for a first letter that was lost or returned: that clears its tracking and deadline and starts them again.
What happens downstream:
Resend overwrites the tracking number and clears the delivery timestamp — only use it if a letter genuinely needs re-mailing. A resend does not re-email the client.
The deadline engine + playbook (Settings → Litigation)
After FRA delivery the portal can run the firm's MMWA deadline playbook — a 15-step cascade (FRA response monitor → complaint → motions → discovery enforcement) that arms each deadline as a Clio task/calendar entry and escalates to the next step if a deadline lapses without its off-ramp. The cross-case Deadlines board lives under Manage ▾ → Deadlines.
All of it is now configurable under Settings → Litigation (admin only, audited):
- Engine (on/off) — a single master switch. Off = the portal arms no litigation deadlines at all (no FRA-delivery auto-arm, no manual firing, no escalation sweeps). Use it if Clio's own workflows already track these deadlines. The FRA delivered date and the card-rail countdown still show either way — only the deadline/Clio-task automation is gated.
- Deadline Settings — every day-count (FRA window, discovery response, MTS, SDT, etc.) and the court-holiday calendar. Change a number, no deploy needed.
- Playbooks — the step-by-step cascade itself: triggers, offsets, owners (attorney/paralegal), and escalation branching.
⚖️ Litigation Deadlines (the firm-wide safety net)
The Litigation Deadlines page (Manage ▾ → Deadlines) is one place to watch every hard deadline across every litigation matter — soonest first. Every litigation matter carries court and statutory deadlines (serve the defendant, file a response, meet a discovery cutoff); missing one can sink a case. This page exists so none of them slip through the cracks.
Where the deadlines come from
You don’t create deadline watches here — they arm automatically. When staff fire a playbook step on a case’s Litigation tab, a watch is created that knows which gate event has to be logged and by when. The deadline engine (see the FRA / deadline-engine section) drives that cascade; this page is the read-across of everything it’s currently watching.
What the statuses mean
- Armed — counting down, on track. The gate hasn’t been logged yet but there’s still time.
- Escalated — the deadline passed without the gate being logged. These need attention today — they’re the whole reason the page exists.
- Resolved — the gate was logged (or the matter closed). Nothing left to do.
The status chips (All / Armed / Escalated / Resolved) filter the table; it opens on Armed.
What you can do here
- Work the escalated (red) rows first, then the soonest armed ones.
- Open the matter (from its Litigation tab) to log the gate event or fire the next step — that’s what clears a watch.
- Extend a deadline right from its row when the court grants more time — the countdown updates.
- ⚖️ Evaluate now forces an immediate re-check across all watches (it escalates anything overdue) instead of waiting for the scheduled background run.
- ↻ Refresh just reloads the current list from the database — no Clio call, no evaluation.
Each row shows the deadline date + countdown, status, the step + gate to log, the assignee role, and the Clio matter it belongs to. There’s also an “What is this page” panel at the top of the page itself with the same rundown.
If the page is empty
No rows usually means no watches match the current filter — try the All chip. If the whole deadline engine is switched off (Admin ▾ → Settings → Litigation → Engine), no watches arm at all; that’s intentional when Clio’s own workflows are tracking these deadlines instead.
Retainer: signed / declined & conversion
Checking whether it is on…
When a case is accepted, the retainer (fee agreement) goes out and the board lane reads Accepted — Awaiting Signature. The retainers live in UrVeedaOS, one per state, in English only, with and without referral, and go out from there. When Client signing is on (Checking whether it is on…), clients who finish the quiz sign their agreement at account setup instead, so they arrive already signed; staff-entered cases, consumer products included, get the retainer after acceptance as usual. You record the outcome from the case header: a Retainer: control with Mark signed / Mark declined buttons (they appear once the retainer has been sent). Clicking Mark signed puts a green ✓ Signed on the control and a Signed ✓ pill on the card — the client is now retained.
Why it matters — the Retainers analytics card
Those two clicks feed the Retainers card on the Analytics dashboard (Admin ▾ → Analytics → Review & retainers). It shows, of all retainers sent (cases that reached Clio), how many clients signed (the retainer sign rate) and declined, with each share, plus how many are still awaiting signature. It used to be a separate Retainer Conversion card. Marking signed/declined promptly keeps those numbers accurate.
Analytics dashboard — what each card means
Admin ▾ → Analytics is the firm-wide dashboard. A time-range selector (7d / 30d / 90d / 6mo / 1yr / All, plus Custom for an exact from/to date range — end date inclusive) sits top-right. It drives every section except Right now, which shows counts as of this moment. While a new range loads, the old numbers stay on screen dimmed under an Updating… note, so a half-loaded page is never mistaken for the new range. The ⬇ Export PDF button (next to the range) downloads a branded, printable report for the selected window — KPIs, a Cases summary, the pipeline funnel, by-source + campaign breakdowns, the money table, and a live Matters-by-stage table pulled straight from Clio — for emailing or archiving. ☁ Publish to Drive uploads that same PDF to the Analytics Reports Drive folder (monthly subfolder, shareable anyone-with-link) and hands you the link. Admins also get a ⚙ Targets button to set KPI goals + monthly ad spend (see below), and a 📄 Report schedule link to Settings → Reports: on/off switches for the weekly and the monthly report, the send day and time (Eastern), and the UrVeedaOS field each link is written to. Each report saves to the same Drive folder, writes its link to each admin's own UrVeedaOS contact (staff are contacts tagged LAF Staff, synced daily; Settings → UrVeedaOS → Staff contacts), then adds the tag analytics-report-weekly or analytics-report-monthly there, which starts the email workflow. The monthly one covers the whole of last month and goes out on the 1st. Make a report now on the same page runs one for the last week, any month or any dates, whatever the switches say. “Email it to” starts at Nobody (Drive only); Just me sends it only to you, All admins to every admin.
The page, zone by zone
The page opens in Summary: the Right now strip, Needs attention, Key numbers and the main funnel. Full detail shows every card (the page remembers your choice), and clicking a key number or an attention item opens the full page at its card. ⚙ Targets (also Settings → Reports) sets the target for each key number: green meets it, amber is within a fifth of it, red is beyond. Each key number also shows how it moved against the same length of time just before the range (none for All time).
Every card carries a Counts: label. Leads that arrived in range follows the range's new leads wherever they went since; what happened in range counts events dated in the range, whoever they belong to; right now ignores the range. That's why the main funnel can show 0 retainers sent while the Retainers card shows 4: both are right. Shares show the count behind them (“2 of 4”), and groups under 10 are marked small. A range under 21 days says it's too early to judge signing.
The full page follows a lead from first contact to settled. The jump bar at the top lists the zones in this order.
- Overview. The Main funnel is the one to quote. Quiz visits, Pipeline detail and Document collection count differently on purpose, and each says how. The strip counts the eligible leads that entered in the range at each stage: leads in, engaged, quiz done, documents complete, pushed to Clio, retainer sent, signed and settled. The small number under each is its share of the stage before. Because the stages aren't nested (a partner case can complete documents without a quiz), a stage can now and then exceed the one before it. Below it, the four numbers to watch: adjusted retention, new leads → signed, median first contact, and call flags overdue right now.
- Leads & speed. Retention step by step, by lead source, speed to lead (with the average first contact under the median), call flags and opt-outs.
- Quiz & documents. The quiz funnel, the quiz step by step, disqualified by reason, disqualifications over time, Intake Quality, and Document collection. That card counts, for cases whose quiz was completed in the range, each required document: how many cases were asked for it, how many sent it, and the median time from quiz to the first upload. It also shows how many have every document, why uploads failed (file too large, unsupported type, virus scan and so on), and what open cases are still missing right now. “Required” is the same rule the chase emails use: repair orders, registration and the purchase or lease agreement, plus the warranty booklet for certified pre-owned and similar cases. The client's upload page shows the same list as “2 of 3 required documents received” with links to what's still needed.
- Review & retainers. The pipeline funnel with marketing attribution and conversion by source, Reviewed in Clio with no retainer, and Retainers: sent, the retainer sign rate (sent → signed), declined with its share, awaiting signature, median days to sign and unsigned over 48 hours.
- Outcomes & money. Case outcomes from Clio, with the case win rate (FRA sent → settled); Settlement & Money as entered in the portal; Paid Ad Economics; why cases closed; referral fees; and outstanding referral fees.
- Partners. Leads referred out to other firms, top referral partners, and VIP cases open right now. VIP is always marked by hand (see the ⭐ VIP badge under the Cases Board).
- Team (admins only). One table per person: assigned, accepted, accept rate and median days to accept for leads that entered in the range, next to contact attempts, flags handled, called by due time, time to first call and signed after their call. Under it, the whole team's logged call time and billable hours. It replaces the old Per-Owner Performance, Team activity and Staff Time & Calls cards. Calls by week follows it: average contact attempts per week and per business day, each week's answered, voicemail, no answer and email, the call flags raised that week and how many were called by their due time, and each person's share. Use it for staffing: flags rising while on-time falls means calls aren't keeping up.
- Right now, Geography and Portal usage close the page. Failed background syncs sit in Portal usage with the integration timings.
The two rates are different numbers. The retainer sign rate is signed ÷ retainers sent. The case win rate is settled ÷ cases whose FRA was sent. The PDF follows the same zones in the same order, after its one-page executive summary, which now opens with the same funnel strip.
What the range covers, and the Right now section
Follows the range: every card outside Right now, each labelled with the range it covers. That includes Intake Quality, which counts cases whose quiz was completed in the range (time to accept: whose documents completed in it); pick All for the lifetime figures it used to show. Right now (its own section near the bottom): the Cases totals (Total / Accepted / Not Eligible / Opted-Out / In Progress / Archived), Accept Rate, Chase Suppression Accuracy, the PNC Watchlist, the Archive tabs, Push Notifications, Most Popular Accepted Makes, Clio Matter Stages, Settlement Data Needed, Pipeline Stage Distribution, Status Emails Sent and Client Status & Engagement. VIP Cases (in Partners) and the call flags open now are snapshots too, and say so on the card. History is retained indefinitely, so All genuinely means since launch.
Quiz, step by step, and how the quiz is tracked
The Quiz, step by step card sits under the quiz funnel. Each row is one quiz screen. It shows how many quiz sessions reached the screen, and how many left here: last seen on that screen without submitting or hitting a dead end. The shaded row is the screen losing the most people. Median time is how long people spend on the screen before moving on.
- Split the table by A/B variant, device, language, source (paid ads, campaign links, direct or organic), ad landing or site button with the buttons at the top.
- Site button is which button on our own website sent the visitor. The site adds a tag to each quiz link, for example
quiz.lemonaidfirm.com/?cta=home-hero(page, then placement), and the portal keeps it on the lead and in this table. Visitors whose link carried none show as No button tag. A link that names our own site as the source (utm_source=lemonaidfirm) is ignored, so it can't replace where the visitor really came from. - Ad landing is for ads sent straight to the quiz. Their link carries a tag, for example
quiz.lemonaidfirm.com/?lp=lemon&mk=jeep, and the quiz shows a matching headline above its first question (“Is your Jeep still not fixed?”), plus the website's own fee wording. Tags: lemon, warranty, used, rv, boat, motorcycle; the make is optional. Visitors without a tag see the quiz unchanged and show as No ad tag. A mistyped tag shows as Unknown tag, so fix that ad's link. - Dead ends are screens that end the quiz on purpose, such as a vehicle that is too old. How old is too old is Settings → Quiz → Vehicle age limit (default 7 years: in 2026, model year 2019 and older are turned away). It moves forward every January, applies to cars, used cars and RVs, and lets a VIN with no readable year through.
- Rejected entries count entries the quiz refused, such as a VIN containing I, O or Q.
- How easy was the form? shows the optional feedback score and, under it, what clients wrote, newest first, each linked to its case when the client submitted. It fills in once the question is switched on in Settings → Quiz.
- A session is one browser tab's visit. A client who leaves and comes back to a saved quiz keeps the same session, so they are counted once and also show under resumed.
The screen ids (classifier, vehicle type, VIN, the eight questions and so on) come from the quiz itself, in the order a client sees them. Screen tracking started on 23 Oct 2026, so earlier ranges show no rows. The same table is in the PDF report. The quiz sends the same events to Google Analytics and Microsoft Clarity, with no names, emails, phone numbers or VINs; the full list is in docs/TRACKING_SPEC_QUIZ_EVENTS.md. The A/B switch and the feedback question are in Settings → Quiz, and both start off.
A/B test: split quiz — reading the card
While the A/B split is on, the top of Quiz & documents shows the A/B test: split quiz card (admins only; also in the PDF). It compares the full quiz (A) with the short quiz (B), counting each visitor from the moment they started.
- What decides it: documents complete within 21 days of starting the quiz, out of everyone who started. Only starts at least 21 days old count, so a new visitor isn't a failure yet.
- Guardrails: B may not be more than 10 points lower on answering every question, more than a day slower to documents complete, or more than 0.3 lower on the feedback score.
- Status: A/A check (split on, short quiz not live: nothing should differ), Collecting, Early read (170 starts each), Ready to decide (320 starts each, 21 days old), or a Stop when the split is further from 50/50 than chance explains (less than 1 time in 1,000) or B is clearly hurting. A split stop means something is sending people to one version; nothing is declared. “B is hurting” is a loss for B, so the full quiz can be declared the winner from there.
- Where the count starts: the later of “short quiz live” and the A/B split being switched on. Switching the split off and back on in Settings starts a fresh count (that is how a second test starts), so leave it on for the length of a test. Quiz runs by anyone with a firm email address are left out.
- B − A is the difference in points with its 95% range; bold means it is clear, not chance.
- Every number above is adjustable (admins): Settings → Quiz → A/B test rule — the days (21), the starts needed (320 and 170), the confidence (95%), each guardrail and the early stops. Each box shows its default, and Reset to defaults puts them back. Change them before the test starts if you can: changing them mid-test changes what “ready to decide” means.
- Each quiz submit is also tagged in UrVeedaOS: quiz variant a or quiz variant b, plus short quiz when they took the short one.
- Does the result hold for each kind of traffic? Under the main table, the deciding number is split into paid ads, campaign links (emails, partners) and organic search and direct. Each visitor's version is chosen at random whatever their source, so the overall result is the one that decides; this shows whether each source points the same way. “Opposite direction” on a large source is worth a look before declaring. A source with under 30 starts per version old enough to count shows “too few starts yet”.
- Export the data (CSV) on the card downloads one row per quiz session (variant, when they started, submitted, documents complete, traffic source and so on; no names, emails or phones) for your own analysis.
- Declaring a winner. Once the rule calls it (Ready to decide, and the result is clear at the confidence you set), a green Declare the winner button appears. It is never offered on an inconclusive or early result. Declaring saves the result as it stood and, unless you untick it, makes the winner the quiz everyone gets and switches the split off. Each test can be declared once. The default can be changed back in Settings → Quiz → Quiz everyone gets while the split is off.
- Past A/B tests lists every declared test with its numbers, its own CSV export, and Plan the next test: copy a brief for Claude, a short summary to paste into a Claude session when choosing what to test next.
The short quiz (variant B) and portal onboarding
The short quiz asks only what decides eligibility (four of the eight questions, the dealership's state, then contact details and consent on one screen) and asks the rest after submit, in the client portal. Two switches in Settings → Quiz control it:
- A/B split puts each new visitor in group A or B.
- Short quiz (B) is live decides whether group B actually gets the short quiz. With the split on and this off, both groups take the full quiz: an A/A test that checks the split and the tracking before the real test starts. The date it went live is shown next to it, and the test is counted from then.
After a short quiz, the client lands on onboarding: (1) about the problem, (2) purchase details, (3) documents, which hands over to the upload page. They can save and finish later; the portal home page and every document reminder link take them back to it until it's done. Their answers go where the full quiz puts them: the case, UrVeedaOS and Clio.
On a call? Open the case → Client View → Onboarding (short quiz). Each answer shows, or “not answered yet”. Click Record answers from call on a step, fill in what the client tells you, and save. It is logged as entered by you on a call, in the Activity Log and on the Clio matter. Quicker still: open the Call script or Call guide on the case. While onboarding is open, both show an Ask while you have them box with only the questions the client hasn't answered. Fill in what they tell you and save; anything they don't know can stay blank. Cards on the board and Workbench rows show Onboarding 1 of 3 (and so on) until it's finished.
Clients see onboarding as setting up their case: a tracker at the top shows Case review started ✓, Your case details, Your documents, Attorney review. Analytics → Onboarding (short questionnaire)shows who never opened it, who stopped on their first visit, who came back and still stopped (they meant to finish, so look at the onboarding itself), and who finished, by week.
Leads & speed — who counts, and what “signed” means
This zone measures signed clients (retainer signed), not just accepted cases, and only counts real leads:
- Eligible leaves out staff test records (@lemonaidfirm.com emails), existing Clio cases added to the portal later (Clio imports), disqualified leads, and leads referred out to another firm.
- New leads also leave out recapture batches: old leads worked again in bulk, like the 89 old Cousins Law referrals imported Jun 24 and the June quiz invites to older leads. They're shown on their own row. An admin can tag a case as recapture on the case page.
- Engaged = took at least one step (finished the quiz, completed documents, reached attorney review in Clio, or was sent a retainer). Signed ÷ engaged is the adjusted retention.
- Given 7+ weeks to decide counts only leads that arrived at least 49 days before the range ended. Clients take about 3 weeks to sign, so newer leads would make the rate look worse than it is.
Speed to lead runs from when the lead arrived to the first logged contact attempt (Mark Contacted); never-contacted leads are counted, not dropped. It shows outside research alongside: Harvard Business Review (2011) found leads contacted within an hour were ~7× more likely to qualify, 37% of companies reply within an hour and 23% never do; Clio found 79% of legal consumers expect a reply within 24 hours; Velocify found 93% of converted leads were reached by the 6th call. Call flags shows open and overdue flags now, and how many flags were called by their due time. Reviewed in Clio, no retainer counts cases that went to attorney review and never got a retainer, with the reason staff picked on the case page (the case page asks when such a case closes without one; the reason is logged and noted on the Clio matter). Why we lost them is wider: every lead in the range that ended without signing (closed, soft closed, rejected, opted out, referred out), by reason, the top reasons for each source, and the firms clients went with. Exits that already say why fill the reason in themselves (rejected → not eligible, opt-out, referred out); Soft Close asks; anything still blank is listed under Needs a reason.
Case outcomes from Clio (Outcomes & money) reads each matter's open date, Date Settled, settled amount, fees and MATTER PHASE STATUS back from Clio about once a day. The case win rate (FRA sent → settled, separate from the retainer sign rate) counts cases where the FRA was sent (the portal sent it, Clio has an FRA sent or delivered date, the Clio stage is FRA Notice Sent or later, or the phase is a litigation, settled or lost phase), so a client who walks away after Intake Accepted isn't counted as a loss. It is a range because some of those cases never get a final phase recorded; they are listed so someone can update them in Clio. The forecast multiplies open signed cases by the median fee and the win rate. The PDF now opens with a one-page executive summary and includes all of these sections.
Intake Quality targets (⚙ Targets)
The Intake Quality cards (upload completion, time-to-accept, re-request rate) and the accept-rate and chase-suppression cards in Right now score green / amber against targets you set. Admins click ⚙ Targets (top-right of Intake Quality) to edit those goals plus your monthly ad spend ($/month) — all stored live, no redeploy. The ad-spend figure is what feeds the Paid Ad Economics card.
Pipeline Funnel — cohort conversion & stage timing
The Pipeline Funnel is a cohort view: it takes every PNC that entered in the selected range and follows that same set of leads through each stage — Quiz → Documents → Pushed to Clio → Eligibility → FRA. The top card shows how many PNCs entered, split by source (Manual / Quiz invite / Quiz organic / Quiz paid / Partner), with a New-PNCs bar chart you can bucket by Day / Week / Month (toggle top-right). Underneath, two breakdowns: Marketing attribution splits paid vs organic by ad network, utm_source, and campaign; and Conversion by source shows each source's entered → accepted → accept-%, so you can tell whether paid leads actually convert better than organic.
Each stage row shows how many leads advanced (the conversion %), the branch outcomes as pills (e.g. completed vs disqualified vs opted out; collected vs soft-closed vs hard reject; accepted vs PNC rejected), and the ⏱ median / avg time to clear that stage (with the sample size n). Two things to keep in mind: because it's keyed by entry date, a recent cohort is still in progress (a lead that entered yesterday can't have settled yet); and each lead is counted once per stage, so manual/partner leads — which enter already past the quiz — never double-count as quiz completions. The push-to-Clio → matter-created step is effectively instant, so that row's timer measures docs-complete → matter open instead.
Settlement & Money — effective vs. net rate
These figures are the settlement amounts staff enter in the portal; Case outcomes from Clio, just above it, reads Clio's own figures. Effective rate = attorney fee ÷ settlement. Net rate (of costs) = (attorney fee − litigation costs) ÷ settlement — the real take-home rate now that litigation costs are captured at settlement. The card also shows avg / total litigation costs alongside fees and client payouts. Cases settled before costs were tracked count as $0 costs.
Paid Ad Economics — CAC / ROAS
Turns your configured monthly ad spend into paid-acquisition economics for the window: Cost per PNC (spend ÷ paid leads), CAC (spend ÷ signed clients), and ROAS (realized attorney fees on paid-acquired settlements ÷ spend). Only Quiz (paid) leads — those carrying a UTM / ad-click signal — count toward the paid math; ambiguous legacy leads are excluded rather than diluting it. Spend is prorated across the selected range, so it needs a fixed/preset window (all-time can't be prorated and shows a hint instead). ROAS fills in over time as paid cases settle. Set the spend under ⚙ Targets.
Speed to lead and the Team table
Speed to lead runs from a new lead arriving to the first logged contact attempt, falling back to the first staff action when nothing was logged. The card shows the median, the average and how many were never contacted. The Team table (admins only) puts each person's volume, accept rate and median time to accept next to their calls and follow-through, so workload and conversion read on one row. Someone who owns cases but logged no calls, or the reverse, still gets a row, with dashes for the other side. In Right now, Status Emails Sent tallies how many of each lifecycle email (2 / 3 / 5 / 6 / 7 / 8) have fired.
PNC Watchlist — who's in limbo + contacted tracking
The other analytics cards give you numbers; the PNC Watchlist gives you names. It lists every open prospective client (pre-decision — not yet accepted, closed, or archived), each linked straight to its case, with two independent flags:
- Contacted (our side) — have we reached them? It lights up automatically on the first staff action logged against the case, OR when someone clicks ☎ Mark contacted on the case page. The badge shows “marked” when it was set explicitly.
- Reached out (their side) — has the client engaged? True once they finish the quiz, upload a document, or tap Request for Help.
Filter chips group the same list four ways: In limbo (open but still awaiting our first contact — the ones to work), Reached out, Stalled (carrying the 📞 Call-Needed badge), and All open. The exported PDF report includes this roster too, with each name as a clickable case link.
Mark contacted is an internal signal only — no client email, no GHL/Clio side effects. Click it again to clear it (which falls back to the automatic first-action signal). Use it when you want the watchlist to precisely reflect who you've actually called or emailed.
Why Cases Closed & Opt-outs
Why Cases Closed breaks closes in the range into Won, Not Eligible, Referred Out, Opted Out, and Closed (other) — the same terminal labels the case-status board uses, so a PNC-rejected case reads Not Eligible, not a generic close. Opt-outs counts DND / STOP / unsubscribe in the range (with an all-time total and a channel breakdown) and links to Archive → Opted Out. Referred Out counts PNCs sent OUT to a partner firm in the range — split by how they were referred (Quiz dealer-dispute vs Manual (staff) vs Clio stage) — plus the rate as a % of PNCs entered, and links to the outbound-referral Tracker.
Referral Fees
Total referral fees is commission accrued in the range (engine output from the settlement auto-calc), with the count of referrals. Lifetime-mode partners, partners total, and the fee-mode mix (Graduated / Flat / Custom) are current configuration snapshots. Top Referral Partners ranks firms by referral volume then commission within the range.
Status emails (1–8) — the post-acceptance email pipeline
Once a case is accepted, the litigation team drives it through Clio matter stages. Each stage change can trigger a status email to the client. You don't fire these yourself(with two exceptions — Settlement and Mark Disbursed, above). They're wired to Clio stages and the portal handles them automatically.
| Subject | Trigger | Guard | |
|---|---|---|---|
| 1 Free Case Eval | Evaluation in Progress | Intake workflows in UrVeedaOS | N/A (pre-acceptance, not portal-driven) |
| 2 Retainer & Onboarding | Retainer Sent—Action Required | First entry into ACCEPTED/RETAINED/Retainer-Review stage group | Send once per case |
| 3 Formal Defect (FRA) | Formal Demand Sent to Manufacturer | First entry into PENDING FRA / FRA Notice Sent group | Send once per case |
| 4 Settlement Negotiation | We're Negotiating Your Settlement | Stage = In Settlement Negotiations | Fires every time stage is entered |
| 5 Discovery & Litigation | Your Case Has Entered Litigation | Any of: Complaint filed, Discovery, Dispositive Motion, Trial | SEND ONCE ONLY — never resent across these stages |
| 6 Resolution Reached | Great News: We've Reached a Resolution 🎉 | Staff submits Settlement form | Blocked until settlement amounts are entered; held with amber banner if Clio hits Settled first |
| 7 Funds Disbursed | Your Lemon Law Settlement Has Been Sent | Staff clicks Mark Check as Mailed | Requires Email 6 to have been sent; cannot be re-fired; flips dashboard to "Case Closed — Won!" |
| 8 Case Closed | Your Lemon Law Case is Officially Closed | Clio matter.status = closed | Sent once at close; vehicle + case_closed_date pushed to UrVeedaOS with an 8s delay before send |
All 7 emails (#2–#8) are individual UrVeedaOS workflows (LAF-032 through LAF-038), each triggered by a unique contact tag. The portal fires an email by adding the matching tag to the contact (same proven pattern as LAF-030 magic link). If a workflow is unpublished or its trigger tag isn't configured, the email is silently skipped but the sent-at timestamp is still recorded — so the once-only guards continue to work while VPS finishes wiring.
Clio stage → client status map
Litigation moves the Clio matter through stages as they work the case. The portal listens for these changes via a Clio webhook and translates them into client-friendly status labels on the client's portal dashboard, plus the GHL {{contact.case_status}}field that email/SMS templates reference. The translation is intentional — clients never see Clio's internal naming.
Settings → Clio → Stage Map edits it. Copy settings from another stage (top of each open row) fills in everything from an existing stage, ready to adjust, so a new Clio column that works like an old one is set up in one step. Stages still under review, before a case is accepted, use the label Free Case Evaluation (offered first in the suggestions): the client sees that, and the case stays on the intake board rather than the post-acceptance Case Status board. “Out of State Matters Need ATTNY” and “Pending on Josh's Review” are set up this way out of the box.
| Clio matter stage | Client dashboard label | GHL case_status value | Email fired |
|---|---|---|---|
| 5 pre-acceptance intake stages | Free Case Evaluation | free_case_evaluation | Email 1 (intake workflows) |
| ACCEPTED / RETAINER (3 stages) | Case Accepted | retainer__onboarding | Email 2 (once per case) |
| PENDING FRA / FRA Notice Sent | Working Your Case | formal_defect_notice | Email 3 (once per case) |
| In Settlement Negotiation | In Negotiation | aggressive_settlement_negotiation | Email 4 (every entry) |
| Complaint Filed | Case Filed | discovery__litigation | Email 5 (once across all 5 litigation stages) |
| Discovery | Discovery Phase | ||
| Dispositive Motion / Trial (3 stages) | In Litigation | ||
| SETTLED (13) | Settlement Reached → Case Closed — Won! (after Mark Disbursed) | resolution__case_closed | Email 6 (after you save settlement) → Email 7 (after Mark Disbursed) → Email 8 (on matter close) |
| PNC Rejected | Not Eligible | not_eligible | None — status only (no status email) |
| Referred Out | Referred Out | referred_out | None — status only (no status email) |
You don't move Clio stages from the portal. Litigation owns stage transitions in Clio. The portal is read-only with respect to stages — it observes the change and reacts.
New: Clio “PNC Rejected” and “Referred Out” are no longer silent — they now surface as Not Eligible and Referred Out on the Case Status board and on the client portal. (They don't fire a status email.)
Referred Out auto-links to the tracker. When you move a Clio matter to the Referred Out stage, the portal automatically creates a row in the Referred Out tracker (Admin ▾ → Referred Out), linked back to the case and its matter number, with a ⚠ Assign firm pill. Click it to pick the destination firm (and add the partner's matter number) — that clears the pill and fills in the firm's contact details. The same optional Matter # field is on the manual + New → Refer out form, so a manual referral can be linked to a matter too.
Not linked to a case? Open the referral on the tracker. Under Client it says “Not linked to a case”: paste the case page link (or our Clio matter number, e.g. 00512) and press Link. The referral then shows View the in-house case →, and notes reach that Clio matter.
💵 A firm paid us a referral fee. Press Record payment, either on the referral in the tracker or on Analytics → Outstanding Referral Fees. The amount starts at what's still owed; change it to what actually came in, and add the date, how it was paid and the check or confirmation number. Choose whether it settles the fee (usually: closes once the balance is covered; or “this settles it” when an agreed lower amount is final; or “keep it open” when more is coming). Press Review, check the summary, then Record payment. The portal records the payment, moves the referral to Won if it wasn't, and adds a note to the linked Clio matter (or the client's Clio contact). A part payment stays on the outstanding list with the balance. The firm paid before telling us about a settlement? Use They already paid us: record it on the referral. The Record payment and Chase links in the weekly report and the “case won” email open a confirm page first, so nothing happens just by opening the email. The portal doesn't touch your bank or accounting: deposit and book the payment as usual.
The firm says it paid. A firm can tell us from its private status link (“Sent our referral fee? Tell us”). Nothing is marked received: the referral shows Firm says paid $X (tracker, drawer and the outstanding list), and Record payment opens with what they said. Check it against the deposit, then record it. Receipt to the firm: off unless Settings → Communications turns it on; then Record payment shows an unticked “Email the firm a receipt” box. Money in UrVeedaOS: a Won referral moves the client's opportunity to Won with our fee as its value, and each payment fills our referral fee received, its date and days won to fee received on the contact.
📄 Monthly statements. Referred Out → Monthly statements: pick a month, read each firm's statement (clients still open with them, settled fees still due, what they paid that month; clients appear as first name and last initial), tick the firms and press Send. Never automatic, and only once Settings → Communications turns it on.
Lost a referral? When you set a referral to Lost, open it and pick Why it was lost (the firm declined, the client decided not to, stopped responding, no case after review, went to a different firm). It feeds Analytics.
Never back to the firm that sent it. If a partner referred the client to us, that firm is left out of the Refer Out firm list, with a line saying why. That includes Sue Your Dealer when SYD is who sent them. Automatic RV routing skips the firm, which keeps its place in the rotation. Choosing it on the tracker's Assign firm is refused. The portal treats two records as the same firm when they share a Clio contact, an email, a business email domain (not gmail etc.), a firm name (ignoring punctuation and LLC / PA), or a phone number. A dealer-dispute lead that arrived on Sue Your Dealer's own referral link isn't sent back to them either: SYD gets no referral notice, and the tracker row and Clio note say it wasn't referred back.
GHL opportunity lifecycle (Lead Captured → Won/Lost)
Separate from the Clio matter pipeline, every case has one opportunity in the UrVeedaOS/GHL Lemonaid Cases (funnel) pipeline. The portal drives it — GHL workflows only react to tags. There are four stages; Won/Lost is the opportunity status, not a stage (the opp stays in Signed for everything post-acceptance — only its value and won/lost status change).
| Stage | When it gets there |
|---|---|
| Lead Captured | Opp created — Invite-to-Quiz / Bulk Invite / a fresh lead. (Manual New Case starts at Quiz Completed.) |
| Quiz Completed | Client finishes the quiz. |
| Docs Collected | All required documents uploaded. |
| Signed | Matter accepted in Clio (and stays here through settlement; value updates at settlement). |
Won — set when you click Mark Disbursed (Email 7 = the Won signal). A Clio matter close also reconciles to Closed - Won if Email 7 already fired, else Closed - Other / Lost.
Lost — set by any of these along the way:
- Quiz disqualified (fires
quiz not qualified→ GHL moves the opp to Lost). - Hard Reject button or PNC-Rejected stage in Clio (both fire
case not qualified→ GHL moves the opp to Lost). - Soft Close (the portal sets the opp to Lost directly).
- Referred Out — Sue-Your-Dealer auto-divert or a staff referral (fires
pnc referred out→ GHL moves the opp to Lost). - Matter closed without disbursement (no Email 7 → reconciled to Lost).
Referred out, then Won — when the referral is marked Won (or a fee payment is recorded), the client's opportunity goes back to Won with our referral fee as its value, so referral wins show in UrVeedaOS pipelines and reports alongside in-house ones.
Money and dates on the contact (for UrVeedaOS reports and smart lists; created by Settings → UrVeedaOS → Create missing): referral_won_date, our_referral_fee, our_referral_fee_received, our_referral_fee_received_date, days_won_to_fee_received, partner_fee_paid_amount, partner_fee_paid_date, funds_disbursed_date, days_signed_to_disbursed. The settlement figures themselves were already sent at settlement.
The tag-driven Lost paths (case not qualified, quiz not qualified, pnc referred out) depend on the matching GHL workflow doing a Find Opportunity → Update Status = Lost in the funnel pipeline. Soft Close and the matter-close reconciliation are set directly by the portal.
Clio fields the portal writes & reads
Everything the portal does in Clio is field-level (no risky bulk operations). Knowing which fields the portal writes vs. reads helps you understand mismatches in the verification table and explain to litigation what to expect.
Written at matter creation (Accept)
| Clio field | Source |
|---|---|
| Practice Area, Matter Stage, Description, Client | Form + canonical "LAF {Last} v. {Mfr} SOL: mm/dd/yyyy" |
| Responsible Attorney, Originating Attorney, Responsible Staff | Accept form dropdowns (default Joshua Feygin / Glykie) |
| VIN, YEAR, MAKE, MODEL, CAR_MILEAGE, LICENSE_PLATE_NUMBER, DEAL_NUMBER | Quiz answers + Accept form overrides |
| MANUFACTURER, PURCHASER, CO_PURCHASER, DEALERSHIP (contact links) | Clio contact lookups (auto-created if missing) |
| PURCHASED / LEASED / VEHICLE REGISTRATION RECEIVED (checkboxes) | Accept form ownership type; Registration Received is checked when a reviewed registration is on file — at push, or the moment one is reviewed after the matter exists (left blank, not "No", until then) |
| FRA_NOTICE_SENT_DATE, DELIVERY_DATE, DATE_OF_CONTRACT, WARRANTY_EXPIRATION, LAF_VEHICLE_INSPECTION_DATE | Quiz + Accept form |
| SOL_DATE (Statute of Limitations) | Staff-confirmed; the Accept form's ⚡ Calculate computes it from the chosen state's anchor + period and the entered dates (always editable before you accept) |
| LAF_REFERRAL_SOURCE (picklist) | Always set: Reffering Attorney when a referral partner is on the case; LAF Paid Campaign for a paid-campaign lead (until that choice exists in Clio, LAF website); otherwise LAF website |
| LAF_REFERRING_LAW_FIRM, LAF_REFERRAL_RATE_PCT | The assigned referral partner (fee $ is written at settlement) |
| PARTY, CAUSE_OF_ACTION, PLAINTIFF, COMPLETE_PLAINTIFF_NAME, CLIENT'S LANGUAGE | Plaintiff; Breach of Magnuson-Moss Warranty (change it in the optional fields if needed); the client's name; English/Spanish from the client's language |
| LAF_CASE_EVALUATION (pre-settlement estimate) | Accept form (purchase price × 0.20 × 0.45, with override) |
How a lead is counted as paid
A tracking tag (UTM) on its own doesn't make a lead paid or organic. It only means someone tagged the link. The portal decides in this order, and the Clio note says which rule applied:
- An ad click id (Google gclid / gbraid / wbraid, Microsoft msclkid) → paid. Meta's fbclid counts as paid too, unless the link is tagged organic: Facebook adds fbclid to every click, organic posts included.
- utm_medium → paid for
cpc,paid_social,display,programmatic,video/ctv/ott,retargeting,qr,print/direct_mail,ooh/billboard,radio/tv. Not paid foremail/sms(our own channels) ororganic/social/referral. - A utm_campaign with no utm_medium → counted as paid (we only tag campaigns we run), and the note says it was assumed.
- Nothing tracked → the referring site (Google = organic search, Facebook = organic social, none = direct), then the client's answer to "How did you hear about us?": "Streaming TV ad" or "Web / app ad" counts as paid.
Tagging tip for marketing: give every paid link, QR code and programmatic/CTV placement a utm_medium from the list above and a utm_campaign. Organic posts should use utm_medium=social or organic.
Fields you fill in by hand on the Push form
Additional / optional Clio fields (collapsed at the bottom of the Push to Clio form) lists the Clio matter fields the portal doesn't fill itself. Each one takes the kind of value Clio expects: dropdowns show Clio's own choices, dates use a date picker, money and number fields take numbers, and checkboxes are Yes / No. Hover a field's name to see what it takes; use Find a field… to jump to one.
- Not shown: fields the portal fills automatically (hover the "fields the portal fills automatically" line to see them), and contact-link fields, which need a Clio contact and are set in Clio.
- Checked before the matter is created. If a value doesn't fit its field (a word that isn't one of a dropdown's choices, a date Clio can't read), the push stops with a message naming the field and the allowed choices. Nothing is created until it's fixed.
- Recorded. Whatever you enter is listed in a Clio note on the matter ("Clio fields set at Push to Clio") and in the case's Activity Log, together with what the portal set on its own (Refferal Source, Registration Received).
Pushing again when the matter already exists
Re-pushing a case that already has a matter updates it, but the portal's own defaults (Party, Cause of Action, Plaintiff names, Client's language, Refferal Source, Registration Received) only fill fields that are blank in Clio. A correction someone made by hand in Clio is never overwritten. If the portal can't read the matter's current values it leaves those fields alone. Values you type on the form are written as entered. What was filled is listed in a "Clio fields filled on re-push" note.
Notes and Activity Log when a Clio field changes
Each time the portal changes a Clio field after the matter exists, it leaves a trail in both places: a Clio matter note, and a Clio fields set row in the case's Activity Log (under Status changes). That covers registration reviewed, vehicle edits, pushes from the Clio field check, linking the manufacturer contact, and adding or removing a referral partner (the note says what Refferal Source became). Settlement, disbursement, FRA mailing and manufacturer-address pushes already wrote their own notes.
Written at Settlement Save (💰 Settlement → Save)
| Clio field (existing — no new fields needed) | Value the portal pushes |
|---|---|
| Total Global Settled Amount* | Total Settlement input |
| Gross Attorney Fees* | Attorney Fee Amount input |
| Date Settled | Today's date |
| Settlement Statement Executed | ✓ checked |
| LAF Referral Fee / LAF Referral Rate % | Referral inputs (if entered) |
| — Matter timeline note | Full breakdown including client payout and atty fee % (which have no Clio field) |
Client Payout Amount and Attorney Fee % are not pushed to Clio — there are no Clio fields for them. They're tracked in the portal DB + UrVeedaOS contact fields only, and the matter note includes them for the litigation team to read.
Written at Mark Disbursed
| Clio field | Value |
|---|---|
| Date Check Disbursed to Client | Today's date |
| — Matter timeline note | "Funds disbursed — marked by [you]" with check amount |
Read-only (verification table only)
These are managed by litigation directly in Clio. The portal displays them so you can verify check-processing state without opening Clio:
- Date Attorney Checks Received
- Date Check Sent For Endorsement
- Date Check Disbursed to PA
- Current Status of Client Check (dropdown)
- Current Status of Attn Fee Check (dropdown)
- Current Status of PA Fee Check (dropdown)
- Collection Status NOTES
Auto-created tasks on every accepted matter
- New Matter / InfoTrack / Complete Clio Matter Fields — assigned to responsible staff
- Mark Funds Disbursed in Staff Portal — long-running reminder; close by mailing the check and clicking the portal button
- Case accepted by [you] — please review — notification ping to the assignee
- Link dealership to matter — [name] — only if dealership wasn't found at intake
- Unknown manufacturer — needs Clio lookup — only if manufacturer wasn't in our lookup table
Auto-created folders on every accepted matter
15 canonical document folders, identical on every matter: Client Folder, Costs and Expenses, D's AAD, D's Motions, D's NOA, D's PFS, Depositions, Discovery, Hearings, Invoices, Letters, Orders, P's Complaint and Summons, P's Motions, Settlement Docs. Don't alter this list without engineering review.
Reading the verification table (Settlement tab)
Clio first. Litigation records settlements in Clio (Total Global Settled Amount, Gross Attorney Fees, Date Settled). When Clio already has figures, the settlement form shows a blue line, “Clio already has figures for this matter”, with Use Clio's figures: it fills the total and attorney fees (and the fee %); press Calculate for the client payout and referral fee, then save. If you save a figure that differs from Clio's, the portal shows both and asks before it replaces Clio's. Analytics → Settlement Data Needed lists each settled case still missing figures and what Clio has for it.
The verification table on the Settlement panel shows the same field in 3 columns — Portal, Clio, UrVeedaOS — so you can spot drift between systems at a glance.
| Symbol | Meaning | What to do |
|---|---|---|
| ⚠ red | Mismatch — Clio or UrVeedaOS has a different value than Portal | Re-save the settlement form — the portal will re-push. If it stays red after a save, escalate to David. |
| ○ amber | Not set in that system yet (portal has a value, downstream doesn't) | Same fix — re-save. If it persists, the field probably isn't wired yet (engineering will know). |
| N/A | No Clio field exists for this value (only happens on the Clio column for Attorney Fee % and Client Payout) | Expected. Those two values live in portal + GHL only; the breakdown is in the matter note. |
| number | In sync | Nothing — you're good. |
Below the main table, if litigation has stamped any check-processing dates in Clio (Date Settled, Date Check Disbursed to Client, Date Attorney Checks Received, Date Check Sent For Endorsement, Date Check Disbursed to PA, Current Status of Client/Attn/PA Fee Check), they appear in a smaller read-only section so you can see check status without opening Clio.
Common scenarios & gotchas
Client calls saying they got the wrong settlement amount in their email
- Open the case → Actions → 💰 Settlement
- Check the verification table — what does Portal show vs UrVeedaOS?
- If Portal is wrong, correct it in the form below and save. Email 6 won't re-fire (the timestamp guards against duplicates), but the corrected values land in Clio and UrVeedaOS.
- For a corrected re-send to the client, email David — we can manually re-fire the workflow.
You mailed the check, closed the Clio task, but the client says they got no email
Closing the Clio task doesn't fire anything. The portal's Mark Check as Mailedbutton is what fires Email 7. Go to the case → Actions → 💰 Settlement → scroll to the bottom → click Mark Check as Mailed. The Clio task description spells this out.
Clio matter just closed and the client says they never got Email 7
If the matter closed without anyone clicking Mark Disbursed, Email 7 was skipped — the dashboard reads plain "Case Closed," not "Case Closed — Won!" If you actually did mail the check, click Mark Disbursed now (it'll still fire Email 7 and flip the dashboard).
Amber settlement banner won't go away after you saved
The banner clears when needs_settlement_dataflips to false. If it's still showing, refresh the page once — the case data caches in the browser. If it persists after a hard refresh, screenshot it and email David.
Case has a Clio matter number but no client portal access
The client's portal access is tied to their UrVeedaOS contact, not their Clio matter. Check the Audit tab for any failed magic-link events. Most often this is fixed by them requesting a fresh link at /portal/request-link.
Litigation says they updated a Clio field but you don't see it in the verification table
The portal fetches Clio values live every time you open the Settlement panel — there's no cache. If you don't see it, the field name doesn't match what the portal expects (e.g., a typo in Clio) or the field ID isn't in CLIO_CUSTOM_FIELD_IDSyet. Forward to David — he can map it.
A case shows the 📞 Call Needed badge but the client says they did upload
Check the Documents tab. The Call Needed badge is a per-case flag set by the GHL chase workflow; it normally clears once the missing documents come in. If the files are clearly there and the badge is still stuck, mark the uploads processed and move the case forward via the stage selector on the case detail page (or flag it to David).
The 'Performed by' dropdown forgot who you are
It's remembered in the browser's local storage. Switching browsers / clearing site data resets it. Just re-select your name; it sticks again.
Requesting a replacement document
On the Documents tab, scroll to Request Additional/Replacement Doc. Pick the doc type and the reason. The reason is shown to the client in the email. When it sends you now get an inline ✓ confirmation right at the button (it used to give no visible feedback), so you know the re-request actually went out.
Common scenarios:
- RO is unreadable or blurry → "Documents are unreadable or low quality"
- Client uploaded the wrong vehicle → "Documents are for the wrong vehicle"
- Service history is incomplete → "Documents are incomplete or missing pages"
- Need extra paperwork (extended warranty, etc.) → use Additional Doc type, pick "Other" and explain
What happens downstream:
Duplicate vs. Won't process — clearing an upload
When a client uploads a file into a doc slot that you don't want to process, each document row (on the Documents tab) has two buttons that clear the blue “needs processing” pill without marking that doc-type received. Both keep the row listed with a small tag for the record, and both are undoable (a dismissed row shows an ↩ Undo dismiss button).
| Button | Means | What to do after |
|---|---|---|
| ⧉ Duplicate | Same document uploaded twice — you already have the real one. | Nothing. The requirement is already met by the other copy. |
| ✗ Won't process | Wrong or unusable file for that slot (e.g. a registration where the repair order goes, or a blurry/blank scan). | Re-request Documents for that type — the doc-type correctly stays missing because you still don't have the right file. |
The key difference: Duplicate is a dead end (nothing more to do), while Won't process is a hand-off — it clears the clutter but leaves the requirement open so you go ask for the correct file. Neither turns the doc-type green; neither notifies the client on its own.
💬 Document chase — pause / resume
When to use: a client calls or emails to say they'll send their documents soon, but the automated chase keeps emailing them the "we'll close your case" reminders. This takes them off the chase so they stop getting those emails while they've already been in touch. You can also do this straight from the Mark contacted popup — there's a "Pause automated document-request follow-up emails" checkbox that does the same thing.
Where: open the case → Actions tab → the 💬 Document chase — pause / resume card →Remove from doc chase or ↻ Resume doc chase (pick your name in Performed by first).
What happens:
↻ Resume doc chase (re-initiate):
The chase workflow is a full exit on pause (not a real pause), so Resume re-enrolls from the start — which requires DOC-CHASE Re-entry = ON in UrVeedaOS.
📥 Importing documents from Clio
Two ways to pull a matter's Clio documents into the portal — one brings the client's own docs IN, the other pushes our casework OUT to the client. Both live on the case's Actions tab.
Import client documents (onboarding)
For matters onboarded from Clio, the 📥 Import client documents from Clio card reads the matter's Client Folder live and lists its files. Tick the ones the client sent and pick each document's type — Repair Order · Registration · Purchase/Lease · Additional (the same set clients upload; no casework). Import pulls them from Clio and lands them as the client's own documents, already marked done (green), and sets the matching doc flag — so the case immediately reflects what's in vs. still missing. Then use ↻ Resume doc chase to chase only the gaps. (Shows only when the case has a Clio matter.)
Automatic quiet-case nudges (proof of motion)
When a retained client's newest shared document is 7+ days old, the portal automatically sends them one push notification (max one per 14 days): "Your legal team is on it", pointing back at that document in their portal. It respects each client's notification preferences, and admins can turn the whole thing off in Settings → Messages and reminders → Proof-of-motion nudges. Sharing something new resets the quiet clock — the best nudge is a real update.
Share casework with the client (retained only)
The 🗂 Share casework with the client card (retained clients only) lets you browse this matter's Clio folders — loaded live, since folders vary per matter — search within a folder, pick the type the client will see it labeled as (e.g. "FRA Letter to Manufacturer", "Motion", "Discovery", "Settlement Document"), then click Share to client to pull the casework document into the client's portal as a"show our work" file they can view or download. In the client portal it shows with a"✦ Prepared by your attorneys" badge and the label you chose, and a reassurance banner tells them their legal team is actively working the case. Leave "Email the client"checked and the client also gets a notification email — your legal team is on it, naming what you just did — with a fresh 1-hour login link to read it (if it expires, the login page lets them request a new one in seconds). Uncheck it to share silently, or when sharing several docs at once send just the last one with the box checked so only one email goes out. For the FRA letter specifically, use the 👁 Show client option on the FRA send form instead.
📓 Warranty Manual Library
A shared, deduped library of vehicle warranty manuals the case card links from — so you stop re-searching the web for the same manual on every case. One 2019 Ford booklet serves every Ford-2019 case: stored once, referenced everywhere, and pushed to Clio per matter. A warranty manual is a required document to Push to Clio, so this is mostly about clearing that step fast.
On the case card — attach in one tap
On a case's Documents tab, if the vehicle's model-year + make match a manual in the library you'll see a green banner: "Warranty manual in library: 2019 Ford (covers all models) → Attach & queue for Clio." One tap creates the warranty-manual document (pointing at the shared file — no re-upload, no per-case copy), which satisfies the Push-to-Clio requirement and queues the Clio Client-Folder push if a matter exists.
No match? The 🔍 Find warranty manual button is still there (it opens a Google search for the exact vehicle). Once you find one, use "+ Add found manual to library"right on the case — it saves the PDF into the library (prefilled with this vehicle) andattaches it — so the next case with that make/year is covered automatically. Every hunt grows the repo.
New-vehicle warranties only — CPO comes from the client
The library holds factory new-vehicle warranties only. A certified-pre-owned warranty depends on the program tier and when that client's coverage started, so the only accurate copy is the client's own CPO booklet. It's a required document on their upload page, and they're reminded until it's in. Once you mark it reviewed, it covers the warranty requirement for Push to Clio.
- Adding a CPO booklet to the library is refused, and a file named like one is flagged on import.
- A CPO case gets both warranties. The client's CPO booklet and the factory new-vehicle warranty from the library. A CPO car usually still has what's left of its factory coverage, and a claim can rest on either. Push to Clio needs both: the case card shows a Factory Warranty Manual item that stays red until the factory booklet is attached from the library (or uploaded as the Warranty Manual and marked reviewed). There's no override for it, because we find it ourselves rather than wait on the client. A matter that was already pushed can still be re-pushed without it.
- On an off-road vehicle, where nothing is published, the card says "This warranty comes from the client" instead of offering a library booklet. Those vehicles don't show up in the library's missing-manuals report.
- If the purchase type is wrong (it was really bought new), correct it on the card. The library booklet is then offered as usual.
- CPO booklets added to the library before this rule are kept, but never used.
- Client emailed it instead? Upload it yourself: + Upload Document → CPO Warranty Booklet (client's) (PDF). A staff upload counts as reviewed. It meets the requirement for Push to Clio, and the client portal stops asking for it.
- Help finding it. The case card's CPO warranty booklet panel has one-click searches built from what the client told us (the dealership's phone number and map, its certified pre-owned department, the manufacturer's booklet, program, customer care and VIN lookup), what to say when calling, and where clients usually find it. The client sees the same help, in English or Spanish, on the booklet's upload page; each button opens a Google search in a new tab.
- Staff override. In the same panel, pick a reason and press Don't require it. The booklet leaves the client's checklist and the reminders, stops blocking Push to Clio, and if nothing else is missing the case is marked documents complete. The reason, who and when are kept on the case and in the Activity Log. Require it again undoes it. The factory warranty rule above doesn't change.
- Everything is written down. Each step leaves a row in the case's Activity Log and a Clio note (on the matter, or on the client's Clio contact before a matter exists):
- the purchase type is answered or corrected (quiz, client portal, staff);
- the booklet arrives;
- it's reviewed or uploaded by staff;
- a case is pushed without it (Activity Log, the Clio intake note and the "Collect CPO warranty booklet" task). When the booklet then arrives, the note says that task can be closed.
Why Warranty Manual isn't in + Upload Document
Deliberate: a manual uploaded through the per-case picker would land on one case only and never reach the shared library — the next case with the same make/year would have to re-find it. The warranty-manual card is the only way in, and it saves to the library and attaches in one step. Attached the wrong one? The card collapses to a summary with Choose a different manual — pick any manual for that make and swap in one tap (if the old one already copied into Clio, the portal tells you to remove it there). And if a case's documents ever miss the ride to Clio, the Documents tab's Send missing docs to Clio button re-runs the push — safe to press repeatedly, already-sent documents are skipped.
Managing the library (Manage ▾ → Warranty Manuals)
Bulk-load your manuals under Manage ▾ → Warranty Manuals (any staff — it moved out of the admin-only Settings hub so everyone can add): drop one or many PDFs at once (named year make model warranty manual.pdf). Each is auto-parsed (make/year/model from the filename), duplicates are detected by content and skipped, and you review each row before importing.
- Make-general vs. model-specific: leave Model blank for the booklet that covers all models of that make/year (the common case); fill Model only for a rare or pricier car that has its own manual. When a case matches, the model-specific manual winsautomatically — you never have to decide which to use.
- Year ranges: a manual that spans years (e.g.
2018-2021) sets a range; a single year sets both ends. Matching is "model-year falls in range." - Trim a full owner's manual: if the warranty is buried in a 400-page owner's manual, tick "keep only the warranty pages." The portal auto-detects the warranty section and pre-fills the page range (✨), you verify it in the inline PDF preview (scroll or jump to the start page), and it confirms exactly which pages are kept vs. discarded before saving. A booklet that's already standalone shows "no trimming needed."
- Coverage worklist: the amber "Most-requested missing manuals" chips at the top show the make/year combos your open cases need but the library doesn't have yet — so you fill the ones that recur most, not one case at a time. The header also shows how many cases are linked and the disk space saved by dedupe.
The library holds one shared file per manual; deleting a case never removes a manual other cases rely on. Any staff can add a manual from a case card; bulk management lives in admin Settings.
Coverage audit — run this after importing matters from Clio
At the top of Manage ▾ → Warranty Manuals sits the Coverage audit. It counts two problems that no board shows you, and counting changes nothing — you see the numbers, and each fix is a separate press.
- "No manual attached — the library already has one." The usual state after importing matters from Clio: the matter comes across but nothing links the manual on our side. Attach links the matching library manual to every one of them — no file is copied, they all point at the one shared PDF — and any case that already has a Clio matter gets the manual uploaded there too.
- "Missing the manual in Clio." The manual is on the case but never reached the matter. Send runs the same push the Documents tab does, so it also sweeps up any other processed staff document that never made it across. Anything already in Clio is skipped, so pressing it twice can't duplicate a file.
A vehicle the library has nothing for won't appear here — no button can invent a manual. Those show up in the amber "Most-requested missing manuals" chips instead, which is your list of PDFs to go find.
📮 Manufacturer addresses — where the FRA is mailed
The firm's manufacturer list (Settings → Manufacturers) is the source of truth for the certified-mail address on every FRA. The Clio matter fields are fed from it, not the other way round.
The FRA is blocked without one — and you can fix it yourself
If the vehicle's make has no mailable address on file, the FRA wizard stops with a red panel naming the make. That block is deliberate: a certified legal notice can't go to a guess. You get two ways forward, and you don't need admin rights for either:
- Request it — one press raises the manufacturer task on the Clio matter and posts a note there explaining what's missing and what unblocks it. Use this when it's someone else's to chase.
- Add it now — type the legal name and certified-mail address right there. It saves to the firm's list (so every future case with that make is covered) and pushes to this Clio matter in the same press.
You can add a manufacturer or fill in blanks on one. Changing an address that's already on file stays an admin change in Settings — a vetted legal-notice address shouldn't change as a side effect of unblocking a case.
Push manufacturer address to Clio
When the manufacturer is on file, the FRA screen shows the address with a Push manufacturer address to Clio button. Settings wins: it overwrites the Clio fields. Anything it replaced is recorded in the case activity log and posted as a note on the matter, so whoever typed the old value finds out where they work. Pressing it when Clio already matches does nothing and posts nothing.
Correct an address in Settings and it does not reach existing matters by itself — press this on the case, or the matter keeps the old one.
Coverage — what's blocking FRAs right now
The Manufacturers page shows an amber count of live cases blocked by a missing or incomplete manufacturer, split by make and ordered by how many cases each one holds up. Zero means every live case's make can be mailed to.
What the system does automatically
You don't have to do these — the portal handles them for you:
- RO chase emails: If the client doesn't upload repair orders, they get reminders at Day 2, Day 4, Day 6, and a final warning at Day 8. After Day 8 with no response, the case gets the 📞 Call Needed badge so a human phones them — it is notauto-closed; whether to Soft Close stays your call.
- Reg + Purchase chase emails: Same 8-day chase (LAF-010), running up front alongside the RO chase — all documents are requested when the client finishes the quiz.
- AI document analysis: Repair orders are analyzed in the background by our AI as soon as they're uploaded. You see the result on the Actions tab.
- Clio matter creation: The matter is created and opened in one step when you click Accept (status Open). There's no separate placeholder matter anymore.
- UrVeedaOS field sync: Every decision you make is reflected in the contact's record in UrVeedaOS (Clio matter number, case status, owner, etc.).
- Audit trail: Every click is logged with your name and a timestamp. Visible on the Actions → Audit view.
- Stage transitions: Cases move between Workbench columns automatically based on doc uploads and your decisions.
- Google Drive filing: client raw uploads land in the case’s
_Originals/folder; anything staff upload or process (the cleaned / renamed copies) goes to a_Processed/subfolder, and the Drive filename matches the portal filename. When you merge a duplicate card, the duplicate’s case-number folder is moved under the canonical card’s and renamedMerged-<case #>. Nothing for you to do — just so the Drive layout makes sense when you go looking. - Post-acceptance status emails (#2–8): Once a case is accepted, the portal listens to Clio matter stage changes (via webhook) and fires the right status email to the client at each stage. The only two that require your input are #6 (Resolution Reached) — you fill in settlement amounts — and #7 (Funds Disbursed) — you click Mark Disbursed when the check is mailed. See the Settlement section above for details.
- Mark Funds Disbursed Clio task: At matter creation, a long-running Clio task is auto-assigned to the responsible staff as a reminder to come back into the portal and click Mark Disbursed once the check is mailed. Closing that Clio task without firing Email 7 will leave the client waiting — always come into the portal first.
Push notifications (client PWA)
Checking whether it is on…
The client portal is a PWA. After clients log in for the first time they're prompted to enable push notifications, and they can manage them anytime via the ⚙ icon in the dashboard header. Preferences are stored per-contact (not per-device), so toggling on one phone applies everywhere.
In Settings, clients now see a “Devices receiving notifications” list (each phone/computer they've turned on), and the four category toggles below are locked until they turn notifications on — they'll see a “Turn on notifications to choose which updates you receive” overlay. So if a client says they can't change their notification settings, the fix is to enable notifications first (on iPhone, that means installing to the Home Screen — see Platform support below).
What automatically fires a push
| When | Category | Title shown to client |
|---|---|---|
| Staff clicks Accept | Decisions & milestones | Great news — we've accepted your case! |
| Staff clicks Hard Reject | Decisions & milestones | A decision on your case |
| Staff clicks Soft Close | Decisions & milestones | An update on your case |
| Staff Re-requests a document | Document chase | Lemonaid Firm needs your [doc] |
| Staff marks a doc Processed | Document chase | We got your [doc] — thanks! |
| Clio matter stage changes | Case stage changes | Your case moved to [stage label] |
| Clio stage → Settled (1518263) | Decisions & milestones | Your case has been settled! |
| Staff clicks Mark Funds Disbursed | Decisions & milestones | Your settlement funds are on the way |
| Clio matter closes (after disbursement) | Decisions & milestones | Case closed — congratulations! |
| Any status email (LAF-032…038) fires | Case update emails | New case update from Lemonaid Firm |
The four categories clients can toggle
- Case stage changes — every time Clio moves the matter to a new stage.
- Document requests & receipts — staff Re-request + Mark Processed.
- Case update emails — mirrors each LAF-032…038 status email so they see it on their phone instantly.
- Case decisions & milestones — acceptance, rejection, settlement, funds, closure.
Sending an ad-hoc / custom push
Use the Messaging tab in the top nav to send a one-off push — appointment reminders, a chase that doesn't fit Re-request, or a firm-wide announcement. Four targeting modes:
- Pick people (default) — search opted-in clients and partners (each row is tagged Client or Partner), optionally narrow clients by case stage, and tick exactly who to message. “Select all shown” grabs everyone currently matching your search.
- Filter by case state — pipeline stage, Clio matter stage, accepted-only, open-only. Clients only; sends to everyone matching who has a push device.
- Everyone subscribed — broadcast with an audience picker: all clients, all partners, or everyone subscribed. Use sparingly.
- Paste contact IDs — advanced: paste one or more GHL contact IDs (clients).
Click Preview & send to see the resolved recipient count and a sample of who's about to get it before anything goes out. Sends to more than 5 people require an explicit "I understand" checkbox. Every send respects each client's per-category opt-out and is written to the audit log.
Channels & the audit trail
- Push — needs an enabled device and respects the category opt-out. Keep the body short (push truncates around 160 chars).
- Email — sent to the contact's address via UrVeedaOS. Body can be long. Email reaches clients even if they never enabled push, so the recipient count grows when you add email to a filter/broadcast.
- Partners are push-only — the Email channel applies to clients. Partner recipients (picked individually, or via the partners / everyone broadcast) are reached by push to their partner-portal PWA; they don’t get these emails. Partners also receive automated good-news pushes as their referred cases progress, and the milestone emails (accepted, settled) fire from UrVeedaOS.
- Log a note to UrVeedaOS + Clio (on by default) — records the exact message on the contact timeline, and on the Clio matter if the case is accepted. This is how custom messages stay in the audit trail. (Notes are logged for client recipients.)
Note: the system's automated notifications (accept, reject, re-request, settlement, disbursement, etc.) already write their own notes from the triggering action, so you don't need to re-log those — the Messaging note exists specifically for the free-form messages you compose here.
The category bucket you pick (case stage / document chase / case update emails / decisions & milestones) determines which clients are reachable — anyone who turned that category off in their settings won't receive it. Choose the bucket closest to the message intent. An admin-only POST /api/v1/admin/push-custom endpoint also exists for scripted/VPS use.
Platform support (heads-up for client questions)
- Android Chrome / Edge / Samsung Internet: works whether or not the PWA is installed.
- Desktop Chrome / Edge / Firefox: works in any browser tab.
- iPhone / iPad (iOS 16.4+): only works if the client adds the portal to their Home Screen first. Tell them to tap Share → Add to Home Screen, then enable from inside the installed app.
- In-app browsers (Instagram, Facebook, TikTok webviews): no support — they have to open it in a real browser.
Failure handling
Pushes fire after the underlying business action commits, so a failed push will never roll back an accept/reject/disbursement. Dead device endpoints (404/410 from the push provider) are auto-pruned from the subscriptions table on next send.
Portal Access — one-time login link
Sometimes a helper fills out and manages a case for the client — a family member, a friend, an assistant. Instead of the old reusable “People with access” co-user list, each case now has a single Portal Access control on the case detail page (under Actions → Overview) that mints a one-time-use login link for one filler. Clients no longer self-manage who has access — every change is made by staff and audited.
How the one-time link works
- One filler per case. Enter their name, email, and phone, then Issue one-time link. The link is single use and expires in 1 hour — once they open it, it won’t work again, so they can’t keep re-entering.
- Tick “Email the one-time link now” to send it to the filler immediately, or leave it unchecked and copy the link straight from the panel to share it yourself.
- ✎ Edit updates the filler’s name / email / phone. ↻ Re-issue one-time link mints a fresh single-use link (e.g. after they’ve already used the first one). Revoke stops their link resolving to this case.
Email copy reference
Here's the actual copy clients receive at each step, so you know what they're seeing.
After they finish the quiz (all documents requested up front)
Day 2 / 4 / 6 reminders (if they don't upload)
Day 8 soft close (no response)
When the case is accepted (intake specialist accepts the matter in Clio)
After you click Hard Reject
After you submit Settlement Data (Status Email #6 — Resolution Reached)
After you click Mark Disbursed (Status Email #7 — Funds Disbursed)
When the Clio matter is closed (Status Email #8 — Case Closed)
Avoiding duplicate cards
The portal now works hard to keep one card per person. Invite to quiz, the Manual intake form, and a client re-taking the quiz all reuse an existing active card by email instead of spinning up a duplicate. So a person who gets invited, then fills out the quiz, then resubmits, ends up with a single card — not three.
📩 Send quiz invite (per card)
On a case that has no Clio matter yet, the case header shows a 📩 Send quiz invite button. It sends (or re-sends) the quiz link to this existing card — no duplicate is created. Use it when a lead never finished the quiz and you want to nudge them again. (This is different from + New → Invite to quiz, which creates from a fresh email — though that one dedupes by email too.)
Duplicate-cards banner & merge
If duplicates still slip through (e.g. a co-purchaser who used a different email), a case shows an amber duplicate-cards banner near the top. It lists other cards with the same email OR VIN — the VIN match is what catches a co-purchaser on a different email. Each one has a “Merge into this card” button.
Merged-<case #>.Merge is refused if both cards already have a different Clio matter — we won’t silently collapse two live matters. If you hit that, forward both to David.
Client language (English / Spanish)
Every case carries a client language (English or Spanish). It’s set wherever a case is created — Invite to quiz, the Manual intake form (beside State), and each Bulk Add Leads row — and the staff card shows an EN / ES badge.
The chosen language carries through end to end: the per-contact quiz link opens in it, the document-chase and status emails/SMS fire from their EN/ES branch, and the client portal renders in it. (The staff portal itself stays in English — this only controls what the client sees.)
Bulk Add Leads
Use Bulk Add Leads to give portal access to clients who are already in your pipeline — clients onboarded before the portal existed, or anyone you collected documents from outside the portal. Each new enrollee gets a portal login, a GHL contact, and a welcome email with a 72-hour login link.
00123-Smith), not the internal ID, and the portal looks it up in Clio to confirm it exists and wire up automatic status updates. Intake rows can skip the matter # — a fresh lead with no matter yet goes straight into document collection.Per client, you enter
- Email, first name, last name (phone optional). For Case-status rows the name fields are hidden — the name is pulled from Clio.
- A mode — Intake (still collecting documents, pre-acceptance) or Case status (matter already accepted, post-acceptance).
- The Clio matter number — required for Case-status rows, optional for Intake.
- Vehicle Year / Make / Model — required on Intake rows (the document-request chase emails merge them). On Case-status rows the vehicle is pulled from Clio on Preview (see below) into editable fields.
- A per-row Language (English / Spanish) selector — sets the client’s language for the quiz link, the doc-chase emails, and the client portal.
- Per card: whether to send the portal-invite email and (Intake only) the document-request emails, plus any documents you already have to attach (these attach to the newly created card).
Per-card email toggles
Each client card has its own checkboxes — ✉️ Send portal invite email and (Intake rows only) 📄 Send document request emails. Leave them on for the normal welcome + chase flow, or untick either to enroll quietly (e.g. you’ve already talked to the client and don’t want to re-spam them). The choice is per card, so you can mix loud and silent enrollments in one batch.
Intake mode — pick the stage + attach docs you already have
Choose where they are in document collection (e.g. Collecting Documents). Then attach any documents you already collected from them offline — Repair Orders, Registration, Purchase/Lease, Additional. The files upload straight to the new case once it’s created, and any doc type you attach counts as already collected, so the client isn’t asked to re-upload paperwork they already handed over.
Case-status mode — Preview pulls name, stage & vehicle from Clio
For accepted matters, you don’t pick a stage or type the name. When you click Preview, the portal reads the matter straight from Clio and fills in:
- the client name (that’s why the name fields are hidden for these rows);
- the current Clio stage, and which of the 8 client-status buckets it maps to (e.g. Clio “Discovery” → Discovery Phase);
- the vehicle — Clio’s YEAR plus the combined “MAKE AND MODEL” field — into editable Year + Make & model inputs you can override. If Clio has none, the preview shows “not in Clio — add above.”
Clicking Enroll confirms the mapping. From then on, Clio stage changes flow into the portal automatically.
How it works
- Fill in one or more client rows (set each card’s email toggles + attach any docs).
- Click Preview — resolves each matter number, flags typos / already-enrolled / missing stages.
- Click Enroll — each card honors its own invite / document-request toggles, so untick them to enroll silently.
- For each new client the portal: creates the case record, upserts a GHL contact (tag
portal-migration-complete), and ~60s later sends a 72-hour login link via your GHL workflow.
GHL workflow you must create
Create a workflow triggered by “Contact tag added” → tag =portal-migration-complete. Use {{contact.portal_upload_url}} in the email body for the login link. This is a one-time “your portal is ready” announcement — the normal “request a link” flow works for them afterward.
Safe to re-run
Preview and enrollment both dedupe by email — if a case already exists for that email it shows "Already enrolled" and is skipped. Re-running the same list is harmless.
Case status board (post-acceptance)
The Case Status board is a read-only view of where every accepted case sits in the Clio matter lifecycle — so you can see the whole post-acceptance pipeline without logging into Clio.
What you see
- Columns for the 8 client-status buckets (Free Case Evaluation → Settlement Reached), plus Case Closed — Won! and Case Closed, and the two outcome columns Not Eligible (Clio “PNC Rejected”) and Referred Out (Clio “Referred Out”) — these also show on the client portal.
- Closed cases keep their reason. When a matter closes, the board still shows Not Eligible or Referred Out if that’s how it ended (rather than collapsing into a generic Case Closed). Only a settled-and-disbursed close reads Case Closed — Won!, and anything else closed reads Case Closed.
- Each card shows the client, vehicle, Clio matter number, and how long since the stage last changed.
- Click any card to open the full case detail page.
Portal cards ⟷ Clio matters (live) — reconciliation + onboard
A toggle at the top of the board flips between Portal cards (cases that have a client portal) and Clio matters (live): a read of every matter in our Lemon-Law practice area in Clio, grouped by stage. The board now opens on the Clio matters (live) view by default, since it’s the fuller picture. Because Clio holds more matters than the portal (only intake-originated cases get a portal card), this is the drift / QA check — the header tallies N in Clio · M in portal · K not yet, and a green border marks each matter the portal already has a card for.
Finding a matter: use the search box at the top of the view to filter by client name, email, or matter number (the same quick-search you have on the Dashboard), and the Matter status chips to narrow by Open / Pending / Closed.
It’s also actionable: tick any un-synced matter that has a client email in Clio and click “Bring N into portal” — that creates the case card and sends the welcome / portal link, and never the quiz (these are signed matters; it reuses the case-status enrollment path). Matters with no email in Clio show a badge and can’t be auto-onboarded — add the email in Clio first. The Clio read is cached a few minutes; ↻ Refresh from Clio forces a fresh pull. This view lives only in our portal and only for Lemon Law — nothing about it appears to other Clio departments.
It's read-only — by design
You don’t move cards here. Stages are managed in Clio; when a matter’s stage changes there, the board updates automatically (via the Clio matter webhook). This board is purely for visibility.
Unmapped stages — now self-serve
Clio occasionally adds or renames matter stages. When a case sits in a stage the portal doesn’t recognize, it falls back to the Case Accepted column and shows a ⚠ unmapped badge alongside the raw Clio stage name (hover it for the fix).
You no longer need an engineer — or the old “Verify stage map” button (it’s been retired). The stage map is now a real, editable table: go to Admin ▾ → Settings → Clio → Stage Map, which shows Clio’s live stages joined against the portal’s map and flags any that are missing. Map the new stage there — its client label, board lane, GHL status value, and which status email fires — and it takes effect immediately, no code deploy. Unmapped stages are also surfaced on the System Health banner so they don’t go unnoticed.
Partners (its own tab)
Checking whether it is on…
Partners is reachable two ways: a top-level Partners tab for quick staff access to the management list (most of it is staff-accessible; a couple of destructive actions stay admin-only), and the fuller program under Admin ▾ → Settings → Partners (admins) which adds Partner Branding and Affiliate Banners. The amber badge on the nav link is the number of pending applications waiting for a decision.
A partner gets no emails
Partner emails come from UrVeedaOS, so a partner needs a UrVeedaOS contact linked to their card. When approved partners are not linked, an amber note at the top of the list says how many; tick Show only these. Open each one and press ↻ Resync to Clio + UrVeedaOS. It finds their contact by email, or makes one with the firm’s name and no tags (so no workflow fires and nothing is emailed), links it, and says which. If UrVeedaOS refuses, the reason shows in red: send it to the admin. A red “Last UrVeedaOS send failed” line on a card is the same kind of reason, from an earlier send. Done looks like: the card shows UrVeedaOS contact ↗. Linking does not send the welcome email; Reset password does, if they still need to sign in. The emails themselves only go out when the partner workflows are built and Published (Settings → UrVeedaOS → Which workflows are built).
Partner Management
The management list — the top-level tab, and the first sub-tab under Settings → Partners:
- Approve → creates the login and emails a one-time temp password (also shown once here as a backup); the partner is forced to set their own password on first sign-in.
- Deactivate blocks sign-in (reversible); Reactivate restores an Inactive partner, keeping their password + code (admin only).
- Delete is permanent (behind a confirm) and blocked if the partner has any referrals — deactivate those instead. Junk/test partners only (admin only).
- Referral code is editable inline (lowercase letters/numbers/dashes, unique). Partners can also change their own from their dashboard. ⚠ Changing it breaks any
?ref=links already shared with the old code. - Referral fee — open a partner to set their fee mode: Firm graduated schedule (the default tiers), Flat override % (a single negotiated rate — e.g. Cousins Law at 25%; a warning shows above the 20% cap), or Custom schedule (their own tiers). Pick case-by-case or lifetime ("refer more, earn more" — crossing a cumulative net-fee threshold raises the rate on future cases and emails them). The fee is applied to the net attorney fee at settlement and synced to the case automatically.
- Agreement documents — upload the partner’s signed agreement PDF (staff-only). They see it read-only under Documents in their partner portal.
- 💸 Paying a partner their fee (Record payout). Open the partner → Referred cases → press Record payout on the client (or use Analytics → Partner Payouts Due). The amount starts at what we still owe: change it to what was actually paid, add the date, how it was paid and the check or confirmation number, choose whether it settles the fee, press Review, then Record payout. The fee-paid email to the partner (LAF-P05) is off unless an admin turns it on in Settings → Communications; then the form shows an unticked “Email the partner” box, and the email goes only if you tick it and the fee is covered. Nothing about money is emailed on its own. A note goes to the client's Clio matter, and the partner's portal shows the fee as paid (or “$X paid so far” after a part payment). A payout is due once Funds Disbursed is pressed on the case. The portal doesn't send money: cut the check or wire as usual, then record it. The payout and its date also go to the client's UrVeedaOS contact (partner fee paid amount and date).
The firm-wide graduated schedule + class-action rate live under Settings → Partners → Referral Fees (admin).
RV Routing — where RV referrals go by default
Checking whether it is on…
Settings → RV routing (admin). Sets which outbound firm an RV referral goes to, so Push to Partner on an RV doesn’t have to ask. Refer-out on an RV case then defaults to Automatic (RV routing) and names the firm before you save; you can still override to any firm, and overriding is not an error.
Three things about it surprise people, so they are worth knowing before you touch it:
- Weights are relative, not percentages. 7 / 3 is the same split as 70 / 30. Adding a third firm does not mean editing the other two back down to 100. The Share column does that division for you.
- A weight of 0 is paused, not removed. The row and its history stay, so the firm can come back. Remove is the other operation, and it is not undoable.
- Changing a weight rebases the counters. The new split applies from the next RV forward rather than re-cutting RVs already referred out. Without this, a firm that gained share would be handed a long run of consecutive RVs to “catch up” on history that never ran under those weights. You are warned before saving.
Each RV goes to whichever live firm is furthest behind its share, so the split holds over time instead of only on average — and a firm that gets ahead through a manual override is simply skipped until it is level again. Assigned is scheduling state, not a record of how many RVs a firm has received; for that, read the Referred Out tracker. Zero counters is for drift from outside routing (a manual override, a backfill), not for a weight change — that rebases by itself.
With no firms configured, or every firm paused, Push to Partner falls back to choosing the firm case by case — the behaviour that existed before this panel. That is the designed answer, not a failure.
How we refer clients to each firm. Every outbound firm's record (Settings → Partners) has How we refer clients to this firm: We collect documents first (the default, and what every firm had before) or Introduce only. The split above still decides which firm gets the next RV; the firm's choice decides what happens next. We collect documents first: the quiz asks the RV questions, the client uploads documents, staff refer the case out and the firm gets the documents. Introduce only: a quiz visitor who picks RV sees that firm named, gives their name, email and phone, ticks the referral acknowledgement, and is introduced to the firm at once. No RV questions, no documents.
Introduce-only referrals is the master switch on this page (admin). Off: every firm is treated as We collect documents first, whatever its record says; the choice is saved and used once the switch is on. On: the quiz looks at the next firm in the split without using its turn; if that firm is set to Introduce only, the visitor gets the hand-off card, and the turn is used only when they submit. If, at that moment, the split lands on a different firm or on a firm that collects documents first, nothing is sent, the turn is given back and the visitor carries on with the RV questions. The firm that referred the client to us is skipped, as for staff refer-outs. Each introduction shows in Referred Out (source “quiz introduce only”), staff get the usual referred-out alert, the client and the firm get the introduction email (REF-INTRO, built in UrVeedaOS), and a Clio prospect note says no documents were collected. Clients already partway through the RV questions are not affected.
Check Clio refer-out fields (read-only)
Referred Out → 🔎 Check Clio fields lists every matter in Clio's REFERRED OUT stage, plus every matter a referral here points at. For each it shows what Clio has in Matter Reffered Out to, the matter's stage and status (Open, Pending, Closed; filter by it with Matter status) and Co-Counsel Fee Received, next to the firm and fee recorded in the portal, and what a fill would write. It writes nothing to Clio or the portal.
- Blank in Clio: the portal knows the firm; Clio's field is empty.
- Different firm: Clio and the portal disagree. A person decides; nothing would be overwritten.
- Assign firm: the portal has no firm for it yet. Assign one on the referral first.
- Not in Clio: a referral here carries a matter number Clio's Lemon Law matters don't have.
- Wrong stage / Fee not ticked: the firm is right, but the stage isn't REFERRED OUT, or the fee is paid here and not ticked in Clio.
- Agrees: nothing to do.
- Each row also says whether the receiving firm has an agreement on file (uploaded under Settings → Partners → Agreement documents, or e-signed), and the Agreement filter picks the rows without one.
⬇ Download CSV gives the list (or the filtered part) with a blank “Team check” column to mark up. 📋 Copy as text copies the same list for a DM or an email: one block per matter with every line labelled (matter, result, what Clio says, the portal's firm, what a fill would write, “Right firm?”). Filling Clio from it is a separate step that comes later, after the list is checked.
Client documents to the receiving firm
When we refer a case out, the receiving firm can get the client's Google Drive folder (every document, originals included), shared with one email at that firm as a viewer, never “anyone with the link”. Which cases:
- RV cases: always.
- Other cases: only when the firm's Share client documents box is ticked (Settings → Partners → the outbound firm) and we collected documents for the case.
- The email to the firm (every case shared): the REF-PKG email: the intake for that kind of case (the RV questionnaire, or the vehicle or product answers) plus the documents link. The firm also sees the link on its status page.
- Which address: the firm's Email for client documents (same place), or the firm's referral email when that is blank. The firm can set it itself on its status page; if documents are waiting and we have no address, the page asks for one. Changing it, there or in Settings → Partners, shares every open referral with the new address straight away (Partners says how many). The folder the firm receives is named for the client, for example “Jane Smith — case 1234”.
- Where the firm sees it: each referral on the firm's status page shows “Open the client's documents (Google Drive)” and the address it was shared with. A firm without a Google account gets Google's invite and opens the folder with a one-time code (if the owner allowed it in Google Admin) or by making a Google account on that email.
- Referred before this existed, or the firm says it has no link: Outbound referrals → open the referral → Send documents to firm. It needs the referral linked to its case.
- More documents later: reviewing a document (the green pill) on a case whose package already went out re-sends the package once, 30 minutes later, so several reviews make one email.
- The email is the UrVeedaOS workflow REF-PKG (tag
referral-package). Until the owner builds it, the folder is still shared and Google's share email still reaches the firm.
Adding a partner you already know — Inbound vs. Outbound
For a partner you don’t need to vet, skip the application/review entirely: use + New → Add a partner. The modal opens with an Inbound / Outbound toggle:
- Inbound — refers to us (the default): a partner who sends us cases. Creates a pre-approved (Active) partner with a portal login and emails them a temp password on the spot — the email is required. The modal is laid out contact on the left (incl. a payout address — where their referral checks are mailed) and commission on the right: pick a fee mode — Standard schedule (the firm graduated tiers set the rate, so there’s no per-partner %) or Flat override % (enter the negotiated rate; a 20%-cap warning shows above it). On the standard schedule you also choose Case-by-case vs Lifetime (cumulative). You can set a custom referral code (blank = auto-generate), and after creating the partner you can upload their signed agreement PDF right from the confirmation screen.
- Outbound — we refer out: a firm we send cases to (e.g. wrong case type). Only the law firm name is required plus a reason we refer out dropdown; no portal login is created and no temp password is emailed. It just records the firm so you can attribute outbound referrals to it.
A custom fee schedule (a partner’s own tier table) is still built in Partner Management — the confirmation screen links you there. The signed agreement can be uploaded straight from the confirmation screen.
Referral fees — how a partner's commission is calculated
When a partner-referred case settles, the portal computes the partner’s referral fee automatically and writes it to both the case and the partner’s referral record (no double entry). The fee is a percentage of the firm’s net attorney fee, not the settlement amount.
The basis: net attorney fee
Net attorney fee = attorney fee − litigation costs. You enter both on the Settlement form; the referral % is applied to that net figure. (Fla. Bar 4-1.5(g) caps the schedule at 20% of the net fee.)
The firm graduated schedule (default)
Partners on the default schedule earn a rate that steps up with the net attorney fee:
| Net attorney fee | Referral % |
|---|---|
| $0 – $5,000 | 10% |
| $5,001 – $10,000 | 15% |
| $10,001 – $15,000 | 20% |
| $15,001+ | 20% (cap) |
| Class action | 5% |
Admins edit this firm-wide schedule + the class-action rate under Settings → Partners → Referral Fees.
Per-partner options (set in the partner drawer)
- Firm graduated schedule — the default tiers above.
- Flat override % — one negotiated rate, no tiers (e.g. Cousins Law = 25%). A rate above 20% shows a cap warning — keep the signed agreement on file.
- Custom schedule — the partner’s own tiers, edited inline.
- Case-by-case vs lifetime — case-by-case picks the tier from each case’s net fee; lifetime (“refer more, earn more”) picks it from the partner’s cumulative net fee. Crossing a lifetime threshold raises the rate on future cases only and sends the partner a tier-upgrade email.
At settlement — what you do
- Enter the attorney fee + litigation costs; the referral %/$ auto-fills from the partner’s setup and the resolved tier is shown.
- It’s editable — you can override the amount, set a one-off per-case % override, or tick class action.
- On save, the fee lands on the case and the partner’s referral record, so the partner-portal balance is correct without re-typing.
Precedence when resolving the %: per-case override → class action → partner flat override → schedule tier.
Partner documents (agreements)
Upload a partner’s signed agreement PDF from the partner drawer (Agreement documents). It’s staff-upload only; the partner sees it read-only under Documents in their portal. Useful as the paper trail for negotiated rates above the cap.
Settings (admin only)
Everything under Admin ▾ → Settings is admin-only — non-admins don’t see the Admin menu, and the routes reject them server-side. Every change is audited. Settings opens on the Overview: every On/Off switch in the portal, whether it is on right now, since when, what it does while on, and a link to the page that changes it. The menu on the left groups the pages by the job: The firm (People and notices, Business hours, Reports), Clients (Quiz, Client signing, Messages and reminders, Unsigned retainers, Follow-ups, Communications), Staff work (Workbench, Call flags and scripts, Product cases, Litigation), Partners (Partners, Branding, Banners, Referral fees, RV routing) and Connections and data (Clio, UrVeedaOS, Manufacturers, Recovery). Type in the search box to find a page by what it does (“holidays”, “address”, “shout-outs”). Each page starts with what it is for, who sees the result, and the state of any switch on it. On a phone the menu is a dropdown. The address bar follows the page, so you can copy a link to one; old links to the former tabs still open the right page. (The shared Warranty Manual library moved out to Manage ▾ → Warranty Manuals so any staff can reach it.)
Communications has one switch per optional message, all Off to start: the thank-you receipt to a firm, the fee-paid email to a partner (LAF-P05), monthly firm statements, and the lost-client survey. The three about money are only On or Off, never automatic: On adds an unticked box to the form that sends it (or, for statements, a Send button), so a person decides each one. The survey can also be Automatic (every Soft Close).
Checking whether it is on… Checking whether it is on… Checking whether it is on… Checking whether it is on…
Texting for existing clients (bottom of Communications, admin only) is a one-time catch-up, not a switch. Clients may be texted about their case until they say no (firm policy, 11 Nov 2026), and new clients get that on their own when the retainer is marked signed or a Clio matter is imported. For clients from before: Check how many shows how many have no text consent on record, how many already have it, and how many replied STOP, opted out or had texts turned off by staff (those are left alone). It changes nothing. Turn texting on for these N clients, then Yes, turn texting on, records consent as existing client (firm policy) on each case, lifts their text block in UrVeedaOS, and writes an audit log row with who pressed it and how many. Pressing it again later only picks up clients still without consent.
Partners has four sub-tabs: Partner Management, Partner Branding, Affiliate Banners, and Referral Fees — the firm-wide graduated fee schedule (tiers on the net attorney fee) plus the class-action rate. Edit the tiers here to change the default every partner on the firm schedule resolves against.
Quiz
Two switches for the public quiz. Changes reach the live quiz within about a minute.
Checking whether it is on… Checking whether it is on… Checking whether it is on… Checking whether it is on…
- A/B test: Off gives everyone the current quiz. Split assigns each new visitor to A or B and keeps them there. Until the short quiz (B) is built, Split only labels sessions; nobody sees a different quiz.
- Feedback question after submit: first confirms “Your free case evaluation is in” and says documents come next, then asks “How easy was the evaluation to fill out?” (1 to 5), noting the answer has no effect on their case. After a score, an optional box asks what made it hard or what could be easier. Clients can skip it, and it moves on to the upload page by itself after a minute. The average, the 1–5 counts and what clients wrote (newest first, linked to the case) show in Analytics → Quiz & documents → Quiz, step by step.
- RV referral acknowledgement: Off gives RV clients the same consent boxes as everyone else. On adds one more required box for RV clients only, at the consent step: that we may refer their RV case to a partner law firm that handles RV cases and share their answers and documents with it. The quiz can’t be submitted until it is ticked. What they agreed to is recorded on the case (event rv_referral_consent.captured, with the exact words, when and from where), like the Sue Your Dealer hand-off records its consent.
People
- Create staff/admin logins (@lemonaidfirm.com or @maclegalpa.com), set each person’s role, and deactivate accounts.
- Map each portal user to a Clio user so owner-routed actions + time entries attribute correctly. The dropdown lists all active Clio users; if it only shows a few, Clio isn’t connected on this environment (see Admin ▾ → System Health) and it’s falling back to a short built-in list.
Reference Data
- UrVeedaOS → Which workflows are built (admin): press Check workflows to see every workflow the portal and the owner’s tracker expect, and whether each is Published (running), in Draft (not running) or Not found, with the tracker step that builds it. It flags two published copies of one workflow, because both would send. It only reads; it changes nothing in UrVeedaOS. It matches by the code in the workflow’s name, so one named differently is listed underOther workflows.
- Manufacturers, SOL Years, Activity Durations — the firm’s lookup tables, used by the Clio sync, the FRA letter, and the SOL suggestions. These used to sit under a tab called “Clio Sync”, which is where the code reads them from, not where you’d look for them.
- Sync Health moved. It is now Admin ▾ → System Health — it is a live operational view, not a setting, and it was three levels deep behind a word that doesn’t suggest health. It has the live outbox queue, the Clio TEST/LIVE mode toggle, failed events with Retry, and a live Clio connection check that flags a dead/missing Clio token (which otherwise silently breaks Clio reads like the staff→Clio user list, and every Accept). Same signal as the status badge in the top-right (which now also lights up when Clio isn’t connected); this tab is its home.
- Fix & Resync (dead letters): a failed (dead-lettered) event often means the case’s downstream links drifted — a retry alone just fails again. Each dead letter now has a Fix & Retry button (and a bulk Fix & Resync all) that first repairs the case’s links (GHL contact, Clio contact, matter relink, opportunity), then requeues the event behind those repairs so it succeeds. The person’s name on each row is a link straight to their case card.
No Dealerships screen: dealerships are created in Clio automatically when you accept a case (from the quiz’s dealership field) plus a verify-task — nothing to maintain by hand.
Clio → Task Settings
- Control every task the portal creates in Clio: turn each on/off, set the default assignee (from your live Clio users), and give it a due date of +N days. The Push-to-Clio screen can still override an assignee per case.
- Who gets new cases (top of the page): two rotations that share new matters out like RV routing shares RVs between firms. Each new matter goes to whoever is furthest behind their share. Weights are relative (1 and 1 take turns; 2 and 1 give the first person twice as many); 0 pauses someone. People come from the intake team mapped to Clio (Settings → People).
- Case evaluators get the Vincent: evaluation prep task on each new matter.
- Responsible staff become the matter's responsible staff and the default assignee for the push tasks, instead of one fixed person.
- Vincent task only (default): each rotation picks its own person. Responsible staff + Vincent task: the evaluator rotation picks one person for both.
- Vincent: evaluation prep (a task, on by default): its description is a prompt written for that case: the file names in the Client Folder, the Clio fields to fill with their names and ids, what we already hold (VIN or serial, the vehicle or product, the problem), and the state's SOL rule. The evaluator pastes it into Vincent with the matter selected. Vincent fills a field only when the value is printed clearly and agrees with what we hold; anything in doubt, or where documents disagree, goes on a “Needs a person” list. It checks the SOL but never changes it, and never touches the manufacturer, its address, the dealership, the purchasers or the matter description. It finishes with three tables: fields changed (before and after, with the source), needs a person, and three fields to check against the documents. The same prompt, read live from Clio, is on the case page: Actions → Vincent: evaluation prep → Copy.
- The SOL lives in two places on the matter: the SOL Deadline to file complaint field and the end of the matter description (LAF-FL Name v. Maker SOL: date; the LAF-FL is the state whose rule was used). The prompt shows both, works out the date from the state's rule, and when it differs gives the description exactly as it should read. The evaluator changes the field and the description together, then completes the task.
- When the evaluator completes the task, the portal reads the SOL back from Clio. Field and description agree (descriptions vary, so it looks for “SOL” and a date anywhere in it; a description with no SOL date leaves the field to stand alone): the case page and board show that date (logged with before and after). The field is blank, or the description has a different, unreadable or second SOL date: nothing changes in the portal and a Clio task Check the SOL: field and matter description goes to the evaluator; completing it reads the SOL again.
- A re-push keeps the SOL in Clio. If Clio already has a different SOL, Push to Clio keeps it in the field and the description, brings it into the portal, and says so. Change the SOL in Clio, not on the push form, once the matter exists.
- With the Vincent task switched Off (and Vincent task only mode), nobody is counted in the evaluator rotation, since nobody gets a task.
- Push to Clio again on a case that has a matter shows the matter description as Clio holds it and the standard one the push would write (Current → New, like VIP and referral). Keep the current one, use the new one, or edit it. A matter pushed before its documents were in (left in Pending Review) gets its Vincent task on that later push, and the evaluator rotation picks who.
- Don't close a matter in Clio to park it. Closing stops the client's document reminders, shows “Case Closed” in their portal and can send the case-closed email. Leave it in Pending Review; the next push updates it.
- Analytics → Team → Case evaluators: per evaluator, Vincent tasks received and done, median days to done, and what the SOL read-back found (confirmed, changed, sent to a person).
Clio → Stage Map
What each Clio matter stage means to the portal — the client dashboard label + copy, the staff board lane, the GHL case_status value, and which status email fires — all editable here. When Clio adds or renames a stage, map it in this panel and it takes effect immediately: no code deploy. New/unmapped stages are pinned amber at the top (and a matching banner appears on System Health), so a Clio change never silently shows the client the wrong status or skips an email. The behaviors are explicit toggles (accepted / pending-FRA / settled / reject / referred-out / RO Nurture / Docs pending), so editing the client wording can never break a comms trigger.
RO Nurture and Docs pending are the two that gate the nurture sweep, and nothing moves until one stage carries each. That is deliberate — an unticked flag means “we don’t know where to put this matter”, and leaving it alone beats guessing a stage — but it does mean nurture looks like it is doing nothing until they are set. Tick RO Nurtureon the stage a parked matter should sit in, and Docs pending on the “still waiting on documents to evaluate” stage. Renaming those stages in Clio afterwards is always safe: the portal keys on the numeric stage id, never the name.
Reordering. Drag a row to move it, or use the ▲ / ▼ arrows — both do the same thing, and the arrows exist so reordering works from a keyboard. The order is the firm’s reading order only; it changes nothing about behaviour. Rows pinned amber at the top (new/unmapped, or stale) can’t be moved: their position is a count the banners depend on, not a preference. Nothing saves until you press Save.
Clio → Clio Reference (IDs)
Its own sub-tab under Clio, collapsed until you open it. Load from Clio pulls Clio’s own lists live — custom fields (with their ids, types and picklist option ids), matter stages, users, document templates, practice areas, expense categories, webhooks and notification methods. Use it whenever you need an id: the Clio user to assign a task to, the field id for a new merge token, the option id a picklist has to be written by. Fields the firm created are prefixed LAF and are listed first. Copy everything as Markdown puts the whole pull on your clipboard, timestamped, so you can paste it straight into a chat instead of asking someone to run an API pull on the server. It is read-only — it writes nothing to Clio and nothing here. If a section can’t be loaded it says Failed and gives the reason; it never shows a count of zero, because “Clio has none of these” and “we couldn’t ask” would send you to two different places.
Warranty Manuals
The shared warranty-manual library — bulk-load PDFs, set whether each booklet is the new-vehicle or the certified-pre-owned warranty (or both), dedupe by content, trim a full owner's manual to the warranty pages (with auto-detect), and see the "most-requested missing" worklist. Full details in Warranty Manual Library.
Staff training: skills and sign-offs
Checking whether it is on…
Why: every client should get the same good first experience, whoever picks up their case. So each intake skill says what good looks like before you try it, and you can see for yourself what you have shown a trainer.
If you are learning
- Open Account ▾ → My training. The top line says how many skills are signed off and which one is Next.
- Open that skill. Read why it matters and What good looks like. There are no hidden checks.
- Practise with your trainer. Your trainers are named at the top of the page.
- When you feel ready, press Ask for sign-off. You can add a line for your trainer.
- The answer is Signed off, with the trainer's name and the date, or Not yet with one note on what to work on. Not yet is a normal part of learning: work on the note, then press Ask again for sign-off.
Nobody expects you to know all of this on day one. You see everything that is recorded about you. Your trainers and the admins see the same page; nobody else does.
If you are a trainer
- Open Account ▾ → Training. People who asked for a sign-off are at the top, and the menu shows how many are waiting.
- Open the person, then the skill. The same checks show as What to look for. Watch them do it, on a call or on the screen.
- Press Sign off, or Not yet with one specific note. Not yet needs a note.
The trainee reads every note, so write what you saw, what they did and what it led to (“On the Spanish call you confirmed the address twice, so the client didn't have to repeat it”), not “good job”. No client names or details in notes. Nobody signs off their own skill. A decision is never edited: a later one is added, and History shows them all.
The skills
Intake only, in the order the work is met: the Workbench day and call flags, the first call, a quiz that isn't finished, collecting and reviewing documents, the certified pre-owned booklet, Push to Clio, a case that comes back for more documents, hard reject and soft close, opt-outs, partner leads and partner upkeep, referring a case out, a Spanish-speaking client and an upset client. Each one has a rough time with a trainer and a link to the Help section for its screen.
Practice cases (training site only)
The training site has a bar across the top: PRACTICE SITE. Nothing here reaches a client, Clio or the mail. That is true of everything on it. Its quiz and client portal carry the same bar, in English and Spanish, with a link to the real site, for anyone who reaches them by mistake. It holds a set of made-up clients to practise on: a new lead for a first call, a case with everything in, one with four wrong documents, a certified pre-owned case with no booklet, a Spanish-speaking client, a quiz that isn't finished, an upset client, one to close, one who replied STOP, a lead from a referral partner, and a case that was pushed and came back for one more document.
If you are learning: the practice cases are on the board like any other case. Work them the way you would a real one. Every name, dealer and vehicle number is made up, and every document is stamped SAMPLE: TRAINING ONLY. You can't break anything.
Push to Clio is practice there too. It makes the same checks as the real one and stops you with the same words. When it goes through, nothing is sent: a box shows what would have gone to Clio, what you left blank, and whether the dates and VIN you typed match the documents. The card then moves to Matter Created / Pending Review.
If you are a trainer: open Account ▾ → Practice cases on the training site. Each case says what it is for, which documents are wrong on purpose, and what to say as the client. Trainees don't see that page. Press Reset practice cases before the next person: every practice case is removed and built again, fresh, and nothing else on the site is touched. Record the sign-off on the live site (Account ▾ → Training).
For admins: turning it on and choosing trainers
Off (how it starts): staff see nothing. You can still tick trainers and open the Training page to look, and nothing can be recorded. On: everyone sees Account ▾ → My training, and trainers and admins see Account ▾ → Training. Turn it on in Settings → People and notices.
Tick Trainer on a person's row in Settings → People and notices. Admins can sign off without the tick. Unticking keeps every sign-off that person recorded. A sign-off is a record, not a lock: it never hides a screen or a button.
Preferences — your personal layout
Under Account ▾ → Preferences (top-right, available to everyone — not just admins) you can tune how the portal looks for you. These are per-device display choices; they never change anyone else’s view and never hide a feature — they only reorganize the layout.
- Compact case actions (on by default) — keeps a case’s Actions tab focused on the primary decision and tucks the secondary controls under a tap More. Turn it off for the classic layout with every button and box expanded. You can also flip it right from the link under the buttons on any case’s Actions tab.
Troubleshooting & support
Checking whether it is on… Checking whether it is on…
Recovering a deleted case card
Deleting a case card is now recoverable — it moves the case to the Trashinstead of being erased. Clio, UrVeedaOS, and the Google Drive document backups are never touched by a delete.
- To get it back: an admin opens Settings → Recovery and clicks Restore — the card and its documents come back exactly as they were. The same tab shows how much disk each trashed case is holding, and Delete permanently reclaims that space (admin only).
- Deleted before Trash existed? On the same Settings → Recovery tab, use Rebuild a case from UrVeedaOS: enter the client’s email and it re-creates the card from the still-existing UrVeedaOS contact and re-links Clio — the client does not retake the quiz. It restores their identity (name / email / phone / state); top up vehicle/quiz details by hand, and re-pull documents from Google Drive if needed.
If a decision button shows a red error
- Read the error message carefully — it usually says what's missing.
- If it says "Clio matter created but local save failed" — DO NOT click again. Email David immediately (info below).
- For "Missing required field" errors — scroll up, fill in the missing field, try again.
- For anything else — screenshot the error and email David.
If a case doesn't appear in the Workbench
Try the "All" view toggle — it might be in a closed stage. If it's truly missing, email David with the client's email address.
If a client says they didn't get an email
Ask them to check spam first. If it's not there, email David with the client's name and what email should have gone out — we can re-send manually.
Report bugs or ask questions
📧 David Jones — marketing@lemonaidfirm.com
Send a screenshot, the client's name or email, and what you were trying to do. The more specific, the faster it gets fixed.