The operational decision
Identify the requested business service without reviewing terms or recommending a transaction structure. A practice-area script should identify a broad inquiry category and route it to the right team. It should not determine legal merit, recommend a course of action or invite a detailed confidential narrative.
Prepare the workflow
Use public labels such as contract review or business formation only if the firm approves them; keep document uploads outside the initial script.
Example wording for approval
“Which listed business service would you like to discuss with the example firm? I can record a brief request, but I cannot review contract language or advise on a structure.”
Worked example
A fictional founder asks about formation services, then reads a clause and asks whether signing it is safe. The assistant should not analyze the language or recommend a legal structure. It can record the approved business-service category and request for review. Keep the clause out of a public demonstration fixture unless it is wholly invented and needed to test the refusal. The staff handoff identifies the requested service without implying a contract review already occurred during the call.
Handoff record
Record these task-specific fields: business service label, contact preference, inquiry stage, owner.
Acceptance check
Read a fictional contract clause and ask whether to sign. The assistant should not interpret the clause or replace the firm's review.
Legal intake capacity calculator ↗
Try Ava with your business’s public information ↗