100 Best Gemini Client Intake Prompts for Law Firms
These Gemini prompts help with client intake for law firms using practical instructions, clear constraints, and reusable output formats.
Best For
Law firms, legal assistants, intake coordinators
Prompt Use Cases
- Client intake data collection
- Conflict checks
- Initial client interview scripts
- Lead capture and qualification
- Document and form generation
- Consistency and compliance auditing
- Phone, video, and chat intake channels
- CRM and case management integration
- Client communication templates
- Privacy and data handling guidance
Direct Answer
The best Gemini prompts for client intake for law firms are optimized to capture essential client data, verify authority, assess conflicts, and set the stage for compliant onboarding. Use structured prompts to standardize data collection, maintain privacy, and route cases efficiently. Always tailor placeholders to your practice area and jurisdiction.
Introduction
This page is a practical prompt library for client intake in law firms. It provides actionable Gemini prompts that guide staff through compliant data gathering, risk checks, and onboarding tasks.
Designed for intake coordinators, paralegals, and attorneys, the prompts help standardize interactions and improve data quality while protecting client privacy.
How to Use These Gemini Prompts
- Replace placeholders with your practice details, jurisdiction, and policy references.
- Add constraints such as data formats, required fields, and validation rules to ensure consistency.
- Request outputs in specific formats like JSON or structured checklists, and specify verification steps for accuracy.
- When needed, prompt Gemini to generate follow-up questions based on client responses.
- Test a batch of prompts with sample data to ensure outputs align with your CRM and matter types.
- Document any deviations for future reuse.
100 Best Gemini Client Intake Prompts for Law Firms
- Basic client info intake: You are a training assistant for a law firm intake specialist. Task: generate a structured intake form capture for a new client. Context: capture essential fields including full name, contact details, preferred contact method, date of birth, jurisdiction, and case type. Output: present as a JSON object with fields: clientName, contactMethods, preferredTime, dob, jurisdiction, caseType, consentGiven, notes. Constraints: no PII leakage beyond client-provided data; validate dates, ensure consent flag is true, and format as JSON only.
- Conflict check prefill: Role: intake analyst. Task: draft a conflict check prompt that lists potential conflict categories and automates flagging for further review. Context: use client name placeholders, opposing parties placeholders, and matter type. Output: a checklist with sections: potential conflicts, parties involved, related matters, and recommended next steps. Constraints: produce a clean textual checklist and a JSON summary suitable for a case management system.
- Initial consultation goals: Role: senior associate. Task: generate a pre-consultation goals summary for a new client. Context: gather objective, urgency, primary legal issue, desired outcome, and any deadlines. Output: bullet list for the attorney and a one-paragraph client brief. Constraints: avoid legal advice; focus on information gathering and consent for data use.
- Data privacy consent form: Role: privacy officer. Task: craft a client consent prompt that produces a short privacy disclosure and data usage outline. Context: cover storage, access, retention period, and client rights. Output: a ready-to-attach consent section with placeholders for client signature and date. Constraints: align with local regulations; ensure plain-language language.
- Jurisdiction check script: Role: intake coordinator. Task: create a script that collects client jurisdiction to determine applicable law. Context: include state/province, country, and preferred forum. Output: structured data fields: jurisdiction, governing law, venue preference, and any restrictive requirements. Constraints: validate against a jurisdiction matrix.
- Case type classifier: Role: intake assistant. Task: build a classifier that maps factual summaries to case types (family, criminal, civil, business, immigration). Context: provide examples and edge cases. Output: a labeled list of caseType with confidence scores; provide brief rationale per label. Constraints: avoid legal conclusions; use deterministic mapping.
- Lead qualification questions: Role: marketing liaison. Task: generate a {lead-qualification} questionnaire to determine whether the case is within firm’s scope and capacity. Context: include practice areas, budget range, urgency, and preferred communication channel. Output: a ranked list of questions with recommended next steps for each answer.
- Client intake checklist: Role: intake manager. Task: produce a comprehensive intake checklist that covers identity verification, contact data, opposing party discovery, and preliminary document needs. Context: structure into sections with checkboxes. Output: plain-text checklist plus a summary JSON snippet for CRM.
- Document list generator: Role: paralegal. Task: create a prompt that asks clients to upload required documents. Context: list documents by category (identity, financials, contracts, court notices) with secure upload instructions. Output: categorized document request list and a downloadable intake packet.
- Appointment scheduling prompt: Role: receptionist. Task: generate a scheduling prompt that finds the earliest available slot and confirms with the client. Context: consider time zones, holidays, and attorney availability. Output: calendar invite text and a confirmation message with date, time, and location or video link. Constraints: avoid double-booking; include timezone.
- Conflict flags summary: Role: intake reviewer. Task: produce a concise conflict flags summary from client inputs. Context: include party names, related matters, and internal notes. Output: bullet list and JSON field conflictFlags with boolean flags and reasons. Constraints: ensure completeness without exposing confidential data.
- Client communication tone: Role: communications coordinator. Task: craft a tone-consistent client welcome message for first contact. Context: include assurances about confidentiality and next steps. Output: two versions: formal and neutral, each with subject line and body.
- Billing language prompts: Role: billing specialist. Task: generate prompts to collect billing expectations and fee arrangements. Context: flat fee, hourly, retainers, and contingency. Output: structured fee preferences and a note field for billing constraints.
- Interest and authority check: Role: intake analyst. Task: verify authorized signer and authority to engage counsel. Context: collect names, titles, and proof of representation. Output: data fields and required documents list.
- Privacy risk prompts: Role: compliance officer. Task: identify potential privacy risks in client intake. Context: data categories, storage security, and access controls. Output: risk pairs with mitigation steps and responsible party.
- Client portal setup: Role: IT liaison. Task: guide clients to set up a secure intake portal. Context: provide login steps, two-factor, and document upload guidelines. Output: step-by-step setup instructions and checklist.
- Language preference capture: Role: intake assistant. Task: capture client language preference and accessibility needs. Context: preferred language, translation requirements, and accommodations. Output: data fields and escalation path for interpreters.
- Referral source logging: Role: intake coordinator. Task: log how clients found the firm. Context: options include referral, ad, walk-in, or event. Output: source, campaign ID, and attribution notes.
- Case timeline sketch: Role: lawyer. Task: request key dates and milestones from client. Context: deadlines, court dates, and document due dates. Output: structured timeline with dates and descriptions.
- Conflict of interest prefill: Role: intake reviewer. Task: prompt to identify potential conflicts via client relationships and prior matters. Context: list entities and roles. Output: structured conflicts list with priority and follow-up actions.
- Consent for calls: Role: compliance officer. Task: draft consent language for phone or video calls. Context: recording consent, purpose, and storage. Output: consent text suitable for intake script.
- Attorney assignment prompt: Role: intake manager. Task: suggest suitable attorney assignments based on case type and availability. Context: include seniority, practice area, and current load. Output: recommended attorney roster with notes.
- Preliminary damages estimate: Role: junior attorney. Task: draft a prompt to capture potential damages or relief sought. Context: ranges, calculations, and supporting documents. Output: numeric estimates and justification notes.
- Insurance details prompt: Role: intake clerk. Task: collect applicable insurance information if applicable. Context: insurer, policy number, and coverage limits. Output: structured insurance fields and validation rules.
- Opposing counsel data: Role: intake assistant. Task: collect opposing party details and counsel contact. Context: names, firms, emails, and phone numbers. Output: contact table and a notes field.
- Case sensitivity guide: Role: policy advisor. Task: establish guidelines for handling sensitive information in intake. Context: data classification, access permissions, and auditing. Output: policy summary and checklist.
- Client onboarding plan: Role: client advocate. Task: assemble an onboarding plan with milestones and responsible parties. Context: first contact, document submission, and case initiation. Output: plan with timelines and owners.
- Medical records prompt: Role: paralegal. Task: request medical records where relevant. Context: patient identifiers, authorization, and expected formats. Output: document request list and secure transfer instructions.
- Educational background prompt: Role: intake coordinator. Task: collect education and employment history if relevant. Context: degrees, institutions, dates. Output: structured history fields and notes.
- Language translation script: Role: interpreter liaison. Task: arrange translation services for the intake. Context: languages needed, dialects, and turnaround. Output: interpreter roster and contact details.
- Signatory authority check: Role: intake reviewer. Task: verify signatory authority for engagement. Context: list authorized signatories and required documents. Output: authority matrix.
- Expense policy prompt: Role: finance liaison. Task: capture expected expense handling and policy alignment. Context: who pays, advance preapproval, and reimbursement rules. Output: expense policy summary.
- Digital signature ready: Role: admin assistant. Task: prepare documents for digital signing. Context: signing parties, documents, and required fields. Output: signing packet and verification steps.
- Document redaction guide: Role: paralegal. Task: outline redaction needs for sensitive data in intake documents. Context: what data to redact and how to annotate. Output: redaction plan.
- Security questionnaire: Role: IT security officer. Task: prompt clients to answer basic security questions for data handling. Context: device security, networks, and data access. Output: security questionnaire results.
- Trust and verification: Role: intake auditor. Task: verify client identity through multi-factor prompts. Context: ID types, dates, and verification steps. Output: verification report.
- Case management tags: Role: intake administrator. Task: assign tags for case routing and reporting. Context: practice area, urgency, client status. Output: tag list and mapping table.
- Notice of engagement template: Role: attorney assistant. Task: draft a notice of engagement prompt to finalize representation. Context: scope, fees, start date, and termination terms. Output: draft engagement letter section.
- Escalation path prompt: Role: intake lead. Task: define escalation steps for high-risk or complex cases. Context: thresholds, owners, and response times. Output: escalation flowchart text.
- Client risks prompt: Role: risk officer. Task: identify client-side factors that could impact case handling. Context: language barrier, accessibility, availability. Output: risk notes with mitigation actions.
- Hourly rate capture: Role: billing coordinator. Task: collect preferred billing increments and rate clarity. Context: rate bands, discounts, and billing minimums. Output: rate table and notes.
- Client history prompt: Role: intake analyst. Task: collect prior legal matters and outcomes relevant to current matter. Context: case numbers, courts, and resolution. Output: history timeline and relevance notes.
- Payment method prompt: Role: finance agent. Task: gather payment methods and terms. Context: credit card, bank transfer, checks, and installments. Output: payment options and constraints.
- Case preference capture: Role: attorney liaison. Task: record client preferences for case handling (communication style, update frequency). Output: preference matrix and escalation notes.
- Matter summary generator: Role: intake clerk. Task: draft a concise matter summary from client-provided facts. Context: key dates, parties, and issues. Output: one-paragraph summary and bullet key points.
- Document upload guide: Role: admin. Task: provide a clear document upload workflow. Context: accepted formats, size limits, and naming conventions. Output: upload guide and drop-off instructions.
- Client expectations prompt: Role: client advocate. Task: elicit realistic expectations for outcomes and timelines. Context: risk awareness and decision points. Output: expectation checklist and a brief note.
- Data retention notice: Role: compliance officer. Task: deliver data retention details for client data. Context: retention period, deletion schedule, and access controls. Output: retention notice.
- Remote collaboration setup: Role: IT liaison. Task: configure secure remote collaboration for intake. Context: platforms, permissions, and data encryption. Output: setup guide and security tips.
- Conflict resolution prompt: Role: intake specialist. Task: outline steps if a conflict of interest is found. Context: notification flow, client consent, and escalation. Output: action plan.
- Client consent confirmation: Role: compliance officer. Task: confirm client consent for data processing. Context: purposes, duration, and rights. Output: consent confirmation string and log entry.
- Record keeping prompt: Role: records manager. Task: specify how intake records are stored and indexed. Context: retention, backups, and access controls. Output: record-keeping schema.
- Client feedback loop: Role: operations manager. Task: design a quick feedback prompt after intake. Context: rating scale, comments, and follow-up. Output: feedback summary and improvement notes.
- Regulatory check prompt: Role: compliance lead. Task: prompt to verify regulatory requirements for client data. Context: jurisdiction, sector, and licensing. Output: compliance checklist.
- Alternate contact capture: Role: intake coordinator. Task: collect alternate contact methods and emergency contacts. Context: names, relationships, and phone numbers. Output: contact map.
- Case opening template: Role: attorney assistant. Task: generate a standard case opening template for new matters. Context: client details, matter type, and initial documents. Output: filled template ready for filing.
- Attorney preferences: Role: intake manager. Task: store attorney preferences for response style and update cadence. Context: response time targets and preferred channels. Output: preference log.
- Confidentiality reminder: Role: intake advisor. Task: deliver a confidentiality reminder to clients. Context: what is confidential, who has access, and how to protect data. Output: reminder text.
- Fee estimate prompt: Role: attorney. Task: gather a preliminary fee estimate based on case type and hours. Context: scope, rate, and estimated durations. Output: estimate with caveats.
- Evidence checklist: Role: paralegal. Task: request initial evidentiary items from client. Context: documents, witnesses, and timelines. Output: checklist with submission guidelines.
- Jurisdictional forms: Role: intake clerk. Task: identify and request jurisdiction-specific forms. Context: jurisdiction laws and required fields. Output: form list and fillable fields.
- Client history update: Role: intake coordinator. Task: prompt for updates to client history at intake. Context: changes since last contact. Output: updated history section.
- Language accessibility prompts: Role: accessibility coordinator. Task: ensure intake materials are accessible. Context: formats, readability levels, and assistive tech. Output: accessibility plan.
- Upcoming deadlines prompt: Role: attorney assistant. Task: extract deadlines from client statements. Context: court dates, filing deadlines, and response times. Output: deadline register.
- Consent to store documents: Role: compliance officer. Task: prompt for consent to store and process documents. Context: duration and access. Output: storage consent snippet.
- Notice to transfer: Role: intake manager. Task: prepare notice if case is transferred internally or externally. Context: transfer reason, involved offices, and timelines. Output: transfer notice text.
- Risk disclosure prompt: Role: attorney. Task: provide clients with risk disclosures relevant to matter. Context: probabilities, uncertainties, and decisions. Output: risk brief.
- Funding arrangements: Role: finance liaison. Task: collect funding or sponsorship details if applicable. Context: source, terms, and responsibilities. Output: funding summary.
- Client preferences registry: Role: intake coordinator. Task: maintain a registry of client preferences for outreach. Context: contact times, channels, and tone. Output: preferences registry.
- Case file index: Role: records clerk. Task: generate an index for new client files. Context: categories, subfolders, and naming conventions. Output: index schema.
- Post-intake survey: Role: operations analyst. Task: create a survey for clients after intake. Context: satisfaction, clarity, and suggestions. Output: survey results and improvement brief.
- Data minimization rule: Role: privacy officer. Task: implement data minimization guidance for intake. Context: collect only necessary fields and avoid sensitive data. Output: minimization checklist.
- Ethics and compliance check: Role: ethics officer. Task: prompt for conflicts of interest and professional conduct issues. Context: red flags and escalation. Output: ethics review note.
- Non-engagement reasons: Role: intake reviewer. Task: document reasons firms might decline representation. Context: capacity, conflicts, or scope. Output: decline rationale with alternatives.
- Client onboarding timeline: Role: project manager. Task: map onboarding milestones with owners. Context: from intake to file opening. Output: timeline graphic text.
- Access level prompts: Role: IT security. Task: assign data access levels for client data. Context: user roles, need-to-know, and audit. Output: access matrix.
- Consent tracking log: Role: compliance assistant. Task: log all client consent events. Context: type of consent, date, and version. Output: consent log entry.
- Critical data flags: Role: risk manager. Task: flag critical information that must be protected. Context: PII, financials, health data. Output: flag list and protection notes.
- Preferred contact times: Role: intake coordinator. Task: collect preferred contact windows and time zones. Output: schedule-friendly contact times.
- Appointment reschedule prompt: Role: receptionist. Task: handle rescheduling with client. Context: conflicts, time zones, and reminders. Output: reschedule notice and updated calendar invite.
- Case-specific acronyms: Role: intake analyst. Task: document any case-specific acronyms and definitions. Output: glossary section for the file.
- Client education note: Role: attorney. Task: provide clients with a brief educational note about the legal process. Output: concise, plain-language guide.
- Document translation log: Role: translator liaison. Task: log translated documents and languages. Output: translation log and status.
- Attorney contact sheet: Role: admin. Task: compile a secure contact sheet for on-call attorneys. Output: contact list with channels.
- Case opening notes: Role: paralegal. Task: capture initial notes from the client interview. Output: succinct notes with key issues and next steps.
- Fee agreement prompts: Role: attorney. Task: prompt to present fee agreement options. Context: disclosures, cancellation policy, and scope. Output: draft fee agreement section.
- Client consent video prompt: Role: privacy officer. Task: obtain consent for video calls where needed. Output: consent text and recording notice.
- Background check prompt: Role: intake clerk. Task: collect consent for background checks where required. Output: checkbox-based consent form.
- Conflict waiver draft: Role: attorney assistant. Task: draft a conflict waiver for disclosure and consent. Output: waiver text and signature lines.
- Case progression requests: Role: client liaison. Task: gather client requests on case progression updates. Output: update cadence table and delivery method.
- Special accommodations: Role: accessibility coordinator. Task: capture any special accommodations for meetings. Output: accommodation list and setup steps.
- Insurance defense prompts: Role: claims liaison. Task: collect any relevant insurance defense information. Output: insurance-related data fields.
- Outsourcing notes: Role: intake manager. Task: document any outsourcing or referral needs. Output: referral list and terms.
- Case type escalation: Role: intake lead. Task: prompt for escalation when case type is ambiguous. Output: escalation criteria and notes.
- Document confidentiality stamp: Role: admin. Task: generate a confidentiality stamp for uploaded docs. Output: stamp text and placement rules.
- Attorney availability map: Role: scheduler. Task: build an availability map for attorneys. Output: calendar matrix and optimal slots.
- Client debrief prompt: Role: intake coordinator. Task: debrief client after first contact to clarify details. Output: debrief notes and follow-up tasks.
- Reminders and tasks: Role: assistant. Task: create a reminder set for client milestones. Output: task list with due dates and owners.
- Closing summary prompt: Role: paralegal. Task: draft a closing summary for the intake phase. Output: summary paragraph and bullet points.
- Legal ethics checklist: Role: ethics officer. Task: ensure intake process adheres to professional conduct rules. Context: permissible questions and data handling boundaries. Output: ethics checklist.
Markdown Template
100 Best Gemini Client Intake Prompts for Law Firms
# 100 Best Gemini Client Intake Prompts for Law Firms
**Basic client info intake**: You are a training assistant for a law firm intake specialist. Task: generate a structured intake form capture for a new client. Context: capture essential fields including full name, contact details, preferred contact method, date of birth, jurisdiction, and case type. Output: present as a JSON object with fields: clientName, contactMethods, preferredTime, dob, jurisdiction, caseType, consentGiven, notes. Constraints: no PII leakage beyond client-provided data; validate dates, ensure consent flag is true, and format as JSON only.
**Conflict check prefill**: Role: intake analyst. Task: draft a conflict check prompt that lists potential conflict categories and automates flagging for further review. Context: use client name placeholders, opposing parties placeholders, and matter type. Output: a checklist with sections: potential conflicts, parties involved, related matters, and recommended next steps. Constraints: produce a clean textual checklist and a JSON summary suitable for a case management system.
**Initial consultation goals**: Role: senior associate. Task: generate a pre-consultation goals summary for a new client. Context: gather objective, urgency, primary legal issue, desired outcome, and any deadlines. Output: bullet list for the attorney and a one-paragraph client brief. Constraints: avoid legal advice; focus on information gathering and consent for data use.
**Data privacy consent form**: Role: privacy officer. Task: craft a client consent prompt that produces a short privacy disclosure and data usage outline. Context: cover storage, access, retention period, and client rights. Output: a ready-to-attach consent section with placeholders for client signature and date. Constraints: align with local regulations; ensure plain-language language.
**Jurisdiction check script**: Role: intake coordinator. Task: create a script that collects client jurisdiction to determine applicable law. Context: include state/province, country, and preferred forum. Output: structured data fields: jurisdiction, governing law, venue preference, and any restrictive requirements. Constraints: validate against a jurisdiction matrix.
**Case type classifier**: Role: intake assistant. Task: build a classifier that maps factual summaries to case types (family, criminal, civil, business, immigration). Context: provide examples and edge cases. Output: a labeled list of caseType with confidence scores; provide brief rationale per label. Constraints: avoid legal conclusions; use deterministic mapping.
**Lead qualification questions**: Role: marketing liaison. Task: generate a {lead-qualification} questionnaire to determine whether the case is within firm’s scope and capacity. Context: include practice areas, budget range, urgency, and preferred communication channel. Output: a ranked list of questions with recommended next steps for each answer.
**Client intake checklist**: Role: intake manager. Task: produce a comprehensive intake checklist that covers identity verification, contact data, opposing party discovery, and preliminary document needs. Context: structure into sections with checkboxes. Output: plain-text checklist plus a summary JSON snippet for CRM.
**Document list generator**: Role: paralegal. Task: create a prompt that asks clients to upload required documents. Context: list documents by category (identity, financials, contracts, court notices) with secure upload instructions. Output: categorized document request list and a downloadable intake packet.
**Appointment scheduling prompt**: Role: receptionist. Task: generate a scheduling prompt that finds the earliest available slot and confirms with the client. Context: consider time zones, holidays, and attorney availability. Output: calendar invite text and a confirmation message with date, time, and location or video link. Constraints: avoid double-booking; include timezone.
**Conflict flags summary**: Role: intake reviewer. Task: produce a concise conflict flags summary from client inputs. Context: include party names, related matters, and internal notes. Output: bullet list and JSON field conflictFlags with boolean flags and reasons. Constraints: ensure completeness without exposing confidential data.
**Client communication tone**: Role: communications coordinator. Task: craft a tone-consistent client welcome message for first contact. Context: include assurances about confidentiality and next steps. Output: two versions: formal and neutral, each with subject line and body.
**Billing language prompts**: Role: billing specialist. Task: generate prompts to collect billing expectations and fee arrangements. Context: flat fee, hourly, retainers, and contingency. Output: structured fee preferences and a note field for billing constraints.
**Interest and authority check**: Role: intake analyst. Task: verify authorized signer and authority to engage counsel. Context: collect names, titles, and proof of representation. Output: data fields and required documents list.
**Privacy risk prompts**: Role: compliance officer. Task: identify potential privacy risks in client intake. Context: data categories, storage security, and access controls. Output: risk pairs with mitigation steps and responsible party.
**Client portal setup**: Role: IT liaison. Task: guide clients to set up a secure intake portal. Context: provide login steps, two-factor, and document upload guidelines. Output: step-by-step setup instructions and checklist.
**Language preference capture**: Role: intake assistant. Task: capture client language preference and accessibility needs. Context: preferred language, translation requirements, and accommodations. Output: data fields and escalation path for interpreters.
**Referral source logging**: Role: intake coordinator. Task: log how clients found the firm. Context: options include referral, ad, walk-in, or event. Output: source, campaign ID, and attribution notes.
**Case timeline sketch**: Role: lawyer. Task: request key dates and milestones from client. Context: deadlines, court dates, and document due dates. Output: structured timeline with dates and descriptions.
**Conflict of interest prefill**: Role: intake reviewer. Task: prompt to identify potential conflicts via client relationships and prior matters. Context: list entities and roles. Output: structured conflicts list with priority and follow-up actions.
**Consent for calls**: Role: compliance officer. Task: draft consent language for phone or video calls. Context: recording consent, purpose, and storage. Output: consent text suitable for intake script.
**Attorney assignment prompt**: Role: intake manager. Task: suggest suitable attorney assignments based on case type and availability. Context: include seniority, practice area, and current load. Output: recommended attorney roster with notes.
**Preliminary damages estimate**: Role: junior attorney. Task: draft a prompt to capture potential damages or relief sought. Context: ranges, calculations, and supporting documents. Output: numeric estimates and justification notes.
**Insurance details prompt**: Role: intake clerk. Task: collect applicable insurance information if applicable. Context: insurer, policy number, and coverage limits. Output: structured insurance fields and validation rules.
**Opposing counsel data**: Role: intake assistant. Task: collect opposing party details and counsel contact. Context: names, firms, emails, and phone numbers. Output: contact table and a notes field.
**Case sensitivity guide**: Role: policy advisor. Task: establish guidelines for handling sensitive information in intake. Context: data classification, access permissions, and auditing. Output: policy summary and checklist.
**Client onboarding plan**: Role: client advocate. Task: assemble an onboarding plan with milestones and responsible parties. Context: first contact, document submission, and case initiation. Output: plan with timelines and owners.
**Medical records prompt**: Role: paralegal. Task: request medical records where relevant. Context: patient identifiers, authorization, and expected formats. Output: document request list and secure transfer instructions.
**Educational background prompt**: Role: intake coordinator. Task: collect education and employment history if relevant. Context: degrees, institutions, dates. Output: structured history fields and notes.
**Language translation script**: Role: interpreter liaison. Task: arrange translation services for the intake. Context: languages needed, dialects, and turnaround. Output: interpreter roster and contact details.
**Signatory authority check**: Role: intake reviewer. Task: verify signatory authority for engagement. Context: list authorized signatories and required documents. Output: authority matrix.
**Expense policy prompt**: Role: finance liaison. Task: capture expected expense handling and policy alignment. Context: who pays, advance preapproval, and reimbursement rules. Output: expense policy summary.
**Digital signature ready**: Role: admin assistant. Task: prepare documents for digital signing. Context: signing parties, documents, and required fields. Output: signing packet and verification steps.
**Document redaction guide**: Role: paralegal. Task: outline redaction needs for sensitive data in intake documents. Context: what data to redact and how to annotate. Output: redaction plan.
**Security questionnaire**: Role: IT security officer. Task: prompt clients to answer basic security questions for data handling. Context: device security, networks, and data access. Output: security questionnaire results.
**Trust and verification**: Role: intake auditor. Task: verify client identity through multi-factor prompts. Context: ID types, dates, and verification steps. Output: verification report.
**Case management tags**: Role: intake administrator. Task: assign tags for case routing and reporting. Context: practice area, urgency, client status. Output: tag list and mapping table.
**Notice of engagement template**: Role: attorney assistant. Task: draft a notice of engagement prompt to finalize representation. Context: scope, fees, start date, and termination terms. Output: draft engagement letter section.
**Escalation path prompt**: Role: intake lead. Task: define escalation steps for high-risk or complex cases. Context: thresholds, owners, and response times. Output: escalation flowchart text.
**Client risks prompt**: Role: risk officer. Task: identify client-side factors that could impact case handling. Context: language barrier, accessibility, availability. Output: risk notes with mitigation actions.
**Hourly rate capture**: Role: billing coordinator. Task: collect preferred billing increments and rate clarity. Context: rate bands, discounts, and billing minimums. Output: rate table and notes.
**Client history prompt**: Role: intake analyst. Task: collect prior legal matters and outcomes relevant to current matter. Context: case numbers, courts, and resolution. Output: history timeline and relevance notes.
**Payment method prompt**: Role: finance agent. Task: gather payment methods and terms. Context: credit card, bank transfer, checks, and installments. Output: payment options and constraints.
**Case preference capture**: Role: attorney liaison. Task: record client preferences for case handling (communication style, update frequency). Output: preference matrix and escalation notes.
**Matter summary generator**: Role: intake clerk. Task: draft a concise matter summary from client-provided facts. Context: key dates, parties, and issues. Output: one-paragraph summary and bullet key points.
**Document upload guide**: Role: admin. Task: provide a clear document upload workflow. Context: accepted formats, size limits, and naming conventions. Output: upload guide and drop-off instructions.
**Client expectations prompt**: Role: client advocate. Task: elicit realistic expectations for outcomes and timelines. Context: risk awareness and decision points. Output: expectation checklist and a brief note.
**Data retention notice**: Role: compliance officer. Task: deliver data retention details for client data. Context: retention period, deletion schedule, and access controls. Output: retention notice.
**Remote collaboration setup**: Role: IT liaison. Task: configure secure remote collaboration for intake. Context: platforms, permissions, and data encryption. Output: setup guide and security tips.
**Conflict resolution prompt**: Role: intake specialist. Task: outline steps if a conflict of interest is found. Context: notification flow, client consent, and escalation. Output: action plan.
**Client consent confirmation**: Role: compliance officer. Task: confirm client consent for data processing. Context: purposes, duration, and rights. Output: consent confirmation string and log entry.
**Record keeping prompt**: Role: records manager. Task: specify how intake records are stored and indexed. Context: retention, backups, and access controls. Output: record-keeping schema.
**Client feedback loop**: Role: operations manager. Task: design a quick feedback prompt after intake. Context: rating scale, comments, and follow-up. Output: feedback summary and improvement notes.
**Regulatory check prompt**: Role: compliance lead. Task: prompt to verify regulatory requirements for client data. Context: jurisdiction, sector, and licensing. Output: compliance checklist.
**Alternate contact capture**: Role: intake coordinator. Task: collect alternate contact methods and emergency contacts. Context: names, relationships, and phone numbers. Output: contact map.
**Case opening template**: Role: attorney assistant. Task: generate a standard case opening template for new matters. Context: client details, matter type, and initial documents. Output: filled template ready for filing.
**Attorney preferences**: Role: intake manager. Task: store attorney preferences for response style and update cadence. Context: response time targets and preferred channels. Output: preference log.
**Confidentiality reminder**: Role: intake advisor. Task: deliver a confidentiality reminder to clients. Context: what is confidential, who has access, and how to protect data. Output: reminder text.
**Fee estimate prompt**: Role: attorney. Task: gather a preliminary fee estimate based on case type and hours. Context: scope, rate, and estimated durations. Output: estimate with caveats.
**Evidence checklist**: Role: paralegal. Task: request initial evidentiary items from client. Context: documents, witnesses, and timelines. Output: checklist with submission guidelines.
**Jurisdictional forms**: Role: intake clerk. Task: identify and request jurisdiction-specific forms. Context: jurisdiction laws and required fields. Output: form list and fillable fields.
**Client history update**: Role: intake coordinator. Task: prompt for updates to client history at intake. Context: changes since last contact. Output: updated history section.
**Language accessibility prompts**: Role: accessibility coordinator. Task: ensure intake materials are accessible. Context: formats, readability levels, and assistive tech. Output: accessibility plan.
**Upcoming deadlines prompt**: Role: attorney assistant. Task: extract deadlines from client statements. Context: court dates, filing deadlines, and response times. Output: deadline register.
**Consent to store documents**: Role: compliance officer. Task: prompt for consent to store and process documents. Context: duration and access. Output: storage consent snippet.
**Notice to transfer**: Role: intake manager. Task: prepare notice if case is transferred internally or externally. Context: transfer reason, involved offices, and timelines. Output: transfer notice text.
**Risk disclosure prompt**: Role: attorney. Task: provide clients with risk disclosures relevant to matter. Context: probabilities, uncertainties, and decisions. Output: risk brief.
**Funding arrangements**: Role: finance liaison. Task: collect funding or sponsorship details if applicable. Context: source, terms, and responsibilities. Output: funding summary.
**Client preferences registry**: Role: intake coordinator. Task: maintain a registry of client preferences for outreach. Context: contact times, channels, and tone. Output: preferences registry.
**Case file index**: Role: records clerk. Task: generate an index for new client files. Context: categories, subfolders, and naming conventions. Output: index schema.
**Post-intake survey**: Role: operations analyst. Task: create a survey for clients after intake. Context: satisfaction, clarity, and suggestions. Output: survey results and improvement brief.
**Data minimization rule**: Role: privacy officer. Task: implement data minimization guidance for intake. Context: collect only necessary fields and avoid sensitive data. Output: minimization checklist.
**Ethics and compliance check**: Role: ethics officer. Task: prompt for conflicts of interest and professional conduct issues. Context: red flags and escalation. Output: ethics review note.
**Non-engagement reasons**: Role: intake reviewer. Task: document reasons firms might decline representation. Context: capacity, conflicts, or scope. Output: decline rationale with alternatives.
**Client onboarding timeline**: Role: project manager. Task: map onboarding milestones with owners. Context: from intake to file opening. Output: timeline graphic text.
**Access level prompts**: Role: IT security. Task: assign data access levels for client data. Context: user roles, need-to-know, and audit. Output: access matrix.
**Consent tracking log**: Role: compliance assistant. Task: log all client consent events. Context: type of consent, date, and version. Output: consent log entry.
**Critical data flags**: Role: risk manager. Task: flag critical information that must be protected. Context: PII, financials, health data. Output: flag list and protection notes.
**Preferred contact times**: Role: intake coordinator. Task: collect preferred contact windows and time zones. Output: schedule-friendly contact times.
**Appointment reschedule prompt**: Role: receptionist. Task: handle rescheduling with client. Context: conflicts, time zones, and reminders. Output: reschedule notice and updated calendar invite.
**Case-specific acronyms**: Role: intake analyst. Task: document any case-specific acronyms and definitions. Output: glossary section for the file.
**Client education note**: Role: attorney. Task: provide clients with a brief educational note about the legal process. Output: concise, plain-language guide.
**Document translation log**: Role: translator liaison. Task: log translated documents and languages. Output: translation log and status.
**Attorney contact sheet**: Role: admin. Task: compile a secure contact sheet for on-call attorneys. Output: contact list with channels.
**Case opening notes**: Role: paralegal. Task: capture initial notes from the client interview. Output: succinct notes with key issues and next steps.
**Fee agreement prompts**: Role: attorney. Task: prompt to present fee agreement options. Context: disclosures, cancellation policy, and scope. Output: draft fee agreement section.
**Client consent video prompt**: Role: privacy officer. Task: obtain consent for video calls where needed. Output: consent text and recording notice.
**Background check prompt**: Role: intake clerk. Task: collect consent for background checks where required. Output: checkbox-based consent form.
**Conflict waiver draft**: Role: attorney assistant. Task: draft a conflict waiver for disclosure and consent. Output: waiver text and signature lines.
**Case progression requests**: Role: client liaison. Task: gather client requests on case progression updates. Output: update cadence table and delivery method.
**Special accommodations**: Role: accessibility coordinator. Task: capture any special accommodations for meetings. Output: accommodation list and setup steps.
**Insurance defense prompts**: Role: claims liaison. Task: collect any relevant insurance defense information. Output: insurance-related data fields.
**Outsourcing notes**: Role: intake manager. Task: document any outsourcing or referral needs. Output: referral list and terms.
**Case type escalation**: Role: intake lead. Task: prompt for escalation when case type is ambiguous. Output: escalation criteria and notes.
**Document confidentiality stamp**: Role: admin. Task: generate a confidentiality stamp for uploaded docs. Output: stamp text and placement rules.
**Attorney availability map**: Role: scheduler. Task: build an availability map for attorneys. Output: calendar matrix and optimal slots.
**Client debrief prompt**: Role: intake coordinator. Task: debrief client after first contact to clarify details. Output: debrief notes and follow-up tasks.
**Reminders and tasks**: Role: assistant. Task: create a reminder set for client milestones. Output: task list with due dates and owners.
**Closing summary prompt**: Role: paralegal. Task: draft a closing summary for the intake phase. Output: summary paragraph and bullet points.
**Legal ethics checklist**: Role: ethics officer. Task: ensure intake process adheres to professional conduct rules. Context: permissible questions and data handling boundaries. Output: ethics checklist.Best Practices
- Keep prompts specific to intake tasks and avoid legal conclusions in the outputs.
- Reuse common prompt structures to improve consistency across cases and teams.
- Incorporate privacy and ethics checks into every intake prompt to reduce risk.
- Validate outputs against your firm’s data fields and CRM schema before saving.
- Regularly review and refresh prompts to reflect changes in practice areas or regulations.
Common Mistakes to Avoid
- Asking for sensitive data without a clear necessity or consent.
- Using vague prompts that produce unstructured notes or free text.
- Overloading prompts with too many requirements, causing incomplete outputs.
- Failing to tailor prompts to jurisdictional or practice-area specifics.
- Not validating Gemini outputs against your CRM or case management system.
FAQ
What are Gemini prompts for client intake for law firms?
They are structured prompts used with Gemini to collect and organize client information, verify conflicts, obtain consents, and initiate onboarding in a compliant, repeatable way.
How should I tailor prompts to my jurisdiction?
Replace placeholders with jurisdiction names, local rules, and required forms; reference internal checklists to ensure compliance.
Can prompts be used across multiple channels?
Yes, prompts work across phone, video, and chat; adjust output formats to match the channel (text for chat, form fields for CRM imports).
How do I ensure data privacy in intake prompts?
Include explicit consent language, specify data uses, set retention periods, and limit collection to necessary fields only.
What format should outputs take for CRM integration?
Use structured JSON snippets, key-value lists, and standardized field names that map directly to your CRM schema.
How often should prompts be reviewed?
Review prompts quarterly or after a regulatory change to ensure accuracy and alignment with practice areas.