Perspective added GPT Live 1 to its opt in Live (Beta) voice conversations, using full duplex audio so the agent keeps listening while it speaks and can stop to follow a participant's correction; answers stay paired with audio for playback. Live (Beta) also adds 12 voices, and GPT-6 Sol became the default model for analysis sessions and scheduled insights. The existing Realtime voice engine remains the default unless an owner or admin switches.
P
Perspective AI
Perspective AI replaces static intake forms with adaptive conversations led by AI, marketed as Intelligent Intake and positioned as structured capture rather than a chatbot. It asks follow up questions on vague answers, adapts to responses, captures urgency and the reasoning behind an inquiry, and turns answers into the same fields a form would collect while keeping the context a form loses. The firm describes who it wants to qualify and what determines fit, and the system builds the conversation.
Questions can then be adjusted, routing rules set for strong and weak fits, branding matched and the full conversation previewed before launch. The agent runs as a website widget, popup, email link or standalone page, and completed conversations arrive as structured summaries in an inbox, CRM or Slack. Named legal uses are qualifying personal injury, family law, estate planning and immigration inquiries before a paralegal makes contact.
The vendor says the platform captures the parties and matter details needed to flag conflicts, and that staff then confirm against the firm's own records. The product is horizontal, also serving healthcare, financial advisory, insurance, internal requests, education and real estate. A free tier with no code templates is offered.
Perspective AI, head to head
Side by side on the same 15 capability axes and 12 legal signals: where the two part company, and what neither one publishes.
Alternatives to Perspective AI
Vendors in the same categories as Perspective AI whose graded profiles look most alike, with a line on what each product does.
Similar is not the same, so check that each one does the job you need. No vendor pays for placement.
- IIntakerIntaker is a cloud intake and client relationship management platform for law firms, built around website chat that qualifies leads around the clock.
- CCasefloodCaseflood is an AI intake platform, sold with an advisory engagement, for plaintiff and consumer law firms that run their own intake teams.
- KKalindaKalinda is an AI intake agent for personal injury law firms from a San Francisco company founded by Sayan and Sohil Bhatia, two former AI researchers, and part of Y Combinator's Summer 2025 batch.
- LLawDroidLawDroid is an AI legal automation platform for law firms, legal aid organizations, courts and government agencies, operating since 2016.
- LLawmaticsLawmatics is a client relationship management and marketing automation platform built for US law firms, founded in 2017 by a team including practicing attorneys and a cofounder who…
- SSimplyConvertSimplyConvert is an intake, client relationship and case management platform for plaintiff and mass tort firms, founded by a mass tort lawyer, covering first contact through intake, filing…
Ordered by how closely the graded profiles match across the 15 capability axes, inside the same categories. See how each axis is graded in the methodology.
Capability grades
All 15 axes, graded from public sources on the date shown. Hover a grade to see what the letter means on that axis.
AI Centrality
How much of the product is actually AI. Whether the machine learning is the mechanism the buyer is paying for or a feature layered onto conventional software, and whether the vendor is specific about which is which.
The model is the entire product. Adaptive conversation, follow up on vague answers and extraction that turns unstructured answers into structured fields are what the vendor sells. Remove the model and nothing remains, because the thing being replaced is the form. Perspective AI is a horizontal intake platform serving healthcare, financial services, insurance, education, real estate and internal operations as well as legal.
Its legal offering is specific: a dedicated legal use case names personal injury, family law, estate planning and immigration qualification, the vendor publishes an analysis of legal intake software that places itself in that market, and it describes capturing the parties and matter details needed to flag conflicts. Legal is one of several verticals rather than the company's center of gravity.
Citation Accuracy and Hallucination Disclosure
Whether the vendor publishes measured accuracy on citations and assertions, grounds output to primary sources, and says plainly what its system does when it does not know. Legal has a documented public record of fabricated citations reaching filed briefs, so an untested claim of accuracy is not evidence.
Nothing published, and the extraction claim is the thing that needed measuring. The vendor's central technical proposition is schema aligned data extraction, structuring unstructured conversational answers into defined fields, and it markets the output as validated structured outputs on which downstream automation triggers rather than guesswork from dropdowns. Extraction accuracy is directly measurable and no figure is published: no field level accuracy, no error rate, no evaluation, no statement of what happens when a conversational answer is ambiguous and the schema requires a value.
The word validated is doing significant work in the marketing and nothing states what validation means or who performs it. The consequence is specific: a misextracted field in legal intake produces a structured summary that reads as authoritative and routes a matter incorrectly, and the conversation it came from is the only place the error is visible.
Autonomy and Oversight Model
What the system decides on its own, what a lawyer must approve, and whether the vendor documents where the review point sits. A tool that drafts under review and a tool that files without one are different products and different risks.
Two published mechanisms put a person at the right points. First, configuration can be reviewed before deployment: the firm sets routing rules for strong and weak fits and can preview the full conversation before it goes live, so a lawyer can inspect exactly what the system will say to a prospective client rather than finding out afterward. Second, on conflicts, the vendor states that the platform captures the parties and matter details during the conversation and routes the summary to staff who confirm against the firm's own records.
That is an explicit statement that the machine gathers and a person decides on the one question where an automated determination would be indefensible. The qualification decision itself is autonomous. Routing strong and weak fits happens without a person, and nothing states what a weak fit outcome does to the inquiry or whether a borderline case is escalated.
Operational and Outcome Evidence
Named, dated evidence that the product works in production at real firms or legal departments. Case studies with figures and identified customers count. Unattributed testimonials and launch announcements do not.
Nothing located. No customer is named in any vertical, and no case study, usage figure, funding announcement, independent analyst placement, award or third party review of this vendor was found. The evidence is entirely self authored, though large in volume: an extensive blog publishing category analysis, buyer frameworks and comparative rankings across legal intake, insurance, education, real estate and internal request management, in several of which the vendor ranks itself first. Rankings a vendor publishes about itself are marketing rather than evidence.
Privilege and Confidentiality Posture
How client confidences are handled: attorney client privilege and work product treatment, segregation of one client matter from another, whether client data trains any model, and what the vendor commits to in writing rather than in marketing.
Nothing located. No confidentiality statement, no encryption reference, no data handling description and no treatment of privilege or prospective client confidences was found. The exposure is heightened by the product's own design proposition: the vendor argues that forms lose the context that matters and that its conversations capture the why behind each inquiry, which means the system is built to elicit more sensitive detail from a prospective client than a form would, in named practice areas including family law and immigration.
It also operates across healthcare, where the same conversations capture presenting concerns and care needs. A platform designed to extract fuller disclosure publishes nothing about how that disclosure is protected.
UPL and Professional Responsibility Posture
Whether the vendor is clear that it supplies a tool rather than legal advice, who its audience is, and how it addresses unauthorized practice of law, competence and supervision duties, and jurisdiction limits. ABA Formal Opinion 512 is the reference point. Where the advice line is not the duty a product raises, the axis is read through the nearest professional duty it does raise: judicial conduct rules and the reviewing duty for products sold only to courts, and the duty to bill for time actually spent for products that draft time entries.
Not located. The system holds an adaptive conversation with a prospective client, asks follow up questions about their legal situation, assesses fit against the firm's criteria and routes on that basis, all before any lawyer is involved. The vendor's own framing is that this happens before the paralegal picks up the phone. That is an automated system holding a substantive discussion about a person's legal problem and reaching a conclusion about it.
Nothing published states that the conversation is not legal advice, describes what the agent may say when a prospective client asks a substantive legal question during the conversation, or discloses to the person that they are speaking to an AI. The interaction is conversational and adaptive rather than form based.
AI Governance and Bias Disclosure
Published governance over model behavior: who owns it inside the vendor, what is tested before release, and what is disclosed about disparate output across matter types, parties, or populations.
Nothing is published on governance. The platform qualifies inquiries against fit criteria the firm defines and routes strong fits differently from weak ones, so it decides which people reach a professional. That includes immigration and family law, where the people being assessed are often in difficulty and have few alternatives. The adaptive design adds to the risk. Because the conversation branches on responses, two people in similar situations can be asked different questions and produce different summaries depending on how articulately they answer early, and nothing indicates whether performance across different groups of respondents has been examined.
No AI policy, model card, bias or fairness testing, evaluation, monitoring, governance body, ISO 42001 or EU AI Act positioning is published.
AI Safety and Data Stewardship
Retention, deletion, access control, and what happens to prompts and documents after they are processed. Whether the vendor states its subprocessors and its incident practice, or leaves the buyer to assume.
No stewardship position is published. Nothing states whether intake conversations, extracted data or routing outcomes are used to train or improve models, no retention period is published, and no deletion right is described. The horizontal footprint widens the omission. The same platform captures presenting concerns and care needs in healthcare intake and financial position in wealth management qualification, so one undisclosed training and retention posture covers health information, financial information and legal matter details together.
The free tier with no code setup adds to this, since anyone can deploy an agent collecting such material with no published statement about where it goes.
AI Liability and Recourse
What the vendor stands behind contractually when its output is wrong. Indemnities, caps, carve outs, insurance, and whether any of it is published or only reachable through a negotiated agreement.
No published position is published on liability for AI output, warranty, service levels or remedy. Two exposures are specific to this product. A misextraction produces a structured summary that a firm acts on without seeing the conversation behind it, and the vendor markets automation triggered by those outputs, so an error spreads into routing and workflow before anyone reads it. And a person qualified as a weak fit is routed away without anyone learning it happened.
The vendor's own marketing frames the problem it solves as teams moving forward on incomplete information and making weaker decisions, which describes the risk its extraction would create if wrong, and no position addresses it.
Practice Systems Integration Depth
How deeply the product reaches into the systems legal work already lives in: document management such as iManage and NetDocuments, Word and Outlook, contract lifecycle management, matter management, e-billing, and court filing systems.
Destinations are named by type and no system is named individually. Structured summaries go to an inbox, a CRM or Slack, and the agent can run as a website widget, popup, email link or standalone page, so both the output path and the input surface are described. Slack is the only product named. What a law firm would check is absent. No practice management system is named, there is no Clio, MyCase or Filevine integration or case management connector, and no API documentation is published.
A firm cannot confirm that its own CRM is a supported destination or that intake will reach its matter records. A generic CRM destination describes a category rather than an integration.
Deployment Model and Data Residency
Where the software runs and where the data sits. Multi tenant cloud, single tenant, private deployment, on premises, and whether region of residence is a published option or an enterprise conversation.
Nothing located. No hosting provider is named, no region or residency commitment is published, and no deployment or tenancy options are described beyond the places the intake agent can be embedded, which is a placement question rather than an infrastructure one. The gap is wider because the same platform is marketed for healthcare patient intake and financial services qualification, so health and financial data flow through infrastructure whose location is unstated, and both carry obligations that turn on location.
Security Certifications and Trust Center
Independent attestation a buyer can pull without a sales call: SOC 2, ISO 27001, penetration test summaries, a trust center with current reports and named scope rather than a badge image.
No certification, attestation, trust center or security page is published. No SOC 2 of either type, ISO 27001, HIPAA statement, named auditor, penetration testing partner or encryption statement was found. The material is absent rather than gated. The HIPAA omission is the notable one. The vendor markets healthcare patient intake that captures history, urgency and care needs, which is protected health information, and publishes no HIPAA posture, no offer of a business associate agreement and no security credential of any kind.
Model Supply Chain Disclosure
Which models sit underneath, whose they are, where they run, and whether the vendor commits to telling customers when that changes. A legal buyer inherits every dependency it cannot see.
Nothing located. No foundation model provider, model family or version is named, no distinction is drawn between proprietary and third party models, and no subprocessor list was found. The absence is conspicuous against the vendor's own published expertise: it writes detailed comparative analysis of the conversational AI category, classifying competitors by architecture and distinguishing AI native platforms from chat skins on form builders, so it demonstrably understands that the underlying architecture matters to a buyer, and it discloses nothing about its own.
A platform conducting adaptive conversations and performing schema aligned extraction is running one or more language models supplied by someone, and no party in that chain can be identified from public material.
Commercial Transparency
Whether a buyer can learn what this costs without entering a sales process: published rates, the unit being charged, what sits behind an enterprise tier, and what implementation adds.
A free entry point is published and no price is. The vendor offers a free tier with no code setup and lead capture agent templates, so a buyer can deploy and evaluate the product without a sales conversation. Nothing above it is published. No price, range, tier structure or unit of charge is published, and nothing says whether pricing runs per conversation, per completed intake, per agent, per seat or by volume, which are very different economics as inquiry volume grows.
No figures from other sources are published either. The barrier to trying is low and the cost of adopting is undisclosed.
Firm and Practice Coverage
Who the product is actually built for. AmLaw, midlaw, small firm and solo, in house departments, government and courts, and which practice areas are supported rather than merely claimed.
Practice areas are named and nothing bounds them. Legal coverage names four practice areas: personal injury, family law, estate planning and immigration. Coverage extends well beyond legal into healthcare patient intake, financial advisory and wealth management, insurance first notice of loss and quoting, internal request management, education and real estate, with use case material for each. Firm coverage is not described.
There is no firm size, no jurisdiction and no statement of who the product is not for, and nothing says whether the legal configuration differs materially from the healthcare or insurance one or is the same engine pointed at different criteria. The breadth cuts both ways: a platform serving seven verticals is unlikely to carry deep legal knowledge in any one of them, and nothing published shows what the legal version knows that the generic one does not.
1 public document
The public pages on file for Perspective AI, with the recorded signals each one supports and the date it was last read. Open any of them and check the reading against the record.
-
Client Data in Training
Read Aug 29, 2026
Tracked changes at Perspective AI
Perspective changed how its Form Data extraction treats questions a participant never answered: missing text, number and yes or no fields now stay empty instead of being filled with an empty string, 0 or No. A conversation that ends before qualification is decided is no longer filed as disqualified. The same release makes GPT-6 Sol the default model for agent design, with GPT-6 Luna also selectable.
Legal Signals
What each signal meansA signal records what public sources say on the date shown. It is not a grade and it is not a recommendation. Where a signal reads Not addressed, it means the index did not locate the material in public sources on that date, which is a statement about disclosure rather than about the product.
Client Data in Training
Can material a lawyer puts into this product be used to train a model?
A published agreement or policy exists and none of it addresses the question either way, or the document that would answer it could not be read and the summary names the retrieval limit. The summary states which shape the silence takes: an improvement right granted that never names training, or no improvement right granted at all.
Silent, and the quoted design goal is why the silence carries weight. The vendor's stated proposition is that forms lose the context that matters and that its conversations capture the reasoning behind an inquiry, so the platform is deliberately built to elicit fuller and more personal disclosure than a form would. No statement in either direction was located on whether those conversations, the structured data extracted from them, or routing outcomes are used to train or improve models, and no retention or deletion position exists.
The horizontal footprint widens the exposure: the same undisclosed posture covers legal matter details, healthcare presenting concerns and care needs, and financial position captured in wealth management qualification. The people in these conversations are prospective clients and patients who are not the customer and cannot consent, object or ask. Recorded as silent, not as a negative commitment. Checked the home page, the Intelligent Intake page, the blog material and the site navigation on 29 Aug 2026.
Prompt and Output Retention
How long does the product keep what a lawyer typed, and can that be set to zero?
No located public material states how long prompts and outputs are retained.
Not addressed. No retention period is published for intake conversations, extracted structured data, generated summaries or routing decisions, and no deletion right is described. Retention is implied by the product's own workflow, since structured summaries are routed onward to an inbox, CRM or Slack while the underlying conversation is the only place the extraction can be checked against, and nothing states whether the vendor retains that conversation, for how long, or whether a firm can purge records of people who never became clients. Checked the home page, the Intelligent Intake page and the blog material on 29 Aug 2026.
Ethical Walls and Matter Segregation
Does retrieval respect the firm’s ethical walls, or can the model read across them?
Segregation is asserted in public materials with no published detail on how it is enforced.
Separation is claimed and not documented, though the claim is well shaped. The vendor states that the platform captures the parties and matter details needed to flag conflicts during the intake conversation, then routes the structured summary to staff who confirm against the firm's own records. That is the right division of labor: the machine gathers the facts a conflicts check needs, and a person performs the check against the authoritative record, rather than the system asserting a determination it cannot make.
Nothing further is documented. No statement covers what happens to intake data between capture and confirmation, whether it is held back pending the check or visible across the firm at once, and no permission or segregation model is described within a firm or between customers.
Third Party Request and Subpoena Notice
If someone subpoenas the vendor for a firm’s data, does the firm hear about it first?
No located term or policy addresses third party requests for customer data.
Not addressed. No government or law enforcement request clause, no commitment to notify a customer before producing their data, and no transparency report was located. The material held is broad because of the horizontal footprint: legal matter details in immigration and family law, healthcare presenting concerns and financial position are all captured through the same platform under a single undisclosed posture. Nothing published addresses requests to the vendor from any direction. Checked the home page, the Intelligent Intake page, the blog material and the site navigation on 29 Aug 2026.
Primary Law Corpus Provenance
Where does the law in this product come from, and does the vendor have the right to use it?
No located public material identifies the corpus behind the product’s answers.
Not addressed, and inapplicable in the usual sense with a live residue. The platform has no primary law corpus: intake conversations run against criteria the firm defines, so the substantive content is customer supplied. The residue is what the conversational and extraction models were built on. Conducting an adaptive interview that follows up on vague answers and mapping free text into a schema are both learned behaviors, and nothing published states what corpus supports either, whether any of it is domain specific to legal, healthcare or insurance, or whether prior customer conversations contribute.
The vendor states that configuring an agent requires no script, which means the conversational competence comes from the model rather than from customer authored content, making the provenance question more rather than less material. Checked the Intelligent Intake page, the home page and the blog on 29 Aug 2026.
Good Law Verification
Does the product tell you when the authority it just cited has been overruled?
No located public material addresses whether authority is checked for subsequent history.
Not addressed, and not applicable on the facts. Perspective AI holds intake conversations, extracts structured data and routes summaries. It produces no legal research or citation to authority, so there is nothing for a citator to check. This is a fact about the product's scope rather than a disclosure failure. The product's legal role ends at qualifying an inquiry and handing a summary to staff, before any research or advice begins. Checked the Intelligent Intake page, the home page and the legal use case material on 29 Aug 2026.
Refusal and Uncertainty Behavior
What does the product do when the answer is not in the corpus?
No located public material addresses what the product does when it cannot ground an answer.
Not addressed, and the extraction layer is where it matters. The vendor states that the system follows up on vague answers, which is a real uncertainty behavior in the conversation and the closest thing published. The harder case is not described: what happens when follow up fails and a required field still has no supportable value. Nothing states whether the field is left empty, filled with a best guess, or flagged as uncertain in the summary a firm acts on.
The vendor markets automation triggered by validated structured outputs, so an unflagged guess would flow into routing without a person seeing the conversation it came from. Nothing says whether the agent will decline to qualify, or escalate a case it cannot resolve, rather than routing it as a weak fit. Checked the home page, the Intelligent Intake page and the blog material on 29 Aug 2026.
Fabricated Citation Record
Does a public court record exist addressing fabricated or hallucinated legal citations in output from this product?
No court order, opinion or disciplinary record addressing fabricated or hallucinated legal citations produced by this product has been located as of the date shown. This is a statement about the public record on that one subject, not a finding about the product, and this signal is not a litigation history.
None located, with the instrument named. General web searches combining the vendor and product names with court, order, sanction and complaint terms returned nothing on 29 Aug 2026, and no named docket database, court record tracker or state consumer protection register was searched. Recorded as a statement about what this search found, not as a clearance. The exposure shape is not fabricated citations, since no legal authority is generated: the analogous adverse finding would be a complaint arising from an automated intake conversation, a misextracted fact that caused a matter to be misrouted or missed, or a disclosure issue in the healthcare configuration, none of which a citation focused search would surface.
Bar Guidance Alignment
Has the vendor engaged in public with the ethics opinions its buyers are bound by?
No located public material engages with bar or ethics guidance.
Not addressed. No named ethics opinion, ABA Formal Opinion 512, state bar guidance or engagement with professional conduct rules was located. The vendor publishes a substantial analytical library on conversational intake, including a comparison of legal intake platforms and buyer frameworks aimed at firms. It addresses the legal market analytically and reaches none of the rules governing communications with prospective clients, automated advice or advertising.
Those rules govern exactly the conversations the product holds. Checked the blog index, the legal intake comparison material, the home page and the Intelligent Intake page on 29 Aug 2026.
Billing and Fee Posture
Does the vendor address what happens to the bill when the work takes an hour instead of six?
The product does not touch a fee between a lawyer and a client. It operates before an engagement exists, or it is bought by a team that bills no client for the work. Savings claims aimed at the buyer’s own cost are recorded in the summary and do not make the row a savings claim, because no client bill is in the loop.
The product operates before an engagement exists, and no savings claim is published. No time saving, conversion improvement or return on investment figure attributable to this vendor's customers was located. The vendor does publish industry figures in its analytical content, including form completion rates of 20 to 40 percent and deflection and cycle time improvements attributed to insurance carriers generally, but those are category research rather than product outcomes.
Nothing appears on the client's side. There is no position on whether an automated intake interaction is disclosed to the person as handled by a machine, and no record showing which part of an intake was automated. Checked the home page, the Intelligent Intake page and the blog material on 29 Aug 2026.
Outside Counsel Guideline Readiness
Can a firm get this vendor through a client’s AI clause without a bespoke negotiation?
No located public material supports a client side disclosure obligation.
Not addressed. No trust center, security page, named certification, subprocessor list, named model provider, data processing agreement or route to request documentation was located, so a firm has nothing to forward and nowhere to point a client. The gap reaches beyond legal. The same platform is marketed for healthcare patient intake with no HIPAA posture or business associate agreement published, so a medical practice would face the same problem. Checked the home page, the Intelligent Intake page, the blog material and the site navigation on 29 Aug 2026.
Court Disclosure Support
If a judge’s standing order requires an AI disclosure, can the product produce one?
No located public material addresses court disclosure or verification certification.
Not addressed. Nothing indicates that output records which model produced it, no human verification record is captured, and no export or audit artifact was located. The product does create a lasting artifact in the ordinary course: the structured summary routed to an inbox, CRM or Slack. That is a record of what the system concluded, not of what was said, and nothing states whether the conversation transcript is kept alongside it or available to the firm.
That distinction is the whole question. If a prospective client later disputes what an intake agent asked or told them, or a firm needs to show why a matter was routed as it was, the summary is the machine's account and the conversation is the evidence. The forum here is a bar complaint, a fee dispute or a malpractice claim rather than a filing. Checked the home page, the Intelligent Intake page and the blog material on 29 Aug 2026.