AI Prompts Library

Chatbot flow for [USE CASE]:

**Greeting** → Options
**Intent Detection** → Branch
**Info Gathering** → Validate input
**Resolution** → Provide solution
**Escalation** → Seamless handoff to human

**NLP**: Variations, typos, synonyms, context
**Personality**: Consistent tone, emojis (if appropriate)
**Fallbacks**: "I'm not sure" → human handoff
**Analytics**: Track paths, drop-offs, resolution rate

Friendly, efficient, helpful.

Create structured A/B test hypothesis:

**Test Subject**: [PAGE/FEATURE]
**Current Metric**: [VALUE]

**Hypothesis**: If [CHANGE] then [EXPECTED OUTCOME] because [REASONING]

**Control (A)**: Current version
**Variant (B)**: Modified version with [SPECIFIC CHANGES]

**Success Metrics**:
- Primary: [METRIC]
- Secondary: [METRICS]

**Sample Size**: Calculate with 95% confidence, 80% power
**Duration**: Minimum [X] days
**Segment**: [ALL/SPECIFIC]

**Risks**: [POTENTIAL ISSUES]
**Rollback Plan**: [IF NEGATIVE IMPACT]

Write user story following Agile best practices:

**Epic**: [EPIC NAME]

**User Story**:
As a [USER ROLE]
I want to [ACTION/FEATURE]
So that [BENEFIT/VALUE]

**Acceptance Criteria** (Given-When-Then):
1. Given [CONTEXT], When [ACTION], Then [EXPECTED RESULT]
2. Given [CONTEXT], When [ACTION], Then [EXPECTED RESULT]
3. [ADD MORE AS NEEDED]

**Technical Notes**:
- Dependencies: [SYSTEMS/APIS]
- Edge Cases: [SCENARIOS]
- Performance: [REQUIREMENTS]

**Definition of Done**:
- [ ] Code complete & reviewed
- [ ] Unit tests (>80% coverage)
- [ ] Integration tests pass
- [ ] Documentation updated
- [ ] Acceptance criteria validated

**Story Points**: [ESTIMATE]
**Priority**: [HIGH/MEDIUM/LOW]

Incident response plan for [SYSTEM/SERVICE]:

**Severity Levels**:
- **P0 (Critical)**: Total outage, data breach
- **P1 (High)**: Major feature down, perf degradation
- **P2 (Medium)**: Minor feature issue
- **P3 (Low)**: Cosmetic, no user impact

**Response Timeline**:
- P0: Immediate response, 15min updates
- P1: 30min response, hourly updates
- P2: 4hr response, daily updates
- P3: Best effort

**Incident Response Steps**:

**1. Detection & Alerting** (0-5min)
- Monitor alerts trigger
- On-call engineer paged
- Acknowledge alert

**2. Assessment** (5-15min)
- Determine severity
- Identify affected systems/users
- Assemble incident team
- Create incident channel (#incident-123)

**3. Communication** (15-30min)
- Post status page update
- Notify stakeholders
- Start incident log (timeline)

**4. Mitigation** (Ongoing)
- Implement temporary fix
- Monitor metrics
- Update stakeholders regularly

**5. Resolution**
- Deploy permanent fix
- Verify resolution
- Monitor for regression
- Close incident

**6. Post-Mortem** (Within 48hr)
- Timeline of events
- Root cause analysis
- Impact assessment
- Action items (with owners)
- Lessons learned
- Preventive measures

**Communication Templates**:
- Initial: "We're investigating [issue]."
- Update: "Still working. ETA: [time]. Impact: [scope]."
- Resolved: "Issue resolved at [time]. RCA to follow."

**Tools**:
- Monitoring: [Datadog/New Relic]
- On-call: [PagerDuty/Opsgenie]
- Status: [StatusPage]
- Comms: [Slack/Teams]

Create a comprehensive library of customer service response templates for [COMPANY NAME] in [INDUSTRY].

**Company Details:**
- Brand Voice: [Friendly/Professional/Casual/Empathetic]
- Product/Service: [DESCRIPTION]
- Common Issues: [LIST TOP 5-10 ISSUES]
- Support Channels: [Email/Chat/Phone/Social]

**Generate templates for these scenarios:**

**1. Order & Delivery Issues**
- Delayed shipment
- Lost package
- Wrong item received
- Damaged goods
- Order cancellation request

**2. Account & Billing**
- Password reset help
- Billing inquiry
- Refund request
- Subscription cancellation
- Payment failed

**3. Product Support**
- How-to questions
- Troubleshooting
- Feature requests
- Bug reports
- Compatibility issues

**4. Complaints & Escalations**
- Service complaint
- Product quality issue
- Escalation response
- Apology for mistake

**5. Positive Interactions**
- Thank you for feedback
- Responding to compliments
- Review request

**For each template include:**
- Subject line (for email)
- Greeting
- Empathy statement
- Clear explanation/solution
- Next steps
- Closing with contact info
- [PERSONALIZATION TAGS] to customize

**Tone Guidelines:**
- Always acknowledge the customer's feeling
- Be concise but thorough
- Offer clear next steps
- Maintain brand voice
- Include escalation path when needed