Interactive planning tool
Legal intake capacity calculator
Estimate the call minutes your firm needs for a defined intake workflow. Use your own forecast; the starting numbers are illustrative.
Use the calculator ↗Resources for your team
Useful answers.
Practical next steps.
Explore 102 guides for clearer calls, useful websites, better chatbot answers and reliable staff handoffs.
102 guides
Urgency and escalation
Define an after-hours attorney-routing path
Make out-of-hours behavior clear when the normal intake team is unavailable.
Read the guide ↗Knowledge maintenance
Maintain a public attorney and team directory
Keep names and public roles accurate without exposing individual schedules or client assignments.
Read the guide ↗Urgency and escalation
Explain an unsuccessful attorney connection
Give the caller an accurate status after a routing attempt fails.
Read the guide ↗Initial contact
Ask for a broad matter category before a narrative
Route the inquiry without inviting a detailed account of the underlying events.
Read the guide ↗Practice-area boundaries
Route a business-law inquiry without contract advice
Identify the requested business service without reviewing terms or recommending a transaction structure.
Read the guide ↗Calendar verification
Verify a cancellation before sending confirmation
Ensure a test cancellation changes the provider record and the caller-facing status consistently.
Read the guide ↗Calendar verification
Test two requests for the same consultation slot
Check that competing requests cannot both be promised the same unavailable time.
Read the guide ↗Calendar verification
Verify a consultation calendar connection end to end
Replace a connected badge with evidence that the intended operation works.
Read the guide ↗Calendar verification
Verify a reschedule as one controlled operation
Check that changing a test meeting does not leave contradictory old and new appointments.
Read the guide ↗Calendar verification
Test timezone conversion for consultation slots
Verify that the caller-facing time and staff calendar refer to the same instant.
Read the guide ↗Calendar verification
Handle a consultation calendar write failure
Preserve truthful request status when the provider does not confirm the booking.
Read the guide ↗Getting started
A law firm’s first-call intake checklist
Create a repeatable handoff that lets your attorneys review the inquiry before accepting a matter.
Read the guide ↗Initial contact
Ask for a callback preference without promising a time
Capture a useful contact window while preserving the difference between preference and commitment.
Read the guide ↗Pilot testing
Test a demand for immediate conflict clearance
Ensure a preliminary lookup cannot be presented as a professional decision.
Read the guide ↗Conflict-review workflow
Reserve conflict-result communication for the firm's approved process
Prevent an assistant from translating an internal technical response into a legal conclusion.
Read the guide ↗Conflict-review workflow
Handle incomplete preliminary review information
Keep a missing-field case usable without pressuring the caller to disclose extra detail.
Read the guide ↗Conflict-review workflow
Use a clear pending-conflict-review status
Stop preliminary information capture from looking like conflict clearance.
Read the guide ↗Consultation requests
Describe a cancellation request accurately
Avoid telling a caller that a consultation is canceled before the authorized process completes.
Read the guide ↗Consultation requests
Handle a request to change a consultation
Keep a change request separate from a completed calendar modification.
Read the guide ↗Consultation requests
Share only approved public consultation-fee information
Prevent a general price answer from becoming an individualized fee quote.
Read the guide ↗Consultation requests
Record a preferred consultation format
Give staff a useful preference without guaranteeing a room, video link or attorney schedule.
Read the guide ↗Consultation requests
Define the consultation-request stage
Make a submitted preference distinguishable from a booked meeting.
Read the guide ↗Consultation requests
Ask for a timezone before interpreting a time preference
Prevent staff from receiving an ambiguous callback or consultation window.
Read the guide ↗Conflict-review workflow
Review possible duplicate inquiries without merging matters automatically
Help staff notice repeated contact while preserving uncertain identity and scope.
Read the guide ↗Urgency and escalation
Keep the legal intake line separate from emergency response
Avoid presenting attorney routing as a substitute for emergency services.
Read the guide ↗Practice-area boundaries
Create a brief employment-law inquiry script
Capture a broad consultation request without deciding whether conduct was unlawful.
Read the guide ↗Practice-area boundaries
Scope an estate-planning consultation request
Identify an estate-planning inquiry without recommending documents or explaining their legal effect.
Read the guide ↗Routing and exclusions
Separate existing-client contact from new inquiries
Prevent an existing caller from being asked to repeat a matter narrative through the new-inquiry flow.
Read the guide ↗Staff notifications
Recover a failed intake notification without losing ownership
Give failed delivery a visible owner and a safe retry process.
Read the guide ↗Pilot testing
Test the full failed-transfer path
Check what happens after the first attorney destination does not answer.
Read the guide ↗Practice-area boundaries
Keep a family-law first call focused on routing
Help the firm identify a broad service inquiry without conducting a sensitive personal interview.
Read the guide ↗Conflict-review workflow
Limit preliminary name questions to firm-approved fields
Collect only what the firm authorizes for the initial review stage.
Read the guide ↗Knowledge maintenance
Maintain a register of approved firm facts
Give staff a traceable basis for each public service or contact answer.
Read the guide ↗Knowledge maintenance
Resolve contradictory firm instructions before launch
Prevent the assistant from choosing between incompatible consultation or routing policies.
Read the guide ↗Staff notifications
Separate delivery from staff acknowledgment
Show whether a notification reached a system and whether a person took responsibility.
Read the guide ↗Practice-area boundaries
Define an immigration inquiry boundary
Route an inquiry without assessing eligibility, status or a filing strategy.
Read the guide ↗Routing and exclusions
Route location and jurisdiction questions to the firm
Collect only the approved routing fact without deciding whether the firm may act in a particular matter.
Read the guide ↗Public website
Make the law-firm homepage's next step explicit
Help visitors distinguish information, a consultation request and existing-client contact.
Read the guide ↗Pilot testing
Test a request for legal advice during intake
Verify that the assistant does not turn a familiar inquiry into an advisory conversation.
Read the guide ↗Accessible communication
Offer an approved alternative to the automated intake route
Let visitors choose another way to reach the firm without explaining a personal limitation.
Read the guide ↗Firm approval controls
Use a concise change request for intake improvements
Keep routine improvements traceable without turning every suggestion into live behavior.
Read the guide ↗Operational management
Prepare a backup operator to manage the pilot
Keep routine operations from depending on one person's memory or account access.
Read the guide ↗Supplier evaluation
Specify what one consultation connection includes
Make the included calendar work concrete enough to price and test.
Read the guide ↗Measurement and budgeting
Forecast legal-intake call minutes
Estimate allowance needs using the firm's actual intended intake scope.
Read the guide ↗Supplier evaluation
Review a case-management integration claim
Distinguish generic webhook capability from a tested connection to the firm's system.
Read the guide ↗Public website
Label consultation buttons according to actual behavior
Stop a request form from promising a booking it cannot perform.
Read the guide ↗Supplier evaluation
Ask precise questions about intake-record retention
Understand what records exist and who can access them before the firm approves the service.
Read the guide ↗Fictional demonstrations
Simulate urgent routing without contacting real attorneys
Demonstrate the order and fallback of an escalation tree safely.
Read the guide ↗Fictional demonstrations
Introduce a legal-intake demonstration clearly
Tell callers the fictional-data rule before asking an intake question.
Read the guide ↗Fictional demonstrations
Show a sample intake summary without implying acceptance
Make the demonstration result useful and clearly fictional.
Read the guide ↗Fictional demonstrations
Inspect legal-demo assets before sharing them
Remove accidental private information from screenshots and recordings.
Read the guide ↗Fictional demonstrations
Keep public demonstration sessions separate
Prevent one visitor from seeing or influencing another visitor's fictional inquiry.
Read the guide ↗Pilot testing
Test repeated inquiry submission
Prevent a retry or double click from producing contradictory staff tasks.
Read the guide ↗Fictional demonstrations
Create synthetic matter fixtures for a public demonstration
Show the intake structure without copying a real person's legal problem.
Read the guide ↗Initial contact
Write a first-call greeting with a clear purpose
Explain that the assistant handles an initial inquiry before asking the caller to continue.
Read the guide ↗Public website
Write form errors that help without exposing details
Let visitors correct a business-intake field without losing context or revealing content in the error message.
Read the guide ↗Public website
Place intake instructions before the message field
Tell visitors what the first-contact form is intended to collect.
Read the guide ↗Firm approval controls
Define evidence for the firm's go-live decision
Make activation depend on passed workflow checks and clear ownership.
Read the guide ↗Pilot testing
Build a repeatable set of fictional intake tests
Check the core inquiry path consistently after configuration changes.
Read the guide ↗Measurement and budgeting
Measure whether staff receive usable inquiries
Assess the approved handoff fields without rewarding unnecessary data collection.
Read the guide ↗Operational management
Define a pause rule for an unsafe or misleading intake behavior
Give the operator authority to stop a failing route while preserving the firm contact path.
Read the guide ↗Measurement and budgeting
Define inquiry stages before reporting conversion
Keep requests, consultations and accepted matters from being combined into one misleading metric.
Read the guide ↗Staff notifications
Build a concise staff intake summary
Give the receiving team enough context to act without burying the next step.
Read the guide ↗Accessible communication
Review the consultation-request form with a keyboard
Find interaction barriers before visitors need to submit an inquiry.
Read the guide ↗Supplier evaluation
Define who maintains an external integration
Prevent an initially working connection from becoming an unsupported dependency.
Read the guide ↗Supplier evaluation
Review the managed legal plan before activation
Connect the monthly offer to specific operating responsibilities.
Read the guide ↗Operational management
Run a monthly review of the intake script
Catch drift in practice scope, contact routes and consultation wording.
Read the guide ↗Accessible communication
Offer spelling choices without making assumptions
Help callers communicate a permitted name field in a way they can manage.
Read the guide ↗Operational management
Plan intake behavior during an office closure
Explain holiday or unexpected closure handling without promising normal staff response.
Read the guide ↗Measurement and budgeting
Set an overage review process before launch
Avoid an unclear response when the pilot approaches its agreed minute allowance.
Read the guide ↗Accessible communication
Structure intake guidance with descriptive headings
Make public intake instructions easy to scan and navigate.
Read the guide ↗Operational management
Write the first practice-area pilot scope
Keep the managed legal pilot bounded enough for the firm to approve and test.
Read the guide ↗Accessible communication
Replace intake jargon with clear questions
Make the first request understandable to someone unfamiliar with firm terminology.
Read the guide ↗Public website
Write public practice pages with a defined intake scope
Describe the firm's approved services without claiming every inquiry can be handled.
Read the guide ↗Public website
Check that the resource sitemap reflects public pages
Help maintain a discoverable resource library without treating sitemap submission as a ranking guarantee.
Read the guide ↗Firm approval controls
Review who can change intake and routing settings
Limit operational changes to the roles the firm has authorized.
Read the guide ↗Measurement and budgeting
Measure correct routing separately from call volume
Find whether inquiries reach the intended staff destination and receive an owned next step.
Read the guide ↗Operational management
Review the attorney-routing roster
Keep destinations aligned with current staff responsibility and availability.
Read the guide ↗Firm approval controls
Create a script approval record the firm can maintain
Make it clear which wording the firm has approved and for what scope.
Read the guide ↗Knowledge maintenance
Version the approved intake script
Make a changed question easy to review and reverse.
Read the guide ↗Firm approval controls
Treat a second practice area as a new review gate
Prevent a working pilot from inheriting unsuitable questions or routing for another team.
Read the guide ↗Supplier evaluation
Ask suppliers to prove the proposed intake behavior
Evaluate a vendor using the firm's actual handoff and boundary requirements.
Read the guide ↗Accessible communication
Pace intake questions one at a time
Reduce errors caused by a long string of questions read without pauses.
Read the guide ↗Measurement and budgeting
Report inquiries that have no staff owner
Make operational gaps visible after submission or notification delivery.
Read the guide ↗Knowledge maintenance
Use an honest fallback for an unapproved firm question
Give callers a useful next step when the knowledge set lacks an answer.
Read the guide ↗Initial contact
Choose the minimum contact fields for an initial inquiry
Give staff a usable contact route without collecting every field available in the software.
Read the guide ↗Conflict-review workflow
Confirm spelling without exposing other records
Reduce handoff errors while keeping identity and conflict decisions with the firm.
Read the guide ↗Staff notifications
Keep confidential detail out of notification previews
Make alerts useful without displaying a matter narrative on a locked screen or shared inbox preview.
Read the guide ↗Staff notifications
Assign a recipient to every inquiry category
Stop otherwise complete inquiries from landing in an unowned inbox.
Read the guide ↗Routing and exclusions
Define a route for an opposing-party caller
Keep a special caller category out of the ordinary prospective-client script.
Read the guide ↗Initial contact
Capture a language preference as an operational request
Help staff prepare an appropriate contact route without making an interpreter promise.
Read the guide ↗Knowledge maintenance
Control changes to public consultation-fee wording
Prevent an outdated price or exception from remaining in the intake script.
Read the guide ↗Practice-area boundaries
Scope a real-estate legal consultation request
Separate a legal-service inquiry from brokerage, title or closing promises.
Read the guide ↗Urgency and escalation
Record a caller-reported date without calculating a deadline
Give staff a factual time reference while leaving its legal meaning unresolved.
Read the guide ↗Pilot testing
Test an attempt to make the assistant accept a matter
Keep commercial enthusiasm from becoming a false representation commitment.
Read the guide ↗Urgency and escalation
Handle a same-day consultation request honestly
Distinguish a caller's preferred urgency from the firm's confirmed capacity.
Read the guide ↗Staff notifications
Carry unresolved inquiries across a staff shift change
Prevent pending work from disappearing when responsibility moves to another team member.
Read the guide ↗Routing and exclusions
Review suspected spam without making caller-based assumptions
Reduce irrelevant handoffs using explicit firm-approved rules and reviewable outcomes.
Read the guide ↗Initial contact
Interrupt a detailed narrative respectfully
Keep the first inquiry brief when a caller begins sharing more than the approved script needs.
Read the guide ↗Routing and exclusions
Handle an inquiry outside the published practice list
Give an uncertain inquiry a clear route without inventing firm capabilities.
Read the guide ↗Urgency and escalation
Require acknowledgment for an urgent operational handoff
Make an unacknowledged alert visible to the responsible staff team.
Read the guide ↗Routing and exclusions
Give vendors a separate business-contact path
Keep supplier messages from filling the prospective-inquiry queue.
Read the guide ↗No matching guides. Try another topic or choose all topics.
Your workflow, first
Let’s map your first week.
Bring the calls you want covered. We’ll agree the script, handoff and limits.