Small law firms: what an AI agent can and can't do with your software
- Last verified
- Updated Published
A solo practice or a firm with a few lawyers usually pays for a small set of subscriptions: practice management for matters, time and billing, an intake or CRM tool, document management, e-signature, a payment processor that knows the difference between trust and operating money, QuickBooks, and sometimes a marketing platform. This guide asks how much of that Meta's Muse assistant, or any agent that works through connectors, can reach right now, which office chores make sense to give it, and why client confidences, trust money and lawyer advertising call for a lawyer's eyes on every step. It's written for firms of one to roughly ten lawyers. Large firms, legal aid programs, in-house legal teams and the question of which practice management system to buy aren't covered.
Each claim has a badge showing its backing:
| Label | Meaning on this page |
|---|---|
| Confirmed by vendor | Backed by the maker of the product, or by Meta, through its help center articles, developer documentation, press releases or blog. |
| Confirmed by agency | Rests on a federal statute published by the House's Law Revision Counsel, a federal regulation from eCFR or the Federal Register, or an order or rule a state supreme court published on its own site; the badge names the issuer. |
| Published by the ABA | We read it directly on americanbar.org: an ABA Model Rule of Professional Conduct, its comment, or a formal opinion of the ABA's ethics committee. The ABA is a private bar association, so this is national guidance, not law; it binds a lawyer only where that lawyer's state has adopted it, and a state's version can differ, as Arkansas's does in places. |
| Unverified | We looked and found nothing we could cite; it stays an open question. |
How this page was put together: our sources were the API and help documentation of every practice management, intake, payments, document and e-signature product in the table, the Meta and partner pages for the connectors Meta lists, the Muse terms of service and privacy policy from Meta, the ABA Model Rules on competence, confidentiality, nonlawyer assistance, safekeeping property and lawyer advertising together with ABA Formal Opinion 512, the current Arkansas Rules of Professional Conduct as the Arkansas Supreme Court posts them, two December 2025 orders of that court, the FCC robocall rule and its latest amendment, and the CAN-SPAM Act and rule. The date we read each one is beside it in the source list. No assistant, Muse or otherwise, was linked to a client matter, document store, trust account or ledger, and we sent nothing to any client. What a vendor documents is how its product is designed to behave, which isn't the same as your bar rules allowing that use.
Short version
- Of the products here, only HighLevel, Stripe and Intuit QuickBooks appear as Muse connectors in Meta's launch post; no legal product does. (Confirmed by vendor 1)
- MyCase, Filevine, NetDocuments and iManage each describe an MCP connection, and Clio offers one for its Vincent research tool inside OpenAI's Codex. The client lists their makers give are Claude, ChatGPT, Microsoft Copilot or Codex; Muse isn't named by any of them. (Confirmed by vendor 9 10 13 16 19)
- By default, Meta's privacy policy lets it train its AI on your Muse interactions, which can include what a connector pulls in, and the terms rule out unlicensed legal work and relying on Muse to substantially decide someone's legal rights unless a person meaningfully reviews it. (Confirmed by vendor 8)
- Since Dec 11, 2025, the Arkansas Rules of Professional Conduct have said AI help is allowed but never excuses or lessens a rule violation, and Rule 5.3 now covers technological tools such as generative AI. (Confirmed by the Arkansas Supreme Court 26)
- The FCC's changes to how people revoke consent for robocalls and robotexts take effect Nov 25, 2026, so firms that text should check their stop-request process before that date arrives. (Confirmed by the FCC 30)
Stack map
| Software | In Meta's launch-post connector list? | How else it connects | Label and source |
|---|---|---|---|
| Clio (Manage and Grow) | No | Clio's developer docs describe two API families, one for Clio Manage and one for the Clio Platform, which carries the Clio Grow APIs. Building on Manage starts with a seven-day trial that can become a free developer account, and a private app can be limited to one firm's own account. Clio's Sept 17, 2026 release says firms using Vincent or Clio Work can turn on a plugin that links OpenAI's Codex to their Clio account through MCP so Codex can call Vincent's research and docket tools, and that lawyers remain responsible for checking what comes back. (Confirmed by vendor 9) We found no Clio page offering an MCP server for Muse or setting out which Manage records, if any, the Codex plugin can read. Unofficial Clio MCP servers on GitHub and connector marketplaces aren't Clio's, and we didn't evaluate them. (Unverified) | Confirmed by vendor 9 |
| MyCase | No | The MyCase Open API comes only with the Advanced tier, uses OAuth 2.0, and MyCase expects the firm to have technical people to build on it. MyCase also offers an MCP connector, made by its parent 8am, which it calls read-only, bound by each user's existing permissions, included on every plan at no added cost and available only to Claude Team and Enterprise accounts. (Confirmed by vendor 10) | Confirmed by vendor 10 |
| PracticePanther | No | PracticePanther has a RESTful API that supports OData queries and OAuth 2, and you have to ask PracticePanther for API access before using it. (Confirmed by vendor 11) The only PracticePanther MCP server we came across is a community project, not one PracticePanther publishes. (Unverified) | Confirmed by vendor 11 |
| Smokeball | No | Smokeball's REST API signs in through OAuth 2.0 with separate US, Australian and UK base URLs, and developers begin by filling in a registration of interest form for its partnerships or product teams. (Confirmed by vendor 12) We found no Smokeball MCP server. (Unverified) | Confirmed by vendor 12 |
| Filevine | No | Filevine's API Gateway takes a client ID and secret, which outside developers request from Filevine Partnerships and a customer can create in Account Manager, plus a personal access token from an account admin; calls run as a service account user with that user's permissions, and default credentials get tighter rate limits. Filevine's September 2026 release notes add a Platform MCP that lets a firm connect Claude, acting as the signed-in user with that person's permissions, by contacting a Filevine representative. (Confirmed by vendor 13) Filevine hasn't published setup steps for that MCP that we could find, and nothing says it works with Muse. (Unverified) | Confirmed by vendor 13 |
| Lawmatics | No | Lawmatics offers a REST API and outbound webhooks, both needing someone technical; Lawmatics support has to switch on Developer Settings before you can create an app with a client ID and secret, and the API allows 150 requests a minute per firm. (Confirmed by vendor 14) We found no Lawmatics MCP server. (Unverified) | Confirmed by vendor 14 |
| LawPay | No | LawPay's integration settings list authorized partner applications and API credentials, with an optional allowlist of IP ranges, and LawPay says payments sync to QuickBooks Online. (Confirmed by vendor 15) We found no LawPay MCP server. (Unverified) | Confirmed by vendor 15 |
| NetDocuments | No | NetDocuments describes MCP access through ndConnect as an advanced tier for ndMAX Enterprise customers. Administrators opt the firm in through Security Center, document permissions, ethical walls and data loss prevention settings keep applying, and the approved MCP platforms it lists are Claude, ChatGPT and Microsoft Copilot through Copilot Studio. NetDocuments adds that what an AI vendor does with content after delivery is governed by the firm's own agreement with that vendor. (Confirmed by vendor 16) | Confirmed by vendor 16 |
| iManage | No | iManage has an MCP server whose access is authenticated, limited by permissions and logged, with ethical walls respected. Its help pages explain adding iManage Work, Tracker and Search to MCP-enabled clients as custom connectors by URL, with instructions for Claude, ChatGPT and Copilot Studio, and iManage tells customers to find out from each AI vendor what data leaves iManage. (Confirmed by vendor 19) Whether Muse accepts iManage's connector is untested. (Unverified) | Confirmed by vendor 19 |
| Docusign | No | Docusign hosts an MCP server reached over Streamable HTTP with an OAuth login. Using a production account through a custom connector requires Docusign to add it to an allow list via a request form, and Muse isn't among the official connectors Docusign names, which cover Claude, Gemini Enterprise, ChatGPT, Perplexity, Copilot Studio and Slackbot. (Confirmed by vendor 17) | Confirmed by vendor 17 |
| Adobe Acrobat Sign | No | For Acrobat Sign, Adobe publishes a REST API, webhook support and a partner program. (Confirmed by vendor 18) We came across no MCP server for Acrobat Sign run by Adobe. (Unverified) | Confirmed by vendor 18 |
| HighLevel | Yes (Confirmed by vendor 1 6) | Muse talks to an MCP endpoint that HighLevel operates; when you sign in with OAuth you choose the CRM sub-accounts it may see and review the requested scopes. (Confirmed by vendor 6) | Confirmed by vendor 1 6 |
| Stripe | Yes (Confirmed by vendor 1) | Stripe's MCP server accepts OAuth or an agent API key, and refunds and outbound payments wait until a person follows a link the agent sends and approves them. Stripe says that from December its MCP rejects secret keys with no restrictions and any restricted key not tagged Agent; the migration deadline is Nov 30, 2026. (Confirmed by vendor 7) We didn't check how Stripe takes its fees or handles chargebacks on an account that receives client trust money. (Unverified) | Confirmed by vendor 1 7 |
| QuickBooks Online | Yes (Confirmed by vendor 1 4) | Intuit says its Muse connector reads profit and loss, balance sheet and cash flow numbers, creates and sends invoices that clients can pay online, and nudges clients whose invoices are late. (Confirmed by vendor 4) | Confirmed by vendor 1 4 |
| Zapier | Not in Meta's post, though Zapier's docs walk through adding it in Muse's Connectors settings. (Confirmed by vendor 5) | Zapier is the bridge | Confirmed by vendor 1 5 |
If you want a custom connector
Anything Meta doesn't list would need a go-between: an MCP server the vendor runs, like those from NetDocuments, iManage or Docusign, an app built through the vendor's API program, or Zapier. Before building anything, list every company that would handle client information along the way, because each is a service provider whose safeguards you have to check under the confidentiality and supervision rules below. Meta's help center says custom connectors and their data handling get no review from Meta, and that Muse's memory and chat history may hold on to information after a connector is removed. (Confirmed by vendor 2) Under Meta's rules for people building connectors, every sensitive write gets its own approval and blanket, ongoing permission is forbidden. (Confirmed by vendor 3) The Muse terms make you alone responsible for the services you connect. (Confirmed by vendor 8)
Jobs you could hand off today
None of these needs client matter data.
| Task | Where it runs | What the vendor documents | Label and source |
|---|---|---|---|
| Reviewing, each month, operating-account cash flow, balance sheet and P&L | QuickBooks in Muse | Intuit says the connector reads each of these three reports. (Confirmed by vendor 4) Keep trust ledgers and client names out of it; use firm-level totals. | Confirmed by vendor 4 |
| Bill earned fees and chase late invoices | QuickBooks in Muse | Sending invoices and following up on overdue ones are both on Intuit's list. (Confirmed by vendor 4) Only for fees already earned and payable to the operating account; describe the work generically, since invoice text can reveal client confidences. | Confirmed by vendor 4 |
| First drafts of blog posts, newsletters and social posts on general legal topics | Muse, with HighLevel for prospect lists | HighLevel lets you choose which sub-accounts and scopes Muse can use. (Confirmed by vendor 6) A lawyer approves each piece under the advertising rules below, and the email and text rules apply on top. | Confirmed by vendor 6 |
| Look over operating-account card payments and disputes | Stripe MCP, read-only to start | Stripe lets you restrict an agent key to the permissions the job needs. (Confirmed by vendor 7) Keep matter names and case details out of payment descriptions. | Confirmed by vendor 7 |
| Reminders for CLE deadlines, bar dues, insurance renewals and a yearly review of your software vendors | Muse calendar or task reminders | Arkansas's comment 8 to Rule 1.1, worded like the ABA's, ties keeping up with technology to continuing study and meeting CLE requirements. (Confirmed by the Arkansas Supreme Court 28) Store dates only; no bar numbers or client details. | Confirmed by the Arkansas Supreme Court 28 |
None of these has been tested by us. Your plan, user roles and connector settings change what happens, so try a small batch first and review every output.
Keep these out
- Client files, matters, documents and intake answers. Don't connect practice management, document management, intake or e-signature accounts to an assistant, or paste client facts into a chat, until you've done the vendor diligence and, where needed, gotten the client's informed consent described below.
- Legal advice and decisions about a client's rights. Muse's terms say it gives no legal or other professional advice, prohibit using it for unlicensed regulated activity including legal services, and prohibit relying on it as a substantial factor in whether someone receives a legal right or benefit unless a person meaningfully reviews the outcome. (Confirmed by vendor 8)
- Trust account money. No agent should move, refund or disburse client funds. Meta's terms say Muse isn't acting as a fiduciary, a money transmitter or a financial institution, and expect a person to review actions that change something, such as sending communications, before they happen. (Confirmed by vendor 8)
- Mass texts and emails. The terms forbid bulk messages lacking the consent required by the TCPA, CAN-SPAM or state telemarketing rules, and forbid passing off Muse responses as written by a person where disclosure is required. (Confirmed by vendor 8)
- Court e-filing and portal logins. Muse's terms prohibit evading another service's terms, access controls or CAPTCHAs, or signing in with credentials you're not authorized to use. (Confirmed by vendor 8) Keep court and agency credentials away from any agent, Muse included.
Risks to keep a person on
Competence and confidentiality
The ABA Model Rules aren't law by themselves; each state supreme court adopts its own version, so read your state's text. Where Arkansas's rule matches the ABA's, we cite the Arkansas text from the Arkansas Supreme Court's site, and we point out where the two differ. Anything marked Published by the ABA is national guidance read on americanbar.org; it binds a lawyer only where that lawyer's state has adopted it.
In Arkansas, comment 8 to Rule 1.1 says staying competent includes keeping up with the benefits and risks of relevant technology. Arkansas's Rule 1.6(a) bars revealing information relating to a representation without informed consent, implied authorization or an exception, and 1.6(c) requires reasonable efforts to prevent inadvertent or unauthorized disclosure of, or access to, that information; comment 18 lists what goes into judging those efforts. (Confirmed by the Arkansas Supreme Court 28) The ABA's model text says the same in comment 8 to Rule 1.1 and in Rules 1.6(a) and 1.6(c). (Published by the ABA 20 21) The exceptions in Arkansas's Rule 1.6(b) aren't the ABA's list; its first one, for instance, covers preventing a criminal act. (Confirmed by the Arkansas Supreme Court 28)
In Formal Opinion 512 of July 29, 2024, the ABA's ethics committee says lawyers using generative AI need a reasonable grasp of what the tools can and can't do, should get a client's informed consent before putting that client's information into a self-learning tool, and can't rely on generic consent language in an engagement letter for that. It also tells lawyers to read a tool's terms of use and privacy policy before using it. (Published by the ABA 23) Muse is exactly that case to check: training on interactions is on unless you switch it off under Data Controls, and Meta can look at and store records of what Muse does. (Confirmed by vendor 8)
Supervising the assistant and its vendors
ABA Model Rule 5.3 makes lawyers with managerial authority put measures in place that give reasonable assurance nonlawyer assistance fits the lawyer's duties, and makes a lawyer answerable for conduct they order, ratify or fail to fix in time. The comment names a document management company and an internet-based service storing client information as examples of outside assistance, and says the right steps depend partly on the contract terms protecting client information. (Published by the ABA 22) Opinion 512 applies those duties to generative AI and calls for firm policies and training on its use. (Published by the ABA 23)
Arkansas, Tennessee and Mississippi
Arkansas. In a per curiam order of Dec 11, 2025, effective immediately, the Arkansas Supreme Court added a preamble paragraph saying nothing in its professional conduct rules bars non-human help, artificial intelligence included, but that using it doesn't excuse or reduce any violation. The same order renamed Rule 5.3 to cover nonlawyer assistance and added a comment that this assistance includes technological tools such as generative AI platforms. (Confirmed by the Arkansas Supreme Court 26) Its Administrative Order No. 25, issued the same day, warns everyone working in the court system that some generative AI tools keep what users submit to build their models, so anyone entering confidential or sealed information should first find out whether the tool retains it, since that disclosure may break the Rules of Professional Conduct. (Confirmed by the Arkansas Supreme Court 27)
In the court's current text, Arkansas's Rule 5.3 keeps the ABA's three duties but attaches them to the nonlawyer assistance itself rather than to a nonlawyer person, and holds a lawyer responsible for a use they order or ratify, or fail to correct in time. Its comment 3 names the same outside services as the ABA's, a document management company and an Internet-based service storing client information among them, and its comment 5 says nonlawyer assistance includes work done by human staff and by technological tools such as generative AI platforms. The ABA's comments have no counterpart to that comment 5. (Confirmed by the Arkansas Supreme Court 28)Tennessee. We found no Tennessee Supreme Court rule or Board of Professional Responsibility formal ethics opinion on lawyers using AI. A Tennessee Bar Association blog post reports an Oct 9, 2026 Supreme Court policy on AI for CLE providers, which we didn't confirm on the court's site and which doesn't address client work. (Unverified)
Mississippi. Secondary sources report a Mississippi Bar ethics opinion on generative AI, numbered 267 and dated Nov 14, 2024, but the Bar keeps its formal opinions behind a member login, so we couldn't read the text. (Unverified) Mississippi lawyers should pull it from the Bar directly.
Trust money and card payments
ABA Model Rule 1.15 has a lawyer hold client and third-party property apart from the lawyer's own, keep client money in a separate trust account, put advance fees and expenses into trust until earned or incurred, and add the lawyer's own funds only to cover bank service charges; the comment says commingling is otherwise impermissible. (Published by the ABA 24) Arkansas's Rule 1.15, titled Safekeeping Property and Trust Accounts, goes further than the ABA's and numbers it differently. Lawyer funds in trust may cover bank charges or a minimum balance but never more than $500. Each trust account must be set up so overdrafts are reported to the Executive Director of the Office of Professional Conduct. Nominal or short-term client money goes in a pooled IOLTA account whose interest is paid monthly to the IOLTA Program of the Arkansas Access to Justice Foundation, records are kept five years, and lawyers certify compliance every year when they renew their license. (Confirmed by the Arkansas Supreme Court 28) Interest on Lawyers' Trust Accounts (IOLTA) programs and trust account recordkeeping are set state by state; we didn't read the Tennessee or Mississippi rules for this page. (Unverified)
LawPay says firms connect both trust and operating accounts so earned and unearned money don't get commingled, that it deposits the whole payment and takes its fees monthly from the operating account and never from trust, and that it won't debit a trust account for any reason, chargebacks and disputes included. (Confirmed by vendor 15) Those are LawPay's own claims. Whatever processor you use, confirm in writing where fees and chargebacks come from before a payment link can touch unearned money, and never let an agent pick the deposit account.
Advertising and solicitation
Under ABA Model Rules 7.1 and 7.2, nothing a lawyer communicates about their services may be false or misleading, which includes leaving out a fact needed to keep it from misleading, and any communication under Rule 7.2 has to give the name and contact details of at least one lawyer or firm responsible for it. The comment to Rule 7.3 says live person-to-person solicitation doesn't include text messages or other written messages that are easy to ignore, but still forbids solicitation that involves coercion, duress or harassment or that targets someone who has said they don't want contact. (Published by the ABA 25) Arkansas still uses the ABA's older structure, and its versions are stricter. Its Rule 7.1 bans false or misleading communications too but also counts any testimonial or endorsement as one, and its Rule 7.2 requires keeping a copy of each ad for five years, naming at least one Arkansas-licensed lawyer responsible for it and stating where the lawyers who will do the work practice. Its Rule 7.3 bars soliciting by in-person, live telephone or real-time electronic contact when a significant motive is the lawyer's pecuniary gain, and a written solicitation to someone known to need help in a particular matter must go by regular mail, with "Advertisement" on the envelope and on every page. (Confirmed by the Arkansas Supreme Court 28) We found no ruling on whether a real-time AI voice agent calling prospects counts as live person-to-person contact under ABA Rule 7.3, or as real-time electronic contact under Arkansas's, so don't use one for outreach. (Unverified) A lawyer should approve every AI-drafted ad, post and email before it goes out.
Calls and texts
Under the FCC's rule, an autodialed or prerecorded call to a cell phone requires the prior express consent of whoever is called, and that consent has to be in writing if the call advertises or telemarkets; that written consent is a signed agreement, electronic signatures included where law allows, that identifies the number and says agreeing isn't required to buy anything. Telephone solicitations to residences may only be made between 8 in the morning and 9 at night, local time, and can't go to numbers on the national do-not-call list, which the FCC also applies to telemarketing texts and calls made to wireless numbers, as far as its 2003 TCPA order provides. The do-not-call exemption for an established business relationship covers 18 months following a purchase and 3 months following an inquiry. (Confirmed by the FCC 29)Beginning Nov 25, 2026, callers can designate one of the revocation methods the rule allows as the exclusive way to opt out, provided its calls and texts say so, and may limit a stop request about one type of informational message to that type. (Confirmed by the FCC 30) Keep an agent from editing stop keywords, folding appointment or case-status texts into marketing, or adding contacts to a promotional list.
The CAN-SPAM Act requires a commercial email to identify itself as an ad unless the recipient gave prior consent, to offer an unsubscribe option that remains usable for a minimum of 30 days after the send, and to show a valid physical postal address; once someone opts out, mail to them must stop within 10 business days. (Confirmed by Congress 32) The FTC's rule forbids charging a fee or asking for more than an email address and opt-out preferences to unsubscribe, and counts a mixed message as commercial when its subject line would make a recipient think it's an ad or when the transactional or relationship part isn't mainly at the top of the message. (Confirmed by the FTC 31)
Treat this page as a summary of published sources, not as legal or ethics advice. Your state's rules of professional conduct, its ethics opinions, your malpractice carrier and your software contracts may ask more of you than this page does, so talk to your state bar's ethics counsel or an ethics lawyer before an assistant touches anything that holds client information.
FAQ
Does Clio have an MCP server I can plug into Muse?
Clio's MCP offering, announced Sept 17, 2026, connects its Vincent research and docket tools to OpenAI's Codex for Vincent and Clio Work customers; it isn't described as a Muse connector. (Confirmed by vendor 9) For other uses Clio points developers to its Manage and Grow APIs.
Is the MyCase MCP connector safe to use with client data?
MyCase says the connector only reads data, follows each user's existing permissions and is limited to Claude Team and Enterprise accounts. (Confirmed by vendor 10) Read-only still means client information leaves MyCase for the AI provider, so the confidentiality and consent questions above still apply.
Can I take card payments with Stripe for retainers?
We didn't review Stripe's terms for trust money. (Unverified) Unearned retainers belong in trust under your state's version of Rule 1.15, so get your processor's fee and chargeback handling in writing and check it with your state bar before you do.
How does Zapier charge for this?
Each MCP tool call that succeeds counts as two Zapier tasks. (Confirmed by vendor 5) Plan your task budget around that before an agent starts creating Lawmatics or PracticePanther records.
Changes to this page
| Date | What changed | Sources |
|---|---|---|
| Oct 28, 2026 | First published. | All sources listed on this page |
| Oct 28, 2026 | Dropped the unused Conflicting row from our key to the labels; no statement in the law firm guide carries it. | No sources changed |
Found a mistake or a newer source? Send it through Corrections, with a link to the source, and we'll recheck the claim and record the change here.
Sources
- Source 5: Zapier Docs “Zapier MCP for Muse: setup from the Connectors settings; Zapier MCP usage and billing.” docs.zapier.comAlso: https://docs.zapier.com/mcp/overview/usage
- Source 9: Clio “Clio developer documentation; Clio press release on the Vincent plugin for Codex.” docs.developers.clio.comAlso: https://www.clio.com/about/press/clio-vincent-codex-plugin/
- Source 10: MyCase (8am) “MyCase Open API; MyCase MCP.” supportcenter.mycase.comAlso: https://supportcenter.mycase.com/en/articles/16237229-mycase-mcp
- Source 13: Filevine “Authenticate requests to the API Gateway; September 2026 release notes.” support.filevine.comAlso: https://support.filevine.com/hc/en-us/articles/55420679436059-September-2026-Release-Notes
- Source 15: LawPay (AffiniPay) “LawPay compliance; Integrations settings overview.” lawpay.comAlso: https://help.lawpay.com/en/articles/10671852-integrations-settings-overview
- Source 20: American Bar Association, Center for Professional Responsibility “ABA Model Rule 1.1, Competence: Comment.” americanbar.org
- Source 21: American Bar Association, Center for Professional Responsibility “ABA Model Rule 1.6, Confidentiality of Information.” americanbar.org
- Source 22: American Bar Association, Center for Professional Responsibility “ABA Model Rule 5.3, Responsibilities Regarding Nonlawyer Assistance, and its Comment.” americanbar.orgAlso: https://www.americanbar.org/groups/professional_responsibility/publications/model_rules_of_professional_conduct/rule_5_3_responsibilities_regarding_nonlawyer_assistant/comment_on_rule_5_3/
- Source 23: American Bar Association, Standing Committee on Ethics and Professional Responsibility “ABA Formal Opinion 512, Generative Artificial Intelligence Tools.” americanbar.org
- Source 24: American Bar Association, Center for Professional Responsibility “ABA Model Rule 1.15, Safekeeping Property, and its Comment.” americanbar.orgAlso: https://www.americanbar.org/groups/professional_responsibility/publications/model_rules_of_professional_conduct/rule_1_15_safekeeping_property/comment_on_rule_1_15/
- Source 25: American Bar Association, Center for Professional Responsibility “ABA Model Rules 7.1 and 7.2, and the Comment to Rule 7.3.” americanbar.orgAlso: https://www.americanbar.org/groups/professional_responsibility/publications/model_rules_of_professional_conduct/rule_7_2_advertising/, https://www.americanbar.org/groups/professional_responsibility/publications/model_rules_of_professional_conduct/rule_7_3_direct_contact_with_prospective_clients/comment_on_rule_7_3/
- Source 26: Supreme Court of Arkansas “In re Amendments to the Arkansas Rules of Professional Conduct, 2025 Ark. 221.” opinions.arcourts.gov
- Source 27: Supreme Court of Arkansas “In re Administrative Order No. 25: Artificial Intelligence, 2025 Ark. 220.” opinions.arcourts.gov
- Source 28: Supreme Court of Arkansas “Arkansas Rules of Professional Conduct [Current]: Scope [22] and Rules 1.1, 1.6, 1.15, 5.3, 7.1, 7.2 and 7.3 with comments.” opinions.arcourts.gov
- Source 30: Federal Communications Commission, in the Federal Register “Enhancing the Ability of Consumers To Control the Robocalls (FR Doc. 2026-21821, 91 FR 67214).” federalregister.gov
- Source 31: Federal Trade Commission regulation, read on eCFR “16 CFR part 316, CAN-SPAM Rule (sections 316.2, 316.3 and 316.5).” ecfr.gov
- Source 32: Office of the Law Revision Counsel, U.S. House of Representatives “15 U.S.C. 7704, Other protections for users of commercial electronic mail.” uscode.house.gov