Canned Responses Skill

Template Management Methodology

Template Organization

1. Category: The type of inquiry the template addresses
2. Template name: A descriptive identifier
3. Use case: When this template is appropriate
4. Escalation triggers: When this template should NOT be used
5. Required variables: Information that must be customized for each use
6. Template body: The response text with variable placeholders
7. Follow-up actions: Standard steps after sending the response
8. Last reviewed date: When the template was last verified for accuracy

Template Lifecycle

1. Creation: Draft template based on best practices and team input
2. Review: Legal team review and approval of template content
3. Publication: Add to template library with metadata
4. Use: Generate responses using the template
5. Feedback: Track when templates are modified during use to identify improvement opportunities
6. Update: Revise templates when laws, policies, or best practices change
7. Retirement: Archive templates that are no longer applicable

Response Categories

1. Data Subject Requests (DSRs)

• Acknowledgment of receipt
• Identity verification request
• Fulfillment response (access, deletion, correction)
• Partial denial with explanation
• Full denial with explanation
• Extension notification

• Reference to applicable regulation (GDPR, CCPA, etc.)
• Specific timeline for response
• Identity verification requirements
• Rights of the data subject (including right to complain to supervisory authority)
• Contact information for follow-up

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]

2. Discovery Holds (Litigation Holds)

• Initial hold notice to custodians
• Hold reminder / periodic reaffirmation
• Hold modification (scope change)
• Hold release

• Matter name and reference number
• Clear preservation obligations
• Scope of preservation (date range, data types, systems, communication types)
• Prohibition on spoliation
• Contact for questions
• Acknowledgment requirement

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.

3. Privacy Inquiries

• Cookie/tracking inquiry responses
• Privacy policy questions
• Data sharing practice inquiries
• Children's data inquiries
• Cross-border transfer questions

• Reference to the organization's privacy notice
• Specific answers based on current practices
• Links to relevant privacy documentation
• Contact information for the privacy team

4. Vendor Legal Questions

• Contract status inquiry response
• Amendment request response
• Compliance certification requests
• Audit request responses
• Insurance certificate requests

• Reference to the applicable agreement
• Specific response to the vendor's question
• Any required caveats or limitations
• Next steps and timeline

5. NDA Requests

• Sending the organization's standard form NDA
• Accepting a counterparty's NDA (with markup)
• Declining an NDA request with explanation
• NDA renewal or extension

• Purpose of the NDA
• Standard terms summary
• Execution instructions
• Timeline expectations

6. Subpoena / Legal Process

• Acknowledgment of receipt
• Objection letter
• Request for extension
• Compliance cover letter

• Case reference and jurisdiction
• Specific objections (if any)
• Preservation confirmation
• Timeline for compliance
• Privilege log reference (if applicable)

7. Insurance Notifications

• Initial claim notification
• Supplemental information
• Reservation of rights response

• Policy number and coverage period
• Description of the matter or incident
• Timeline of events
• Requested coverage confirmation

Customization Guidelines

Required Customization

• Correct names, dates, and reference numbers
• Specific facts of the situation
• Applicable jurisdiction and regulation
• Correct response deadlines based on when the inquiry was received
• Appropriate signature block and contact information

Tone Adjustment

• Audience: Internal vs. external, business vs. legal, individual vs. regulatory authority
• Relationship: New counterparty vs. existing partner vs. adversarial party
• Sensitivity: Routine inquiry vs. contentious matter vs. regulatory investigation
• Urgency: Standard timeline vs. expedited response needed

Jurisdiction-Specific Adjustments

• Verify that cited regulations are correct for the requester's jurisdiction
• Adjust timelines to match applicable law
• Include jurisdiction-specific rights information
• Use jurisdiction-appropriate legal terminology

Escalation Trigger Identification

Universal Escalation Triggers (Apply to All Categories)

• The matter involves potential litigation or regulatory investigation
• The inquiry is from a regulator, government agency, or law enforcement
• The response could create a binding legal commitment or waiver
• The matter involves potential criminal liability
• Media attention is involved or likely
• The situation is unprecedented (no prior handling by the team)
• Multiple jurisdictions are involved with conflicting requirements
• The matter involves executive leadership or board members

Category-Specific Escalation Triggers

• Request from a minor or on behalf of a minor
• Request involves data subject to litigation hold
• Requester is in active litigation or dispute with the organization
• Request is from an employee with an active HR matter
• Request scope is so broad it appears to be a fishing expedition
• Request involves special category data (health, biometric, genetic)

• Potential criminal liability
• Unclear or disputed preservation scope
• Hold conflicts with regulatory deletion requirements
• Prior holds exist for related matters
• Custodian objects to the hold scope

• Vendor is disputing contract terms
• Vendor is threatening litigation or termination
• Response could affect ongoing negotiation
• Question involves regulatory compliance (not just contract interpretation)

• ALWAYS requires counsel review (templates are starting points only)
• Privilege issues identified
• Third-party data involved
• Cross-border production issues
• Unreasonable timeline

When an Escalation Trigger is Detected

1. Stop: Do not generate a templated response
2. Alert: Inform the user that an escalation trigger has been detected
3. Explain: Describe which trigger was detected and why it matters
4. Recommend: Suggest the appropriate escalation path (senior counsel, outside counsel, specific team member)
5. Offer: Provide a draft for counsel review (clearly marked as "DRAFT - FOR COUNSEL REVIEW ONLY") rather than a final response

Template Creation Guide

Step 1: Define the Use Case

• What type of inquiry does this address?
• How frequently does this come up?
• Who is the typical audience?
• What is the typical urgency level?

Step 2: Identify Required Elements

• What information must be included in every response?
• What regulatory requirements apply?
• What organizational policies govern this type of response?

Step 3: Define Variables

• What changes with each use? (names, dates, specifics)
• What stays the same? (legal requirements, standard language)
• Use clear variable names: {{requester_name}}, {{response_deadline}}, {{matter_reference}}

Step 4: Draft the Template

• Write in clear, professional language
• Avoid unnecessary legal jargon for business audiences
• Include all legally required elements
• Add placeholders for all variable content
• Include a subject line template if for email use

Step 5: Define Escalation Triggers

• What situations should NOT use this template?
• What characteristics indicate the matter needs individualized attention?
• Be specific: vague triggers are not useful

Step 6: Add Metadata

• Template name and category
• Version number and last reviewed date
• Author and approver
• Follow-up actions checklist

Template Format

## 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]