Intake & client communication
Answering Legal
U.S.-based virtual receptionists for law firms.
Last observed 42 days ago. Records are treated as awaiting re-check after ninety days.
Only some data-handling statements were found. The checked sources did not contain all three of a confidentiality, training, and data-location statement. That is a gap in what the vendor publishes, not a finding about the product. Ask the vendor directly, or weigh it however your firm sees fit.
Editorial assessment
U.S.-based virtual receptionists who answer for law firms, with a published price.
This section is the CounselAtlas editorial desk’s own reading of the dated facts below. It is not a vendor statement, not a rating, and not a recommendation. Every product fact it rests on is recorded with a source in the record.
What it is
A legal answering service staffed by U.S.-based virtual receptionists, with an AI intake chatbot alongside the human service. It publishes pricing and offers a free trial.
What it is not
It is not a CRM or practice-management system. It answers and screens calls rather than managing the client relationship afterward.
Who it tends to fit
- Solo and small firms that cannot staff a receptionist
- Firms that want calls answered by a person rather than an automated system
- Firms that want to try the service before committing
Who it tends not to fit
- Firms that want an AI-only intake product at lower cost
- Firms that need intake data to flow automatically into a CRM
- Firms outside the United States, given the U.S.-based staffing model
What to ask before you buy
- What is the per-minute or per-call rate, and what counts toward it?
- What does the receptionist do with a caller whose question needs a lawyer?
- How does call information reach my firm, and in what format?
- What does the AI chatbot do differently from the human receptionists?
Limits in the record
- The checked pages state that receptionists are U.S.-based and trained but do not publish a data-handling statement.
- Pricing is usage-based, so the monthly cost depends on call volume.
- The product answers calls; it does not manage the client relationship afterward.
How it sits in Intake & client communication
This competes with Ruby, Smith.ai, and LEX Reception on the same job. Its differentiator in the record is the combination of U.S.-based human receptionists and an AI chatbot in one service.
Reading the vendor’s wording
The vendor states that its receptionists are U.S.-based and highly trained. That describes staffing rather than data handling. The checked pages do not publish a confidentiality, training, or data-location statement, so a firm should ask how call information and caller details are stored.
How to evaluate it in a trial
- Confirm the per-minute or per-call rate and what counts toward it.
- Test how the receptionist handles a caller whose question needs a lawyer.
- Check how call information reaches your firm and whether it can flow into your CRM.
- Ask where caller data is stored and how long it is kept.
What adopting it costs
The switching cost is the phone number and the intake script. A firm changing answering services has to redirect its number and retrain the new service on its screening questions.
Closest alternative
LEX Reception — The closest alternative. Both are legal answering services with published pricing; the choice usually turns on call handling and contract terms rather than on features.
The record
Everything below is a dated observation from the vendor’s own published material. Each line links to the page it came from so you can confirm it yourself.
What we verified
- Vendor
- Answering Legal. Observed September 21, 2026 · Vendor page ↗
- Price path
- Public price: Vendor publishes a pricing page. Observed September 21, 2026 · Source ↗
- What it does
- General practice. Answering Legal presents U.S.-based virtual receptionists and an AI intake chatbot for law firms. Observed September 21, 2026 · Source ↗
- Firm-size scope
- Not stated. Observed September 21, 2026 · Checked page ↗
- Connections
- Not stated. Observed September 21, 2026 · Checked page ↗
- Data location
- Not stated. Observed September 21, 2026 · Source ↗