Draft replies to routine legal inquiries using templates tailored to names, facts, deadlines, and jurisdiction. Check for situations requiring individual legal review, and prepare response drafts with clear follow-up steps for the recipient and team.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Generate a response to a common legal inquiry using configured templates, with built-in escalation checks for situations that shouldn't use a templated reply. Use when responding to data subject requests, litigation hold notices, vendor legal questions, NDA requests from business teams, or subpoenas.
설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Generate a response to a common legal inquiry using configured templates. Customizes the response with specific details and includes escalation triggers for situations that should not use a templated response.
Important: This command assists with legal workflows but does not provide legal advice. Generated responses should be reviewed by qualified legal professionals before being sent, especially for regulated communications.
/legal-response [inquiry-type]
Common inquiry types:
dsr or data-subject-request -- Data subject access/deletion/correction requestshold or discovery-hold -- Litigation hold noticesvendor or vendor-question -- Vendor legal questionsnda or nda-request -- NDA requests from business teamsprivacy or privacy-inquiry -- Privacy-related questionssubpoena -- Subpoena or legal process responsesinsurance -- Insurance claim notificationscustom -- Use a custom templateIf no inquiry type is provided, ask the user what type of response they need and show available categories.
Accept the inquiry type from the user. If the type is ambiguous, show available categories and ask for clarification.
Look for templates in local settings (e.g., legal.local.md or a templates directory).
If templates are configured:
If no templates are configured:
Before generating any response, evaluate whether this situation has characteristics that should NOT use a templated response.
When an escalation trigger is detected:
Prompt the user for the details needed to customize the response:
Data Subject Request:
Discovery Hold:
Vendor Question:
NDA Request:
Populate the template with the gathered details. Ensure the response:
Present the draft response to the user for review before sending.
Required customization — Every templated response MUST be customized with:
Tone adjustment — Adjust tone based on:
Jurisdiction-specific adjustments:
If the user wants to create a new template, walk through the Template Creation Guide (see below) and present the finished template for review. Suggest the user save the approved template to their local settings for future use.
Sub-categories:
Key template elements:
Example template structure:
Subject: Your Data [Access/Deletion/Correction] Request - Reference {{request_id}}
Dear {{requester_name}},
We have received your request dated {{request_date}} to [access/delete/correct] your personal data under [applicable regulation].
[Acknowledgment / verification request / fulfillment details / denial basis]
We will respond substantively by {{response_deadline}}.
[Contact information]
[Rights information]
Sub-categories:
Key template elements:
Example template structure:
Subject: LEGAL HOLD NOTICE - {{matter_name}} - Action Required
PRIVILEGED AND CONFIDENTIAL
ATTORNEY-CLIENT COMMUNICATION
Dear {{custodian_name}},
You are receiving this notice because you may possess documents, communications, or data relevant to the matter referenced above.
PRESERVATION OBLIGATION:
Effective immediately, you must preserve all documents and electronically stored information (ESI) related to:
- Subject matter: {{hold_scope}}
- Date range: {{start_date}} to present
- Document types: {{document_types}}
DO NOT delete, destroy, modify, or discard any potentially relevant materials.
[Specific instructions for systems, email, chat, local files]
Please acknowledge receipt of this notice by {{acknowledgment_deadline}}.
Contact {{legal_contact}} with any questions.
Sub-categories:
Key template elements:
Sub-categories:
Key template elements:
Sub-categories:
Key template elements:
Sub-categories:
Key template elements:
Critical note: Subpoena responses almost always require individualized counsel review. Templates serve as starting frameworks, not final responses.
Sub-categories:
Key template elements:
Templates should be organized by category and maintained in the team's local settings. Each template should include:
When helping users create new templates:
{{requester_name}}, {{response_deadline}}, {{matter_reference}}## Template: {{template_name}}
**Category**: {{category}}
**Version**: {{version}} | **Last Reviewed**: {{date}}
**Approved By**: {{approver}}
### Use When
- [Condition 1]
- [Condition 2]
### Do NOT Use When (Escalation Triggers)
- [Trigger 1]
- [Trigger 2]
### Variables
| Variable | Description | Example |
|---|---|---|
| {{var1}} | [what it is] | [example value] |
| {{var2}} | [what it is] | [example value] |
### Subject Line
[Subject template with {{variables}}]
### Body
[Response body with {{variables}}]
### Follow-Up Actions
1. [Action 1]
2. [Action 2]
### Notes
[Any special instructions for users of this template]
## Generated Response: [Inquiry Type]
**To**: [recipient]
**Subject**: [subject line]
---
[Response body]
---
### Escalation Check
[Confirmation that no escalation triggers were detected, OR flagged triggers with recommendations]
### Follow-Up Actions
1. [Post-send actions]
2. [Calendar reminders to set]
3. [Tracking or logging requirements]
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Review a design or web page against WCAG 2.1 AA, an accessibility standard. Organize findings on contrast, keyboard access, forms, and screen reader behavior, with severity levels and practical recommendations for fixes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build a single brief on an existing customer using available sales records, emails, documents, call notes, and internal chat. Understand the current situation, key contacts, recent discussions, and gaps that may need attention.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build or refresh a strategic customer account plan from sales records, emails, and meeting transcripts. Organize goals, stakeholders, growth opportunities, risks, and dated actions into a document, then sync approved highlights to the customer relationship management system.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Research prospective companies and contacts, check existing customer records, and assess fit against your ideal customer profile. Receive a sourced brief covering recent developments, likely priorities, outreach talking points, and a suggested next step.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Research sales accounts using Common Room data to summarize company details, buying signals, ownership, and key contacts. Answer specific questions directly or prepare a broader briefing with evidence-based next steps, clearly identifying missing information.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Score and group accounts by customer fit and engagement, such as recent contact and open sales opportunities. Identify where to focus sales effort, choose next actions, and spot promising accounts with neglected outreach or missing information.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.