Give the public chatbot a narrow job
A law firm intake chatbot should help a visitor find the appropriate next step, not invite a complete account of a dispute. Start the planning conversation with a simple question: what does the receptionist need to route this inquiry before an attorney decides what information to request? That is a narrower task than evaluating a case, assessing evidence, or deciding whether the firm can represent someone.
AIQ FastChats publicly describes practice-area explanations, contact collection, and consultation routing for legal and professional businesses. Its custom chatbot page describes FAQ handling and inquiry capture; these descriptions are not evidence of an automated legal conflict-checking system.[1][2]
The field choices and example responses below are planning recommendations, not reports of deployed law-firm client workflows. This article is workflow education, not legal advice. Applicable state rules and firm counsel determine actual intake requirements. Neither this guide nor a public chatbot should promise confidentiality, privilege, or an attorney-client relationship. Leave determinations about representation and legal obligations to a lawyer.
Why the first question matters
ABA Model Rule 1.18 addresses duties to prospective clients. Paragraph (b) limits use or disclosure of information learned from a prospective client even when no client-lawyer relationship results, subject to the exception it specifies. Paragraphs (c) and (d) address significantly harmful information, disqualification, and limited exceptions. These are reasons to examine the invitation to share information, not simply the final submit button.[3]
The ABA commentary explains that whether electronic communications constitute a consultation depends on the circumstances. Comment [2] discusses requests for information about potential representation and clear, reasonably understandable warnings. Comment [4] recommends limiting an initial consultation to information reasonably necessary to determine whether to undertake a new matter.[4]
The ABA material is model guidance, not a statement of binding law in every jurisdiction. Do not treat a checkbox or disclaimer as a device that automatically erases duties or guarantees compliance. Ask firm counsel to review the actual questions, introductory wording, follow-up prompts, and human handling together. A narrow opening followed by an unrestricted request to “tell me everything” is not a coherent information boundary.
A minimal inquiry versus a matter narrative
Recommended field-selection artifact: review each card with the attorney responsible for intake. Keep a field only when the firm can explain its routing purpose. Offer a direct contact alternative for visitors who do not want to use chat. This is a proposed worksheet, not an enabled form or a claim that every deployment collects the same information.
Preferred contact method
Ask how the person would like the firm to contact them and collect only the approved contact detail needed for that choice. Do not require both a telephone number and email merely to complete a longer record. Let the visitor correct a mistyped detail before follow-up.
Broad practice area
Offer firm-approved categories, with an “unsure” route. A broad request such as a question about an estate-planning consultation is enough for this routing stage. Do not turn category selection into a merits assessment or ask for detailed allegations to decide whether the visitor qualifies.
Relevant geography
Ask for the geographic detail the firm actually uses to route inquiries, if needed. Explain why it is requested. Do not infer that a location match means a lawyer is licensed for the matter, has accepted it, or can provide representation.
Leave detailed material out
Do not solicit evidence uploads, correspondence, identification documents, sensitive third-party facts, or a chronological matter narrative in public chat. If the firm needs additional information, an authorized person should explain its separate approved intake channel and the appropriate next steps.
Keep conflict review in the firm-approved process
Recommended handoff design: distinguish a request for contact from a completed conflict review. A chatbot should not label an inquiry “conflict cleared,” accept an engagement, or suggest that a practice-area match is an acceptance decision. If party names or related entities are required, let the firm decide when and where to obtain them. Do not invent a secure portal, connected database, or integration to make that step sound complete.
Write down who receives the inquiry, what minimum details that person needs, and which published contact route remains available if chat cannot complete the request. Review any proposed summary for unnecessary repetition of sensitive material. AIQ FastChats describes limited collection, response guardrails, and human escalation as public design boundaries; those descriptions are not a confidentiality guarantee or security certification.[5]
Use precise status wording in the proposed flow. “Contact request received” must only appear when receipt is actually verified. “An attorney will take your case” is not a substitute. The visitor should understand what has happened and what remains for the firm to decide, without being promised a reply time the firm has not approved.
Illustrative responses for three difficult requests
These original, fictitious edge cases are draft wording for attorney review. They illustrate limits, not legal conclusions about a particular visitor or conversation.
Edge case 1: volunteered confidential facts
Visitor: “I have private emails proving what happened. Can I paste them here?” Draft response: “Please do not share confidential documents or detailed facts in this public chat. Use the firm’s published contact route to ask about its approved intake process.” Review goal: stop soliciting detail rather than summarize the proposed evidence or promise that it will be protected.
Edge case 2: a predicted case outcome
Visitor: “Based on that practice area, will I win?” Draft response: “I cannot assess your case or predict an outcome. The firm must decide whether it can discuss your matter through its intake process.” Review goal: do not provide odds, strategies, settlement values, or reassuring claims disguised as general information.
Edge case 3: an approaching deadline
Visitor: “I think something is due tomorrow. Can I wait for a callback?” Draft response: “This chat cannot calculate or verify legal deadlines, and a contact request does not promise a timely response or representation. Contact the firm promptly through its published route or seek other qualified legal assistance.” Review goal: do not calculate a date, advise waiting, or imply that the firm is monitoring the deadline.
Before launch: the attorney approval checklist
Recommended review sequence: first approve the assistant’s narrow purpose and introductory boundary. Next review every field and optional follow-up. Then check the real destination and alternate contact route. Finally, test the complete visitor journey with fictitious information only. Do not use an actual client file to demonstrate that the intake flow works.
- Have the responsible attorney approve warnings, practice-area descriptions, information limits, and escalation wording under applicable rules.
- Identify who handles unsolicited sensitive details and how that situation enters the firm-approved process; do not let the chatbot improvise a legal determination.
- Test a visitor who declines contact capture, changes their contact detail, asks for a lawyer immediately, or sends a deadline question before answering any fields.
- Check that a failed or incomplete submission does not display a success message and that the published alternate route remains easy to find.
- Keep an owner and revision record for the approved wording so later FAQ edits do not quietly expand intake into legal advice.
For the broader service context, Explore industry chatbot use cases. Review custom FAQ and inquiry-capture scope alongside the public information and escalation boundaries before discussing a build. Bring the field worksheet and attorney-approved limits, not confidential case materials.
Sources
Primary sources retrieved September 13, 2026. First-party pages describe public scope, not proof of features in every deployment.
Bring your intake boundaries to the planning conversation
Discuss the questions, approved answers, and human follow-up process your business needs. The demo is a starter flow, not a sector-specific production demonstration.