Insights/legal-intake
legal-intake

8 AI Lead Response Scripts That Qualify Title IX Inquiries Within Minutes

Eight ready-to-deploy AI lead response scripts that qualify Title IX inquiries fast, route cases correctly, and protect sensitive intake conversations.

8 AI Lead Response Scripts That Qualify Title IX Inquiries Within Minutes

Title IX inquiries arrive fast, carry deadlines, and require a conflict check before a single fact is discussed. A generic "thanks for contacting us" auto-reply loses the case. The eight scripts below are built for AI-assisted intake systems, meaning chatbots, SMS automations, and after-hours response tools. Each one collects the specific data points that let your team qualify, route, and follow up on Title IX matters before a competitor answers the phone.

Quick reference: what each script does

  • Initial parent inquiry: confirms case type, collects school level and incident details
  • Student self-report: captures role, process status, and any investigation notice
  • Upcoming hearing deadline: surfaces the hearing date, institution, and charges notice
  • Complainant-vs-respondent routing: triggers a conflict check before substantive intake
  • Confidentiality reassurance: delivers privilege and confidentiality language before sensitive facts are shared
  • School or employee matters: identifies the respondent's role and administrative phase
  • After-hours crisis response: collects urgency data without giving legal advice
  • Missed-call follow-up: re-engages callers who hit voicemail within five minutes

1. Initial Parent Inquiry Script

The script confirms the firm handles Title IX matters, collects the school level and incident type, and routes the inquiry to a licensed attorney before the conversation ends.

Most parent inquiries about school misconduct arrive with partial information. A parent knows something happened to their child at school. They do not yet know whether it qualifies under Title IX, whether the school has opened a formal process, or whether they need a lawyer. The AI script does not sort that out for them. It collects enough information to let your intake team make that determination on the first call.

The script should capture, in this order: the relationship of the caller to the student (parent, guardian), the grade level and type of institution (K-12 public, K-12 private, college or university), whether the school has communicated with the family in writing, and a callback number and preferred time. It ends with a clear statement that a member of the team will follow up, not a promise about case strength.

Example exchange (AI chatbot or SMS, labeled as example, no results implied):

"Thank you for reaching out. We handle Title IX education matters, including incidents at K-12 schools and colleges. To connect you with the right person on our team, can you tell us: (1) Is this for a K-12 school or a college or university? (2) Has the school sent any written notices or emails about the incident? (3) What is the best number and time to reach you?"
Title IX intake scripts must ask about the caller's role, complainant or respondent, in the first two minutes to trigger a conflict check before any substantive case discussion begins.

Takeaway: A parent inquiry script qualifies the institution type and written-notice status before staff time is spent, so the attorney who returns the call knows whether this is a fresh complaint or an active investigation.

2. Student Self-Report Script

When a student contacts the firm directly, the script captures their role, the school's current process status, and any notice-of-investigation letter details.

Students who call directly are often further into a school's internal process than parent callers. They may have already received a notice of investigation, been assigned an advisor, or attended a preliminary hearing. This detail changes the urgency and the scope of the engagement.

The student self-report script asks: whether the student is the complainant or the person accused (do not use the word "respondent" in the script unless your intake team has confirmed the caller understands the term), whether the school has opened a formal grievance process, whether any written notices have been received, and the name of the institution.

The role question is the most important. It is not asked to categorize the student; it is asked to trigger the conflict check your intake manager must run before any further discussion. If the firm already represents the other party in the same matter, the call ends there, politely.

Takeaway: Collecting the student's role and the school's process status in the first message, before any facts are discussed, is what makes a self-report script legally safe and operationally efficient.

3. Urgency Script for an Upcoming Hearing Deadline

A deadline-triggered script asks for the hearing date, the institution name, and whether a written charges notice has been received. These three data points let staff assess whether emergency representation is feasible.
Federal Title IX regulations require schools to resolve complaints within specific timeframes, which means inquiries involving an active hearing notice are often time-sensitive from the first call.

The 2020 Title IX regulations issued by the U.S. Department of Education, 34 C.F.R. Part 106, required institutions to hold live hearings for postsecondary cases with cross-examination rights, and to follow written grievance procedures with defined timelines. Under the 2024 final rule, 89 Fed. Reg. 33474, schools have different procedural options, but timeline obligations remain. A caller with a hearing scheduled within days is a different triage category from one at the beginning of a school investigation.

The urgency script should not promise that the firm can take the case. It should immediately surface the hearing date so the intake manager can flag the matter to an attorney before the callback. A script that buries the deadline question in the fifth exchange wastes the one resource that cannot be recovered: time.

Example question set (labeled as example, no results implied):

"To make sure we connect you with the right team member quickly: (1) Has your school or university scheduled a hearing or disciplinary conference? (2) If yes, what is the date? (3) Have you received a written notice listing the charges or allegations? (4) What institution is this?"

Takeaway: The hearing date goes in the first exchange, not buried in a long form, so your intake team can triage before the callback queue.

4. Routing Script That Separates Complainant-Side from Respondent-Side Cases

Because a firm cannot represent both sides of the same Title IX matter, the routing script asks a single early question about the caller's role and immediately flags the case for a conflict check.
Complainant-side and respondent-side Title IX cases require different litigation strategies, so a single generic intake script creates misrouted leads that the firm cannot ethically serve.

This is not a question of preference. The American Bar Association's Model Rules of Professional Conduct, Rule 1.7, prohibit concurrent representation of clients with directly adverse interests. Title IX complainant and respondent, in the same matter at the same institution, are directly adverse. A firm that takes both calls without a routing mechanism risks a conflict that requires withdrawal from one or both.

The routing script delivers this question plainly, in the first or second exchange:

"Are you reaching out because you experienced something, or because you have been accused or notified of an allegation?"

The language avoids legal terms. It surfaces the information the conflict-check requires. If the firm already represents the opposing party in the same matter, the script routes to a standard "we are unable to assist" message with a referral to the state bar's lawyer referral service.

Firms that specialize in one side, complainant or respondent, can use this routing point to filter even earlier, before the callback, and to set accurate expectations in the confirmation message.

Takeaway: One routing question, in the first exchange, prevents the ethical conflict that can follow from collecting detailed facts before a conflict check runs.

5. Confidentiality Reassurance Language for Sensitive Details

Before the caller shares facts, the script delivers a plain-English statement that intake staff operate under a duty of confidentiality and that the conversation becomes attorney-client privileged once connected to counsel.
A confidentiality statement delivered before sensitive details are requested reduces caller drop-off and protects the firm if the intake conversation is later disputed.

Title IX inquiries involve sexual misconduct allegations, disciplinary records, and information about minors in K-12 cases. Callers often pause or abandon the intake process at the point where the script asks for specific details. The reason is not reluctance to hire a lawyer; it is uncertainty about whether the information is safe.

A confidentiality statement does two things. First, it reduces the drop-off. Second, it accurately describes the firm's obligations. The statement should be short, plain, and accurate:

"Before you share any details, we want you to know: our intake team holds what you share in confidence. When you speak with one of our attorneys, that conversation is protected by attorney-client privilege. We do not share information about your inquiry with anyone outside our firm."

This language does not create an attorney-client relationship through the AI response. It describes how the firm handles sensitive information. Any firm using this language should confirm with its own ethics counsel that the statement is accurate for its jurisdiction and intake process.

Takeaway: A four-sentence confidentiality statement, delivered before the fact-gathering questions, keeps callers on the line through the most sensitive part of the intake exchange.

Title IX complaints involving school employees, coaches, or administrators follow a different administrative path than student-on-student matters. The script identifies the respondent's role and whether the matter is in the administrative phase or civil litigation phase.

When the accused party is a school employee, teacher, coach, or administrator rather than another student, the institutional liability calculus changes. The school's response obligations under Title IX differ, and the potential for a civil claim against the institution is a distinct track from the school's internal grievance process.

The script for these matters should capture: whether the alleged conduct involved a school employee or adult staff member, whether the school has been notified and what their response has been, and whether any law enforcement report has been filed. This last question is not for legal advice purposes. It is a triage question that tells the intake manager whether the matter is in a criminal, administrative, or civil posture, or some combination of all three.

Example question set (labeled as example, no results implied):

"(1) Did the incident involve a school staff member, teacher, or coach rather than another student? (2) Has the school responded in writing to what happened? (3) Has any law enforcement report been filed? (4) Are you contacting us on behalf of yourself or your child?"

Takeaway: A script that identifies the respondent's role routes employee-misconduct matters to the attorney on your team with the right civil-litigation background, not the attorney who handles student-on-student hearings.

7. After-Hours Script for Crisis or Time-Sensitive Situations

An after-hours AI script confirms receipt of the inquiry, collects the hearing date and contact preference, and sends an automated CRM-flagged confirmation. It does not give legal advice and routes urgent matters to an on-call attorney flag.
An after-hours AI response that collects hearing date and contact preference, without offering legal advice, keeps urgent Title IX matters in the pipeline rather than losing them to competing firms.

Title IX crises do not follow business hours. A student who receives a suspension notice at 6:00 p.m. on a Friday, with a hearing scheduled Monday morning, will search for representation that night. If the firm's after-hours system returns a voicemail and nothing else, that caller will reach a competing firm's AI system by 6:15 p.m.

The after-hours script has a narrow job: acknowledge the inquiry, collect the data that determines urgency (hearing date, institution, the caller's role), and set an accurate callback expectation. It does not assess the merits, estimate fees, or promise representation. It ends with an automated SMS or email confirmation that includes the callback window, so the caller knows the firm has the inquiry in hand.

Example after-hours confirmation (labeled as example, no results implied):

"We received your message about a Title IX matter. Our team will follow up with you [by 9:00 a.m. / within one business hour of opening]. If you have a hearing scheduled within 48 hours, please note that in your reply and we will escalate your inquiry to the attorney on call."

The CRM record created by the after-hours script should carry a field for the hearing date. Any record with a hearing date within 72 hours should auto-assign an urgent flag before the team arrives the next morning.

Takeaway: An after-hours script that collects the hearing date and sets an accurate callback window recovers the Friday-night inquiry that a voicemail system loses.

8. Follow-Up Script After a Missed Intake Call

A missed-call follow-up sequence sends an SMS and email within five minutes of the missed call, confirms the firm received the inquiry, and offers a direct scheduling link.
A missed-call SMS follow-up sent within five minutes recovers Title IX leads who would otherwise go to voicemail and not call back.

Title IX callers are calling during a stressful, often acute situation. They are not browsing for a lawyer the way someone shops for a contractor. They want to speak with someone now, or close to now. A voicemail that goes unreturned for two hours is, functionally, a referral to whoever answers their next search result.

The five-minute window is the operational target for a missed-call response. The mechanism is a CRM automation: when an inbound call is missed, the system triggers an SMS to the caller's number and an email to any address captured in the web form or chatbot session. Both messages confirm the firm received the inquiry, name the practice area so the caller knows they reached the right firm, and include a scheduling link for a callback at the caller's preferred time.

Example SMS (labeled as example, no results implied):

"Hi, this is [Firm Name]. We missed your call and want to make sure we follow up. We handle Title IX matters for students and families. Click here to schedule a time that works for you: [link]. Reply STOP to opt out."

The scheduling link removes the friction of a phone-tag loop. For a caller who is at school, at work, or in a situation where they cannot take a call at a random time, the ability to book a 15-minute intake call at a specific hour is what converts the missed call into a consultation.

Takeaway: A five-minute missed-call SMS with a scheduling link is the single highest-leverage automation for recovering Title IX inquiries that reach voicemail.

How These Scripts Connect to a Case Acquisition System

Each script above is a conversation design decision. The decisions only pay off when the system behind them works: the AI response tool, the CRM record it creates, the conflict-check trigger, the attorney notification, and the pipeline stage that tracks whether the inquiry became a signed retainer.

RGDM builds that full pipeline for law firms, from the ad that generates the inquiry through the signed-case signal sent back to the ad platform. The scripts are the intake layer. The CRM automation behind them is what tells you, six months from now, which script variation produced the cases your firm actually wanted to sign.

If your intake system is handling Title IX inquiries with a generic contact form and a next-day callback, the gap between what you are capturing and what you could be capturing is not a script problem. It is a system problem.

Book a free Case Acquisition Review at /contact. In 30 minutes, we map the full intake path for your Title IX practice and identify where inquiries are leaving the pipeline before your team ever reaches them.

Frequently Asked Questions

How fast should law firms respond to Title IX inquiries?

The practical target is under five minutes for an initial automated acknowledgment and under one business hour for a human or attorney callback during business hours. Title IX callers are often in an active school proceeding with a near-term deadline. A same-day callback window is the minimum; a five-minute SMS acknowledgment keeps the caller from moving to the next firm in their search results.

Can AI handle sensitive Title IX intake conversations?

AI-assisted intake tools, chatbots, SMS automations, and after-hours response systems, can collect the structured data that qualifies a Title IX inquiry: the caller's role, the institution, the hearing date, and whether written notices have been received. They should not assess case merit, estimate fees, or give legal advice. The AI layer handles data collection and confirmation; the attorney handles the substantive conversation.

What should a Title IX lead response script include?

A complete Title IX lead response script collects the caller's role (complainant or respondent), the type and name of the institution, the current status of the school's process (pre-investigation, active investigation, or hearing scheduled), any written notices received, and the best callback number and time. It delivers a confidentiality statement before requesting sensitive details and ends with a clear, accurate statement of when the firm will follow up.

Do complainant and respondent cases need different scripts?

Yes. Complainant-side and respondent-side Title IX cases require different litigation strategies, different discovery targets, and different arguments to the institution. More immediately, a firm cannot represent both sides of the same matter without an impermissible conflict under the ABA Model Rules of Professional Conduct, Rule 1.7. The routing question that identifies the caller's role must appear early in the script, before any facts are exchanged, so the conflict check can run before the intake conversation goes further.

What happens when a Title IX caller reaches an after-hours system?

An after-hours AI script should acknowledge the inquiry, collect the hearing date and contact preference, and send an automated confirmation with the next-business-day callback window. If the hearing is within 72 hours, the CRM record should auto-flag the matter for the on-call attorney. The script does not give legal advice or assess the case. Its job is to keep the inquiry in the firm's pipeline rather than losing it to a competitor who answers after hours.

How do you handle Title IX cases involving school employees versus students?

The intake script for employee-related matters captures whether the respondent is a staff member, teacher, coach, or administrator, whether the school has responded in writing, and whether any law enforcement report exists. These data points determine whether the matter is in an administrative, civil, or criminal posture, which routes it to the right attorney on the team.

What data from intake scripts should flow into the CRM?

Every intake exchange should create a CRM record with: caller role (complainant or respondent), institution name and type, hearing date if applicable, written-notice status, the script variant that handled the inquiry, and the timestamp of first contact. The hearing date field should trigger an urgency flag for any matter within 72 hours. The signed-retainer stage in the CRM is the downstream source of truth that tells the firm which script variant and which ad source produced cases worth signing.

How do missed Title IX calls get recovered?

A CRM automation triggered by a missed inbound call sends an SMS to the caller's number within five minutes. The message confirms the firm received the inquiry, identifies the practice area, and includes a scheduling link for a callback at the caller's preferred time. The same trigger sends an email if an address was captured in a prior form or chatbot session. This two-channel follow-up recovers callers who will not leave a voicemail or call a second time without a prompt.

← All insights
Ready when you are

Let's turn your clicks into customers.

Book a 30-minute call. We'll review your spend, your tracking, and where customers are slipping away.

Book a call