Precision Case Lens

Prospect Guide · Add-On Module

Office Communications

The outbound call that was never made again, made. Every time.

What it isoverview

The four callsscripts

Cadence & batchingthe engine

The touch loga week of calls

Four documents. The same synthetic case, Reyes, Maria Elena, from the PCL sample-report set: the records and source statements that case development asked for are what this module goes and gets.

What Office Communications does for your practice

Turns every request into a pursuit

A records request, a source-statement request, a status check, a client check-in. Each becomes an item with a status, a next-action date and a cadence that cannot silently die. It closes on receipt, on documented human abandonment, or on case closure. Nothing else.

Makes the follow-up calls

An AI receptionist calls the provider's records department, the treating doctor's office, the hearing office, or your client, from a script generated for that case, with disclosure first and identity confirmed before any patient detail is spoken.

Compresses when a hearing is coming

A source-statement chase runs every few weeks on a quiet case and every day inside the last two weeks before a hearing. The hearing date re-baselines every open pursuit the moment it posts.

How it moves your win rate

Case development tells you what to go get. This is what goes and gets it. The treating-source statement that arrives at day 60 instead of day 12 is the one that arrives after the five-business-day evidence window closes. Records chased on a fixed cadence arrive in weeks, not months, and every attempt is logged in a form you can put in front of a judge when an agency or a provider delayed.

Walk-through in 60 seconds

"Case development flagged two source statements and one records gap. Three pursuits opened the same day."
"Here are the four call types. Read one script: disclosure, identity check, what it captures, what it leaves on voicemail. Nothing about the patient until the right person is on the line."
"Here is the cadence. Day 3, 10, 17, 24, 30. Then daily when the hearing is fourteen days out."
"And the log after one week. Who was called, what they promised, when the promise gets verified."

Synthetic case. Maria Elena Reyes and every provider named are fictional. No real claimant data appears anywhere in this set.

Office Communications at a glance

Add-on module inside PCL · lives in each case's outreach tab
Script generation live · live dialing when voice credentials are configured
Prospect guide

1.The four call types

Call	Who it calls	What it captures	When it fires
Records follow-up	Provider medical-records or HIM department	Receipt confirmed, facility reference number, estimated completion, responsible contact, any fee.	Day 3, 10, 17, 24, 30 after the request; weekly after, with escalation to a human at day 30.
RFC / MSS chase	Treating doctor's office staff	Form received, completion estimate, obstacles, return method, direct contact. Obstacles route to the representative; the AI never discusses the clinical content.	First chase at 30 days before hearing; every 3 days inside 21; daily inside 14.
SSA status inquiry	Field office or hearing office	Current status, hearing date, outstanding development, the representative's name and extension.	Portal first. Phone only when the portal is stale or a date has not posted. Monthly, re-triggered by notices.
Client hearing check-in	The claimant	Hearing date confirmed, scheduling conflicts, new records since last contact, preferred way to get them in.	40, 30 and 15 days before the hearing.

2.What every call has in common

Disclosure first. "This is an automated call from the firm. I am an AI system calling on behalf of the legal team." Before anything else.
Identity before information. No patient identifier is spoken until the callee's role and entity are confirmed. A misdial hears nothing.
Administrative only. Dates, receipts, reference numbers, estimates. Never case merits, never a prediction, never an exact deadline unless the representative has confirmed it.
Zero-detail voicemail. Firm name, a reference number, a call-back number. Nothing else.
Every attempt logged with outcome, promise and promise-verification date, in a chronology built to be exhibit-ready.

3.The engine underneath

Cadence you approve, not a prompt

Cadence profiles are configuration: named, versioned, attorney-approved. The default records profile is the firm-wide standard; a firm can register a tighter variant. Compression near deadlines has a hard ceiling of one call per business day per phone number per matter.

Custodian batching

Six pursuits pointing at the same hospital records line become one call: "I have status checks on six requests; reference numbers ready." Up to eight items per call, ordered by deadline. Providers are not blacklisting you, and frequency caps hold.

Humans win ties

A staff member's call to a provider is logged as a touch and suppresses the AI's touch for that target for one business day. A human-negotiated promise resets the next action. Staff can check a pursuit out and the AI waits.

Portal first for agencies

Where an agency has a portal, it is pulled first. The phone is the exception, used when the portal is stale, and every hold minute is logged as agency-delay evidence.

4.Status today, stated plainly

Script generation for all four call types is live inside PCL today and appears in each case's outreach tab. Live dialing runs through a voice platform and a workflow engine; it activates for a firm once those credentials are configured and the add-on is active. Until then, every script generates in preview and "schedule call" is a stub. The larger design, an inbound reception engine across five practice areas, is specified and is roadmap, not product.

Pricing is not shown in this set. Ask for the current rate sheet.

Vocational analysis — case preparation only. Grid rules, transferable-skills questions, occupational-base erosion and cross-examination material are prepared from the written record. Vocational-expert testimony at hearing turns on the hypothetical as actually posed, the expert's own sources and methodology, and context the file does not carry. Nothing here predicts what a vocational expert will say or how an adjudicator will rule. All vocational conclusions require evaluation by a vocational expert and the representative of record. · PCL output for attorney review. Not legal advice. All conclusions require evaluation by a licensed attorney or accredited representative. · Outbound contact is administrative and scheduling only; the AI never discusses case merits or predicts outcomes. · Sample on a synthetic case; no real claimant data. · Precision Case Lens · Beta Build — Pre-Production v0.5

Precision Case Lens

Sample Scripts · Synthetic Case

The four calls

What the AI receptionist actually says, generated for the Reyes case.

What it isoverview

The four callsscripts

Cadence & batchingthe engine

The touch loga week of calls

Position: the scripts a representative sees in the outreach tab before a call is scheduled. Each is generated from the case: provider, reference, days to hearing.

What the scripts do for your practice

Nothing improvised

The opening, the identity check, the capture list, the closing and the voicemail are structured. The AI fills in what the provider says; it does not decide what to ask.

Nothing said out of turn

Patient identifiers only after the callee confirms they are records staff at the right facility. Voicemail carries a reference number and nothing else. Clinical content of a form is never discussed; obstacles go to the representative.

Everything captured

Receipt, reference number, estimate, contact, fee, obstacle, preferred return method. Captured fields become the next action and the promise-verification date.

How it moves your win rate

A source statement returned by day 12 is the difference between an opinion in the record and an opinion missing from it. These calls are what make day 12 happen, on every case, without a paralegal remembering to call.

Walk-through in 60 seconds

"Read the first script top to bottom. Disclosure, transfer to records, confirm who is on the line, then and only then the reference number."
"The source-statement chase: same shape, plus urgency language when a hearing is close, and obstacles routed to you."
"The hearing office call is the exception: portal first, phone only if the portal is stale."
"The client call: hearing reminder and 'any new records?' Nothing about the case itself."

Synthetic case. Providers, phone numbers and dates are fictional. Placeholder brackets are shown exactly as the generator leaves them for the firm to complete.

Call scripts · Reyes, Maria Elena · PCL-2026-0412

Generated in the outreach tab · preview mode
Firm: Stafford & Associates (fictional)
Preview

1.Records follow-up · Dr. Patricia Williams (psychiatry)

AI RECEPTIONIST — RECORDS FOLLOW-UP CALL SCRIPT TARGET: Dr. Patricia Williams — Lakeside Behavioral Health CASE REF: PCL-2026-0412 (original request sent 05/06/2026) OPENING — AI DISCLOSURE (required before any substantive content) "Hello, this is an automated call from Stafford & Associates. I am an AI system calling on behalf of the firm's legal team. This call may be recorded for quality purposes. I'm calling your medical records or HIM department regarding a records request we sent previously. Could you please transfer me?" IDENTITY CONFIRMATION (patient details only after role confirmed) "May I confirm I'm speaking with someone in medical records or HIM at Lakeside Behavioral Health?" [If not confirmed → do not proceed; request a transfer or callback] RECORDS REQUEST STATUS "We previously sent a records request for a patient file under case reference PCL-2026-0412. I'm calling to confirm receipt and get a status update." CAPTURE: confirmed receipt (Y/N) · facility reference number · estimated completion date · responsible staff contact · any fee required CLOSING "Thank you. We'll follow up if we haven't received the records by [ETA+3 days]. Please direct completed records to the fax number or email in the original request. Our reference number is PCL-2026-0412. Have a good day." VOICEMAIL (zero patient detail) "Hello, this is an automated message from Stafford & Associates. We are following up on a records request — reference PCL-2026-0412. Please call us at [Firm Phone] or respond via fax. Thank you."

2.RFC / MSS chase · Dr. Michael Chen (orthopedic surgery)

AI RECEPTIONIST — RFC / MSS CHASE CALL SCRIPT TARGET: Dr. Michael Chen — Northgate Orthopedics CASE REF: PCL-2026-0412 PRIORITY: Standard follow-up (becomes "URGENT — hearing in approximately N days" once a hearing is inside 45 days) OPENING — AI DISCLOSURE "Hello, this is an automated call from Stafford & Associates. I am an AI assistant calling on behalf of the firm's legal team. This call may be recorded. I'm calling regarding a Medical Source Statement form we sent to Dr. Chen — could I speak with the doctor's office administrative staff?" IDENTITY CONFIRMATION "Am I speaking with someone in Dr. Chen's office?" [If not → request transfer; do not discuss patient matters] RFC / MSS STATUS "We sent a Medical Source Statement — a functional capacity form — to Dr. Chen for a disability case. Case reference: PCL-2026-0412. I'm calling to check whether the doctor has received the form and to get an estimated completion date." CAPTURE: received (Y/N) · completion estimate · questions or obstacles · preferred return method (fax or mail) · direct contact IF OBSTACLES REPORTED → Routing obstacle to the representative's task queue for follow-up. → Do NOT discuss clinical content of the form — the representative will call. VOICEMAIL (zero patient detail) "Hello, this is an automated message from Stafford & Associates. We are following up on a functional capacity form — reference PCL-2026-0412. Please call us at [Firm Phone] or fax the completed form to the number in our original letter. Thank you."

3.SSA status inquiry · Office of Hearings Operations

AI RECEPTIONIST — SSA STATUS INQUIRY SCRIPT ⚠ PORTAL-FIRST RULE: check the electronic records portal before placing this call. Use the phone only if portal data is stale, unavailable, or a verbal confirmation is specifically required. TARGET: OHO — [hearing office] CASE REF: PCL-2026-0412 OPENING — AI DISCLOSURE "Hello, this is an automated call from Stafford & Associates, an accredited disability representative calling on behalf of a claimant. I am an AI system. I'm calling to inquire about the status of a pending case. Our reference number is PCL-2026-0412." IVR / HOLD NOTES • Navigate to: representative caller → hearing status • Hold budget: up to 30 minutes; hold time logged as agency-delay evidence STATUS INQUIRY CAPTURE: current status · hearing date if scheduled · outstanding development items · SSA representative name and extension IF HEARING DATE RECEIVED → Re-baseline every evidence and source-statement pursuit to hearing − 5 business days → Representative task: confirm notice receipt and the five-day evidence window → Do NOT state the date to any unverified caller in a later call IF STATUS IS "DECISION ISSUED" → Do NOT read or relay decision content to any caller → Route to the representative for review and client notification

4.Client hearing check-in · the claimant

AI RECEPTIONIST — CLIENT HEARING CHECK-IN CALL SCRIPT TARGET: Maria Elena Reyes (claimant — own case) CASE REF: PCL-2026-0412 HEARING: September 22, 2026 (video) OPENING — AI DISCLOSURE "Hello, is this Maria Elena Reyes? This is an automated call from Stafford & Associates, your Social Security disability representative's office. This call may be recorded. I'm calling with an update about your upcoming hearing and to check whether you have any new medical records to share." IDENTITY CONFIRMATION "Before I continue, can you confirm your date of birth, for verification?" [If not confirmed → do not discuss case details; offer a callback] HEARING REMINDER (administrative and scheduling only) "I wanted to let you know your hearing is currently scheduled for September 22, 2026. Please contact our office if you have any questions about that date." CAPTURE: scheduling conflict reported? (Y/N → route to representative) RECORDS CHECK-IN "Have you seen any new doctors or therapists, or received any new medical records, since we last spoke?" CAPTURE: new records (Y/N) · provider(s) · approximate date(s) IF NEW RECORDS — OFFER OPTIONS (do not act during the call) "I can text or email you a secure link to upload those records, you're welcome to mail them to our office, or we can contact that provider ourselves. Which would you prefer?" CAPTURE preferred method → staff follow-up task. No case discussion.

Each script ends with the PCL disclaimer footer. The generator never includes a patient's name in a script to a provider or agency; the client call is the one exception, because it is the client's own information.

Vocational analysis — case preparation only. Grid rules, transferable-skills questions, occupational-base erosion and cross-examination material are prepared from the written record. Vocational-expert testimony at hearing turns on the hypothetical as actually posed, the expert's own sources and methodology, and context the file does not carry. Nothing here predicts what a vocational expert will say or how an adjudicator will rule. All vocational conclusions require evaluation by a vocational expert and the representative of record. · PCL output for attorney review. Not legal advice. All conclusions require evaluation by a licensed attorney or accredited representative. · Outbound contact is administrative and scheduling only; the AI never discusses case merits or predicts outcomes. · Sample on a synthetic case; no real claimant data. · Precision Case Lens · Beta Build — Pre-Production v0.5

Precision Case Lens

Prospect Guide · Synthetic Case

Cadence and batching

Why a pursuit cannot die quietly, and why a provider never gets six calls in one morning.

What it isoverview

The four callsscripts

Cadence & batchingthe engine

The touch loga week of calls

Position: the engine that decides who gets called when. Cadences are attorney-approved configuration. Deadlines compress them; humans can pause them; nothing skips them.

What the engine does for your practice

A schedule, not a reminder

Each pursuit carries its own next-action date. The day arrives, the call is placed or the fax goes, the outcome is logged, and the next date is set. Nobody has to remember.

Escalation is a state, not a suggestion

Day 30 without receipt escalates to a human. Day 45 escalates to the representative. A broken promise tightens the next interval. An unresolved pursuit cannot fall off the list.

Compression you can defend

The hearing date re-baselines everything to five business days before the hearing. Chases tighten to daily inside two weeks, capped at one call per business day per number, with fax and portal as the second channel.

How it moves your win rate

Records are lost to time, not to refusal. A request that is confirmed on day 3, chased on day 10 and escalated on day 30 arrives. A request that was sent once and forgotten is discovered missing at the pre-hearing sweep. The cadence is the difference, and it runs on every case whether the office is busy or not.

Walk-through in 60 seconds

"Default records profile: send, confirm at day 3, then 10, 17, 24, human at 30, representative at 45."
"Source-statement chase measured backward from the hearing: 45, 30, every three days inside 21, daily inside 14."
"Three Reyes pursuits opened May 6. Here is what the calendar looked like."
"Batching: one call to the hospital covers every open request the firm has there."

Synthetic case. Dates follow the fictional Reyes timeline used across the PCL sample sets.

Cadence profiles and the Reyes calendar

Profiles: attorney-approved, versioned configuration
Hard ceiling: 1 call / business day / phone number / matter
Prospect guide

1.Cadence profiles

Profile	Schedule	Escalation
Records, default	Day 0 send · Day 3 confirm receipt · Day 10 · Day 17 · Day 24 (supervisor) · Day 30 (human) · weekly after	Day 30 human; Day 45 representative. Broken promise tightens the next interval.
RFC / MSS chase	T−45 initial send · T−30 first chase · T−21 every 3 days · T−14 daily	Obstacle reported → representative task same day.
SSA status	Portal pull monthly; phone only when stale. Re-triggered on denial notice, CDR notice, hearing notice.	Decision issued → representative review before any client contact.
Client hearing check-in	T−40 · T−30 · T−15	Scheduling conflict or new records → staff task.

T = hearing date. Every pursuit re-baselines to hearing − 5 business days the moment a hearing date posts, matching the five-day evidence rule.

2.The Reyes calendar

Case development (CD2, May 5) queued three requests. All three opened as pursuits on May 6. Hearing notice received June 29 for September 22.

Date	Pursuit	Action	Outcome
05/06	Records — Dr. Williams	Request faxed (Day 0)	Sent; next action 05/09
05/06	MSS — Dr. Chen	Form and cover letter faxed	Sent; next action 05/09
05/06	MSS — Dr. Rivera	Form and cover letter faxed	Sent; next action 05/09
05/09	All three	Day 3 receipt-confirmation calls	Williams: confirmed, ref LBH-4471, ETA 05/16 · Chen: confirmed, ETA 05/20 · Rivera: confirmed, "two to three weeks"
05/15	Records — Dr. Williams	Records received (87 pp)	Pursuit closed on receipt
05/16	MSS — Dr. Chen	Day 10 chase	Received 05/18; closed
05/14	MSS — Dr. Rivera	Staff member called the office personally	Human touch logged; AI touch suppressed 1 business day; promise 05/28 → verify 06/01
05/30	MSS — Dr. Rivera	Statement received (8 pp)	Closed before verification date
06/29	All open pursuits	Hearing notice: 09/22	Re-baselined to 09/15; check-ins scheduled 08/13, 08/23, 09/07
08/13	Client check-in	T−40 call	Date confirmed; no new records
08/23	Client check-in	T−30 call	New record reported: Dr. Williams visit 08/19 → staff task, records pursuit opened, Day 0 that afternoon

3.Custodian batching

Every pursuit pointing at the same phone number, across every matter in the firm, shares one daily call budget. Six requests to one hospital records line become one call, ordered by deadline proximity, up to eight items per call. Overflow rolls to the next business day or to fax. The provider hears from the firm once, with reference numbers ready, and the firm stays under frequency caps.

St. Mary's Hospital — HIM line, 05/09	Reference	Deadline proximity
Reyes (this case) — ER and imaging	PCL-2026-0412	No hearing set
Matter B — ER records	PCL-2026-0398	Hearing in 33 days
Matter C — imaging	PCL-2026-0377	Hearing in 51 days
One call, three items, ordered B · C · Reyes. Three reference numbers captured; three next-action dates set.

4.Humans and the machine

A staff call to a provider is logged as a touch with a one-minute voice note or a one-click action, and suppresses the AI touch for that target for one business day.
A human-negotiated promise resets the next action to promise plus two business days.
Staff can check a pursuit out; the AI waits until it is released or a resume date passes.
Every morning, a briefing: what needs a decision, what arrived yesterday, what is overdue, today's planned calls with a window to intercept any of them, and broken promises.

Vocational analysis — case preparation only. Grid rules, transferable-skills questions, occupational-base erosion and cross-examination material are prepared from the written record. Vocational-expert testimony at hearing turns on the hypothetical as actually posed, the expert's own sources and methodology, and context the file does not carry. Nothing here predicts what a vocational expert will say or how an adjudicator will rule. All vocational conclusions require evaluation by a vocational expert and the representative of record. · PCL output for attorney review. Not legal advice. All conclusions require evaluation by a licensed attorney or accredited representative. · Outbound contact is administrative and scheduling only. · Sample on a synthetic case; no real claimant data. · Precision Case Lens · Beta Build — Pre-Production v0.5

Precision Case Lens

Sample Output · Synthetic Case

The touch log, and the red lines

A week of calls as the firm sees it, and the twelve things the receptionist will never do.

What it isoverview

The four callsscripts

Cadence & batchingthe engine

The touch loga week of calls

Position: what you see afterward. Every attempt, every promise, every verification, in a chronology built to stand up as an exhibit when a provider or an agency delayed.

What the log does for your practice

Proof of diligence

Date, target, call type, who answered, what they said, what they promised, when the promise gets verified. Hold time on agency calls, logged as delay evidence.

Broken promises, counted

A promise that passes its verification date unmet is a broken promise. It tightens the next interval and it appears in the morning briefing. Providers with a pattern get a tighter default cadence next time.

Nothing to clean up before filing

No patient detail in a voicemail, no case discussion with anyone unverified, no adverse decision relayed by a machine. The log can go into the record as it is.

How it moves your win rate

When a treating source ignores three requests, the log is the good-cause showing. When an agency holds a file for months, the log is the timeline. When the five-day window is at issue, the log shows the sweep happened. Diligence that is documented is diligence that counts.

Walk-through in 60 seconds

"Seven touches in one week on the Reyes case. Read across a row: who, what, promise, verify-by."
"One human call on the 14th. The AI stepped back for a day. That is by design."
"Now the red lines. Twelve things it will never do, each one enforced in the script structure, not left to the model."

Synthetic case. Every name, number and outcome is fictional.

Touch log · Reyes, Maria Elena · PCL-2026-0412

Week of May 6–14, 2026
7 touches · 3 pursuits · 1 human touch
Chronology export

1.Chronology

Date	Target	Type	Outcome	Promise · verify by
05/06 09:12	Lakeside Behavioral (Williams)	Fax, Day 0	Records request transmitted; fax confirmation 4471.	—
05/06 09:14	Northgate Orthopedics (Chen)	Fax, Day 0	MSS form and cover letter transmitted.	—
05/06 09:15	Rivera Family Medicine	Fax, Day 0	MSS form and cover letter transmitted.	—
05/09 10:40	Lakeside Behavioral, HIM	AI call, Day 3	Role confirmed (HIM clerk, first name captured). Receipt confirmed. Facility ref LBH-4471. No fee.	ETA 05/16 · verify 05/20
05/09 10:52	Northgate Orthopedics, front desk	AI call, Day 3	Role confirmed. Form on the doctor's desk. Return by fax.	ETA 05/20 · verify 05/22
05/09 11:05	Rivera Family Medicine	AI call, Day 3	Voicemail (zero patient detail). Retry scheduled next business day.	—
05/12 09:30	Rivera Family Medicine	AI call, retry	Role confirmed. Form received. "Two to three weeks; the doctor does these on Fridays."	ETA 05/29 · verify 06/02
05/14 15:20	Rivera Family Medicine	Human touch (staff)	Paralegal spoke with office manager; asked for priority. AI touch suppressed until 05/15.	Promise 05/28 · verify 06/01

Outcomes after this week, for continuity with the case-development sample: Williams records received 05/15; Chen statement received 05/18; Rivera statement received 05/30, before its verification date.

2.Twelve red lines

#	The receptionist will never	How it is enforced
1	Give legal advice, predict an outcome, or say whether someone "has a case."	Not in any script; the capture lists contain no opinion fields.
2	State an exact deadline date unless the representative has confirmed it.	Deadline objects carry an ESTIMATED or CONFIRMED state; only CONFIRMED dates can be spoken.
3	Deny being an AI, or claim to be a person, an attorney or agency staff.	Disclosure is the first line of every script.
4	Speak a patient identifier before the callee's role and entity are confirmed.	Identity confirmation block precedes the status block in every provider script.
5	Leave patient detail in a voicemail or with an unverified third party.	Voicemail scripts carry firm name, reference number and call-back only.
6	Discuss the clinical content of a form with a provider.	Obstacles route to the representative's task queue.
7	Relay an adverse decision to a client before a human releases it.	"Decision issued" routes to the representative; no content is read.
8	Discuss case merits, work capacity or activities with anyone.	Client script is limited to the hearing date and new records.
9	Continue after "stop calling" or "don't record me."	Required fallback executes; the pursuit moves to fax or staff.
10	Act on instructions embedded in what a callee says, or trust a new fax number or address heard on a call.	Learned destinations require out-of-band verification before anything is sent.
11	Exceed one call per business day to the same number on the same matter.	Hard ceiling in the cadence engine; second channel is fax or portal.
12	Delete or alter a call record.	Touch log is append-only.

3.What is and is not live

Live today: script generation for all four call types inside each case, cadence and hearing-date compression, custodian batching logic. Live once a firm's voice and workflow credentials are configured: dialing, the touch log fed by real calls, the morning briefing. Roadmap, specified but not product: the inbound reception engine, insurance and lien pursuits, and mail ingestion described in the master design.

Vocational analysis — case preparation only. Grid rules, transferable-skills questions, occupational-base erosion and cross-examination material are prepared from the written record. Vocational-expert testimony at hearing turns on the hypothetical as actually posed, the expert's own sources and methodology, and context the file does not carry. Nothing here predicts what a vocational expert will say or how an adjudicator will rule. All vocational conclusions require evaluation by a vocational expert and the representative of record. · PCL output for attorney review. Not legal advice. All conclusions require evaluation by a licensed attorney or accredited representative. · Outbound contact is administrative and scheduling only; the AI never discusses case merits or predicts outcomes. · Sample on a synthetic case; no real claimant data. · Precision Case Lens · Beta Build — Pre-Production v0.5