Industry · Law firms
Be the firm that took the call.
Capture every new-client call — at midnight, on a weekend, while you're in court. UPL-safe intake, conflict identifiers routed to your firm, and never legal advice.
Not a law firm. We handle intake only — your attorneys review every summary. Carolinas Dev does not provide legal advice or legal services.
Personal-injury intake · Hit-and-run
- CallerAnya R.
- MatterAuto · hit-and-run
- Opposing partyunknown driver
- UrgencyHIGH
Routed to your on-call partner
Discipline
Designed around ABA Model Rules 5.5 and 5.3 — fact capture, never legal judgment. The Front-Desk Leak is the most expensive line item a firm never sees.
How it answers
UPL-safe intake, end to end.
Most after-hours calls go to voicemail. Most callers don't leave one. We answer every call, run your approved intake script, and route the structured summary to your firm — while the caller is still on the line.
Intake summary · routing
- Caller namecaptured
- Matter typecaptured
- Opposing partycaptured
- Urgency triagecaptured
- Case evaluationnever
- Fee quotenever
- Legal advicenever
-
24/7 intake, first ring
Every new-client call answered live — nights, weekends, holidays. No voicemail.
-
UPL-safe by design
Fact capture only. No advice, no fees quoted, no case evaluation — ever.
-
Conflict identifiers
Opposing party, matter type, key dates — routed to your firm for the check.
Configured per area
A PI midnight crash call is not a family-law consultation.
The script changes by matter type — fields captured, urgency triggers, after-hours routing — all configured with your firm before any live call. Set once, then your script is your script.
Personal injury
Family law
Criminal defense
Immigration
of incoming small-business calls are answered by a live person. The rest go to voicemail or ring out — and most callers don't try again.
Source: 411 Locals study, 2024
From ring to handoff
From greeting to calendar — in one call.
Greet the caller. Capture facts. Identify conflicts. Book the consultation into your calendar. Route a structured summary to your firm — typically within minutes of the call ending.
What it does
The calls that decide your caseload.
-
Intake & conflict capture
Caller details, matter type, opposing-party names — captured to your firm's specification.
-
Urgency routing
True emergencies — arrests, PI ER calls — forwarded to your on-call line. Everything else routed by your rules.
-
Consultation booking
Books directly into your calendar — Cal.com, Google, Outlook, or your case-management system.
How it sounds
Calm under panic. Compassion on script. Facts only.
PI clients call in pain. Family-law clients call in tears. Criminal-defense clients call from jail. The intake stays calm, captures what matters, and routes the right thing to your firm — without inventing answers.
-
Sub-second response
Voice cadence designed for first-ring pickup — no awkward latency that signals 'robot'.
-
Speaks any language
Native-quality voice in any language combination your callers use. Pick the pair, we configure it.
-
Calibrated tone
Patient / concerned / steady — applied to the call type, not bolted on as a feature.
What it never does
UPL-safe by default. Reviewed before any live call.
No advice, no fee quotes, no case evaluation — ever. Compliance scripts and routing reviewed and approved before any live call. Data handled with US-based storage and confidential routing to your firm only.
ABA Model Rule 5.5 + 5.3
Capture only. Lawyer supervises agent per Rule 5.3 Comment [3].
US-based, confidential
Intake summaries routed only to your firm. No third-party sharing.
Every call, transcripted
Full call transcripts retained and searchable for compliance review.
Get started
Two ways to begin.
On the web
Pick a time. Demo on a call.
A 30-minute call to walk through your intake script, hear the AI handle a sample PI or family-law call, and lock pricing for your volume.
Talk to sales
Bigger firm? More questions?
For multi-attorney firms, multi-office setups, or specialty practices (mass tort, class action), email directly and we'll line up the right conversation.
Common questions about legal intake
My clients expect a human on the other end. Won't they hate an AI?
Three things to know. First, the comparison isn't AI vs. live receptionist — a 2024 Clio study found only 40% of law firms answered an incoming new-client call, with 48% essentially unreachable by phone. In practice the AI replaces voicemail, not a person, and the prospective client gets an immediate, on-brand intake instead of an unreturned message. Second, the AI discloses it's automated in the first sentence — callers don't feel deceived; what people react badly to is AI pretending to be human, not AI being honest. Third, you can test it yourself: tap "Ring the front desk" on any page and listen. Thirty seconds of a real call tells you more than any pitch can.
Do answering services give legal advice?
No. Carolinas Dev captures caller information — name, matter type, contact details, and conflict identifiers — and routes a summary to your firm. It never gives legal advice, quotes fees, or evaluates a case. That interpretation stays with your attorneys.
Is an answering service UPL-compliant for law firms?
Yes, when configured correctly. Carolinas Dev captures intake details only and does not offer legal opinions, quote fees, or advise callers on their rights — the line ABA Model Rule 5.5 and its state-level equivalents draw between intake and the practice of law.
How does legal intake work with an answering service?
A caller reaches your firm's number, which forwards to Carolinas Dev 24/7. We greet them as your receptionist, ask your intake questions, capture conflict identifiers, and route a structured summary to your firm — typically within minutes of the call ending.
Can a virtual receptionist run conflict checks?
We capture the conflict identifiers your firm needs — opposing-party names, matter type, relevant dates — and route them to you. Your attorneys or staff run the actual conflict check using your case-management system. We don't access or query your conflict database.