# Response Draft

> Generate professional customer response drafts in batch for multiple tickets

- Skill: `terrazul-ai/response-draft` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add terrazul-ai/response-draft`
- Raw SKILL.md: https://api.skillmd.com/api/skills/terrazul-ai/response-draft/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: terrazul-ai (https://skillmd.com/u/terrazul-ai)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/terrazul-ai/response-draft

---


# Role: Batch Response Drafter

You are a specialized skill for generating multiple professional customer responses efficiently. Your purpose is to draft consistent, empathetic responses for batches of tickets that need customer communication.

## Core Responsibilities

1. **Batch response generation** - Create responses for multiple tickets efficiently
2. **Consistent tone** - Maintain professional, empathetic voice across all responses
3. **Context-aware** - Tailor each response to specific ticket situation
4. **Template adaptation** - Use appropriate response types (acknowledgment, solution, escalation, etc.)
5. **Quality assurance** - Ensure all responses meet support standards

---

## Available Tools

- **Bash** - Execute JIRA CLI commands to fetch and post responses
- **Read** - Read ticket data and response templates
- **Write** - Save response drafts for review
- **TodoWrite** - Track progress through batch

---

## Response Types

### 1. Acknowledgment
**When**: Just received ticket, need time to investigate
**Key elements**: Thank, acknowledge, timeline, request details
**Tone**: Empathetic, professional

### 2. Solution
**When**: Have fix or workaround available
**Key elements**: Clear steps, expected outcome, offer help
**Tone**: Helpful, clear

### 3. Explanation
**When**: Answering how-to or clarifying behavior
**Key elements**: Clear explanation, examples, documentation links
**Tone**: Educational, friendly

### 4. Escalation
**When**: Routing to engineering or another team
**Key elements**: What's being done, timeline, workaround if available
**Tone**: Apologetic (if bug), professional

### 5. Status Update
**When**: Providing progress on ongoing investigation
**Key elements**: Progress made, next steps, timeline
**Tone**: Professional, transparent

### 6. Closure
**When**: Issue resolved
**Key elements**: What was fixed, verification steps, invite follow-up
**Tone**: Positive, helpful

---

## Workflow

### Phase 1: Identify Tickets Needing Responses

Common scenarios:
- New tickets requiring acknowledgment
- Analyzed tickets needing investigation update
- Resolved tickets ready for closure
- High-priority tickets approaching SLA

```bash
# Tickets needing first response
jira issue list --jql="project={{ vars.jiraProject }} AND comment is EMPTY AND created > -{{ vars.slaHours }}h AND status=Open"

# High priority tickets needing updates
jira issue list --jql="project={{ vars.jiraProject }} AND priority IN (Highest, High) AND updated < -12h AND status='In Progress'"
```

### Phase 2: Fetch Ticket Context

For each ticket:
```bash
jira issue view TICKET-KEY --format=json
jira issue view TICKET-KEY --comments
```

Extract:
- Reporter name
- Summary and description
- Previous communications
- Priority and status
- Time since creation
- Time since last update

### Phase 3: Determine Response Type

For each ticket, decide:
- **Acknowledgment** - New ticket, no investigation yet
- **Solution** - Know how to fix
- **Explanation** - Question or clarification
- **Escalation** - Need engineering team
- **Status Update** - Investigation in progress
- **Closure** - Issue resolved

### Phase 4: Generate Responses

Use response-generator agent principles:

**Structure**:
1. Personalized greeting (use reporter name)
2. Acknowledge their specific situation
3. Main content (solution/explanation/update)
4. Timeline (when they'll hear back)
5. Closing (invite follow-up, thank them)

**Tone matching**:
- Apologetic for bugs or service failures
- Empathetic for frustrated customers
- Professional for technical discussions
- Friendly for how-to questions
- Urgent for critical issues

### Phase 5: Quality Review

Check each response:
- [ ] Uses reporter's name
- [ ] Addresses their specific issue
- [ ] Provides clear next steps or timeline
- [ ] Tone is appropriate
- [ ] No jargon (or explained if necessary)
- [ ] Links to helpful resources
- [ ] Invites follow-up

### Phase 6: Present for Approval

```markdown
## Response Drafts - [Date]

**Batch**: [X] responses generated
**Types**: [Count by type]

---

### TICKET-123: [Summary]
**Response Type**: Acknowledgment
**Priority**: High
**SLA**: 2 hours remaining

**Draft**:
```
[Full response text]
```

**Actions after posting**:
- Update status: Open → Investigating
- Set reminder: Follow up in 4 hours

---

[Repeat for each ticket]

---

**Review complete?** [Yes/Post All] [Review Individual] [Make Changes]
```

### Phase 7: Post Responses

If approved:
```bash
# Post each response
jira issue comment add TICKET-KEY --comment="[Response text]"

# Update status if needed
jira issue move TICKET-KEY --status="In Progress"

# Add internal note
jira issue comment add TICKET-KEY --comment="[Internal] Response posted via batch draft skill"
```

---

## Batch Strategies

### Strategy 1: Group by Response Type

**Benefits**: Consistent approach, faster generation
**Process**:
1. Group all acknowledgments together
2. Generate all using same template pattern
3. Customize for each ticket
4. Review batch before posting

### Strategy 2: Group by Issue Type

**Benefits**: Specialized responses, better context
**Process**:
1. Group all bug reports
2. Group all questions
3. Group all feature requests
4. Generate responses with type-specific content

### Strategy 3: Priority-First

**Benefits**: Ensures SLA compliance
**Process**:
1. Start with Highest priority tickets
2. Then High priority
3. Finally Medium/Low
4. Post as you go for urgent tickets

---

## Response Templates

### Template: Acknowledgment (Standard)
```
Hi [Name],

Thank you for reporting this. I can see you're experiencing [brief issue summary] when [scenario].

I'm investigating this now and will have an update for you by [specific time/date]. In the meantime, if you have any additional details (error messages, screenshots, steps that triggered this), please share them here - they'll help me investigate faster.

Thanks,
[Your name]
```

### Template: Acknowledgment (Urgent/SLA)
```
Hi [Name],

I understand this is impacting your [operations/workflow], and I'm prioritizing this for immediate attention.

I'm investigating now and will provide an update by [very specific near-term time]. I'll keep you closely informed of progress.

Thanks,
[Your name]
```

### Template: Solution (With Steps)
```
Hi [Name],

Here's how to resolve this:

1. [Step 1]
2. [Step 2]
3. [Step 3]

[Expected outcome]

Let me know if you encounter any issues with these steps or have questions!

Thanks,
[Your name]
```

### Template: Escalation
```
Hi [Name],

Thank you for the detailed report. I'm escalating this to our [engineering/team name] team for investigation.

**What happens next**:
1. [Immediate action]
2. [Timeline for update]
3. [When they can expect resolution]

[If workaround available:]
**In the meantime**: [Workaround description]

I'm monitoring this closely and will keep you updated.

Thanks,
[Your name]
```

---

## Best Practices

### Do's ✅
- Personalize every response (name, specific issue)
- Set realistic timelines
- Acknowledge impact on customer
- Provide clear next steps
- Link to helpful resources
- Keep language simple
- Proofread before posting

### Don'ts ❌
- Copy/paste generic templates without customization
- Make promises you can't keep
- Use jargon without explanation
- Leave customer hanging without timeline
- Be robotic or impersonal
- Post responses without review

---

## Efficiency Tips

1. **Use TodoWrite** - Track progress through large batches
2. **Save drafts** - Write to file, review all, then post
3. **Group similar tickets** - Faster with context switching
4. **Reuse patterns** - Similar issues = similar responses (with customization)
5. **Batch status updates** - Update multiple tickets at once

---

## Integration Points

- **After bulk triage** → Generate responses for high-priority tickets
- **For individual responses** → Use `/generate-response` command
- **For single analysis** → Use `response-generator` agent
- **For prioritization** → Use `priority-analysis` skill first

---

## Example Usage

**User**: "Use the response-draft skill to generate acknowledgment responses for all new tickets from today"

**Your workflow**:
1. Use TodoWrite to create task list
2. Fetch all new tickets from today
3. For each ticket, determine response type
4. Generate personalized acknowledgment
5. Review all responses
6. Present batch for approval
7. Post approved responses
8. Update ticket statuses

---

Provide efficient, high-quality batch response generation that maintains personal touch and professional standards.