Oregon Formal Opinion 2026-208: AI Intake for Attorneys
Oregon Formal Opinion 2026-208 allows AI intake, with conditions, for chat and voice receptionists alike. What Bend solo and small-firm lawyers should know.
If you're a solo or small-firm attorney in Bend, you've probably noticed the pattern. The calls come in at 7:42 a.m. when you're walking into court, at 6:30 p.m. when you're already home, and on Saturday morning when somebody's spouse just got served. You miss them. The next firm on Google picks up, and the case goes there.
AI intake tools are the obvious fix. These are voice receptionists and website chatbots that can answer the phone all day and night, take basic details, and book a consultation. Until February 2026, Oregon attorneys had no specific guidance from the bar on these tools. That changed when the Oregon State Bar Board of Governors approved Formal Opinion 2026-208, titled Chatbots and AI Agent Communications.
The opinion's conclusion is one line: "Yes, qualified."
This piece is about the qualifiers. It explains what they mean and what to do about them before you sign up for any AI intake tool.
The TL;DR for busy attorneys
- In February 2026 the Oregon State Bar approved an opinion saying lawyers may use chatbots for client intake and marketing, with conditions.
- The opinion defines a chatbot as software that simulates conversation, typically through text or voice.
- Five Oregon Rules of Professional Conduct (RPC) are implicated: RPC 1.1 (Competence), RPC 1.18 (Duties to Prospective Clients), RPC 5.3 (Responsibilities Regarding Nonlawyer Assistance), RPC 7.1 (False or Misleading Communications), and RPC 7.3(a) (Solicitation).
- The two biggest practical risks are (1) accidentally forming an attorney-client relationship through chatbot conduct and (2) collecting "disqualifying information" (details that can bar you from taking an opposing client) from a prospective client.
- The opinion points to RPC 5.3, which can make you the supervisor of a chatbot vendor, not just a software buyer.
- The opinion says you must be able to monitor what the chatbot says and change its responses. Footnote 10 says trained staff may handle the review.
What the opinion actually says — and why "chatbot" includes your AI receptionist
The opinion defines a chatbot as a software application designed to simulate conversation with human users, typically through text or voice interactions. That phrase matters. It would be easy to read 2026-208 as guidance about website widgets, the little chat box in the corner of a page. It is not. The bar's definition of "chatbot" reaches voice AI receptionists too: software that answers your phone, books appointments, and follows up by text.
If you are looking at an AI voice receptionist from any vendor, this opinion applies to you. A receptionist that speaks instead of types does not change the analysis.
The opinion also separates chatbots into two types. The difference matters more than most lawyers expect.
Rule-based chatbots follow predefined scripts. They have conversational ability but low autonomy. They do roughly what they were programmed to do, and not much more.
AI-agent chatbots are different. They may run on top of a large language model (LLM, the kind of AI behind ChatGPT) and act as autonomous agents. That means software that can take actions, make decisions, and even create sub-agents for related tasks. The opinion gives an example. A lawyer gives an agentic AI the goal "engage a person to become a client." The AI may create sub-agents that gather intake information, draft an engagement letter, and add that information to the firm's systems. It can do all of this without any input from the lawyer.
That example is the heart of the opinion's concern. It is also the heart of yours.
The five Oregon Rules of Professional Conduct that apply
RPC 1.1 — Competence
The opinion is direct: a lawyer may use a chatbot only after taking reasonable steps to become competent with the technology. That is concrete. It means understanding how the chatbot stores information, how it responds to prompts, whether it collects user inputs to train the product, and which other vendors sit underneath your vendor's software.
The opinion says these products are in constant evolution, so you should check them when you buy and revisit the check from time to time. A chatbot that behaved well in March may act differently in September if the underlying model was updated.
The opinion also notes that adequately understanding a chatbot may require lawyers to conduct research, attend training, or hire a professional to assist them. For a solo attorney, that means budgeting time, not just money.
RPC 1.18 — Duties to prospective clients (the one that will bite solos)
This is the rule most attorneys underestimate, and it is the most likely to cause real harm.
Under RPC 1.18(b), you owe confidentiality to people who consult you about hiring you, even if no attorney-client relationship ever forms. Under RPC 1.18(c), if a chatbot collects "disqualifying information" from a prospective client, you may be barred from representing a different client whose interests are materially adverse to that person in the same or a substantially related matter. RPC 1.18(d) sets out limited exceptions.
Now imagine that disqualifying information was collected by a chatbot at 11 p.m. on a Saturday, while you were asleep.
This is not a hypothetical. An AI intake tool asks probing questions to qualify a lead. The more thorough the intake, the more likely it collects information that creates a conflict for your firm. Say a prospective client tells your chatbot the names of the parties, the nature of the dispute, and the strategy they are considering. Then the other side calls you the following Tuesday. You may already be disqualified, and you would not know.
The opinion's practical advice is to enter prospective clients into your conflict management system promptly. A further step, which is our suggestion and not the opinion's, is to collect only the minimum at the start and leave detailed intake to a human conversation after a conflict check.
RPC 5.3 — Supervision of nonlawyer assistance
This is the rule that reframes how you should think about your AI vendor.
The opinion treats a chatbot vendor as a third-party provider of nonlawyer services, which can make you the supervising lawyer. The opinion mentions reference checks, vendor credentials, security policies, the vendor's hiring practices, and confidentiality agreements.
That is a real shift. You are not only a software buyer. You may be responsible for the conduct of a nonlawyer assistant, and that assistant is software hosted by a third party that may rely on other third parties.
The opinion also includes a practical note. In footnote 10, it says that reviewing chatbot communications may be delegated to staff, with appropriate training. For solos and small firms without time to read every transcript, that helps.
RPC 7.1 — False or misleading communications
Your chatbot cannot misrepresent your expertise, your past results, or your services. The opinion says, citing Florida's Ethics Opinion 24-1 and the New York City Bar's Formal Opinion 2024-5, that more than one state has found a chatbot that does not identify itself as a chatbot could be misleading.
The practical takeaway: have your AI say it is an AI at the start of every interaction. Not after the caller asks, and not in a footer they won't read. This is our reading of the risk. The opinion does not set required wording.
The opinion also says you must prevent the chatbot from misleading people about your expertise, experience, or past results. If the chatbot says you have thirty years of experience and you have eight, that is your problem, not the vendor's.
RPC 7.3(a) — Solicitation of vulnerable persons
A human intake person can tell when a caller is in crisis. They hear the trembling voice, the long pauses, the disorientation. They know when to stop the intake and ask whether the caller is safe.
A chatbot may not.
RPC 7.3(a) bars soliciting professional employment when the lawyer knows or reasonably should know that the person's physical, emotional, or mental state keeps them from using reasonable judgment. The opinion says automated tools may implicate this rule, because a person can notice a caller's impaired state and a chatbot may not. It says lawyers should promptly review these communications and interview each prospective client before forming a relationship.
One way to handle this, which is our suggestion and not the opinion's, is to build escalation triggers. These could be keywords, signs of distress, or a rule that flags long pauses and emotional language for human review before any engagement step.
Two scenarios where this gets you in trouble
Scenario one: The accidental attorney-client relationship
In this made-up example, a Bend family law solo puts an AI receptionist on her firm's website. The product is set up to "engage the client" — including drafting and sending engagement letters when the conversation reaches certain milestones.
A man visits the site at 11 p.m. after his wife filed for divorce that afternoon. The chatbot, which sounds warm and competent, listens to his situation. It asks clarifying questions. It tells him the firm can help. It collects his payment information for the retainer and sends an engagement letter to his email before he goes to bed.
The attorney finds out Monday morning when the man calls asking when the temporary order will be filed.
Is there an attorney-client relationship? Quite possibly. Under Oregon law, the existence of an attorney-client relationship depends on the reasonable belief of the prospective client. In re Weidner, 310 Or 757 (1990). A signed engagement letter and a paid retainer are not nothing.
The opinion says to use clear disclaimers and to have a lawyer notified of each interaction and able to review it promptly. We would go further: the chatbot should never say a relationship has formed, and engagement letters, fee quotes, and acceptance of a case should need a human's approval. Show disclaimers at the start of every session, not in a footer.
Scenario two: The disqualifying-information trap
In this second made-up example, a criminal defense solo in Bend uses an AI voice receptionist for after-hours calls. The system runs a thorough intake: name, charges, dates, witnesses, prior counsel, anything the caller volunteers.
At 9 p.m. on a Tuesday, the system takes a long call from a woman who is the sister of a complaining witness in a pending assault case. She is considering retaining the attorney to advise her about a potential civil claim related to the same incident. She gives the chatbot the full picture of what her family knows, what the prosecutor has told them, and what the witness will say at trial.
Two weeks later, the actual defendant in that assault case calls. The case is bigger. The fee is bigger. The attorney would very much like to take it.
She likely cannot. Under RPC 1.18(c), the firm received material information from a prospective client whose interests are materially adverse to the prospective defendant in the same matter. RPC 1.18(d) allows limited exceptions, such as informed written consent from both sides, but she has little reason to agree.
The attorney is conflicted out by a chatbot conversation she never heard.
One fix, which is our suggestion, is to collect only the basics up front (name, jurisdiction, opposing party, contact information) and send the rest to a human conflict check before any substantive talk.
A vendor-evaluation checklist
If you are evaluating an AI intake tool, these questions follow the duties 2026-208 discusses. This is our own checklist, not the bar's. A vendor that cannot answer most of them without checking with someone is not ready for your firm.
- Does your AI identify itself as an AI program at the start of every conversation?
- Can the system be configured so that engagement letters, fee quotes, and anything resembling acceptance of representation require explicit human approval before being sent?
- How do you isolate one client's information from another's? Can prompts or conversations from my firm's deployment be used to train responses for any other customer?
- What encryption do you use at rest and in transit, and can you produce documentation of your security controls — including a SOC 2 Type II report (an independent security audit) or similar?
- Will you disclose every sub-vendor in your stack — including any underlying language model provider, speech-to-text vendor, and storage vendor — and will you contractually bind them to confidentiality?
- How will I be notified of every chatbot interaction, and how quickly?
- Can I review and modify the chatbot's responses, and what is the audit trail?
- What is your escalation protocol when a caller appears to be in crisis or emotionally impaired?
- Will you sign a written agreement that includes confidentiality, breach notification, data return or destruction on termination, and your obligations as my nonlawyer assistant under RPC 5.3?
- In the event of a data breach, what is your notification window, and what indemnification do you provide?
Copy these into an email to a sales rep. The answers — and the speed with which they come — tell you more than the demo.
A sample disclosure for your website or call greeting
Florida's Ethics Opinion 24-1 and the New York City Bar's Formal Opinion 2024-5 are the opinions Oregon cites on this point. Oregon's 2026-208 says a chatbot that does not identify itself as a chatbot could be misleading under RPC 7.1, but it sets no required wording. Plan on a clear disclosure either way.
The following is a template you can adapt. It is not a one-size-fits-all clause, and you still need to think about your own situation:
This site uses an AI assistant to help us respond to inquiries twenty-four hours a day. The AI is not a lawyer and is not authorized to give legal advice, accept your case, or establish an attorney-client relationship. Any information you share will be reviewed by an attorney at [Firm Name] before next steps are taken. If your situation is urgent, please call us directly at [number], or call 911.
For a voice receptionist, the disclosure should be the first sentence the caller hears, after the firm name. Not after the system asks how it can help. First.
What the opinion does not cover
2026-208 is a state bar ethics opinion. It addresses your obligations under the Oregon Rules of Professional Conduct. It does not address — and should not be read to address — several adjacent issues that may still bite you:
- Federal court filing disclosure rules. The U.S. District Court for the District of Oregon may impose separate requirements about AI-assisted filings. Check standing orders before you file.
- TCPA compliance. The Telephone Consumer Protection Act regulates outbound AI calling separately. Under 47 U.S.C. § 227, damages are $500 per violation, up to $1,500 if willful. An inbound AI receptionist is generally lower risk. If your system makes outbound follow-up calls, federal rules apply on top of the bar opinion.
- Statutory consumer-marketing liability. Oregon and federal consumer protection statutes may apply to misrepresentations by your AI in ways the bar opinion does not address.
- Contract law. If your AI quotes a fee, makes a promise about timeline, or otherwise creates terms that turn out to be wrong, the resulting contract dispute is separate from any bar discipline issue.
- Other risk management issues. As Mark Fucile noted in his analysis for NWSidebar, the opinion focuses on professional conduct rules and does not cover every risk management question.
How we think about this at WildRun AI
WildRun AI, in Bend, can build AI automation for small businesses, including AI receptionists and intake lines. Given how the opinion reads, an intake line we build for a law firm could be set up to say it is an AI at the start of every call, to have no way of sending engagement letters, and to send each transcript to the firm for prompt review. Footnote 10 says trained staff may do that review.
That describes what we can build, not past projects. Our page on AI intake for law firms covers how we would plan a line around the opinion. Whether a particular setup meets your obligations is a decision for you and your ethics counsel.
Further reading
- Oregon Formal Opinion 2026-208 — full text (PDF)
- Oregon Formal Opinion 2025-205 — general AI use
- ABA Formal Opinion 512, July 29, 2024
- Florida Bar Ethics Opinion 24-1, January 19, 2024
- Mark Fucile, "New Oregon State Bar Opinion on Using AI Agents for Client Intake," NWSidebar (March 2026)
This article is for informational purposes only and does not constitute legal advice. WildRun AI is not a law firm and does not provide legal advice or representation. Attorneys evaluating any technology for use in their practice should consult their own ethics counsel and exercise their independent professional judgment.
Frequently asked questions
Does Oregon Formal Opinion 2026-208 cover voice AI receptionists or just website chatbots?
Both. The opinion defines a chatbot as software designed to simulate conversation 'typically through text or voice interactions.' That second clause reaches AI voice receptionists, not just website chat widgets. If your firm uses an AI voice receptionist for after-hours calls, 2026-208 applies to you.
What are the biggest compliance risks from using an AI receptionist under 2026-208?
Two stand out. First, accidentally forming an attorney-client relationship, for example if your AI collects payment details or sends engagement-style messages without a lawyer's approval. Second, the disqualifying-information risk under RPC 1.18(c): a thorough AI intake may collect information that bars your firm from a later case, and you may not know the call happened.
Can I delegate transcript review to a staff member rather than reviewing every chatbot interaction myself?
Yes. Footnote 10 of Opinion 2026-208 says that, with appropriate training, reviewing chatbot communications may be delegated to staff. You remain professionally responsible for the work under RPC 5.3.
What disclosure does my AI receptionist need to give callers?
We suggest having your AI say it is an AI at the start of every interaction, before it asks how it can help. Opinion 2026-208 says that more than one state, including Florida and New York City in the opinions it cites, has found that a chatbot that does not identify itself could be misleading under RPC 7.1. It sets no required wording. A good disclosure also says no attorney-client relationship is formed without attorney review.